[JIRA] (JENKINS-15506) Broken Rest API: When trying to access the REST API (/api/xml?depth=1) for a build flow job, I encountered an error.
Chris Kramer commented on JENKINS-15506 Broken Rest API: When trying to access the REST API (/api/xml?depth=1) for a build flow job, I encountered an error. I think this is also causing the trouble I have with updating the active buildqueue. The async request just fails after initial load. Also the logfiles get flooded with this 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
[JIRA] (JENKINS-15820) JClouds plugin deadlock
onemanbucket created JENKINS-15820 JClouds plugin deadlock Issue Type: Bug Assignee: abayer Attachments: catalina.out Components: jclouds Created: 14/Nov/12 9:32 AM Description: Jenkins deadlocks on JCloudsRetentionStrategy (we did a copy job in the GUI when it happened). Attached full stack trace, here are the deadlocks: "Remove Node i-42020766": at jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy.check(JCloudsRetentionStrategy.java:22) waiting to lock 0x0006cbca8a60 (a jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy) at jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy.check(JCloudsRetentionStrategy.java:15) at hudson.slaves.SlaveComputer.setNode(SlaveComputer.java:522) at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:116) at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:174) locked 0x0006c06d1088 (a java.lang.Object) at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1175) at jenkins.model.Jenkins.setNodes(Jenkins.java:1687) at jenkins.model.Jenkins.removeNode(Jenkins.java:1682) locked 0x0006c06d0f70 (a hudson.model.Hudson) at hudson.plugins.ec2.EC2Slave$1.run(EC2Slave.java:104) "Jenkins cron thread": at jenkins.model.Jenkins.save(Jenkins.java:2573) waiting to lock 0x0006c06d0f70 (a hudson.model.Hudson) at hudson.model.Node.setTemporaryOfflineCause(Node.java:211) at hudson.model.Computer.setTemporarilyOffline(Computer.java:586) at jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy.check(JCloudsRetentionStrategy.java:30) locked 0x0006cbca8a60 (a jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy) at jenkins.plugins.jclouds.compute.JCloudsRetentionStrategy.check(JCloudsRetentionStrategy.java:15) at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:66) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Environment: Jenkins 1.489, jclouds plugin 2.3.1 Project: Jenkins Priority: Major Reporter: onemanbucket This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Dirk Kuypers commented on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) I think you will have to wait for 1.491: http://jenkins-ci.org/changelog see upcoming 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
[JIRA] (JENKINS-12735) No upstream or downstream resolution with Maven version ranges
Alex Koon resolved JENKINS-12735 as Fixed No upstream or downstream resolution with Maven version ranges Marking as resolved. JENKINS-15367 deals with the bug (now pulled to master) where defined versions are not correctly processes. Change By: Alex Koon (14/Nov/12 10:36 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
[JIRA] (JENKINS-15502) Email-ext issues: attachments feature creating issues
Slide-O-Mix commented on JENKINS-15502 Email-ext issues: attachments feature creating issues I'm going to create a build with more logging turned on, I have no local way of reproducing it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Ulli Hafner commented on JENKINS-15801 Allow root of relative paths to be specified @Joakim: shouldn't this work when you are using the new GCC parser that works in conjunction with make? (This still needs to be refactored, see JENKINS-14064). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15702) InstantiationError: hudson.scm.AbstractCvs
Farzad Valad reopened JENKINS-15702 InstantiationError: hudson.scm.AbstractCvs I'm getting this error and it doesn't go away with a restart. It happens when I try to access any of the job tabs. I searched all my jobs for AbstractCvs and didn't find any file that had it. I'm using version 1.489 of Jenkins and 2.7 of CVS plugin. Any advice? Jenkins is producing lots of errors and performing extremely slow. Change By: Farzad Valad (14/Nov/12 11:10 AM) Resolution: CannotReproduce Status: Closed 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
XYZ created JENKINS-15821 Cannot install prqa-plugin Issue Type: Bug Assignee: Praqma Support Components: prqa Created: 14/Nov/12 12:04 PM Description: hudson.err.log: WARNUNG: Failed to scout net.praqma.jenkins.plugin.prqa.globalconfig.PRQAGlobalConfig java.lang.InstantiationException: file:/C:/Program%20Files/Hudson/plugins/prqa-plugin/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: net.praqma.jenkins.plugin.prqa.globalconfig.PRQAGlobalConfig at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:290) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: net.praqma.jenkins.plugin.prqa.globalconfig.PRQAGlobalConfig at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:935) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 24 more 12.11.2012 09:53:21 hudson.ExtensionFinder$Sezpoz scout WARNUNG: Failed to scout net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier$DescriptorImpl java.lang.InstantiationException: file:/C:/Program%20Files/Hudson/plugins/prqa-plugin/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: net.praqma.jenkins.plugin.prqa.notifier.PRQANotifier$DescriptorImpl at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:290) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ExtensionList.get(ExtensionList.java:129) at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) at hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) at
[JIRA] (JENKINS-15499) HistoryWidget/entry.jelly throws NullPointerException
Sergey Smirnov updated JENKINS-15499 HistoryWidget/entry.jelly throws NullPointerException Change By: Sergey Smirnov (14/Nov/12 12:26 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9353) latest subversion plugin cause svn authentication record lost
evernat commented on JENKINS-9353 latest subversion plugin cause svn authentication record lost have you verified with official 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
[JIRA] (JENKINS-5762) Publish JUnit test result report data is not available
evernat resolved JENKINS-5762 as Incomplete Publish JUnit test result report data is not available No response from the reporter to Mark, so resolving as incomplete. Change By: evernat (14/Nov/12 12:29 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8102) TypeError: jsonElement is null when saving view changes
evernat resolved JENKINS-8102 as Incomplete TypeError: jsonElement is null when saving view changes No response from the reporter, so resolving as incomplete. Change By: evernat (14/Nov/12 12:30 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11727) Discard Unreadable Data - NPE
evernat commented on JENKINS-11727 Discard Unreadable Data - NPE Is it reproduced with a recent version of 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
[JIRA] (JENKINS-11728) Cannot add environment variable.
evernat commented on JENKINS-11728 Cannot add environment variable. I do not reproduce the issue with Jenkins v1.487. Do you reproduce with a recent version of 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
[JIRA] (JENKINS-11734) threadDump URL does not include master threads if no executors run on the master.
evernat commented on JENKINS-11734 threadDump URL does not include master threads if no executors run on the master. Hi Dean, I do not reproduce this issue with Jenkins 1.487 on windows. Do you 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
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
Mads Nielsen commented on JENKINS-15821 Cannot install prqa-plugin Hey, Thanks for trying out our plugin. I tried reproducing your issue by downloading a fresh jenkins 1.489 and installing it via update center. No issues for me installing it that way. Did you by any chance install it in some other way? Upgrading both jenkins and plugin for example, at once? Have you tried clearing prqa from your plugin folder and reinstalling it again thru the update center? We'll be happy to assist in any way we can. Regards, Mads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15822) Add shutdown reason when Jenkins shows Jenkins is going to shut down.
MeTAlMollY created JENKINS-15822 Add shutdown reason when Jenkins shows Jenkins is going to shut down. Issue Type: Improvement Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 14/Nov/12 1:20 PM Description: When the thinBackup plugin forces a quiet mode for jenkins the default shutdown message is displayed: "Jenkins is going to shut down". But as this shutdown is triggered by the thinBackup plugin. It would be nice if the shutdown reason is added. E.g. "Jenkins is going to shut down (triggered by thinBackup plugin)". Other solution is to let the user add an additional general shutdown reason from the thinBackup/backupsettings page. Project: Jenkins Priority: Minor Reporter: MeTAlMollY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15036) [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!)
hagzag updated JENKINS-15036 [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!) Change By: hagzag (14/Nov/12 2:06 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15036) [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!)
hagzag assigned JENKINS-15036 to Alex Nickolaevsky [jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!) Change By: hagzag (14/Nov/12 2:06 PM) Assignee: AlexNickolaevsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15737) MultiJob plugin does not take account current parameters
hagzag assigned JENKINS-15737 to Roni Licht MultiJob plugin does not take account current parameters Change By: hagzag (14/Nov/12 2:08 PM) Assignee: RoniLicht This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4428) Security leak - password parameters are visible
Logan Daigle commented on JENKINS-4428 Security leak - password parameters are visible This issue is still occurring. I am running version 1.471 of the Jenkins service. I have installed the password masking plugin. This effectively removes the passwords from any log files, but if a job that takes a password as a parameter is waiting in the queue and you hover over the hyperlink, the password is shown. This is NOT good. The shows my active directory password to anyone else that hovers over this link and may give someone access to a network resource that they would not otherwise have access to. PLEASE FIX! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
Stephan Pauxberger created JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause Issue Type: Improvement Assignee: rsandell Components: gerrit-trigger Created: 14/Nov/12 2:15 PM Description: If GerritCause was a Subclass of SCMTriggerCause (which is not that far fetched, since a GerritTrigger is in fact an SCMChange), we could make it easier for plugins that react on Code-Changes. In my special case, I am currently working on some improvements in Jenkins' incremental module handling which should behave differently when the a build is ONLY caused by sourcecode changes. Making that change would quite neatly solve a couple of problems without creating unnatural dependencies. I will create a pull request for this. Project: Jenkins Priority: Major Reporter: Stephan Pauxberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ I think the change needed to be done in class WorkspaceList : /** * The token that combines the project name and unique number to create unique workspace directory. */ private static final String COMBINATOR = System.getProperty(WorkspaceList.class.getName(),"@"); I've seen kohsuke mention in the commit message that advanced users can change this string somehow, not sure how though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4428) Security leak - password parameters are visible
Logan Daigle updated JENKINS-4428 Security leak - password parameters are visible Change By: Logan Daigle (14/Nov/12 2:24 PM) Priority: Major Critical Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
XYZ commented on JENKINS-15821 Cannot install prqa-plugin Did you by any chance install it in some other way? Upgrading both jenkins and plugin for example, at once? -- It's manually installed Have you tried clearing prqa from your plugin folder and reinstalling it again thru the update center? -- No, but I cleared and manually installed it but it still doesn't work. Installation via the update center is not possible (Jenkins runs in a closed infrastructure). Regards, Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
Stephan Pauxberger commented on JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause created https://github.com/jenkinsci/gerrit-trigger-plugin/pull/34 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
Christopher Orr commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ For reference: https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to someone on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Djava.hudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to darkrift on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Djava.hudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15824) SBT plugin does not support paths to sbt-launcher.jar to be configured per node
Jan Krag created JENKINS-15824 SBT plugin does not support paths to sbt-launcher.jar to be configured per node Issue Type: New Feature Affects Versions: current Assignee: uzilan Components: sbt Created: 14/Nov/12 2:59 PM Description: The configuration of "sbt launcher jars" paths in the general jenkins configuration page (i.e. globally) should be overridable in "Tool location" for each node (like JDK, Git Hg paths). If running in a mixed environment with both linux and windows slaves, the path to sbt (like the other tools) will typically be very different on the two platforms (e.g. c:\sbt\sbt-launcher.jar vs. /usr/local/bin/sbt) Environment: Mixed environment. Jenkins Master on windows server, and nodes running both windows and Linux Project: Jenkins Priority: Major Reporter: Jan Krag This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
Mads Nielsen commented on JENKINS-15821 Cannot install prqa-plugin Hey Frank, I tried installing it using the manual process, first upload with the UI and selecting the downloaded .hpi file. (Advanced -- Upload) That worked. I then deleted the .hpi and the assoicated folder. And put the .hpi file in the plugins folder. Jenkins correctly installed it, upon restart. I'm assuming you're using the latest 1.1.3 version of the plugin right? Regards, Mads This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
michael d edited a comment on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ According to darkrift on IRC, the workaround is this : You need to add a -D parameter to the startup of jenkins : -Dhudson.slaves.WorkspaceList=! (to change it to ! for example) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15821) Cannot install prqa-plugin
XYZ commented on JENKINS-15821 Cannot install prqa-plugin Hello Mads, no, actually I'm using the 1.1.2. Now I try to install the 1.1.3. Regards, Frank This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12630) Solaris tar does not support gzip (z option)
Jochen Hinrichsen commented on JENKINS-12630 Solaris tar does not support gzip (z option) The issue remains in version 1.466.2. It happens on a SunOS master installation as well. The downloaded file is named 'jdk.sh', but it is a zipped tar. Standard Sun tar does not support zipped tars. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15825) Exception not catched before saving build
vjuranek resolved JENKINS-15825 as Fixed Exception not catched before saving build Already fixed in 51f715162e 1, this is mainly for LTS not to forget to backport it. 1 https://github.com/jenkinsci/jenkins/commit/51f715162eba4dd1c4e081ec15c7ceb12e813ca5 Change By: vjuranek (14/Nov/12 3:46 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
[JIRA] (JENKINS-15737) MultiJob plugin does not take account current parameters
Roni Licht resolved JENKINS-15737 as Fixed MultiJob plugin does not take account current parameters Change By: Roni Licht (14/Nov/12 3:49 PM) Status: Open Resolved Fix Version/s: current 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
[JIRA] (JENKINS-15825) Exception not catched before saving build
vjuranek created JENKINS-15825 Exception not catched before saving build Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Nov/12 3:44 PM Description: Run calls all run listeners without catching exceptions from these listeners. This can result in situation that builds are not stored properly (build.xml is not created) and therefore after next restart build is not loaded + some information (like build parameters) are lost. Project: Jenkins Priority: Critical Reporter: vjuranek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
SCM/JIRA link daemon commented on JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause Code changed in jenkins User: Stephan Pauxberger Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritCause.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/9219b738aef82d67e4d1f6c309ff61487f5667ee Log: JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15823) Make GerritCause a Subclass of SCMTriggerCause
SCM/JIRA link daemon commented on JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritCause.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/ee832ba4018f96cc6eaef2044d6f0222d6c778a1 Log: Merge pull request #34 from pauxus/gerrit-change-is-scm-change JENKINS-15823 Make GerritCause a Subclass of SCMTriggerCause Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/dd8c8131208b...ee832ba4018f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15825) Exception not caught before saving build
vjuranek updated JENKINS-15825 Exception not caught before saving build Change By: vjuranek (14/Nov/12 3:54 PM) Summary: Exceptionnot catched caught beforesavingbuild This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
cjo9900 assigned JENKINS-14545 to cjo9900 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Change By: cjo9900 (14/Nov/12 4:24 PM) Assignee: huybrechts cjo9900 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
cjo9900 started work on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Change By: cjo9900 (14/Nov/12 4:23 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14545) Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname
cjo9900 commented on JENKINS-14545 Unusable environment variable TRIGGERED_BUILD_NUMBER_jobname Pull request for this fix https://github.com/jenkinsci/parameterized-trigger-plugin/pull/27 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-4433) log4j upgrade to version 1.2.12 or later
Thomas Hallgren commented on JENKINS-4433 log4j upgrade to version 1.2.12 or later What needs to be changed in order to move to the latest 1.2.x version? I'm willing to submit a patch if someone can point me to the right pom file(s). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14977) Integrate with Config File Provider plugin
cjo9900 updated JENKINS-14977 Integrate with Config File Provider plugin Could you add more details on how you would expect this to work? Setting to the config-file-provider component as that component should implement the extension point1 from the parameterized trigger plugin to provide the action to pass to the triggered build, so is only present if the config-file-provider is installed. The config-file-provider would also need to perform some behaviour if an "config-file" action was passed into the build, 1 hudson.plugins.parameterizedtrigger.AbstractBuildParameters and optionally if needed hudson.plugins.parameterizedtrigger.AbstractBuildParameterFactory Change By: cjo9900 (14/Nov/12 6:06 PM) Assignee: huybrechts domi Component/s: config-file-provider Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.
Bruno P. Kinoshita commented on JENKINS-15810 Testlink plugin : generated TAP result files are not used for updating Testlink. Hi Stéphane! Glad to hear that that helped. I'm recording screencasts, and have already prepared a sample Virtual Machine with the plugin + jenkins + testlink configured. Hopefully that, plus this issue and your screenshots, will be enough to make sure other users don't have the same issue. Thanks! -B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.
Bruno P. Kinoshita stopped work on JENKINS-15810 Testlink plugin : generated TAP result files are not used for updating Testlink. Change By: Bruno P. Kinoshita (14/Nov/12 6:11 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15810) Testlink plugin : generated TAP result files are not used for updating Testlink.
Bruno P. Kinoshita resolved JENKINS-15810 as Fixed Testlink plugin : generated TAP result files are not used for updating Testlink. Change By: Bruno P. Kinoshita (14/Nov/12 6:11 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
[JIRA] (JENKINS-15588) TestLink is not getting Updated
Bruno P. Kinoshita resolved JENKINS-15588 as Incomplete TestLink is not getting Updated Change By: Bruno P. Kinoshita (14/Nov/12 6:14 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15588) TestLink is not getting Updated
Bruno P. Kinoshita stopped work on JENKINS-15588 TestLink is not getting Updated Change By: Bruno P. Kinoshita (14/Nov/12 6:14 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez commented on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation What kind of documentation do you need ? VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it ie : This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:44 PM) Attachment: VBP1.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Alex Doolittle commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Nearly identical issue, all executors dead on all slaves at item.isStuck(); however, instead of ArrayIndexOutOfBounds we're getting a NullPointerException. Jenkins 1.487 hosted on RHEL, with mixed OSes for the executors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:47 PM) Attachment: VBP2.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez edited a comment on JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation What kind of documentation do you need ? VirtualBox plugin requires vboxwebdrv started and then Jenkins could use it. See attached screenshots This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-6721) Provide Link to VirtualBox Cloud Setup Documentation
Henri Gomez updated JENKINS-6721 Provide Link to VirtualBox Cloud Setup Documentation Change By: Henri Gomez (14/Nov/12 6:47 PM) Attachment: VBP3.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15828) JDK Install fails with SSL Handshake Exception
Jesse Bowes created JENKINS-15828 JDK Install fails with SSL Handshake Exception Issue Type: Bug Assignee: Unassigned Components: core Created: 14/Nov/12 7:18 PM Description: When I set up a JDK to automatically install, build fails with: Installing JDK jdk-7u6-oth-JPR Downloading JDK from http://download.oracle.com/otn/java/jdk/7u6-b24/jdk-7u6-linux-x64.tar.gz FATAL: Remote host closed connection during handshake javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:849) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:637) at com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:89) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) at org.apache.commons.httpclient.HttpConnection.flushRequestOutputStream(HttpConnection.java:828) at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2116) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at hudson.tools.JDKInstaller.locate(JDKInstaller.java:381) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:125) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:203) at hudson.model.JDK.forNode(JDK.java:122) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:943) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:59) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:154) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.init(MavenExtractorEnvironment.java:85) at org.jfrog.hudson.maven3.Maven3ExtractorListener.setUpEnvironment(Maven3ExtractorListener.java:64) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:642) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1516) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.EOFException: SSL peer shut down incorrectly at com.sun.net.ssl.internal.ssl.InputRecord.read(InputRecord.java:333) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:830) ... 29 more Project: Jenkins Priority: Major Reporter: Jesse Bowes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15801) Allow root of relative paths to be specified
Joakim Plate commented on JENKINS-15801 Allow root of relative paths to be specified I would have thoughts so. But maybe it is because i execute the directory change (make -C) directly from the bash script instead of inside another make. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis created JENKINS-15830 Error: Unable to infer the new branch name from XXX Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: svnmerge Created: 14/Nov/12 9:16 PM Description: The problem lies in the fact that the plugin tries to deduce the branch to be create absolute path from the current trunk path. The assumption is that the svn repository is using the following convention: http://svnserver.com/projectName and within that you have a a trunk and a branches folder. Our setup uses a completely different structure where the "trunk" folder is at the root and has a different name other than trunk. Within that "trunk" folder you have another 2 layers at least till you reach the project that has been checked out. trunk example: http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectName branch example: http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranch The "culprit" seems to be: svnmerge-plugin / src / main / java / jenkins / plugins / svnmerge / IntegratableProjectAction.java A possible fix would be to also allow the user to define the full feature branch path from the root of the svn as an additional feature. That would allow us to create a feature branch anywhere within our svn structure since features branches can go in more than one "branch locations" (ie you have no way to automatically deduce the full branch path) Its not critical but currently we cannot use this plugin due to this problem. I have never developed for Jenkins but I am a Java Developer so I could give it a go myself as long as I am pointed in the right direction. Environment: Jenkins Master on Ubuntu 12.04 Project: Jenkins Labels: plugin svnmerge error, Priority: Minor Reporter: Alex Ouzounis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15830) Error: Unable to infer the new branch name from XXX
Alex Ouzounis updated JENKINS-15830 Error: Unable to infer the new branch name from XXX Change By: Alex Ouzounis (14/Nov/12 9:17 PM) Description: Theproblemliesinthefactthattheplugintriestodeducethebranchtobe create created absolutepathfromthecurrenttrunkpath.Theassumptionisthatthesvnrepositoryisusingthefollowingconvention:http://svnserver.com/projectNameandwithinthatyouhaveaatrunkandabranchesfolder.Oursetupusesacompletelydifferentstructurewherethetrunkfolderisattherootandhasadifferentnameotherthantrunk.Withinthattrunkfolderyouhaveanother2layersatleasttillyoureachtheprojectthathasbeencheckedout.trunkexample:http://svnserver.com/FolderTrunk/Folder2/Folder3/Folder4/ProjectNamebranchexample:http://svnserver.com/FolderBranches/Folder2/..At_Least_3_Folders../FeatureBranchTheculpritseemstobe:svnmerge-plugin/src/main/java/jenkins/plugins/svnmerge/IntegratableProjectAction.javaApossiblefixwouldbetoalsoallowtheusertodefinethefullfeaturebranchpathfromtherootofthesvnasanadditionalfeature.Thatwouldallowustocreateafeaturebranchanywherewithinoursvnstructuresincefeaturesbranchescangoinmorethanonebranchlocations(ieyouhavenowaytoautomaticallydeducethefullbranchpath)Itsnotcriticalbutcurrentlywecannotusethispluginduetothisproblem.IhaveneverdevelopedforJenkinsbutIamaJavaDevelopersoIcouldgiveitagomyselfaslongasIampointedintherightdirection. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Overmind DL1 commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Also experiencing this issue with Jenkins ver. 1.489. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14781) Maven Release Plugin performs build without goals
teilo commented on JENKINS-14781 Maven Release Plugin performs build without goals just to confirm when you say it works on Linux with Iceweasel - is it still talking to the jenkins master running on windows and are you still using a password with a " symbol in it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10661) Impossible to assign the permission release using project based matrix security
teilo resolved JENKINS-10661 as Fixed Impossible to assign the permission release using project based matrix security as per previous fix - and latest comment. Change By: teilo (14/Nov/12 10:01 PM) Status: Reopened Resolved Assignee: mohanKumarBM teilo 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
[JIRA] (JENKINS-9268) m2 release fails on Windows using pure java subversion scm provider
teilo updated JENKINS-9268 m2 release fails on Windows using pure java subversion scm provider Note the workspace on windows could also be on a case sensitive filesystem (rather than the default case insensitive case preserving -think CIFS server). Doing this every build seems a bit like a waste - and I have hit this issue elsewhere (but don't recall the exact issue) Perhaps a better fix would be to check the remotefs root when configuring the slave and provide a warning, or to convert the slave root Change By: teilo (14/Nov/12 10:13 PM) Component/s: slave-setup This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14764) Videos aren't being embedded for Maven 2/3 Jobs (ie. non-freestyle)
Ross Rowe resolved JENKINS-14764 as Fixed Videos arent being embedded for Maven 2/3 Jobs (ie. non-freestyle) This issue should be resolved in version 1.31 Change By: Ross Rowe (14/Nov/12 11:43 PM) Status: InProgress 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
[JIRA] (JENKINS-15829) hg share always recreating working copy on slave (on master it's working fine)
Jesse Glick assigned JENKINS-15829 to Willem Verstraeten hg share always recreating working copy on slave (on master its working fine) Afraid I do not know much about the share mode. Change By: Jesse Glick (15/Nov/12 1:15 AM) Assignee: JesseGlick WillemVerstraeten This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15790) Name of Test Case is null
Bruno P. Kinoshita commented on JENKINS-15790 Name of Test Case is null Hi, I'll have to investigate this issue in TestLink. The name is not being returned by TL anymore, since 1.9.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14711) No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine
Akhil Mittal reopened JENKINS-14711 No changelist in CVS plugin 2.5 using rlog, but cli rlog works fine Hi, I am still getting this issue where I am seeing no changes in change log it updated my workspace though rlog command works fine on Solaris CLI as. My set up is Jenkins ver. 1.488 CVS plugin I tried both latest 2.7 2.4 no luck My Project job configuration for SCM is location: Tag Tag name: DEV Use Update is checked (yes) Basically I want Jenkins to kick of build job if there are any updates to a particular tag in this case DEV, which works fine with this scheme for my workspace but the change is not reflected in change log. Console output cvs checkout -r DEV -d temp srcmgr cvs checkout: Updating temp cvs checkout: Updating temp/adhoc cvs checkout: Updating temp/cm cvs checkout: Updating temp/cm/bin cvs checkout: Updating temp/logs cvs checkout: Updating temp/test U temp/test/someotheFile cvs checkout: Updating temp/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs checkout: Updating temp/test/someDir U temp/test/someDir/foo.bar Using locally configured password for connection to :pserver:amittal@melcvs01:/cvs cvs rlog -S -d15 Nov 2012 15:24:35 +110015 Nov 2012 15:39:59 +1100 srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir It updates my workspace however there is nothing in the change log or changes in Jenkins, whereas I can run rlog on Solaris CLI cvs rlog -S -d'15 Nov 2012 15:24:35 +110015 Nov 2012 15:39:59 +1100' srcmgr cvs rlog: Logging srcmgr cvs rlog: Logging srcmgr/adhoc cvs rlog: Logging srcmgr/cm cvs rlog: Logging srcmgr/cm/bin cvs rlog: Logging srcmgr/logs cvs rlog: Logging srcmgr/test RCS file: /cvs/srcmgr/test/someotheFile,v head: 1.3 branch: locks: strict access list: symbolic names: TAGINFO: 1.1 SOURCE_CONTROL: 1.1 QA: 1.1 PRODSTAGE: 1.1 PRODBUILD: 1.1 PRODFIX: 1.1 SITPR1: 1.1 UATPR1: 1.1 TESTGAP: 1.1 TESTMIG: 1.1 TRNG: 1.1 HUGO: 1.1 DEVGAP: 1.1 DEVMIG2: 1.1 DEVMIG: 1.1 DEV: 1.3 keyword substitution: kv total revisions: 3; selected revisions: 1 description: revision 1.2 date: 2012/11/15 04:39:21; author: amittal; state: Exp; lines: +1 -0 empty log message *** = cvs rlog: Logging srcmgr/test/createSomeLongPathDirAveryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVeryVerylongpathDirectory cvs rlog: Logging srcmgr/test/someDir Change log is empty /export/home/amittal/.jenkins/jobs/Akhil/builds/17 cat changelog.xml ?xml version="1.0" encoding="UTF-8"? changelog /changelog TIA Akhil Change By: Akhil Mittal (15/Nov/12 5:29 AM) 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
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Marc Swingler commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Tried adding this as an attachment without luck. Logged from version 1.490 Nov 15, 2012 1:11:46 AM hudson.model.RunMap retrieve WARNING: could not load D:\.jenkins\jobs\configuration.test\builds\1 hudson.util.IOException2: Invalid directory name D:\.jenkins\jobs\configuration.test\builds\1 at hudson.model.Run.parseTimestampFromBuildDir(Run.java:332) at hudson.model.Run.init(Run.java:278) at hudson.model.AbstractBuild.init(AbstractBuild.java:179) at hudson.maven.AbstractMavenBuild.init(AbstractMavenBuild.java:54) at hudson.maven.MavenModuleSetBuild.init(MavenModuleSetBuild.java:135) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1078) at hudson.model.AbstractProject$1.create(AbstractProject.java:277) at hudson.model.AbstractProject$1.create(AbstractProject.java:275) at hudson.model.RunMap.retrieve(RunMap.java:220) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:638) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:601) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:344) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:502) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:355) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:297) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1015) at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:139) at hudson.model.Job.getLastSuccessfulBuild(Job.java:765) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:185) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:365) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:682) at hudson.maven.MavenModuleSet.updateTransientActions(MavenModuleSet.java:361) at hudson.model.AbstractProject.onLoad(AbstractProject.java:301) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:667) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2507) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.text.ParseException: Unparseable date: "1" at java.text.DateFormat.parse(Unknown Source) at hudson.model.Run.parseTimestampFromBuildDir(Run.java:330) ... 38 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15576) LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin
Laurence Hey assigned JENKINS-15576 to Laurence Hey LoadStatistics queue length and Cloud provisioning not working in conjunction with Node and Label parameter plugin Change By: Laurence Hey (15/Nov/12 6:32 AM) Assignee: domi LaurenceHey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14781) Maven Release Plugin performs build without goals
jsirex
updated JENKINS-14781
Maven Release Plugin performs build without goals
Change By:
jsirex
(15/Nov/12 7:09 AM)
Description:
IhavejenkinsmasterinstalledonWindows.Browserischrome(sometimesreproducedinfirefoxtoo).
Steps:#Performmavenreleaseplugin#SpecifySCMCredentials
(mvnreleasefailswithoutit)
withinpassword
#SchedulemavenreleaseResults:InlogsIsee:{code}ExecutingMaven:-B-fc:\opt\Jenkins\jobs\project-ci\workspace\pom.xml-DdevelopmentVersion=4.4.005-SNAPSHOT-DreleaseVersion=4.4.004-Dusername=user-Dpassword=*Nogoalshavebeenspecifiedforthisbuild.Youmustspecifyavalidlifecyclephaseoragoal{code}Buildfails.Expectedresults:Releasegoalsarepassedinmavenduringrelease.
Note:OnLinuxwithIcewasel(firefox)10.0.6allworksfine.Itsverystrangeoddforme.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11519) When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than '@'
ejschuiteman commented on JENKINS-11519 When chosing Execute concurrent builds if necessary extra workspaces created should use a different character than @ That is working, thank you! 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
