On Wednesday, October 19, 2016 at 11:40:50 PM UTC+2, Jason Whittington wrote: > > It's much easier for me to show her "go to this page and click this 'play' > button" than it is "go find the pipeline, click it, then find the manual > stage and click it to run". I guess I can build a UI that uses the REST > API and hides that from here but that might be something that could be > addressed in a future GoCD build. >
Not that this helps you, but I am using an in-house UI similar to what you described. Its job is to track versions in various projects through states like "alpha", "beta", "stable" etc. I have a pipeline in GoCD which talks to this app via a REST api and triggers whichever deployment pipelines it needs to. For example, with the production environment it would ask the versioning app what the current "stable" is, then compare that to what's actually deployed. If the versions are different, it triggers the deployment pipeline (via the gocd api) with the correct materials. It knows what the pipeline materials are, because I have a script that interrogates the upstream testing pipeline to find the Pipeline_run/Stage_run that corresponds to that particular version. This might sound quite convoluted, but it works quite well, and non-technical people have a nice dashboard which lets them deploy with the click of a button. -- 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.
