Hello Sadaf,
I tried this feature with 2 upstream pipelines and it works as expected.
Can you provide more details of your configuration to help reproduce this
issue. What are the materials defined for Pipeline_A and Pipeline_B.
Thanks,
Mahesh
On Friday, November 13, 2020 at 12:05:15 AM UTC+5:30 Sadaf Alam wrote:
> Hello,
>
> I have a pipeline with the following materials
>
> pipelines:
> MY_PIPELINE:
> group: MY_PIPELINES
> lock_behavior: unlockWhenFinished
> label_template: "${COUNT}-${service[:8]}"
> materials:
> service:
> git: <GIT_URL_1>
> branch: master
> auto_update: false
> blacklist:
> - "**/*"
> destination: git1
> pipeline_a:
> pipeline: PIPELINE_A
> stage: deploy
> ignore_for_scheduling: true
> pipeline_b:
> pipeline: PIPELINE_B
> stage: stage_b
> ignore_for_scheduling: false
> configuration:
> git: <GIT_URL_2>
> branch: master
> shallow_clone: true
> auto_update: false
> blacklist:
> - "**/*"
> destination: git2
>
> REQUIREMENT : I need MY_PIPELINE to trigger *only after stage_b of
> PIPELINE_B*. I have to specify PIPELINE_A as a dependency because I need
> to fetch an artifact from PIPELINE_A. Further, I have blacklisted
> everything in both git repos so that MY_PIPELINE doesnt trigger after any
> commit.
>
> PROBLEM : Currently MY_PIPELINE gets triggered after PIPELINE_A as well
> which leads me to assume that ignore_for_scheduling is not working as it is
> supposed to?
>
> Kindly help with this
>
> Best,
> Sadaf
>
>
>
--
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/28d6e061-57c3-4957-adb4-f81f2cb3a382n%40googlegroups.com.
