Hi Helge, Thank you for your input. I also have found something myself what could help me, and maybe also you: It goes towards what you are doing a bit.
Pipelines outside of environments will only be assigned to agents in the > default pool (not associated with any environment). https://docs.gocd.org/current/configuration/managing_environments.html As we only manage two environments; prod and nonprod, I should be able just to remove the nonprod environment as a whole. So everything that shouldn't be touched is included in an environment, everything that should can touched stays outside of an environment. I think that solves my problem. Haven't tested if it works yet though. On Thursday, 11 June 2020 09:52:55 UTC+2, Helge Walter wrote: > > Hello Daan > > I came across the same problem and opened the feature request 7769 > <https://github.com/gocd/gocd/issues/7769> for GoCD. > My current workaround is the following: > 1. Do not give "pipeline users" admin rights to environments. > 2. Do a logical association of pipeline group to environment (which is not > a technical constraint of GoCD because it is not possible to define there) > 3. Run a cron job every 5 minutes to assign newly created pipelines to an > environment as defined by the pipeline group. > The only thing which I did not get managed right is definition of > environment variables on environments. > > Maybe you can push my feature request ;) > > Regards, > Helge > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/b249b620-9535-4824-bdcb-1e8c418502b3o%40googlegroups.com.
