Jenkins pipelines as YAML

Re:Jenkins pipelines as YAML by twblalock on Wednesday July 18, 2018 @01:51PM (#17560536)

> At my current gig, again an enterprise, it is Jenkins everywhere. They do the most complex things with it, orchestrating entire releases, integration tests, etc.

You just answered your own question -- people use Jenkins because it can do all of those things.

[ Parent | on HN ]

Re:Jenkins pipelines as YAML by lomnakkus on Wednesday July 18, 2018 @02:18PM (#17560794)

It's possible to use Jenkins to do all of those things. It's also enormously costly in terms of manpower, etc.

It's truly absurd just how much shepherding Jenkins requires once you have build slaves, etc. The pipeline stuff is heaps better, but unfortunately it doesn't really work for the workflow we're using in our shop, so... sad faces all round :(.

[ Parent | on HN ]

Re:Jenkins pipelines as YAML by michaelneale on Wednesday July 18, 2018 @06:35PM (#17562600)

Yes it is harder than it should be - there is a project under way to try to make this config and plugin pain go away: https://jenkins.io/blog/2018/04/06/jenkins-essentials/ (not sure if that name will stick, will maybe just be Jenkins at some point in the future). Hopefully that will help one day, and be far more efficient use of time.

[ Parent | on HN ]

Re:Jenkins pipelines as YAML by twblalock on Wednesday July 18, 2018 @07:58PM (#17563018)

I don't like it any more than you do, but I'm not aware of a competing enterprise-grade solution that has all of the necessary features and won't take a year to migrate to.

[ Parent | on HN ]