[JIRA] (JENKINS-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
Willem Verstraeten
commented on JENKINS-13669
NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
If the possiblyCachedRepo is null, it means there was an earler error updating or cloning the cache. The polling shouldn't try to continue in that case, but throw an exception.
For instance:
if (!requiresWorkspaceForPolling()) {
launcher = Hudson.getInstance().createLauncher(listener);
PossiblyCachedRepo possiblyCachedRepo = cachedSource(Hudson.getInstance(), launcher, listener, true);
if (possiblyCachedRepo == null) {
throw new IOException("Could not use cache to poll for changes. See error messages above for more details");
}
FilePath repositoryCache = new FilePath(new File(possiblyCachedRepo.getRepoLocation()));
return compare(launcher, listener, baseline, output, Hudson.getInstance(), repositoryCache);
}
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-16943) Allow sorting rows in the Test Statistic Grid portlet
SCM/JIRA link daemon resolved JENKINS-16943 as Fixed Allow sorting rows in the Test Statistic Grid portlet Change By: SCM/JIRA link daemon (17/Mar/13 11:07 AM) Status: In Progress 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-16943) Allow sorting rows in the Test Statistic Grid portlet
SCM/JIRA link daemon commented on JENKINS-16943 Allow sorting rows in the Test Statistic Grid portlet Code changed in jenkins User: Marco Ambu Path: src/main/resources/hudson/plugins/view/dashboard/test/TestStatisticsPortlet/teststatistics.jelly http://jenkins-ci.org/commit/dashboard-view-plugin/cc2d0e8a60547a28cded4777fbe30a916c55ff17 Log: [FIXED JENKINS-16943] Added possibility to sort the test statistics grid portlet results. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-16943) Allow sorting rows in the Test Statistic Grid portlet
SCM/JIRA link daemon commented on JENKINS-16943 Allow sorting rows in the Test Statistic Grid portlet Code changed in jenkins User: Marco Ambu Path: src/main/resources/hudson/plugins/view/dashboard/test/TestStatisticsPortlet/portlet.jelly http://jenkins-ci.org/commit/dashboard-view-plugin/65872572d035041f2adf1b8601ce3af48a535e5e Log: [FIXED JENKINS-16943] Added possibility to sort the test statistics grid portlet results. One file was missing from commit. – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-16778) Timestamper makes the build fail if the slave if put offline during the build.
SCM/JIRA link daemon resolved JENKINS-16778 as Fixed Timestamper makes the build fail if the slave if put offline during the build. Change By: SCM/JIRA link daemon (17/Mar/13 11:42 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-16778) Timestamper makes the build fail if the slave if put offline during the build.
SCM/JIRA link daemon commented on JENKINS-16778 Timestamper makes the build fail if the slave if put offline during the build. Code changed in jenkins User: StevenGBrown Path: src/main/java/hudson/plugins/timestamper/TimestampFormatter.java src/test/java/hudson/plugins/timestamper/TimestampFormatterTest.java http://jenkins-ci.org/commit/timestamper-plugin/4029ac433521b354014aeb730509acd9e61e10e6 Log: [FIXED JENKINS-16778] Allow for a null stapler request – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-16941) Git publisher post build action fails on slave agent - unable to serialize
Liya Katz commented on JENKINS-16941 Git publisher post build action fails on slave agent - unable to serialize same problem with 1.3.0: build has failed on rebase Downgrade to 1.1.26 has solved the problem 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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Michael Clarke commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Searching for changes on a tag in a multi-module setup is not as easy at it sounds. Consider the following: 1. A user checks in changes on a branch/head (we may or may not be monitoring this location, it doesn't really matter). At the same time they check in changes on a branch/head we are monitoring. 2. Polling picks up these changes and a build is scheduled 3. The build completes so the last checked timestamp is rolled forward to the build's start time. 4. The user changes the existing tag to point to a new version of the file. Since tagging doesn't create any commit messages and the commit messages for the changed files have already been seen in the last build, no message appears in rlog for the files changed in the tag. Polling therefore doesn't see a change so doesn't schedule a build. It would be possible to pick-up changes on a tag if the changes and re-tag happen in the same polling cycle, but there's no way to guarantee this especially if polling is scheduled to happen frequently. I can apply such a change before the next release, although this could result in users who change tag contents seeing inconsistent polling behaviour depending on how their commits compare to the polling cycle. To try and pick-up all situations where a tag would change, polling would have to be done using the full repository history - not just changes between the last build and current poll. This isn't particularly practical as frequently changed repositories are going to have a large change-log so require a lot of time, memory and processing cycles to retrieve and parse. 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-8636) TestLink Plugin FATAL: Error creating test project
Bruno P. Kinoshita commented on JENKINS-8636 TestLink Plugin FATAL: Error creating test project @Ruslan: nope, just that it hasn't been well tested with newer versions of TestLink I've got a cycle to work on Jenkins till ~Wednesday. Hopefully I'll have time to work on testlink x java x jenkins integration too. 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Nicolas De Loof commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files https://jenkins.ci.cloudbees.com/job/plugins/job/git-client-plugin/34/org.jenkins-ci.plugins$git-client/ provably is a better candidate to get this issue fixed : it used a patched version of JGit to include https://bugs.eclipse.org/bugs/show_bug.cgi?id=354367 proposed fix 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas De Loof commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly Can you download and test git-client from https://jenkins.ci.cloudbees.com/job/plugins/job/git-client-plugin/34/org.jenkins-ci.plugins$git-client/ ? This one uses a patched JGit version that includes fix proposed for https://bugs.eclipse.org/bugs/show_bug.cgi?id=354367. 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
SCM/JIRA link daemon commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Code changed in jenkins User: StevenGBrown Path: src/main/java/hudson/plugins/timestamper/TimestamperConfig.java src/main/resources/hudson/plugins/timestamper/TimestamperConfig/config.groovy src/main/resources/hudson/plugins/timestamper/TimestamperConfig/config.jelly src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.groovy src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/usersettings.jelly src/test/java/hudson/plugins/timestamper/TimestamperConfigTest.java http://jenkins-ci.org/commit/timestamper-plugin/86ae3272544f4f5b443f3ed5cf3aa965c315b12b Log: Workaround JENKINS-16528 by switching from Groovy views to Jelly views – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
SCM/JIRA link daemon commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/CvsLog.java src/test/java/hudson/scm/CvsChangeLogHelperTest.java src/test/java/hudson/scm/CvsLogTest.java http://jenkins-ci.org/commit/cvs-plugin/1900841791d1fbafc1839f0adea99452718f65a8 Log: JENKINS-14711 Pick up changes on a tag since last polling cycle – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-14711) No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine
Michael Clarke commented on JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but "cli rlog" works fine Snapshot build of changes at https://buildhive.cloudbees.com/job/jenkinsci/job/cvs-plugin/80/org.jenkins-ci.plugins$cvs/artifact/org.jenkins-ci.plugins/cvs/2.9-SNAPSHOT/cvs-2.9-SNAPSHOT.hpi These changes are not currently on head so will not be on the next release until I've had more of a think about this and someone has convinced me that we should poll for tag changes 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-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Liya Katz reopened JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result Got this error after upgrade to 1.8 Change By: Liya Katz (17/Mar/13 2:37 PM) Resolution: Fixed Status: Resolved Reopened 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-16314) cvs plugin removes sticky branch tag
SCM/JIRA link daemon commented on JENKINS-16314 cvs plugin removes sticky branch tag Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/AbstractCvs.java http://jenkins-ci.org/commit/cvs-plugin/d781d2879043784309856eaf169b67d6c517599c Log: [FIXED JENKINS-16314] Retain tag information on post-checkout cleanup – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-16314) cvs plugin removes sticky branch tag
SCM/JIRA link daemon resolved JENKINS-16314 as Fixed cvs plugin removes sticky branch tag Change By: SCM/JIRA link daemon (17/Mar/13 2:57 PM) Status: Reopened 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-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
stevengbrown updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves The Timestamper plugin (1.5.3 or later) will no longer trigger this VM crash, because it uses Jelly views instead of Groovy views. This VM crash may still occur during other usages of Groovy views, e.g. uninstalling the Active Directory plugin: hs_err_pid7064.log. Change By: stevengbrown (17/Mar/13 2:57 PM) Labels: timestamper Component/s: timestamper 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-15872) Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace
Michael Clarke assigned JENKINS-15872 to Michael Clarke Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace Change By: Michael Clarke (17/Mar/13 3:01 PM) Assignee: Michael Clarke 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-15872) Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace
Michael Clarke started work on JENKINS-15872 Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace Change By: Michael Clarke (17/Mar/13 3:01 PM) Status: Open In Progress 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-15872) Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace
Michael Clarke commented on JENKINS-15872 Running 'rlog' after 'cvs up -r TAG' superfluous & giving incorrect change log for the workspace JENKINS-14711 disagrees with your view. I've created a snapshot (https://buildhive.cloudbees.com/job/jenkinsci/job/cvs-plugin/80/org.jenkins-ci.plugins$cvs/artifact/org.jenkins-ci.plugins/cvs/2.9-SNAPSHOT/cvs-2.9-SNAPSHOT.hpi) that parses a tag's log output differently so only picks up changes up to the version the tag is currently on, not future file versions. Please let me know if this resolves your 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 -- 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-15735) CVS "Tag this build" extremely slow
SCM/JIRA link daemon commented on JENKINS-15735 CVS "Tag this build" extremely slow Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/AbstractCvs.java src/main/java/hudson/scm/cvstagging/CvsTagActionWorker.java http://jenkins-ci.org/commit/cvs-plugin/8155c0eb0a1c784aa239bc5a50356ff70edf9f59 Log: [FIXED JENKINS-15735] Group files together to improve cvs rlog efficiency – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-15735) CVS "Tag this build" extremely slow
SCM/JIRA link daemon resolved JENKINS-15735 as Fixed CVS "Tag this build" extremely slow Change By: SCM/JIRA link daemon (17/Mar/13 3:44 PM) 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-16224) ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations
Harald Albers commented on JENKINS-16224 ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations In that case, the force existing option should be removed. The problem only arises because the name verification occurs in an unexpected moment, namely after submitting the job configuration. The best solution would be to trigger the verification before saving, so that a user cannot lose changes. The verification on new jobs works like this. 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-16432) CVS-Plugin: global credential store only works if port is set in CVSROOT string
SCM/JIRA link daemon commented on JENKINS-16432 CVS-Plugin: global credential store only works if port is set in CVSROOT string Code changed in jenkins User: Michael Clarke Path: src/main/java/hudson/scm/AbstractCvs.java http://jenkins-ci.org/commit/cvs-plugin/c239e53e1c09f450c5436a5159c8fe871ae3b7ed Log: [FIXED JENKINS-16432] Match root in global auth when no port specified – You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. 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-16432) CVS-Plugin: global credential store only works if port is set in CVSROOT string
SCM/JIRA link daemon resolved JENKINS-16432 as Fixed CVS-Plugin: global credential store only works if port is set in CVSROOT string Change By: SCM/JIRA link daemon (17/Mar/13 5:54 PM) 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-15879) CVS 'Tag this build' does not work for 'partial checkouts'
Michael Clarke resolved JENKINS-15879 as Fixed CVS 'Tag this build' does not work for 'partial checkouts' Seems to be fixed as part of recent changes to improve tagging actions Change By: Michael Clarke (17/Mar/13 6:29 PM) 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-15879) CVS 'Tag this build' does not work for 'partial checkouts'
Michael Clarke assigned JENKINS-15879 to Michael Clarke CVS 'Tag this build' does not work for 'partial checkouts' Change By: Michael Clarke (17/Mar/13 6:28 PM) Assignee: Michael Clarke 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-15826) CVS plugin excluded regions no longer match on the file path
Michael Clarke assigned JENKINS-15826 to Michael Clarke CVS plugin excluded regions no longer match on the file path Change By: Michael Clarke (17/Mar/13 6:52 PM) Assignee: Michael Clarke 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-15826) CVS plugin excluded regions no longer match on the file path
Michael Clarke commented on JENKINS-15826 CVS plugin excluded regions no longer match on the file path Can you confirm what isn't working here? Are files being excluded that shouldn't or are files not being excluded that should be? The code uses CvsFile#getName() which returns the full file path from the module root (not just the file name) so should be matching the expected file names. Are you able to attach a job config (with any sensitive details) obscured? 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-17220) Add Maven 3.0.5 to the auto installer.
twolfart updated JENKINS-17220 Add Maven 3.0.5 to the auto installer. Change By: twolfart (17/Mar/13 6:58 PM) Component/s: update-center 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Nick Holloway commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. We have a project with a monolithic repository, and Jenkins CI jobs that use "included paths" to only build when required. This means that jobs which only build infrequently, due to the included paths, take longer each time a poll is triggered and eventually fail with an out of memory error. I think this then means the job is no longer built. Would it be more sensible to split the task of identifying changed paths and the changes into two separate calls? I examined a build that hit this condition this morning (OOM after 20 minutes). I can see that the "git show" invocation takes just under 15 minutes to run from the command line, and generates 196MB of output. if i try "git diff --name-only FROM..TO" I get the result in well under a second, and the output is under 1MB. This path information would be sufficient to know whether to trigger a build. It would not support the "excludedUsers", but unless I am missing something, when there are multiple commits in the output of "git show", only the oldest one will be used anyway. This doesn't address the memory usage of getting the change log and parsing it. It might be that for the monolithic repository use case, it should be possible to restrict the change log to specific paths (see JENKINS-10449). I also tried "git log --full-history --no-abbrev -M --format=raw --raw FROM..TO", and found that it completed much quicker (1.5s) and a much smaller output (4MB). I don't understand the reason for commits being omitted from the latter, but as some of them date from 2009 I don't think it is wrong. Perhaps using "git log" instead of "git show" could be investigated. 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-3907) Mercurial updates on matrix projects aren't synced properly
Willem Verstraeten assigned JENKINS-3907 to Willem Verstraeten Mercurial updates on matrix projects aren't synced properly Change By: Willem Verstraeten (17/Mar/13 8:34 PM) Assignee: Kohsuke Kawaguchi Willem Verstraeten 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-3907) Mercurial updates on matrix projects aren't synced properly
Willem Verstraeten commented on JENKINS-3907 Mercurial updates on matrix projects aren't synced properly I've got a pull request to fix this here : https://github.com/jenkinsci/mercurial-plugin/pull/34 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Matt Chotin commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files I installed https://jenkins.ci.cloudbees.com/job/plugins/job/git-client-plugin/34/org.jenkins-ci.plugins$git-client/ and restarted Jenkins and still have this issue. hudson.plugins.git.GitException: Could not checkout 00f6e95c8ff6cc6f7ca544fa07124dd3edaa0586 at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1261) at hudson.plugins.git.GitSCM.access$1200(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1220) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: ios/PorkButt/opentok-ios-sdk/Opentok.framework/Headers/OTError.h at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:246) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) ... 16 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: ios/PorkButt/opentok-ios-sdk/Opentok.framework/Headers/OTError.h at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:1011) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:242) ... 17 more There are symlinks in there. 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Mark Waite edited a comment on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. Thanks for running the command. A 300 MB output file to answer the question "isRevExcluded" seems excessive. Reverting back to 1.1.21 switched from using "git show" to using "git whatchanged". I don't know what issues were being fixed by switching from "git whatchanged" to "git show", but I suspect that they are described in the history of the plugin on github. If it works for you at 1.1.21, that's probably sufficient for now. Eventually the topic will need to be revisited so that the "git show" used in isRevExcluded can be replaced with something faster and more predictable. 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-17221) "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam
Leo Leung commented on JENKINS-17221 "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value I guess the page https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build needs to be updated since the following recommended method no longer works. A build can be started just by accessing http://server/job/myjob/buildWithParameters?PARAMETER=Value I manged to work around the issue by using build trigger authentication tokens as the warning message suggests. 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-15868) Cannot archive big remote log files using "Archive the artifacts" post-build action
sogabe commented on JENKINS-15868 Cannot archive big remote log files using "Archive the artifacts" post-build action PLXCOMP-195 seems to be helpful. 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-17246) Windows slaves die on Jenkins update
Alex Vesely
created JENKINS-17246
Windows slaves die on Jenkins update
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
18/Mar/13 6:00 AM
Description:
I have multiple Windows slaves that are being launched as services.
When I updated Jenkins from 1.495 to 1.506, all the slaves died - they just failed to launch, even though they did it without issues during regular Jenkins restarts.
In order to bring the slaves back to life, I had to remove the services from each Windows host ("sc delete jenkinsslave..."), manually remove the slave directory (containing the .jars and .exe), and then create the service from scratch.
If I skip any of the described steps, the slave fails to launch.
Slaves are running Windows 2003 Server and Windows 2008 Server, the behavior is identical.
Environment:
Jenkins 1.495 -> 1.506
Project:
Jenkins
Labels:
slave
windows
service
Priority:
Major
Reporter:
Alex Vesely
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-17247) Exception while trigger downstream projects
alben shao created JENKINS-17247 Exception while trigger downstream projects Issue Type: Bug Assignee: Jesse Glick Components: secret Created: 18/Mar/13 6:36 AM Project: Jenkins Priority: Critical Reporter: alben shao 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-17247) Exception while trigger downstream projects
alben shao updated JENKINS-17247 Exception while trigger downstream projects Change By: alben shao (18/Mar/13 6:39 AM) Description: I'm running maven jobs and Jenkins will generate dependency automatically based on the POM. However, when jenkins try to trigger downstream project, exception was seen and trigger failed. log is shown below:channel stoppedFATAL: Comparison method violates its general contract!java.lang.IllegalArgumentException: Comparison method violates its general contract! at java.util.TimSort.mergeLo(TimSort.java:747) at java.util.TimSort.mergeAt(TimSort.java:483) at java.util.TimSort.mergeCollapse(TimSort.java:410) at java.util.TimSort.sort(TimSort.java:214) at java.util.TimSort.sort(TimSort.java:173) at java.util.Arrays.sort(Arrays.java:659) at java.util.Collections.sort(Collections.java:217) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:198) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:657) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.cleanUp(MavenModuleSetBuild.java:1020) at hudson.model.Run.execute(Run.java:1532) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) 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.
