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

[JENKINS-27352] Fix commit notification for a parametrized branchspec #309

Closed
wants to merge 1 commit into from

Conversation

jeanblanchard
Copy link
Contributor

(split from PR 293, now with its very own bug in JIRA)

When the branchspec is parametrized, and a commit notification is received for
the tracked repository, the polling is now always triggered, even if a sha1 was
received.

Also, add some FINE logs to the notifyCommit code.

When the branchspec is parametrized, and a commit notification is received for
the tracked repository, the polling is always triggered, even if a sha1 was
received.

Also, add some FINE logs to the notifyCommit code.
@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@MarkEWaite
Copy link
Contributor

Rebased onto the master branch, ready for release. It passed all my interactive tests, and it passed the interactive tests of the other users that were checking it.

@MarkEWaite MarkEWaite closed this Jul 11, 2015
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