Easier integration of external CICD metadata into GoCD about gocd HOT 3 OPEN

Thank you Chad for the prompt, encouraging response. I'll bear these comments in mind...

from gocd.

I think it's generally tough to make this generic especially across source control systems (with respect to tags etc) and certainly with external systems like issue trackers which GoCD isn't directly integrated with.

Have you looked at pipeline labeling https://docs.gocd.org/current/configuration/pipeline_labeling.html and the existing env vars at https://docs.gocd.org/current/faq/dev_use_current_revision_in_build.html ?

I believe env vars were generally chosen to supply these pieces (including the label) as these can also be worked with in a build tool or scripting language of choice, without shell scripting.

I'm not really sure what your proposed solution would look like, or what additional information a task plugin could be supplied that isn't already available as an env var.

If you want to use a task plugin to talk to some external system what additional metadata would be needed which GoCD has but is not currently supplied? Maybe your sample plugin and/or a definition of 'placeholder parameters' might clarify.

What GoCD does (when using GoCD to build GoCD itself) is to generate that metadata inside build tooling (Gradle, Rube/rake) as an artifact (usually some JSON) and carry it along the value stream through multiple pipelines alongside the artifact. Subsequent pipelines can use that to make additional decisions, or say, know how to publish a container image to docker hub, or upload binaries to www.gocd.org.

from gocd.

This issue has been automatically marked as stale because it has not had activity in the last 90 days.
If you can still reproduce this error on the master branch using local development environment or on the latest GoCD Release, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions.

from gocd.