You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Activate Github Autostatus and set to report all stages to GitHub
Run pipeline and wait for status reports on GitHub
Expected Results
The status of the following stages get reported to GitHub:
Working stage
Also working stage
Non-working stage
Actual Results
The status of the following stages get reported to GitHub:
Working stage
Also working stage
The following stage is not reported to GitHub at all (neither pending, nor aborted nor success):
Non-working stage
Anything else?
Jenkins itself can handle this very well: The old UI as well as Blue Ocean displays all stages very well and accurately and everything runs fine. Also, every stage and all steps are running fine.
The given pipeline file in reproduction steps is very basic and only a minimal reproduction. A use case for this is to have a Declarative Pipeline in a shared library which accepts some additional steps in a Closure. These additional steps must be Scripted Pipeline as it's not possible to share parts of a Declarative Pipeline (except from Steps). So my use case is that the part within the script step is actually a call of the given Closure.
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Only Linux - 5.10.127+.
Reproduction steps
Expected Results
The status of the following stages get reported to GitHub:
Working stage
Also working stage
Non-working stage
Actual Results
The status of the following stages get reported to GitHub:
Working stage
Also working stage
The following stage is not reported to GitHub at all (neither pending, nor aborted nor success):
Non-working stage
Anything else?
Jenkins itself can handle this very well: The old UI as well as Blue Ocean displays all stages very well and accurately and everything runs fine. Also, every stage and all steps are running fine.
The given pipeline file in reproduction steps is very basic and only a minimal reproduction. A use case for this is to have a Declarative Pipeline in a shared library which accepts some additional steps in a Closure. These additional steps must be Scripted Pipeline as it's not possible to share parts of a Declarative Pipeline (except from Steps). So my use case is that the part within the
script
step is actually a call of the given Closure.The text was updated successfully, but these errors were encountered: