-
Notifications
You must be signed in to change notification settings - Fork 145
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
Specify git revision #16
Conversation
I'm having the same problem, is it possible to merge this pull request? It's very annoying that Jenkins is not building the right branch when testing PRs! |
I'm sorry to my late response.
line 126 is
and, |
I'll look into it when I get back from my vacation -----Original Message----- I'm sorry to my late response.
line 126 is
and, Reply to this email directly or view it on GitHub: |
Hello, I experience this very annoying issue on a daily basis: sometimes Jenkins builds the wrong branch and the build fails / passes because of the code on another branch. This is really annoying because we cannot rely on Jenkins to validate pull requests! Is it possible to take a look at this issue? Thanks |
@ghusse @nishio-dens |
maybe you are missing some dependencies, but i think maven should take care of this automatically |
Does it work as expected? |
We are using it in production for 6 months now. Works as expected On Jul 15, 2015, 15:28, at 15:28, Guillaume Gautreau notifications@github.com wrote:
|
Is there any reason to now have this merged? @nishio-dens |
@exi Oh, I'm sorry. |
I will fix this PR a little because BitbucketCause.commitHash method is not exists in the latest source code. |
Great ! Please let us know when you're releasing a new version with this fix! Can't wait for it :) |
Upgrading parent pom org.jenkins-ci.plugins to version 2.11.
This pull request fixes #15 by explicitly telling the jenkins git plugin which sha1 to build.