Re: [go-cd] shouldn't required resources also be at the pipeline level?

Taking another stab after Chad at answering the following question, > We have some pipelines that are given higher preferences for agent/build resources. Wanting to do a lot more of this, but it's tricky because resources can only be defined at the job level (in the UI). Also we use a lot

Re: [go-cd] shouldn't required resources also be at the pipeline level?

On Sat, Jul 22, 2023 at 8:21 PM Joshua Franta wrote: > re: using environments rather than resources... environments can't be > defined at the pipeline level either though? > A pipeline is *assigned* to 0 or 1 environments (via the Admin > Environments UI if not using pipelines-as-code) - thus

Re: [go-cd] shouldn't required resources also be at the pipeline level?

thanks ashwanth- we already use parameter a ton. i don't understand how a job could look at a parameter and force the job to a more capable agent. i can definitely have a job fail based on a pipeline level parameter, but obviously trying to keep everything green here. if you're sure it's

Re: [go-cd] shouldn't required resources also be at the pipeline level?

chad, thx for your reply. re: using environments rather than resources... environments can't be defined at the pipeline level either though? or i guess it's more correct to say that using environments is a bit of a side-car feature, in that we use interact w/environments through a different

Re: [go-cd] shouldn't required resources also be at the pipeline level?

Use Parameters. On Sat, Jul 22, 2023, 16:24 Josh wrote: > QUESTION: > > Shouldn't we also be able to communicate a resource requirement at the > pipeline level, and not just inside a single job? > > I get that it definately needs to be at the job level since that's the > smallest unit of work

Re: [go-cd] shouldn't required resources also be at the pipeline level?

Have you tried to use "environments" (or a mix of environments and resources) to achieve what you are trying to? When scheduling jobs it's the combination of the resource and the environment that are matched to an agent, but the relevant environment is declared at the pipeline level like you

[go-cd] shouldn't required resources also be at the pipeline level?

QUESTION: Shouldn't we also be able to communicate a resource requirement at the pipeline level, and not just inside a single job? I get that it definately needs to be at the job level since that's the smallest unit of work and some machines can't execute certain tasks. But at the

Re: [go-cd] Release Announcement - 23.2.0

Thanks, Chad. — Sriram On Sat, 22 Jul 2023 at 4:39 PM, Chad Wilson wrote: > Hello everyone, > > A new release of GoCD (23.2.0) is > out. > > This release is mainly a minor maintenance release. As always, please > remember to take a backup before

[go-cd] Release Announcement - 23.2.0

Hello everyone, A new release of GoCD (23.2.0) is out. This release is mainly a minor maintenance release. As always, please remember to take a backup before upgrading. To know more about the features and bug fixes in this release, see the release notes