News for hackers. Stuff that matters.

A comment on Jenkins 2.0 Beta. Parent comment

Re:Jenkins 2.0 Beta by jquast on Friday March 25, 2016 @05:02PM (#11362669)
Absolutely, tasks/system commands should always be stored in VCS as a shell script, so that feature branches can exercise changes in the task itself. Unfortunately theres the other 90% to worry about, and thats where the highest complexity is, such as configuring a build chains, access control, reporting, etc.

Glad to see jenkins is moving towards a travis-ci ".travis.yml" kind of format, but I'm not hopeful to see it catch up to anywhere near TeamCity, even Bamboo in user or developer UX.

[ Parent | on HN ]
Re:Jenkins 2.0 Beta by yamitty11 on Friday March 25, 2016 @05:25PM (#11362785)
Could use something like this if you are using github https://github.com/groupon/DotCi Job configurations can be version controlled and reviewed like everything else.

For multijob pipelines checkout https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin

[ Parent | on HN ]
Re:Jenkins 2.0 Beta by techman9 on Friday March 25, 2016 @07:59PM (#11363678)
JJB is also a nice tool that seems like it allows similar functionality (I haven't worked with DotCi, so I can't say how they compare)

http://docs.openstack.org/infra/jenkins-job-builder/

[ Parent | on HN ]
Re:Jenkins 2.0 Beta by oblio on Friday March 25, 2016 @06:05PM (#11363036)
Well...

Jenkins 2.0 will provide support for build chains via the pipeline plugin which will be included as a core plugin.

Access control can be configured quite nicely with the Role Strategy Plugin: https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Pl... + AD/LDAP integration.

Reporting automation is covered by the pipeline plugin. Custom reporting is quite easy to implement on top of Jenkins, its APIs cover almost everything you need.

[ Parent | on HN ]