Hello Dan
Can you confirm that you have the following graph of dependencies with "job
C" NOT being triggered by "job B" when "job A" is building?
+-----+
+---------------+-->+job C|
| | +-----+
| |
| |
| |
+-----+ | +-----+ |
|job A+-----+----->+job B+--+
+-----+ +-----+
The idea of "smart skipping" is that if "job A" is building when "job B"
considers to trigger "job C", then we should skip the trigger of "job C"
because very soon, "job A" will finish and will trigger "job B" that will
itself trigger "job C".
Would this work in your use case?
Isn't it what you see?
Cyrille
On Friday, August 3, 2018 at 8:49:41 PM UTC+2, Dan Tran wrote:
>
> Hello
>
> I have 3 level withMaven jobs under the same bitbucket multibranch
> pipeline with setup to allow this scenario
>
> * A --> B --> C(s)
>
> It works. However, if A is actively building, job C will never get
> called, the job B log shows this
>
> [Bitbucket] Build result notified
> [withMaven] Not triggering job-C because it has a dependency job-A already
> building or in queue
>
>
> note i configure job-C to depend on job-B, and job-B to depend on job-A ( via
> maven dependency )
>
>
> is it a bug?
>
>
> Thanks
>
>
> -D
>
>
>
--
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/f384b628-6b9c-411d-b0e0-3de759b87236%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
