[JIRA] [core] (JENKINS-21777) Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly)
SCM/JIRA link daemon resolved JENKINS-21777 as Fixed Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly) Change By: SCM/JIRA link daemon (12/Feb/14 8:14 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] [core] (JENKINS-21777) Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly)
SCM/JIRA link daemon commented on JENKINS-21777 Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly) Code changed in jenkins User: Daniel Beck Path: changelog.html core/src/main/resources/hudson/model/Label/index.jelly http://jenkins-ci.org/commit/jenkins/08a96df6b694314f008186c1748a2c02b5388d8f Log: FIXED JENKINS-21777 Actions contributing to Labels' index page 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] [core] (JENKINS-21778) Fix relative links in sidepanel.jelly of Label to not break when accessing actions
SCM/JIRA link daemon resolved JENKINS-21778 as Fixed Fix relative links in sidepanel.jelly of Label to not break when accessing actions Change By: SCM/JIRA link daemon (12/Feb/14 8:18 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] [core] (JENKINS-21778) Fix relative links in sidepanel.jelly of Label to not break when accessing actions
SCM/JIRA link daemon commented on JENKINS-21778 Fix relative links in sidepanel.jelly of Label to not break when accessing actions Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/Label/sidepanel.jelly http://jenkins-ci.org/commit/jenkins/917ea816364db6bec41ed71044767793360c218c Log: FIXED JENKINS-21778 Fix sidepanel links so they don't break from Actions 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] [gerrit-trigger] (JENKINS-21513) trigger builds drafts if cahnge-set moved from non-draft to draft status and back again.
teilo commented on JENKINS-21513 trigger builds drafts if cahnge-set moved from non-draft to draft status and back again. I do not expect a draft patches to trigger a jenkins job Regardless if a patchesset is just moved in the ui from draft then if the draft changeset is being built it should not be cancelled to perform a new build Of the exact same patchset as it has not changed. What is the point of draft published of there is now way to trigger on only non draft 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] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
SCM/JIRA link daemon commented on JENKINS-21772 Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/cli/ClientAuthenticationCache.java http://jenkins-ci.org/commit/jenkins/237dda40e08f4db759e965738b1b9b3755525161 Log: FIXED JENKINS-21772 Only cache CLI credentials in ~/.hudson if it exists. 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] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
SCM/JIRA link daemon resolved JENKINS-21772 as Fixed Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME Change By: SCM/JIRA link daemon (12/Feb/14 8:23 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] [locale] (JENKINS-21782) Help for Locale plugin should mention ISO-639 two letter language codes as allowed input
Martin Hohl created JENKINS-21782 Help for Locale plugin should mention ISO-639 two letter language codes as allowed input Issue Type: Improvement Assignee: Unassigned Components: locale Created: 12/Feb/14 8:46 AM Description: 1) The help for locale plugin only mentions Locale.setDefault(), but in order to avoid problems like the one reported in Jenkins issue 14703, it should also mention that allowed input can be a ISO-639 two letter language code. 2) It could be helpful to detect a non-existing Locale inside of the locale plugin and to putput an error message to the user, if a locale for the entered language code is unavailable. 3) Since Windows users are used to IETF BCP 47 language tag as Locale specifiers, it would be helpful, if the locale plugin, if a locale is not found for the current value of the "Default Language" input field, tries to find a matching locale using Locale.forLanguageTag(). Fix Versions: current Project: Jenkins Priority: Major Reporter: Martin Hohl 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] [locale] (JENKINS-21782) Help for Locale plugin should mention ISO-639 two letter language codes as allowed input
Martin Hohl updated JENKINS-21782 Help for Locale plugin should mention ISO-639 two letter language codes as allowed input Change By: Martin Hohl (12/Feb/14 8:48 AM) Description: 1)ThehelpforlocalepluginonlymentionsLocale.setDefault(),butinordertoavoidproblemsliketheonereportedinJenkinsissue14703,itshouldalsomentionthatallowedinputcanbeaISO-639twoletterlanguagecode.2)Itcouldbehelpfultodetectanon-existingLocaleinsideofthelocalepluginandto putput output anerrormessagetotheuser,ifalocalefortheenteredlanguagecodeisunavailable.3)SinceWindowsusersareusedtoIETFBCP47languagetagasLocalespecifiers,itwouldbehelpful,ifthelocaleplugin,ifalocaleisnotfoundforthecurrentvalueoftheDefaultLanguageinputfield,triestofindamatchinglocaleusingLocale.forLanguageTag(). 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] [integrity-plugin] (JENKINS-14703) PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin
Martin Hohl commented on JENKINS-14703 PTC Integrity Plugin throws/catches SQL Exception in Combination with Locale Plugin The real problem seems to be that the help for the Locale plugin is insufficent for users, who are not so familiar with the Java API and used to IETF BCP 47 language tags - because they are commonly used in the Windows environment. See http://docs.oracle.com/javase/7/docs/api/java/util/Locale.html#toString() for a list of allowed input for Locale.setDefault(). See also Jenkins issue 21782. 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] [locale] (JENKINS-21782) Help for Locale plugin should mention ISO-639 two letter language codes as allowed input
Martin Hohl updated JENKINS-21782 Help for Locale plugin should mention ISO-639 two letter language codes as allowed input Change By: Martin Hohl (12/Feb/14 9:03 AM) Description: 1)ThehelpforlocalepluginonlymentionsLocale.setDefault(),butinordertoavoidproblemsliketheonereportedinJenkinsissue14703,itshouldalsomentionthatallowedinputcanbeaISO-639twoletterlanguagecode.2)Itcouldbehelpfultodetectanon-existingLocaleinsideofthelocalepluginandtooutputanerrormessagetotheuser,ifalocalefortheenteredlanguagecodeisunavailable.3)SinceWindowsusersareusedtoIETFBCP47languagetagasLocalespecifiers,itwouldbehelpful,ifthelocaleplugin, if incase alocaleisnotfoundforthecurrentvalueoftheDefaultLanguageinputfield,triestofindamatchinglocaleusingLocale.forLanguageTag(). 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] [jacoco] (JENKINS-18863) JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly
jonathan zinger commented on JENKINS-18863 JaCoCo plugin does not handle JaCoCo modules for the coverage trend charts correctly I am coming up with the same issue, can please explain what do you mean by "removing all build information"? 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] [gerrit-trigger] (JENKINS-21513) trigger builds drafts if cahnge-set moved from non-draft to draft status and back again.
rin_ne commented on JENKINS-21513 trigger builds drafts if cahnge-set moved from non-draft to draft status and back again. If you publishes draft patchsets to review, Gerrit sends draft-published event only. No patchset-created event. So when the change is made to a non-draft, any jobs are not triggered as far as you don't set "draft-published" as trigger on events in config. 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] [m2release] (JENKINS-21783) Do not store SVN credentials when option Specify SCM login/password is selected
Michael Rumpf created JENKINS-21783 Do not store SVN credentials when option Specify SCM login/password is selected Issue Type: Bug Assignee: teilo Components: m2release Created: 12/Feb/14 10:30 AM Description: In our corporate environment the policy for user account passwords is to change them every 3 months. In one of our Maven projects we have the M2 release plugin configured so that the Maven release Subversion operations are performed in the context of the user by enabling the option "Specify SCM login/password". This led to the issue that the command line tools of Subversion persisted the credentials in the file C:\Users\jenkins.HOSTNAME\AppData\Roaming\Subversion\auth\svn.simple. When the Subversion plugin was doing the next update this operation was done with the new credentials. After the user had to change its password the Windows build node still had the old credentials stored and was performing every 5 minute Subversion check with the wrong password. Unfortunately we also have a policy that locks an account after 5 failed attempts, locking the user's account after 25 minutes. Maven release plugin already has the option --no-auth-cache added since Maven 2.1 (http://jira.codehaus.org/browse/MRELEASE-497) in order to suppress this behavior. The question is, does the M2 Release Plugin (0.13.0) perform an SVN command line option as well or how could it happen that the credentials were persisted, as described above? Environment: M2 Release Plugin (0.13.0) Jenkins 1.547 Project: Jenkins Priority: Critical Reporter: Michael Rumpf 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] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)
Luc Feys commented on JENKINS-21278 java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102) I am having the same problem, also on Jenkins 1.549 and plugin version 1.81. 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] [ldap] (JENKINS-21784) Implement core SPI to show LDAP group membership
Jesse Glick created JENKINS-21784 Implement core SPI to show LDAP group membership Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap Created: 12/Feb/14 11:09 AM Description: http://jenkins-ci.org/commit/jenkins/4ace130e3b9c4145cc639eb07032d6cc0a0ea84d should be implemented in the LDAP plugin. (Can be done without changing core version dependency—just do not add @Override yet.) Project: Jenkins Priority: Major Reporter: Jesse Glick 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] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Marcel Beister commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it 2.1 seems to fix this problem for us 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] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Marcel Beister
updated JENKINS-21785
Check for changes in folders linked via svn:externals fails due to missing credentials
Change By:
Marcel Beister
(12/Feb/14 12:18 PM)
Description:
Weusesvn:externalstomapfoldersofthesamerepositoryintotheprojectfolders.The2.1versionofthepluginfailstocheckforchangesandreportsasvn:E200015:Nocredentialtotry.Authenticationfailederrorinthestacktrace.{noformat}hudson.util.IOException2:revisioncheckfailedonhttps://svn.dummyserver.org/svn/Data/trunk/Dummy athudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) athudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) athudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:736) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) athudson.model.AbstractProject.checkout(AbstractProject.java:1411) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) athudson.model.Run.execute(Run.java:1670) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)Causedby:org.tmatesoft.svn.core.SVNCancelException:svn:E200015:OPTIONS/
aisvn
svn
/Data/trunk/
MaterialDefinition
Dummy
failed atorg.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) atorg.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) atorg.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) atorg.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) atorg.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) atorg.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) atorg.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) atorg.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) atorg.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) atorg.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) atorg.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) atorg.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) atorg.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) atorg.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) atorg.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) atorg.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) athudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ...11moreCausedby:org.tmatesoft.svn.core.SVNCancelException:svn:E200015:Nocredentialtotry.Authenticationfailed atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) atorg.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) atorg.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) atorg.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) atorg.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ...29more{noformat}
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
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Marcel Beister created JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Issue Type: Bug Assignee: Unassigned Components: subversion Created: 12/Feb/14 12:17 PM Description: We use svn:externals to map folders of the same repository into the project folders. The 2.1 version of the plugin fails to check for changes and reports a "svn: E200015: No credential to try. Authentication failed" error in the stack trace. hudson.util.IOException2: revision check failed on https://svn.dummyserver.org/svn/Data/trunk/Dummy at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:736) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: OPTIONS /aisvn/Data/trunk/MaterialDefinition failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:384) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 11 more Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:694) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:382) ... 29 more Environment: Windows 7 x64 for both hosts and slaves
[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Matthias Kolonko commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it Same here. All seems to work properly again! Just had to delete the workspace for one project and do a complete new checkout, but now it's OK. I guess this issue can be closed. 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] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Marat Mavlyutov assigned JENKINS-21617 to stephenconnolly List Subversion Tags job parameter wants svn credentials but there is no way to fill it Change By: Marat Mavlyutov (12/Feb/14 12:22 PM) Assignee: stephenconnolly 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] [core] (JENKINS-14744) java.lang.OutOfMemoryError: GC overhead limit exceeded
Mikael Larsson commented on JENKINS-14744 java.lang.OutOfMemoryError: GC overhead limit exceeded The same issue remains with version 1.549. INFO UNEXPECTED TOP-LEVEL ERROR: INFO java.lang.OutOfMemoryError: GC overhead limit exceeded 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] [junit] (JENKINS-8713) Display skipped test messages in results
sahumada commented on JENKINS-8713 Display skipped test messages in results Hi, I've been trying to show my skipped tests without much success. My XML looks like: ?xml version="1.0" encoding="UTF-8"? testsuite name="tst_XmlPatterns" tests="2" failures="0" errors="0" skipped="1" time="0.000" properties property name="QtVersion" value="5.2.2"/ property name="QTestVersion" value="5.2.2"/ /properties testcase classname="tst_XmlPatterns" name="initTestCase" time="0.000" skippedtst_xmlpatterns.cpp:120 :: [] Device #x9;IP:169.254.0.13#xA;The command line tool (/usr/lib/qt5/bin/xmlpatterns) could not be run, possibly because Qt was incompletely built or installed. No tests will be run./skipped /testcase testcase classname="tst_XmlPatterns" name="cleanupTestCase" time="0.000"/ system-out/ system-err/ /testsuite but it doesn't show anything. Looking at the source code, I see that you added an attribute called "message", so if I change my XML to ?xml version="1.0" encoding="UTF-8"? testsuite name="tst_XmlPatterns" tests="2" failures="0" errors="0" skipped="1" time="0.000" properties property name="QtVersion" value="5.2.2"/ property name="QTestVersion" value="5.2.2"/ /properties testcase classname="tst_XmlPatterns" name="initTestCase" time="0.000" skipped message="tst_xmlpatterns.cpp:120 :: [] Device #x9;IP:169.254.0.13#xA;The command line tool (/usr/lib/qt5/bin/xmlpatterns) could not be run, possibly because Qt was incompletely built or installed. No tests will be run."/ /testcase testcase classname="tst_XmlPatterns" name="cleanupTestCase" time="0.000"/ system-out/ system-err/ /testsuite then it fails because the XML is not valid according to junit-4.xsd for the xUnit plugin I am using. The error from the xUnit plugin I get is: 13:03:18 [xUnit] [INFO] - Starting to record. 13:03:18 [xUnit] [INFO] - Processing Custom Tool 13:03:18 [xUnit] [INFO] - [Custom Tool] - 29 test report file(s) were found with the pattern 'test-results/tst_*.xml' relative to '/var/lib/jenkins/jobs/qt-5-qtxmlpatterns-dev/workspace/ARCH/ARM' for the testing framework 'Custom Tool'. 13:03:18 [xUnit] [ERROR] - The converted file for the result file '/var/lib/jenkins/jobs/qt-5-qtxmlpatterns-dev/workspace/ARCH/ARM/test-results/tst_xmlpatterns.xml' (during conversion process for the metric 'Custom Tool') is not valid. The report file has been skipped. 13:03:18 [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated. 13:03:18 [xUnit] [INFO] - There are errors when processing test results. 13:03:18 [xUnit] [INFO] - Skipping tests recording. 13:03:18 [xUnit] [INFO] - Stop build. So, is this change incorrect/incomplete or does junit-4.xsd/xUnit need to be updated ? 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Doug Rothauser commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 for this request 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] [m2release] (JENKINS-21783) Do not store SVN credentials when option Specify SCM login/password is selected
teilo commented on JENKINS-21783 Do not store SVN credentials when option Specify SCM login/password is selected The release plugin does not interact with subversion or any other scm. It changes the goals used to build the job to the release goals and unites maven using that. If credentials are getting cached them there may be sole configuration that is missing from you pom to prevent 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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Oliver Milke commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) I've just had the very issue. In order to intermideately workaround this problem, I downgraded the svn-plugin back to version 1.5.4 as enabled by the plugins-management page. Later I re-installed the new version of the svn-plugin in order to provide the log with the failure. Surpringly this issue did not occur again (neither the bug itself nor any relevant log-entry). From what I remember and attribute to this bug: 1) Having a non-up-to-date version of Jenkins (can't remember which, though) 2) update all plugins 3) stop jenkins 4) perform the update of Jenkins (via aptitude install jenkins) to 1.550 and restart the jenkins-service 5) having the problems with the SVN configuration 6) downgrading svn-plugin back to 1.5.4 7) restart the jenkins-service (svn-settings of the projects where back again) 8) again update the svn-plugin to 2.1 and restart the jenkins-service 9) works Stacktrace from what I found in the log: Warnung: Caught exception evaluating: it.scm.descriptor==scmd in /job/myproject/configure. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTEQNode.value(ASTEQNode.java:71) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:191) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Oliver Milke updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Stacktrace found in the log. Change By: Oliver Milke (12/Feb/14 12:57 PM) Attachment: stacktrace.txt 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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Oliver Milke edited a comment on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) I've just had the very issue. In order to intermideately workaround this problem, I downgraded the svn-plugin back to version 1.5.4 as enabled by the plugins-management page. Later I re-installed the new version of the svn-plugin in order to provide the log with the failure. Surpringly this issue did not occur again (neither the bug itself nor any relevant log-entry). From what I remember and attribute to this bug: 1) Having a non-up-to-date version of Jenkins (can't remember which, though) 2) update all plugins 3) stop jenkins 4) perform the update of Jenkins (via aptitude install jenkins) to 1.550 and restart the jenkins-service 5) having the problems with the SVN configuration 6) downgrading svn-plugin back to 1.5.4 7) restart the jenkins-service (svn-settings of the projects where back again) 8) again update the svn-plugin to 2.1 and restart the jenkins-service 9) works I have added the stacktrace from what I found in the log. HTH 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
svollmer commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break Hm, strange: I had the same problem with Subversion Plugin 2.1 and Jenkins 1.532.1 LTS. Then I installed the support-core plugin to generate a bundle and now the SVN plugin seems to work again. Ubuntu 10.04 LTS, JDK 1.7.0_51 Anyway, the content of the plugins directory is: active.txt ant:1.2 artifactory:2.2.1 build-timeout:1.12.2 credentials:1.10 crowd2:1.6 email-ext:2.37.2 external-monitor-job:1.2 jacoco:1.0.14 javadoc:1.1 jira:1.38 jobConfigHistory:2.5 ldap:1.8 mailer:1.8 maven-plugin:2.0.3 pam-auth:1.1 scm-api:0.2 sonar:2.1 ssh-credentials:1.6.1 ssh-slaves:1.6 subversion:2.1 support-core:1.8 token-macro:1.9 translation:1.11 disabled.txt cvs:2.11 failed.txt (empty) 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
stephenconnolly commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break Cool so installing the support core plugin fixed your problem... sounds like that's a cool support 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 -- 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
stephenconnolly resolved JENKINS-21645 as Fixed Upgrading to Subversion plugin 2.0 causes svn integration to break the magical support-core plugins scatters pixie dust all over your jenkins instance and will fix this problem for you Change By: stephenconnolly (12/Feb/14 1:15 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
svollmer commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break I rather would not mark this issue as resolved yet. Just because it worked for me does not mean it works for everyone. Besides, upgrading the Subversion to version =2.0 plugin should not break existing Jenkins installations. If it really is caused by some dependency on the Support Core plugin, at least it should be mentioned in the release notes. 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
stephenconnolly commented on JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break Well there is already a duplicate issue with the same problem, i.e. Subversion plugin missing its descriptor. I don't believe it is the support core installation that fixed the issue, rather I think dancing around the plugin installation and restarting Jenkins fixed the issue... There is a core issue in Jenkins that it is not as good as it should be at synchronizing plugin upgrades and the bundled plugins only further complicate things. 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] [leastload] (JENKINS-20216) Jobs are scheduled on master which has 0 executors
Krzysztof Malinowski commented on JENKINS-20216 Jobs are scheduled on master which has 0 executors Hm... I am not really convinced by this explanation. I have master node configured with 0 executors, meaning that this node is not even listed on the node list and no jobs should be run there. It also did not happen until leastload plugin was installed. Now it happens that such flyweight task is scheduled on master, and master node then shows up in the node list running the task. Can the plugin you mentioned be used to configure master node? Or can it only be used for slaves? 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] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
Alexander Fischer commented on JENKINS-21617 List Subversion Tags job parameter wants svn credentials but there is no way to fill it My problems are fixed with Release2.1 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] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it
stephenconnolly closed JENKINS-21617 as Fixed List Subversion Tags job parameter wants svn credentials but there is no way to fill it Change By: stephenconnolly (12/Feb/14 2:42 PM) Status: Resolved Closed 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
SCM/JIRA link daemon commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java http://jenkins-ci.org/commit/clearcase-plugin/ab085df2c806e01d1b5f84029778da904bf9cae9 Log: JENKINS-21626 Resolve parameters in config spec when checking if config spec has changed. 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] [performance-plugin] (JENKINS-21786) Performance Per Test Case Mode display type use Max. value instead of Average one !
Philippe Koutsoulis created JENKINS-21786 Performance Per Test Case Mode display type use Max. value instead of Average one ! Issue Type: Bug Affects Versions: current Assignee: Manuel Carrasco Attachments: feeds.jtl, screenshot.png Components: performance-plugin Created: 12/Feb/14 3:29 PM Description: "Performance Per Test Case Mode" display type use Max. value instead of Average one See my explicit screenshot as attachment Step to reproduce Use feeds.jtl file (from build 24) Environment: JMeter 2.11 Jenkins 1.542 Project: Jenkins Labels: plugin jenkins Priority: Critical Reporter: Philippe Koutsoulis 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] [template-project] (JENKINS-21787) use all the publishers from this project is not triggering a new build
sampath kumar created JENKINS-21787 use all the publishers from this project is not triggering a new build Issue Type: Bug Assignee: huybrechts Components: template-project Created: 12/Feb/14 3:30 PM Description: Hi, We are facing problems with template project plugin. "use all the publishers from this project" is not triggering a new build. Below are the steps to reproduce this issue. 1. Install Template Project Plugin(version: 1.4) on Jenkins(version: 1.550). 2. Create Job_A, Job_B and Job_C. 3. In Job_A configuration, Under Post build action - Add post-build action - Use publishers from another project, enter "Job_B" for Template Project. 4. In Job_B configuration, Under Post build action - Add post-build action - Build Other Projects -enter "Job_C" for Projects to Build. With this configuration, if I build Job_B, build for Job_C will be triggered. Using Template Project plugin, we have used Job_B as template for Job_A. If I trigger Job_A, it pulls the publisher configuration from Job_B and it is supposed to trigger Job_C. But if I build Job_A, Job_C is not at all triggered. But other post build actions like email, Java doc is working fine. Seems the problem is only in building other projects. Is there already a fix for this problem? Could you please help us to fix this? Thanks, Sampath. Environment: Template Project plugin version: 1.4 Jenkins Version: 1.550 OS: Windows 7 Java Version: 1.7.0_40 Project: Jenkins Priority: Major Reporter: sampath kumar 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] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Brandon Turner commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) Here's a potential patch that works for me: https://github.com/jenkinsci/mercurial-plugin/pull/50 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] [mercurial] (JENKINS-14679) Mercurial cache is not used
Brandon Turner commented on JENKINS-14679 Mercurial cache is not used A hack option that I use is to name one of my mercurial installations: "(Default)", and enable caching on that installation. I'm sure this is not the recommended approach, but for us it beats updating every single job 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] [subversion] (JENKINS-21645) Upgrading to Subversion plugin 2.0 causes svn integration to break
Gaute Lote updated JENKINS-21645 Upgrading to Subversion plugin 2.0 causes svn integration to break Only the active.txt had any content. Change By: Gaute Lote (12/Feb/14 3:48 PM) Attachment: active.txt 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-20896) Git 2.0: fast remote polling fails (missing in-URL password)
Michka Popoff commented on JENKINS-20896 Git 2.0: fast remote polling fails (missing in-URL password) I had the exactly same issue. I just tested with the credentials, and it solved the issue for me. (polling a private bitbucket repo) (git-client-plugin 1.6.2 and git plugin 2.0.1) 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] [clearcase] (JENKINS-18416) CLEARCASE_VIEWPATH contains backslash ( \ ) on Unix
SCM/JIRA link daemon commented on JENKINS-18416 CLEARCASE_VIEWPATH contains backslash ( \ ) on Unix Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/AbstractClearCaseScm.java src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java src/main/java/hudson/plugins/clearcase/util/BuildUtils.java http://jenkins-ci.org/commit/clearcase-plugin/1e9d3a6fbcbb9339813dcc79604b66a997b7d587 Log: JENKINS-18416 Fixing Unit Tests 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] [flow] (JENKINS-20834) Build-Flow cause all executers to Die when executing a simple build job.
dominique clain
commented on JENKINS-20834
Build-Flow cause all executers to Die when executing a simple build job.
This seems to be related to your job's parameter missing a default value.
Try to either:
set parameters to the job you're invoking via Build-Flow i.e:
build("jobName",param1:value1)
or
set default values for the parameter within that job's configuration , i.e: in config.xml of jobName.
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] [performance-plugin] (JENKINS-21786) Performance Per Test Case Mode display type use Max. value instead of Average one !
Philippe Koutsoulis commented on JENKINS-21786 Performance Per Test Case Mode display type use Max. value instead of Average one ! maybe Median value could be more useful... 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] [performance-plugin] (JENKINS-21786) Performance Per Test Case Mode display type use Max. value instead of Average one !
Philippe Koutsoulis edited a comment on JENKINS-21786 Performance Per Test Case Mode display type use Max. value instead of Average one ! Ultimately, maybe Median value could be more useful... 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] [matrix] (JENKINS-16521) Multi-Project Throttle Categories don't work with Matrix jobs
Samu Wikstedt commented on JENKINS-16521 Multi-Project Throttle Categories dont work with Matrix jobs Hi, is this behaviour somehow related to issue we've see lately with matrix jobs and throttle-plugin: throttle plugin do not recognize slave nodes that has been added after the matrix jobs has been gone to queue. Resulting those jobs going to slave nodes that has been there before job launch and new nodes doing nothing. 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] [clearcase] (JENKINS-21626) Permanent build due to the use of an environment variable in config spec
Vincent Nouguier commented on JENKINS-21626 Permanent build due to the use of an environment variable in config spec I just tried version 05/Feb/14. It works fine ! 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] [cloudbees-folder] (JENKINS-21788) Implement ModelObjectWithChildren in Folders
Daniel Beck created JENKINS-21788 Implement ModelObjectWithChildren in Folders Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder Created: 12/Feb/14 4:40 PM Description: Now that Folders has a recent Jenkins version requirement, it can add support for ModelObjectWithChildren. Project: Jenkins Priority: Minor Reporter: Daniel Beck 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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Bert Geens commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) We had the exact same issue and the steps in the earlier comment worked to get the plugin to run for us. However the association between the project's repository and the needed credentials is lost so we would have to reconfigure each single project to use the correct credentials (which are available from the dropdown list). Given the rather large number of jobs in our Jenkins I'd rather not have to do that manually so I reverted back to 1.54 for now. Did you see the same Oliver, or should I treat this as a separate issue and open a separate ticket? 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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
Bert Geens edited a comment on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) We had the exact same issue and the steps in the earlier comment worked to get the plugin to run for us. However the association between the job's SCM repository and the needed credentials is lost so we would have to reconfigure every single build job to use the correct credentials (which are correctly available from the dropdown list). Given the rather large number of jobs in our Jenkins I'd rather not have to do that manually so I reverted back to 1.54 for now. Did you see the same Oliver, or should I treat this as a separate issue and open a separate ticket? 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] [core] (JENKINS-21768) @QueryParameter with doFillxyxItems is broken
Hugo Ares commented on JENKINS-21768 @QueryParameter with doFillxyxItems is broken This commit is changing the behavior of the select to be executed after the rowset name/nameRef fixup(which has priority set to 43) by setting its priority to 1000. I tested by setting different priority to the select behavior and I get the javascritpt error as soon as I put the select behavior priority right after the name/nameRef one. I did not create a pull request because I would have ended up reverting kk's commit. I do not know how to fix this issue without reintroducing the problem that this commit was fixing. 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] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
stephenconnolly
commented on JENKINS-21679
After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management)
A groovy script could easily fix the job SCMs to use the single set of credentials.
It would be something like
for (job in Jenkins.getAllItems(Project.class)) {
if (job.scm instanceof SubversionSCM) {
boolean changed = false;
for (loc in job.scm.modules) {
if (loc.url.contains("svn.acme.org") StringUtils.isEmpty(loc.credentialsId)) {
loc.credentialsId = "uuid of credential goes here";
changed = true;
}
}
if (changed) {
job.save();
}
}
}
But that is more pseudo-code, I will have to try it out a bit to get something that works... the principle is something like the above.
If such a job would work for your use case, please respond and I can see about getting a syntax correct functioning version
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-6203) Git plugin uses default encoding to read change log file
Konst Kolesnichenko reopened JENKINS-6203 Git plugin uses default encoding to read change log file It seems I have same issue with latest jenkins and git. Job's build changelog shows garbled cyrillic characters (They're UTF-8, but shown as CP1251). Here is a screenshot: http://i.imgur.com/wLuXUWV.png Change By: Konst Kolesnichenko (12/Feb/14 5:24 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] [cloudbees-folder] (JENKINS-21788) Implement ModelObjectWithChildren in Folders
Jesse Glick resolved JENKINS-21788 as Duplicate Implement ModelObjectWithChildren in Folders Change By: Jesse Glick (12/Feb/14 5:39 PM) Status: Open Resolved Resolution: Duplicate 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] [leastload] (JENKINS-20216) Jobs are scheduled on master which has 0 executors
Alexander Boyd commented on JENKINS-20216 Jobs are scheduled on master which has 0 executors It can be used to configure the master node; it was, in fact, first brought to my attention by someone on the mailing list with a similar problem to yours (but I've since lost the post). 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] [flow] (JENKINS-20834) Build-Flow cause all executers to Die when executing a simple build job.
nir h commented on JENKINS-20834 Build-Flow cause all executers to Die when executing a simple build job. Upgrading Jenkins version solved 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 -- 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] [maven] (JENKINS-17362) Maven build cannot find JDK when project uses default
Lukasz D commented on JENKINS-17362 Maven build cannot find JDK when project uses default It looks like the issue exists on Jenkins ver. 1.550 on Windows 2008 R2 slave (JDK 7u51, JAVA_HOME is set to C:\Program Files\Java\jdk1.7.0_51). On Jenkins master node (Debian 7.2) in JDK section in configuration settings there's no JDK defined. I duplicated JAVA_HOME variable in slave node representation settings but without any success either (I restarted Jenkins and slave connections several times (both jnlp and java -jar don't work anyway)) -maven build still fails. The work-around for users who don't rely on JDK version is to copy lib folder to path provided in error msg (in my case it was C:\Program Files\Java\lib). 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] [flow] (JENKINS-20834) Build-Flow cause all executers to Die when executing a simple build job.
nir h resolved JENKINS-20834 as Not A Defect Build-Flow cause all executers to Die when executing a simple build job. Upgrading Jenkins version solved it. Change By: nir h (12/Feb/14 6:01 PM) Status: Open Resolved Resolution: NotADefect 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occured
robsimon created JENKINS-21789 Perforce: exception while sync error occured Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 12/Feb/14 7:01 PM Description: An error occurred during workspace sync which caused an exception in the plugin. Better exception handling would be required in such a case. PERFORCE OUTPUT --- Started by timer Building on master in workspace WORKSPACE_DIRECTORY Using master perforce client: JOB_NAME workspace $ p4 workspace -o JOB_NAME workspace $ p4 login -a -p workspace $ p4 -P F9151DF0014D48B57633865E55EDD343 workspace -o JOB_NAME Changing P4 Client Root to: WORKSPACE_DIRECTORY Saving modified client JOB_NAME workspace $ p4 -P F9151DF0014D48B57633865E55EDD343 -s client -i Note: .repository directory in workspace (if exists) is skipped during clean. Wiping workspace... Wiped workspace. Clean complete, took 0 ms Last build changeset: 289943 workspace $ p4 -P F9151DF0014D48B57633865E55EDD343 changes -s submitted -m 1 //JOB_NAME/... workspace $ p4 -P F9151DF0014D48B57633865E55EDD343 -s changes -s submitted //JOB_NAME/...@289944,@289943 Sync'ing workspace to changelist 289943 (forcing sync of unchanged files). workspace $ p4 -P F9151DF0014D48B57633865E55EDD343 -s sync -f //JOB_NAME/...@289943 Caught exception communicating with perforce. Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified. com.tek42.perforce.PerforceException: Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified. at com.tek42.perforce.parse.Workspaces.syncTo(Workspaces.java:167) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:) at hudson.model.AbstractProject.checkout(AbstractProject.java:1415) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: Unable to communicate with perforce. Errors encountered while force syncing: error: chmod: FILE_TO_SYNC: The system cannot find the file specified. Environment: Perforce plugin v1.3.27, Jenkins v1.547 Project: Jenkins Priority: Major Reporter: robsimon 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
robsimon updated JENKINS-21789 Perforce: exception while sync error occurred Change By: robsimon (12/Feb/14 7:03 PM) Summary: Perforce:exceptionwhilesyncerror occured occurred 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
Rob Petti commented on JENKINS-21789 Perforce: exception while sync error occurred Sorry, can you please explain what behavior is expected? There's not a lot we can do if the p4 client throws a legitimate error. 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] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Lucas Smolic commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart This is also happening for me. Has anyone found a fix for this? I have tried upgrading to 1.55, but that cause numerous issues on my system and many plugins were very buggy. Jenkins - 1.532 Java - 1.7.0_51 (OpenJDK) Ubuntu 13.10 Stack Trace: https://gist.github.com/8962410 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
robsimon commented on JENKINS-21789 Perforce: exception while sync error occurred It looked strange to me to see the java stack trace of the plugin when there has been a perforce communication issue. I thought there would be a more graceful end to it or maybe even a retry of the sync. 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-multijob-plugin] (JENKINS-18768) Multijob plugin doesn't aggregate test results from downstream projects
Dirk Hain commented on JENKINS-18768 Multijob plugin doesnt aggregate test results from downstream projects I am using Jenkins 1.548 with multijob-plugin 1.11 and am running into the same problem. I tried the automatic aggregation as well as listing out the relevant projects explicitly but no success. Here is the build log of the post build tasks: POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: Unstable Email was triggered for: Still Unstable Trigger Unstable was overridden by another trigger and will not send an email. Sending email for trigger: Still Unstable Overriding default server settings, creating our own session messageContentType = text/html; charset=UTF-8 Adding recipients from recipient list Successfully created MimeMessage This issues seems to be open for a while now. Any progress on why the aggregation is failing? 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
Rob Petti commented on JENKINS-21789 Perforce: exception while sync error occurred It does retry if it knows that it's a network problem. In this case, however, this is a legitimate error being thrown by the perforce client. Apart from hiding the exception entirely (which is a bad idea) I don't see what else we could do about 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] [cloudbees-folder] (JENKINS-20600) Build issues when folder name (or job name) contains spaces
Daniel Beck commented on JENKINS-20600 Build issues when folder name (or job name) contains spaces You already have the following two options: Define a custom workspace in all affected jobs (in freestyle jobs hidden as Advanced Project Option) Define Display Name (in freestyle jobs hidden as Advanced Project Option). There you can go nuts and use all the spaces, or Unicode snowmen, you want. Limit yourself to basic ASCII (I require something like a-zA-Z0-9._- in Global Configuration » Restrict project naming) and you'll be fine. Given those (you mention neither), is this really a 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
robsimon commented on JENKINS-21789 Perforce: exception while sync error occurred ok, understood. 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
robsimon resolved JENKINS-21789 as Wont Fix Perforce: exception while sync error occurred Change By: robsimon (12/Feb/14 7:27 PM) Status: Open Resolved Resolution: WontFix 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] [perforce] (JENKINS-21789) Perforce: exception while sync error occurred
robsimon closed JENKINS-21789 as Wont Fix Perforce: exception while sync error occurred Change By: robsimon (12/Feb/14 7:27 PM) Status: Resolved Closed 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-18666) Submodule reference
Paul Eipper commented on JENKINS-18666 Submodule reference Please consider merging the pull request as the git-client-plugin now supports 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] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
SCM/JIRA link daemon commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java http://jenkins-ci.org/commit/mercurial-plugin/a1839d86a7c60105c5a03f48978f39b82bc01eb0 Log: Merge pull request #50 from blt04/fix-shared-working-copy-update FIXED JENKINS-15829 Don't recreate workspace when using Repository Sharing Compare: https://github.com/jenkinsci/mercurial-plugin/compare/182c4952b574...a1839d86a7c6 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] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
SCM/JIRA link daemon commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) Code changed in jenkins User: Brandon Turner Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java http://jenkins-ci.org/commit/mercurial-plugin/3173ad4643f4be0aaa43f2bae3aabd93ba852e2f Log: Don't recreate workspace when using Repository Sharing When using Repository Sharing, the working copy is always recloned (from the slave cache), which can take a long time on large repos. This fixes the logic used to detect whether a workspace copy can be reused to support Repository Sharing. JENKINS-15829 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] [mercurial] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
SCM/JIRA link daemon resolved JENKINS-15829 as Fixed hg share always recreating working copy on slave (on master its working fine) Change By: SCM/JIRA link daemon (12/Feb/14 7:57 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] [git] (JENKINS-18698) Toplevel git reference repos
Paul Eipper commented on JENKINS-18698 Toplevel git reference repos Not exactly this, but simply enabling reference repos for submodules would already help those that do have externally managed reference clones: https://issues.jenkins-ci.org/browse/JENKINS-18666 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] [cppcheck] (JENKINS-17363) Ludicrously slow load time [with lazyloading]
Michal Turek commented on JENKINS-17363 Ludicrously slow load time [with lazyloading] Fixed in https://github.com/mixalturek/cppcheck-plugin/commit/e9122560bfc6944395c4a72a628310516a90bf5e, pull request sent. 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] [cppcheck] (JENKINS-19437) Implement load on demand functionality in Cppcheck
Michal Turek commented on JENKINS-19437 Implement load on demand functionality in Cppcheck Fixed in https://github.com/mixalturek/cppcheck-plugin/commit/e9122560bfc6944395c4a72a628310516a90bf5e, pull request sent. 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] [metadata-plugin] (JENKINS-20113) Unable to delete metadata job
Jonathan Brecher commented on JENKINS-20113 Unable to delete metadata job We're seeing the same behavior using Jenkins 1.550 (latest as of today). Is there any way to find WHAT is calling SaveableListener? 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] [metadata-plugin] (JENKINS-20113) Unable to delete metadata job
Steven Christou commented on JENKINS-20113 Unable to delete metadata job You need to upgrade the metadata-plugin as the code changes to resolve this issue are for the metadata-plugin and not core Jenkins. 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] [metadata-plugin] (JENKINS-20113) Unable to delete metadata job
Jonathan Brecher commented on JENKINS-20113 Unable to delete metadata job We don't have the metadata-plugin installed at all. I guess that means I need to open a new issue. I'll go do that... 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] [gui] (JENKINS-21790) Unable to delete any job (job gets recreated immediately)
Jonathan Brecher created JENKINS-21790 Unable to delete any job (job gets recreated immediately) Issue Type: Bug Assignee: Unassigned Components: gui Created: 12/Feb/14 9:28 PM Description: We're seeing symptoms that are basically the same as JENKINS-20113 except that we don't have the metadata-plugin installed at all. Steps to reproduce: Create a new job Delete job (optionally) hit Refresh in the main dashboard The job still exists When I watch the file system, I can see the job folder disappearing from the jobs directory, then getting recreated a moment later. This is on Windows, running Jenkins 1.550. We have a second Jenkins server that theoretically has the same configuration and doesn't exhibit this issue, so it "must" be a config problem... but how to diagnose? Project: Jenkins Priority: Major Reporter: Jonathan Brecher 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] [core] (JENKINS-21768) @QueryParameter with doFillxyxItems is broken
stephenconnolly
commented on JENKINS-21768
@QueryParameter with doFillxyxItems is broken
I actually think it is a problem with your form.
You are nesting things, so that the drop down is at a deeper level than the required field.
If you fix up the form structure so that you don't need to use the name and value attributes but can instead rely on the field attribute to do the right thing then you should end up with a cross-version fix
Note that a fixed up form will probably require a relative path, eg
@QueryParameter("../name")
The number of ../ that you need will fall out of the nesting structure
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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta commented on JENKINS-21791 NPE when trying to add/update credentials in configure global security Here is the stack trace i see javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at
[JIRA] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta created JENKINS-21791 NPE when trying to add/update credentials in configure global security Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: matrix-auth Created: 12/Feb/14 9:41 PM Description: This was noticed on 1.546 and earlier version. Any time i try to add/update users in configure global security i get an NPE. We are using github auth plugin. Project: Jenkins Priority: Major Reporter: Arpit Gupta 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta updated JENKINS-21791 NPE when trying to add/update credentials in configure global security Change By: Arpit Gupta (12/Feb/14 9:43 PM) Description: Thiswasnoticedon1.546andearlierversion.Anytimeitrytoadd/updateusersinconfigureglobalsecurityigetanNPE.Weareusinggithubauthplugin. Weareusingtheprojectbasedmatrixauthorizationstrategy. 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] [clearcase] (JENKINS-18437) Config spec in snapshot view with time element always polls as changes found
Mark Kinnari
commented on JENKINS-18437
Config spec in snapshot view with time element always polls as changes found
A few clarifying details on this issue:
-With our workflow, we use snapshot views on the build machine, with the config spec specified in the job configuration.
-For Jenkins builds, we use a time rule in the config spec, set to the time the build starts. This is done with the Jenkins BUILD_ID variable, using the ZenTimestamp plugin to adjust the formatting to be compatible with the time rule, so there's a line in the config spec that reads "time ${BUILD_ID}".
-We use the time rule to make sure we can easily reproduce any given build with 100% accuracy. The build script will record the config spec (via catcs), and store it as an artifact. If I want to reproduce the exact code used for any given build, I can take the config spec artifact, and load it into a view. Without the time rule, I'd just be getting the latest version.
Looking at the plugin code a bit, it appears that the problem is the logic in compareRemoteRevisionWith(). If it sees that the config spec has changed (which will always be the case, since ${BUILD_ID} will always expand to a different timestamp), then it returns PollingResult.BUILD_NOW, end of story. It looks like the issue was fixed for dynamic views for JENKINS-15202 by having time-based config specs return false for hasNewConfigSpec().
This could be fixed by NOT automatically triggering a new build when the config spec has changed, and just sticking with looking for changes in the repository. I'm having trouble trying to think up a workflow where the automatic build on config spec change would be useful. I would expect that changes to the config spec, other than minor things like this, would be done manually. In that case, the user making the change would probably just hit the "Build now" button afterwards. If removing the automatic behavior outright is a concern, then at least put an option in the GUI to disable it. As it is now, we're just doing builds several times a day on a schedule, whether or not there are any 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Jesse Glick assigned JENKINS-21791 to Unassigned NPE when trying to add/update credentials in configure global security Sounds like a corrupt unpacked WAR, perhaps. Unclear to me. Change By: Jesse Glick (12/Feb/14 9:48 PM) Assignee: JesseGlick 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta commented on JENKINS-21791 NPE when trying to add/update credentials in configure global security Last time around after restarting the jenkins process i was able to make 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta commented on JENKINS-21791 NPE when trying to add/update credentials in configure global security Interesting do you have any insight into how i can check the validity of the war file? BTW i am on centos 6 and using rpm's to bring up jenkins [root@10 ~]# cat /etc/redhat-release CentOS release 6.3 (Final) [root@10 ~]# [root@10 ~]# [root@10 ~]# rpm -qa | grep jenkins jenkins-1.546-1.1.noarch 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta commented on JENKINS-21791 NPE when trying to add/update credentials in configure global security Here is some info on the war file being used [root@10 ~]# rpm -ql jenkins | less [root@10 ~]# ls -latr /usr/lib/jenkins/jenkins.war -rw-r--r--. 1 root root 66180961 Jan 6 09:46 /usr/lib/jenkins/jenkins.war [root@10 ~]# md5sum /usr/lib/jenkins/jenkins.war c404e7dfa19977bc22b0d790ea2ad74a /usr/lib/jenkins/jenkins.war 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] [matrix-auth] (JENKINS-21791) NPE when trying to add/update credentials in configure global security
Arpit Gupta commented on JENKINS-21791 NPE when trying to add/update credentials in configure global security Also at some point of time this was working. I upgraded to 1.546 and restart jenkins because i ran into the same problem and after restart i was able to update the users in the matrix (in jan 2014). However now i am running into the same issue on the same installed version. 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] [core] (JENKINS-8666) Matrix project index page broken by axis with empty values
evernat commented on JENKINS-8666 Matrix project index page broken by axis with empty values It seems that I do not reproduce this anymore with Jenkins 1.549. Does someone reproduce 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 -- 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Trygve Hardersen commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 (before we have all out projects using Git…) 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] [core] (JENKINS-21792) List view broken after enabling Filter build queue
Damien Nozay created JENKINS-21792 List view broken after enabling Filter build queue Issue Type: Bug Assignee: Unassigned Components: core Created: 12/Feb/14 10:58 PM Description: 1. created a list view 2. filter jobs by regular _expression_ (mine is: builds.core..*) view works at this point. 3. check Filter build queue / check Filter build executors then I see the options above and want to play with them results: can't see the view can't edit the view can't delete the view snip listView owner class="hudson" reference="../../.."/ nameCore builds/name filterExecutorstrue/filterExecutors filterQueuetrue/filterQueue properties class="hudson.model.View$PropertyList"/ jobNames comparator class="hudson.util.CaseInsensitiveComparator"/ stringbuilds.core.150.debug/string stringbuilds.core.master.release/string /jobNames jobFilters/ columns hudson.views.StatusColumn/ hudson.views.WeatherColumn/ hudson.views.JobColumn/ hudson.views.LastSuccessColumn/ hudson.views.LastFailureColumn/ hudson.views.LastDurationColumn/ hudson.views.BuildButtonColumn/ /columns includeRegexbuilds.core..*/includeRegex recursefalse/recurse /listView snip Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.549.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [statusmonitor] (JENKINS-21793) Status Monitor Plugin not rendering HTML properly
Jared Griffith created JENKINS-21793 Status Monitor Plugin not rendering HTML properly Issue Type: Bug Affects Versions: current Assignee: danielgalan Attachments: status_monitor.png Components: statusmonitor Created: 12/Feb/14 11:12 PM Description: Status Monitor Plugin not rendering HTML properly Environment: CentOS 6.x, Oracle JDK 1.7.0_40, Jenkins 1.550-1.1 Project: Jenkins Labels: plugin Priority: Major Reporter: Jared Griffith 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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
Ok, I was able to resolve the issue by creating a correct chain of fingerprinting across my builds. The piece that was missing was that the build where I was not able to see dependent changes did not have a copy of the artifacts in the workspace. Although that particular build does not require the artifacts Jenkins needs them in the workspace to establish the connection that the build is dependent on a previous build that created the artifact. Since Jenkins does not support fingerprinting outside the workspace directory it is easiest just to use the "Copy artifacts from another build" option and tick the fingerprinting option.
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] [port-allocator] (JENKINS-6647) Add ability to allocate range of TCP Ports
Jeff Ekhardt commented on JENKINS-6647 Add ability to allocate range of TCP Ports I also need this and do need the consecutive assignment of ports. I see that the PortAllocationManager has allocatePortRange now, but it doesn't seem to have been exposed in the plugin UI. Is someone working on that? 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-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Hiroshi Wada edited a comment on JENKINS-21518 Error while using SSH credentials to fetch git repository. I've got the exactly same issue with the combination of Linux master (Jenkins 1.550 on Ubuntu 12.04) and Windows slave (slave.jar is up-to-date.) We manage private keys with Jenkins credentials plugin and directly paste keys on Jenkins console. Strange thing is remote build succeeds after rebooting a master or a slave. However, after while, all remote builds start failing. Not exactly sure what triggers the failure but it seems to occur after running a project which uses a different key, or after one of Jenkins projects fails due to wrong key settings. 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-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Hiroshi Wada commented on JENKINS-21518 Error while using SSH credentials to fetch git repository. I've got the exactly same issue with the combination of Linux master (Jenkins 1.550 on Ubuntu 12.04) and Windows slave (slave.jar is up-to-date.) We manage private keys with Jenkins credentials plugin and directly paste keys on Jenkins console. Strange thing is remote build succeeds after rebooting a master or a slave. However, after while, all remote builds start failing. Not exactly sure what triggers the failure but it seems to occur after running a project which uses a different key, or after one of Jenkins projects fails due to wrong key settings. (say, one of projects All build after the first one fail. Looks very strange. 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.
