Chad Wilson

I'm not really sure I understand what you are trying to do. Can I request that you start a discussion on the Google Group at https://groups.google.com/g/go-cd where there are more...

No, environment variables are only known at execution time i.e in https://plugin-api.gocd.org/current/tasks/#execute-task Some set by GoCD are dynamic such as the pipeline number etc. Not sure why you'd need them...

I don't really understand what you are specifically trying to do, so excuse my ignorance if so. My perspective is that GoCD's design philosophy here is that if you want...

Yeah, I noted that in https://github.com/gocd/gocd/pull/10576#issuecomment-1193149267 but thanks for raising it separately. Not sure on historical context or approach to these things but I sense generally new API versions were...

I wonder if this is related to why you get an error if you try to click a link off the popup to an elastic agent since removed: e.g https://build.gocd.org/go/agents/7c736314-cd8b-4b01-898f-2ca6e2817d99/job_run_history

For better or worse, it's a part of the original design that pipelines are keyed by name (not a composite key of `(group, pipelineName)` nor some other surrogate key/id, and...

Most folks I have seen prefix or suffix the pipelines with the component/team/group that they are relevant to (and often environment) as it also makes it easier to search/filter for.

Looks like dependabot took care of this in #28550 - this BOM contains the micro patch release.

Am I right in assuming this PR never saw the light of day? 'tis a shame because this feature would be really useful.

Looks like this is an attempt to address #167