There have been other threads talking about a Jenkins that could be fully configured from some "source config" repo (which would add an extra missing piece) - of course that is non trivial. The other risk with "everything in a repo" is that there are (more often than you think) accidental leakages of credentials and other things being pushed to the wrong repo.
On Friday, October 23, 2015 at 8:13:13 PM UTC+11, Jesse Glick wrote: > > On Fri, Oct 23, 2015 at 4:53 AM, [email protected] <javascript:> < > [email protected] <javascript:>> wrote: > > They have some points compared to jerkins: > http://concourse.ci/concourse-vs.html#jenkins > > ..specially: > > - every configuration must be backed in a version control system > > - first class support for pipelines > > Yes, it is an interesting read. I think multibranch Workflow plus > Docker integration starts to close the gap on these two bullet points. > (See my recent webinar for background.) It is not the same as having a > system designed according to these principles from the start. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/628e94a2-420c-43ee-97b3-e3629819e7a3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
