-
Notifications
You must be signed in to change notification settings - Fork 19
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
Not Triggered, Manual Build Fails Too (No Candidate Revisions) #5
Comments
Is it public or private repo? This plugin isn't working with privete repos yet because of hub4j/github-api#19 And the manual building: |
Private repo. :/ I added a +1 on that issue and started watching it. I look forward to private repository support. |
I am also receiving this error: The source tree of the Jenkins workspace shows that it pulled in the Pull Request refs just find: $ ls .git/refs/remotes/origin/pr/1/
head merge This is using Github Enterprise with Jenkins 1.481 Github pull requests builder version 1.2. Repository URL: |
I am also receiving this error, even on manual builds. I have the latest github-api version 1.33 which resolves the authentication issue. I am using an HTTPS url to my private repository. Repository URL: |
Can you start the jenkins with java option -Dhudson.plugins.git.GitSCM.verbose="true", try to build the job again and post output of the build? |
Sorry for the delay, I never got an email that you responded. Here is the log:
|
Just to back this up. I am having this same error. (private repository but github-api 1.33) |
@ericbmerritt Is your private repository a personal one or a organization? |
It is a organization repo (private) Sent from my iPhone On Oct 19, 2012, at 22:45, Herman Radtke notifications@github.com wrote: @ericbmerritt https://github.com/ericbmerritt Is your private repository — |
I wonder if that is an issue: the repository is not the same as the owner. |
Is there any way I can pull useful information to verify this? Sent from my iPhone On Oct 20, 2012, at 0:52, Herman Radtke notifications@github.com wrote: I wonder if that is an issue: the repository is not the same as the owner. — |
I setup a debug version of the plugin to try and see what is going on. I am not familiar with Java, so it is a little slow going. I should have some updates later today. |
@ericbmerritt I have this sort of working. For manual builds make sure you have the build parameterized and that you are specifying the pull request. Example: There is a separate report of organizations not triggering the builds: #12 I did a private organization repo build to trigger on a debug build of jenkins. There may not be a bug here, but just a lot of confusion over how to set this plugin up. @janinko I think this issue can be closed. |
Document that "Prune remote branches before build" must not be set
@doubleotoo @ericbmerritt Please read @hradtke's comment #5 (comment) If you are sure you have specified the |
I just had the same issue with v1.5 and I got it solved by cloning the job and deleting the old one. |
I have the same issue with last version of the plugin (v1.8). I set -Dhudson.plugins.git.GitSCM.verbose="true" and this is my output: Using strategy: Default |
Hi @janinko, is there any progress on this issue? Thanks in advance |
Well, I had same issue. In my case, "Branches to build" field in jenkins configuration form was like "feature/abc/main". My colleague @defragged has suggested to specify branch name without forward slashes ("/"). So I checked out new branch "abcMain" of "feature/abc/main" and build the job. It worked for me. I hope this would be helpful. |
Thanks for your answer :) I have this value in "Branches to build": "${sha1}", as described on the wiki. |
Apparently there is a bug somewhere but luckily (same as guimonz #5 (comment) ) it went away by setting all values correctly and then cloning the job. |
I've been having this issue frequently for several months:
Sometimes it works, sometimes it doesn't. If I manually clear out the xml file's I would be curious in seeing a "correct" job xml if anyone could share it. This is a very annoying issue. |
I was having the same problem with a Github Pull Request job, and it turned out I was missing the necessary refspec "+refs/pull/:refs/remotes/origin/pr/" from my job. |
I must say that cloning the build solved this problem for me :) |
I just looked in my Btw, what do you mean by "cloning"? Do you mean creating a new job and selecting "Copy existing Job"? |
Nope, even with recreating from scratch this still produces the same error. Note that I am using a private repo. However, this was working at some point. |
Any update on this? |
bump... |
This might be related: https://issues.jenkins-ci.org/browse/JENKINS-20502 Seems to characterize my issues. You might also want to checkout the table at the bottom of https://wiki.jenkins-ci.org/display/JENKINS/GitHub+pull+request+builder+plugin which lists all the Jenkins JIRA issues related to this plugin. |
We are having this issue as well but only on merge commits... all the actual PRs are fine but then it has a failure for each time a PR is merged in. Started by an SCM change |
@danmayer we're seeing the exact same thing |
@guimonz: You saved my day. Lol, just clone the Jenkins project and everything works like a charm. |
Hey there!
Just installed and configured as the readme says and I'm running into an issue: it won't pull.
From Jenkins:
Fetching upstream changes from git@github.com:Tout/pullrequest-jenkins-test.git
No candidate revisions
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
Inside of the repository, the model is git flow, so the pull request is being held on the
feature/edit_test
branch. The pull request is open but if I try to manually build from within Jenkins the build fails. Also, it is not hooking whenever a new pull request is opened, but I feel that might be another ticket.Thoughts?
The text was updated successfully, but these errors were encountered: