Skip to content
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.

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

Fixes Jenkins job search responses which doesn't have downstreamProjects #3431

Conversation

ralfclaassens
Copy link

@ralfclaassens ralfclaassens commented Jan 16, 2017

Regarding: #3135

@davidstaheli: you were right. The main problem exists in the Jenkins TFS plugin. However, there is a small bug in the JenkinsQueueJob task as well. Therefore, it would be nice if you would review/merge this pull request.

In more details: the Job class currently assumes thisJob.search.parsedTaskBody.downstreamProjects as being an array. However, in the case of a MultibranchPipeline Job, Jenkins does not return 'downstreamProjects' as a JSON key at all (i.e. undefined). Of course, downstreamProjects.forEach() fails in this case. This fix / pull request will avoid this failure.

@msftclas
Copy link

Hi @ralfclaassens, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

@ralfclaassens ralfclaassens changed the title Fixes Jenkins job search responses which don't have downstreamProjects Fixes Jenkins job search responses which doesn't have downstreamProjects Jan 16, 2017
@davidstaheli
Copy link
Contributor

Thanks very much for the contribution, @ralfclaassens! Also for your work on the TFS Plugin for Jenkins. We'll get to that separate PR as soon as possible.

@davidstaheli davidstaheli merged commit 154f5e3 into microsoft:master Jan 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants