I'm not sure if I understood correctly what user branches of the CICD mean
in this particular case, can you clarify it?
Some other questions:
- Are the master and CICD branches part of the same projectA?
- If so, how do users interact with the project?
As far as I see the upstream trigger option allows to listen for changes in
some other projects.
Will it work if you split two pipelines instead?
*Pipeline for the master branch *
or even a multibranch pipeline if needed, then you can exclude the CICD
branch to be built.
*Pipeline for the branch CICD*
or event a multibranch pipeline if needed, then you can exclude everything
but the CICD branch.
triggers {
upstream("projectA/master'")
}
Cheers
On Friday, 22 October 2021 at 11:17:46 UTC+1 sverr...@gmail.com wrote:
> We have a branch in projectA called CICD.
> This branch we want to be triggered automatically after the master branch
> has built.
> However we do not want user branches of the CICD to be triggered
> automatically.
>
> Is it possible to avoid configuring a trigger if the branch is not CICD?
>
> This is probably not possible, but would be very useful.
>
> triggers {
> upstream 'projectA/master'
> when {
> branch 'CICD'
> }
> }
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/78393c2a-24ca-4780-b259-9f8e1a40b310n%40googlegroups.com.
