For deployment on production we use a 4-eyes principle. We use the jobStrongAuthSimple plugin as a build step (in a conditional step, only applicable if environment is production). 

For normal single job deployments this works. The job status goes to NOT_BUILD. We rebuild the job (with rebuild plugin), using same parameters and the job finishes. 

I want to make a pipeline of dependent jobs, to be run after each other, some parallel. The status for the job goes to FAILED (in stead of NOT_BUILD), and the pipeline stops. 

Console output

In Single Job:

stop build. number of authed people does not satisfy. Caused by 'StrongAuthSimple for Job' Build step 'StrongAuthSimple for Job' changed build result to NOT_BUILT. Build step 'StrongAuthSimple for Job' makred buils as failure. (....) Finished: NOT_BUILT.

In Pipeline:

internal error. getCauseFromRun Failed. Causes by 'StrongAuthSimple for Job''. Build step 'StrongAuthSimple for Job' changed build result to FAILURE. Build step 'StrongAuthSimple for Job' makred buils as failure. (....) Finished: FAILURE.

Is this due to pipeline not supporting this plugin? Is there a way to fix this, or another way to have the 4-eyes principle when deploying pipelines?

Thanks so much