[JIRA] [git-client-plugin] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mattias Andersson commented on JENKINS-21248 Re: Add shallow update init for submodule +1 for adding this. We have very large sub-module repositories and would really benefit from this feature. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/d/optout.
[JIRA] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mattias Andersson commented on JENKINS-17653 git-plugin cause endless number of builds I wouldn't mind if you would make the hpi available because I have no jenkins plugin development environment. If so I could probably squeeze in some time to verify the fix on Friday. 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] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mattias Andersson created JENKINS-17653 git-plugin cause endless number of builds Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, plugin Created: 17/Apr/13 1:16 PM Description: When git-plugin is configured to use the integration branch feature and the there are multiple candidate revisions and the merge fails an endless number of builds are scheduled. As you can see from the log below and new build is scheduled before the merge fails. And the new scheduled build will schedule a new build and fail for the exact same reason Endless loop The build is configured to merge all branches matching /order/* and /bug/* into project/man/integration464 branch Here's the log from jenkins build: 15:03:52 Started by an SCM change 15:03:52 Building on master in workspace C:\Users\.hudson\jobs\Test Git integration branch\workspace 15:03:52 Checkout:workspace / C:\Users\.hudson\jobs\Test Git integration branch\workspace - hudson.remoting.LocalChannel@21777ce4 15:03:52 Using strategy: Default 15:03:52 Last Built Revision: Revision e1a5d142152e8fbcf6248cbe939d402dcca776d4 (origin/order/148) 15:03:52 Fetching changes from 1 remote Git repository 15:03:52 Fetching upstream changes from origin 15:03:54 Pruning obsolete local branches 15:03:54 Seen branch in repository origin/HEAD 15:03:54 Seen branch in repository origin/bug/10825 15:03:54 Seen branch in repository origin/bug/10827 15:03:54 Seen branch in repository origin/master 15:03:54 Seen branch in repository origin/order/148 15:03:54 Seen branch in repository origin/order/149 15:03:54 Seen branch in repository origin/order/150 15:03:54 Seen branch in repository origin/order/151 15:03:54 Seen branch in repository origin/order/152 15:03:54 Seen branch in repository origin/order/153 15:03:54 Seen branch in repository origin/project/man/integration464 15:03:54 Multiple candidate revisions 15:03:54 Scheduling another build to catch up with Test Git integration branch 15:03:54 Commencing build of Revision 7ca6fe365e8a5eff214456b2b0c7575bc8ec2da8 (origin/order/153) 15:03:54 Merging Revision 7ca6fe365e8a5eff214456b2b0c7575bc8ec2da8 (origin/order/153) onto project/man/integration464 15:03:58 ERROR: Branch not suitable for integration as it does not merge cleanly 15:03:58 WARNINGS Parsing warnings in console log with parser Java Compiler (javac) 15:03:58 Archiving artifacts 15:03:58 Recording fingerprints 15:03:58 Description set: 15:03:58 Build did not succeed and the project is configured to only push after a successful build, so no pushing will occur. 15:03:58 Sending e-mails to: x...@xxx.com 15:03:59 Finished: FAILURE Environment: windows x64 java 1.7.0_17 Project: Jenkins Priority: Critical Reporter: Mattias Andersson 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] [git] (JENKINS-17653) git-plugin cause endless number of builds
Mattias Andersson commented on JENKINS-17653 git-plugin cause endless number of builds Jenkins GIT client plugin - version 1.0.5 Jenkins GIT plugin - version 1.3.0 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-13568) Clicking on view link in workspace does not give the same file content as clicking on the file it self.
Mattias Andersson created JENKINS-13568: --- Summary: Clicking on view link in workspace does not give the same file content as clicking on the file it self. Key: JENKINS-13568 URL: https://issues.jenkins-ci.org/browse/JENKINS-13568 Project: Jenkins Issue Type: Bug Components: gui Environment: Client Firefox 11.0, Windows 7 Jenkins installed on Windows 2008 R2 /JDK 1.6 Slave on Windows 2008 R2 / JDK 1.7 Reporter: Mattias Andersson Priority: Minor Attachments: workspace_view.png When clicking on the view link in the workspace of a job the content of the file is not the same as clicking on the file it self. When clicking on the view link the content of file from an old build is returned. It could also be the opposite that clicking on the view link gives the correct content. The Job is executed on a slave (installed as a Windows service) so the workspace is on a remote host. -- 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
