config-repo rules

[Laurence MacGuire]

Hey folks,

Can someone help confirm my understanding of config-repo rules? I'm interpolating the doco, the unit tests, and my own testing.

1) Pipelines defined in the same config repo can refer to each-other without restriction.

2) When allowing a config-repo to "refer" to a pipeline group, that just means it can create/change pipelines within that pipeline group. It does NOT allow for a pipeline in the config repo to depend on the specified pipeline group.

3) To allow one pipeline to depend on another, you must allow it to refer to the specific pipeline. And by "depend" I mean making it an upstream/material.

I recently upgraded, and the config-repos which define pipelines with non-trivial visual-stream-maps all broke. Specifying they can refer to the other pipeline-group didn't fix it, I have to make the entity pipeline, and not pipeline-group.

Does that sounds about right?

My situation does permit for `allow, *, *`, but hey, might as well try to do it right.

[Aravind SV]

Hello Laurence,

Yes, your understanding of the pipeline group vs. pipeline difference seems correct. I got confused too just now, and had to go find the GitHub issue which discussed this: https://github.com/gocd/gocd/issues/7605#issuecomment-575600153

You’ll have to ignore the mention of the action “define” there, since it wasn’t implemented (as you can see in the comments that followed the one above).

If you are able to improve the documentation, please do: https://github.com/gocd/docs.go.cd/blob/master/content/advanced_usage/pipelines_as_code.md

Cheers,
Aravind

--
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 go-cd+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/go-cd/ea7e1d96-40d4-4e78-8396-66037e5f3c22n%40googlegroups.com.

[Laurence MacGuire]

Awesome.

Yeah, was thinking this is worth jotting down.