Skip to content

The check if job is running returns prematurely in a multistage build #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
MindaugasLaganeckas opened this issue Nov 26, 2020 · 0 comments · May be fixed by #36
Open

The check if job is running returns prematurely in a multistage build #37

MindaugasLaganeckas opened this issue Nov 26, 2020 · 0 comments · May be fixed by #36

Comments

@MindaugasLaganeckas
Copy link

MindaugasLaganeckas commented Nov 26, 2020 •
edited
Loading

The check
!string.IsNullOrEmpty(buildItem?.Result)
exits the
while statement in Jenkins.Net/Utilities/JenkinsJobRunner.cs:227 on the first finished stage of the job, but not when the whole job is complete.

We propose to check the flag Building instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check the flag 'building' in order to find out if the job is still running 3shape/Jenkins.NET
1 participant
@MindaugasLaganeckas