Hi Cyrille
My job-C does not have a direct dependency on job-A from Maven perspective
for my use case
* job-A: a UI build (20 min)
* job-B: a server build ( 60 min)
* job-C(s): a number of Git repo hosting integration test running in
parallel
Since the integration tests jobs are ver
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|
| | +-+
| |
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 tri
