With the right controls, we can implement change control in GoCD as well. For e.g., one can regulate who gets to deploy, use script checks + SCM-stored values to determine whether this is the authorised deployment time + passphrase, and so on.
Ideally, one should maintain configurations outside of GoCD or any tool, and deliver configurations via config management tool packages. One can always use GoCD to deliver such packages. -- Ram On Sun, Mar 12, 2017 at 8:49 AM, Michael Roepke <[email protected]> wrote: > GoCD runs a pipeline with different test levels and creates packages to be > deployed by and ARA Tool like XLDeploy which holds Application > Configuration and a deployment pipeline for release management purposes. If > you have a simple value stream and no ITIL (Change and Release Management > Process) involved you might use GoCD as well for UAT and PROD deployments, > which normaly is done by a visualized deployment pipeline offered by ARA > vendors like CA, IBM and XebiaLabs.. So both arent really comparable.. > > > Em segunda-feira, 18 de abril de 2016 13:13:13 UTC+2, Abhradip Mukherjee > escreveu: >> >> Can I consider GoCD as an opensource alternative for XL Deploy or >> uDeploy? If so then can anyone help me understand what features are not >> available in GoCD against these tools? >> >> Also why compare a CI like Jenkins with GoCD if GoCD is about CD? Can >> GoCD integrate with Jenkins as a deployment tool like XL Deploy or uDeploy? >> > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
