Thanks but I was doing CI in 1980 and it is IMO a non started that the core system doesn't implement versioning and uses a local file store instead of a network based store. Given the advances in technology I am seeing less and less value in systems that require more and more plugins for basic things that should be part of the core.
On Monday, November 7, 2016 at 7:45:57 AM UTC-5, Rinaldo DiGiorgio wrote: > > Hi, > > I tried to version my jobs with the Jobs SCM plugin for example and it > often gets confused and ends up making my system unusable. Perhaps an > entire rewrite is needed and the backend store needs to move to something > like redis. I don't think version control should be done with optional > plugins. It should be part of the core system and all configuration data > should be in a network store. > > I can see a solution using docker where one makes a base image. What > happens when you change the configuration however. Do you make a new docker > base image? Some organizations want all the source code to generate an > image in some type of SCM and this is the issue. If you change job > configurations or config params you just incurred the hit of a new image > generation cycle. Perhaps I am not looking it in the right way or in the > future when everything is pipeline the configuration is pipeline with > supporting json and property files. > > Rinald > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/310010e3-af9c-4091-ba56-44a54510cff2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
