Next phase is EXECUTING even though the previous phase is FAILED

[waguerin]

See the following for a similar issue: https://issues.jenkins-ci.org/browse/JENKINS-51126

I have a multijob project which is encountering the same issue as above. All of the phase configurations are as follows:
Job Execution Type: Running phase jobs sequentially
Continuation condition to next phase when jobs' statuses are: Successful

For example, I will build the multijob project, a job will fail, yet the next phase will execute. Then I immediately rebuild it (without making any changes), the same job fails, but the phase execution is correctly stopped.

What is is about my multijob configuration that is causing it to occasionally ignore the continuation condition? Is there something I can do as a workaround?

Using Multijob Plugin 1.32

[waguerin]

Example project where the issue is observed:

Both phases are set as follows:

Env variable PHASE_1_RESULT was set to SUCCESS, yet it had a failure:

Console output:

[yorammi]

Are you sure that '*failure*' job is set to *propagate* the phase?

…

On Tue, Aug 6, 2019 at 11:10 PM waguerin ***@***.***> wrote: *Example project where the issue is observed:* [image: Capture] <https://user-images.githubusercontent.com/53836275/62573656-204e1180-b85c-11e9-9a1f-c3713cce2b2d.PNG> *Both phases are set as follows:* [image: ex5] <https://user-images.githubusercontent.com/53836275/62573123-e4667c80-b85a-11e9-885e-6fade07bfa14.PNG> *Env variable PHASE_1_RESULT was set to SUCCESS, yet it had a failure:* [image: ex3] <https://user-images.githubusercontent.com/53836275/62573251-3e674200-b85b-11e9-8b25-8551f66f30b0.PNG> [image: ex4] <https://user-images.githubusercontent.com/53836275/62573396-9aca6180-b85b-11e9-9806-df6aa743bb21.PNG> *Console output:* [image: Capture2] <https://user-images.githubusercontent.com/53836275/62573702-3eb40d00-b85c-11e9-86a8-f691dd2b050d.PNG> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#189>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASZBEWKNVJ3HUWUGELV5QDQDHLEBANCNFSM4IJZR6DA> .

-- *Yoram Michaeli* DevOps Tech Leader 052-5766838 [email protected] [image: Picture]

[waguerin]

Are you sure that 'failure' job is set to propagate the phase?
…
On Tue, Aug 6, 2019 at 11:10 PM waguerin @.***> wrote: Example project where the issue is observed: [image: Capture] https://user-images.githubusercontent.com/53836275/62573656-204e1180-b85c-11e9-9a1f-c3713cce2b2d.PNG Both phases are set as follows: [image: ex5] https://user-images.githubusercontent.com/53836275/62573123-e4667c80-b85a-11e9-885e-6fade07bfa14.PNG Env variable PHASE_1_RESULT was set to SUCCESS, yet it had a failure: [image: ex3] https://user-images.githubusercontent.com/53836275/62573251-3e674200-b85b-11e9-8b25-8551f66f30b0.PNG [image: ex4] https://user-images.githubusercontent.com/53836275/62573396-9aca6180-b85b-11e9-9806-df6aa743bb21.PNG Console output: [image: Capture2] https://user-images.githubusercontent.com/53836275/62573702-3eb40d00-b85c-11e9-86a8-f691dd2b050d.PNG — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#189?email_source=notifications&email_token=AASZBEVJ5CLTGDENORN564DQDHLEBA5CNFSM4IJZR6DKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3WKG7Y#issuecomment-518824831>, or mute the thread https://github.com/notifications/unsubscribe-auth/AASZBEWKNVJ3HUWUGELV5QDQDHLEBANCNFSM4IJZR6DA .
-- Yoram Michaeli DevOps Tech Leader 052-5766838 [email protected] [image: Picture]

How do I know if a job is set to propagate the phase or not?

The success and failure jobs only return an exit code. Other than that, they are blank projects with default configurations. The phase jobs in the multijob config are also default settings.

[Leenachaudhari25]

Hi
Is the fix for this issue available. We have encountered the same issue. We noticed that in the Multijob project the phase result was returning Success even when one of the jobs failed.

[Leenachaudhari25]

Hi any update on the issue. Is there a work around available for this?

[RochaStratovan]

Encountering the problem off and on in our environment too. Fix would be appreciated.