I recommend https://concourse-ci.org/
Jenkins Is Getting Old
61–70 of 340 posts
Re: Jenkins Is Getting Old
#62I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup/config, test-in-production mentality and boundless plugins) but I've never found something that fits the bill. The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos. But when you have many similar repos (modules) with similar build steps…
Gitlab and Concourse both support windows runners as far as I can see. They also don't require docker, but you might actually want that for most of your jobs.
My biggest gripe about gitlab is you can't schedule a job in code, and I suppose it's less then ideal to support 3rd party repos in hosted gitlab, but I don't know why you'd not use it as an SCM.
The bigger problem, would be using a group job that triggers a bunch of other jobs to do the many modules type of development you spoke about, but I'd just develop my modules seperatly, and build them in parallel steps if need be.
Re: Jenkins Is Getting Old
#63Jenkins is to CI, as Nagios is to monitoring.
Both work ?
They both work perfectly fine for the very limited use cases they were meant to, at the time they were made, with the limited resources that were available.
Just like foot is the best way to travel and commute to work every day, as proven by the last 10000 years of people using theirs.
Re: Jenkins Is Getting Old
#64There are lots of alternatives for Jenkins as a CI builder but I haven't found many for Jenkins as a web-based cron with a nice UI that keeps track of history, has tons of options for notifications on failures, and quickly allows re-building (even with user-supplied parameters!) We use Jenkins for running backup jobs, periodically updating data, and building quick little jobs for support staff to run--infrequently en…
For periodic admin tasks, you might consider giving Ansible AWX a try (https://github.com/ansible/awx). It is a web interface for managing Ansible playbooks, and lets you configure jobs that another user can then execute and provide parameters. It keeps track of all run results, has a fair number of supported integrations for notifications, and can schedule runs.
I work for Red Hat, and AWX is the upstream community project for Ansible Tower, which we provide support for. AWX is one of our newer open source projects (we open sourced it after acquiring Ansible), so you'll sometimes have better luck searching for information on "Ansible Tower".
Re: Jenkins Is Getting Old
#65Unrelated to the content, but the stock photos throughout this article felt completely needless to me. We're not 5 year olds, we don't need pictures unless they add to the content.
Re: Jenkins Is Getting Old
#66Trying to integrate Jenkins w/ Github Enterprise proved to be a real pain for me. It wasn't clear what git* plugin is the best to use for how I wanted to setup builds. It's literally impossible to deploy Jenkins in a repeatable manner with just configuration files, you must get it online and use the api to configure such simple things as API keys (eg, specify the ID of the key so your jobs actually reference the key and don't break).
Another big pain point, for me was, no obvious openstack integration. I wanted my jobs to run on ephemeral instances so all my dependencies could be defined in the job themselves, not having to rely that the Jenkins worker is setup just right.
I think Gitlab runners get this right, but I have not investigated too far.
Re: Jenkins Is Getting Old
#67I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup/config, test-in-production mentality and boundless plugins) but I've never found something that fits the bill. The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos. But when you have many similar repos (modules) with similar build steps…
side note: I am confused by your usage of "TFA". I looked it up and it stands for what I thought it does, which has a pejorative connotation. That doesn't seem to be what you meant? https://www.urbandictionary.com/define.php?term=TFA
Actually, historically its use doesn't necessarily have a pejorative connotation. You can take it to mean "The Fine Article" just the same. It's more of a joke reference with roots to 'RTFA' used frequently in discussion forums like this.
Re: Jenkins Is Getting Old
#68I sincerely wish I could move away from Jenkins for the reasons stated in TFA (GUI-oriented, slow, hard to backup/config, test-in-production mentality and boundless plugins) but I've never found something that fits the bill. The much-touted repo integrations (travis, circle...) all have an exclusive focus on build-test-deploy CI of single repos. But when you have many similar repos (modules) with similar build steps…
Happy Buildkite user here across two companies. We've built some custom tooling around the GraphQL API here but have since found it solid for both periodic jobs and CI needs.
Re: Jenkins Is Getting Old
#69Earlier quoted context omitted.
Both work ?
They both work perfectly fine for the very limited use cases they were meant to, at the time they were made, with the limited resources that were available. Just like foot is the best way to travel and commute to work every day, as proven by the last 10000 years of people using theirs.
I find when people say the tools are limited they are trying to use the wrong tool for the job.
2 cents
Re: Jenkins Is Getting Old
#70Earlier quoted context omitted.
It's used so much in conversation that it has ceased to be pejorative.
I'd argue that while RTFA had negative connotations, TFA never did. It was just a humorous reference to the former.
Agreed. I think of it more as a joking reference to RTFA. The humor of this probably originates from the early slashdot days.