[JIRA] (JENKINS-14078) Fetch stopped working
tfnico commented on JENKINS-14078 Fetch stopped working @Nicolas: We just upgraded to 1.480.3, and upgraded these plugin: Jenkins GIT plugin: 1.3.0 Jenkins GIT client plugin: 1.0.4 As far as I can tell from the plugin docs on https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyJGit - it is now using JGit. But the error is still occurring. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14078) Fetch stopped working
tfnico edited a comment on JENKINS-14078 Fetch stopped working @Nicolas: We just upgraded to 1.480.3, and upgraded these plugin: Jenkins GIT plugin: 1.3.0 Jenkins GIT client plugin: 1.0.4 As far as I can tell from the plugin docs on https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-WhyJGit - it is now using JGit. But the error is still occurring. Update: Strike the above comment. I had a missing tag in the target repository which caused a very similar error message. Now it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14078) Fetch stopped working
Nicolas De Loof resolved JENKINS-14078 as Fixed Fetch stopped working rev-parse is now implemented with JGit, so this issue should be fixed as well (not system dependent anymore) Change By: Nicolas De Loof (13/Mar/13 8:56 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14078) Fetch stopped working
Morgan Tocker commented on JENKINS-14078 Fetch stopped working I found more information on this (at least for my Jenkins install): It is not specific to Windows (Linux host) When I changed from using MultiSCM to just a single git SCM, it didn't fix it. When I changed the branch from */master to origin/master it did fix it. We have about 20 jobs in Jenkins building from Git. They work fine for weeks, then all the sudden they stop fetching. I tried recreating the workspace - it didn't fix it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
David Gibson commented on JENKINS-14078 Fetch stopped working I'm also seeing this issues on approx 50% of builds on Windows hosted Jenkins and Windows based nodes. Is there a workaround other than rolling back the plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
Scott Lavender commented on JENKINS-14078 Fetch stopped working How/were can I find previous releases of this plugin? I need to get back to 1.1.18 until 1.1.22 is released to avoid this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
W Bosse
edited a comment on JENKINS-14078
Fetch stopped working
We experiencing the same problem after upgrading to 1.1.19. According to the git trace the fetch aborts with a broken git command:
trace: built-in: git 'rev-parse' 'origin/master^^\{commit\}'
With 1.1.18 the same command was issued as
trace: built-in: git 'rev-parse' 'origin/master^{commit}'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
W Bosse
commented on JENKINS-14078
Fetch stopped working
We experiencing the same problem after upgrading to 1.1.19. With Git tracing enabled the last applied Git command seems to be broken:
trace: built-in: git 'rev-parse' 'origin/master^^{commit}'
With 1.1.18 the same command was issued as
trace: built-in: git 'rev-parse' 'origin/master^{commit}'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
W Bosse
edited a comment on JENKINS-14078
Fetch stopped working
We experiencing the same problem after upgrading to 1.1.19. With Git tracing enabled the last applied Git command seems to be broken:
trace: built-in: git 'rev-parse' 'origin/master^^\{commit\}'
Note: The curly braces are preceded by a backslash (the
With 1.1.18 the same command was issued as
trace: built-in: git 'rev-parse' 'origin/master^{commit}'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
W Bosse
edited a comment on JENKINS-14078
Fetch stopped working
We experiencing the same problem after upgrading to 1.1.19. With Git tracing enabled the last applied Git command seems to be broken:
trace: built-in: git 'rev-parse' 'origin/master^^\{commit\}'
With 1.1.18 the same command was issued as
trace: built-in: git 'rev-parse' 'origin/master^{commit}'
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
Fabio Sobral created JENKINS-14078: -- Summary: Fetch stopped working Key: JENKINS-14078 URL: https://issues.jenkins-ci.org/browse/JENKINS-14078 Project: Jenkins Issue Type: Bug Components: git Environment: Windows 7, Jenkins 1.468, also using Multiple SCM plugin. Reporter: Fabio Sobral Assignee: Nicolas De Loof Priority: Blocker Branch specifier is develop, no special characters. Fetching works on version 1.1.18, but on 1.1.19 I get the following output: Last Built Revision: Revision 4bc9103xxx09aaxxf06f70a39c8e1a376 (origin/develop) Cloning the remote Git repository Cloning repository origin Fetching upstream changes from ssh://@192.168.1.10:/myrepo/MyProject ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job. java.io.FileNotFoundException: File 'X:\Jenkins\jobs\MyJob\builds\2012-06-11_18-14-53\changelog.xml.temp' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:137) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1102) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1120) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:127) at hudson.model.AbstractProject.checkout(AbstractProject.java:1242) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1460) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Build does not meet criteria for workspace archiving - result is not at least SUCCESS. Description set: Notifying upstream projects of job completion Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
