[JIRA] [jenkins-tracker] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Alex Skoropad commented on JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard some log on 1.522: Jul 8, 2013 9:26:36 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading job web_acr.mlsdev.com_deploy_to_test hudson.util.IOException2: Unable to read /var/lib/jenkins/jobs/web_acr.mlsdev.com_deploy_to_test/config.xml at hudson.XmlFile.read(XmlFile.java:147) at hudson.model.Items.load(Items.java:220) at jenkins.model.Jenkins$18.run(Jenkins.java:2553) 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:895) 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(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null Debugging information cause-exception : java.lang.NullPointerException cause-message : null class : org.jruby.runtime.builtin.IRubyObject required-type : org.jruby.runtime.builtin.IRubyObject converter-type : org.jenkinsci.jruby.JRubyXStreamConverter path: /project/buildWrappers/ruby-proxy-object/ruby-object line number : 124 class1: org.jenkinsci.jruby.JRubyMapper$DynamicProxy converter-type1 : org.jenkinsci.jruby.JavaProxyConverter class2: hudson.util.DescribableList converter-type2 : hudson.util.DescribableList$ConverterImpl class3: hudson.model.FreeStyleProject converter-type3 : hudson.util.RobustReflectionConverter version : null --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at org.jenkinsci.jruby.JavaProxyConverter.unmarshal(JavaProxyConverter.java:60) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.readItem(AbstractCollectionConverter.java:71) at hudson.util.CopyOnWriteList$ConverterImpl.unmarshal(CopyOnWriteList.java:193) at hudson.util.DescribableList$ConverterImpl.unmarshal(DescribableList.java:263) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:333) at hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:275) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:222) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at
[JIRA] [config-file-provider] (JENKINS-15976) Provided maven settings.xml in maven builder is lost
Bastian Glöckle commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost I verified this again this morning. I used a fresh Jenkins 1.522 installation inside a Tomcat 7.0.41. There are two plugins installed into Jenkins: token-macro (1.7) and config-file-provider (2.5.1). Steps to reproduce: Fresh installation Go to configuration, add a "Maven settings.xml" in "Managed files" Create a new Freestyle project Add a "Execute Maven goals" build step Click "Advanced" Settings file: "provided settings.xml" Choose the created settings.xml Save Re-open configuration of job and inspect the Advanced settings of the Maven build step - "Settings file: Use default maven 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] [core] (JENKINS-18525) Jenkins 1.520 update breaks Jenkins . Jenkins wont start
sogabe edited a comment on JENKINS-18525 Jenkins 1.520 update breaks Jenkins . Jenkins wont start dellooks like JENKINS-18404/del 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-18592) JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520
Bob Verbrugge commented on JENKINS-18592 JDK jdk1.5.0_12 builds fail with java.lang.UnsupportedClassVersionError since upgrade to Jenkins 1.520 Is this related to the following 1.520 change? Core started relying on Java 1.6 as per the agreement in the dev list. If you have a serious objection against it, please let us know before we really start relying on 1.6 features. 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
sogabe updated JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard Change By: sogabe (08/Jul/13 7:15 AM) Component/s: ruby-runtime Component/s: jenkins-tracker 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Alex Skoropad commented on JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard thanks a lot) After upgrading ruby-runtime-plugin and upgrading Jenkins to 1.522 all jobs present 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-13597) Linkage error after upgrade to 1.461
Jakub Štiller resolved JENKINS-13597 as Not A Defect Linkage error after upgrade to 1.461 We finally found the problem. One of our maven plugin cause the problem. It incorrectly manipulates with classloader, and as result jenkins try to load class that is already in system classloader. Change By: Jakub Štiller (08/Jul/13 7:33 AM) 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] [github] (JENKINS-18165) NPE in github status notification, if build not triggered by github push trigger
Jon Pascoe commented on JENKINS-18165 NPE in github status notification, if build not triggered by github push trigger Whilst 1.7 no longer gives a NPE, the commit status notification does not seem to be pushed to GitHub. 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-18621) Weird IllegalArgumentException prevents SVN polling from working
Pawel Gronkiewicz commented on JENKINS-18621 Weird IllegalArgumentException prevents SVN polling from working This Maven version is used by other jobs without problem. I have tried changing it too. I will attach build 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] [config-file-provider] (JENKINS-18635) Option to encrypt config file
domi commented on JENKINS-18635 Option to encrypt config file and how do you think such files should be handled on the slave site? these files can be referenced in every job, how can/should we protect it there? maybe we have to create a new config file type, and prevent this typ of file to be available on every job - but then, how would such a file be helpful for anyone? 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Igor Balos commented on JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard I can confirm the same, all jobs are present with new ruby-runtime 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Igor Balos resolved JENKINS-18404 as Duplicate When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard Change By: Igor Balos (08/Jul/13 7:56 AM) 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Igor Balos edited a comment on JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard I can confirm the same, all jobs are present with new ruby-runtime in 1.522 , upgraded couple of minutes ago. Thanks! 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-18641) People View does Not Populate (makeStaplerProxy)
Wolf Wolfswinkel commented on JENKINS-18641 People View does Not Populate (makeStaplerProxy) Observing the same issue on Windows 7. The issue appeared in after upgrading to 1.520. 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] [ruby-runtime] (JENKINS-18404) When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard
Yuu Yamashita commented on JENKINS-18404 When I upgrade from Jenkins 1.517 most of my jobs are not visible in the Dashboard There were same problems had have been reported as JENKINS-18314 and JENKINS-18528. They have been fixed in ruby-runtime 0.12. 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-18650) Updating snapshot view on master fails with Unconnected pipe
Vincent Latombe commented on JENKINS-18650 Updating snapshot view on master fails with Unconnected pipe Trying to reproduce... 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-18650) Updating snapshot view on master fails with Unconnected pipe
Dirk Kuypers commented on JENKINS-18650 Updating snapshot view on master fails with Unconnected pipe BTW, the failing job uses SCM polling. I started another job in parallel which does not use SCM polling and alway runs on a slave--it worked. 09:16:19 Snapshots $ cleartool -version 09:16:19 ClearCase version 7.1.2.1 (Fri Dec 17 17:22:14 EST 2010) (7.1.2.01.00_2010D.FCS) 09:16:19 ClearCase version 7.1.2.2 (Tue Mar 29 16:47:51 EST 2011) (7.1.2.02.00_2011A.FCS) 09:16:19 ClearCase version 7.1.2.3 (Thu Jun 23 22:31:05 EDT 2011) (7.1.2.03.00_2011B.FCS) 09:16:19 ClearCase version 7.1.2.4 (Fri Sep 09 23:31:19 EDT 2011) (7.1.2.04.00_2011C.FCS) 09:16:19 ClearCase version 7.1.2.5 (Thu Dec 22 03:31:03 EST 2011) (7.1.2.05.00_2011D.FCS) 09:16:19 ClearCase version 7.1.2.6 (Thu Apr 05 18:01:28 EDT 2012) (7.1.2.06.00_2012A.FCS) 09:16:19 ClearCase version 7.1.2.7 (Thu Jun 21 15:34:01 EDT 2012) (7.1.2.07.00_2012B.FCS) 09:16:19 ClearCase version 7.1.2.8 (Thu Sep 13 15:31:20 EDT 2012) (7.1.2.08.00_2012C.FCS) 09:16:19 ClearCase version 7.1.2.9 (Mon Nov 26 20:31:04 EST 2012) (7.1.2.09.00_2012D.D121126) 09:16:19 @(#) MVFS version 7.1.2.9 (Tue Nov 13 21:55:00 2012) 09:16:19 cleartool 7.1.2.9 (Mon Nov 19 22:05:59 2012) 09:16:19 db_server 7.1.2.9 (Tue Nov 13 23:09:29 2012) 09:16:19 VOB database schema version: 54 09:16:19 Running cleartool setcs, this operation may take a while 09:16:19 RunSonarContest $ cleartool setcs -current -overwrite 09:19:52 # ClearCase snapshot view update log 09:19:52 # Update session parameters: 09:19:52 # 09:19:52 FormatVersion: 4 09:19:52 SnapshotView:D:\Snapshots\RunSonarContest 09:19:52 StartTime: 2013-07-08T09:16:20+02:00 09:19:52 UserID: sa_mu_1sp1cm-build@1SP1-SLAVE12 09:19:52 ProcessID: 17812 09:19:52 ConfigSpecSet: TRUE 09:19:52 PreviewOnly: FALSE 09:19:52 PreserveVOBTimes:FALSE 09:19:52 UpdateHijackedFiles: TRUE 09:19:52 RenameHijackedFiles: FALSE 09:19:52 # 09:19:52 # Actions taken to update the view: 09:19:52 # 09:19:52 Updated: contest_sw\Devices\PhysicalDevicesTest\SwitchUnitTests\ScuTest.cs \main\27 \main\28 09:19:52 Updated: contest_sw\Devices\PhysicalDevicesTest\SwitchUnitTests\SscuMimoTest.cs \main\21 \main\22 09:19:52 Updated: contest_sw\Devices\PhysicalDevicesTest\SwitchUnitTests\SscuMimoVar12Test.cs \main\11 \main\12 09:19:52 Updated: contest_sw\Devices\PhysicalDevicesTest\SwitchUnitTests\SscuMimoTest03.cs \main\4 \main\5 ... 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-18650) Updating snapshot view on master fails with Unconnected pipe
Vincent Latombe commented on JENKINS-18650 Updating snapshot view on master fails with Unconnected pipe I've managed to reproduce, it's happening only for jobs running on Master, I will release 1.3.16 asap with the fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-18650) Updating snapshot view on master fails with Unconnected pipe
Vincent Latombe resolved JENKINS-18650 as Fixed Updating snapshot view on master fails with Unconnected pipe Fixed version can be downloaded through (until the update center is updated) http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/clearcase/1.3.16/clearcase-1.3.16.hpi Change By: Vincent Latombe (08/Jul/13 8:42 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18621) Weird IllegalArgumentException prevents SVN polling from working
Vincent Latombe updated JENKINS-18621 Weird IllegalArgumentException prevents SVN polling from working Change By: Vincent Latombe (08/Jul/13 8:43 AM) Component/s: pollscm 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] [groovy-postbuild] (JENKINS-18651) Enable *correct* writing to the job's log from a post build script
Timor Raiman
created JENKINS-18651
Enable *correct* writing to the jobs log from a post build script
Issue Type:
New Feature
Assignee:
wolfs
Components:
groovy-postbuild
Created:
08/Jul/13 8:55 AM
Description:
I'm able to write to the build's log with:
manager.build.logFile.withWriter{log -
log.println "Hello Log."
}
However, features, such as log timestamping don't work. I'm assumming, the script's output won't be subjected to warning parsing either (did not check).
There should be some way to access the logging facilities that exist during the build proper.
Project:
Jenkins
Priority:
Major
Reporter:
Timor Raiman
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] [msbuild] (JENKINS-18652) Handling of Configuration and Platform parameters
Drew Reed created JENKINS-18652 Handling of Configuration and Platform parameters Issue Type: Bug Affects Versions: current Assignee: kdsweeney Components: msbuild Created: 08/Jul/13 9:00 AM Description: When using the plugin with out any explicit command options but using the "Pass build variables as properties" option I'm finding the generated command line has broken properties generated. I get the following Path To MSBuild.exe: C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe Executing the command cmd.exe /C C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /nologo /p:label=VS2012WDK;Configuration=Win8+Debug;Platform=x64 exit %%ERRORLEVEL%% from C:\jenkins\workspace\VCHIq_Interface_Driver_(staging)\Configuration\Win8 Debug\Platform\x64\label\VS2012WDK As you can see the /p option has no quotes and has change the space in the Configuration name into a plus. version 1.16 work as expected. Environment: Windows 7 64bit slave, Visual Studio 2012, Jenkins 1.509.2 Project: Jenkins Priority: Major Reporter: Drew Reed 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-18650) Updating snapshot view on master fails with Unconnected pipe
Dirk Kuypers commented on JENKINS-18650 Updating snapshot view on master fails with Unconnected pipe Thanks Vincent. Most colleagues are now working and some longer running jobs are in the pipe now. It will take some time until I will be able to restart.:-/ 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-18644) Loading Overlay
Krystian Kuczek edited a comment on JENKINS-18644 Loading Overlay Works onIE10-IE8, not working on IE7. I use Firefox 22 and Chrome 27 on both Linux and Windows (on both not working). 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-18644) Loading Overlay
Krystian Kuczek edited a comment on JENKINS-18644 Loading Overlay Working in IE10-IE8, not working on IE. I use Firefox 22 and Chrome 27 on both Linux and Windows (on both not working). 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-18644) Loading Overlay
Krystian Kuczek commented on JENKINS-18644 Loading Overlay Working in IE10-IE7, I use Firefox 22 and Chrome 27 on both Linux and Windows (on both not working). 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
Jan Darmochwal commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button I still see this bug in Jenkins 1.522 when using the Plot 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] [core] (JENKINS-18644) Loading Overlay
sogabe commented on JENKINS-18644 Loading Overlay Does _javascript_ error happen on project configuration page? or system configuration 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-18644) Loading Overlay
Krystian Kuczek commented on JENKINS-18644 Loading Overlay On Project 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] [copyartifact] (JENKINS-18653) Fingerprinting by CopyArtifact plugin should be optional
mwebber created JENKINS-18653 Fingerprinting by CopyArtifact plugin should be optional Issue Type: Improvement Assignee: Unassigned Components: copyartifact Created: 08/Jul/13 9:24 AM Description: The CopyArtifact plugin always creates fingerprints. This is by design, according to the plugin description: All artifacts copied are automatically fingerprinted for you The fingerprinting should be optional. I do not need the fingerprints, and there is no point sending CPU and disk for no reason. Project: Jenkins Priority: Major Reporter: mwebber 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-18654) DependencyClassLoader#getTransitiveDependencies returns disabled plugins
Nicolas De Loof created JENKINS-18654 DependencyClassLoader#getTransitiveDependencies returns disabled plugins Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Jul/13 9:33 AM Description: plugin that optionally depend on a disabled one, will get this one returned by DependencyClassLoader#getTransitiveDependencies. Typical result is a warning in startup logs : WARNING: Failed to scout hudson.tasks._ant.AntTargetNote$DescriptorImpl java.lang.InstantiationException: file:/Volumes/HD/Users/nicolas/Boulot/cloudbees/JE/cloudbees-license-plugin/work/plugins/ant/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.tasks._ant.AntTargetNote$DescriptorImpl at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:644) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:283) at hudson.ExtensionList.load(ExtensionList.java:278) Project: Jenkins Priority: Minor Reporter: Nicolas De Loof 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] [hp-application-automation-tools-plugin] (JENKINS-18655) HP Allication Automation Tools Plugin Not working
Rahul Goyal created JENKINS-18655 HP Allication Automation Tools Plugin Not working Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Attachments: Jenkins_HPALMIssue.jpg Components: hp-application-automation-tools-plugin, plugin Created: 08/Jul/13 9:48 AM Description: When using HP Application Automation Tool Plugin it gets configured in 'Manage Jenkins - Configure System - Application Lifecycle Management' without any issue but on configuring a Project/Job from 'Configure - Build ' using any of the HP Option is giving a issue. There is no any Field populated to accept the input . PFA Due Date: 08/Jul/13 12:00 AM Environment: Win 7 Fix Versions: current Project: Jenkins Labels: plugin jenkins windows configuration job build Priority: Blocker Reporter: Rahul Goyal 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] [selenium] (JENKINS-18638) Selenium Plugin New Configuration error: 'config.jelly' for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser
Michael Niestegge commented on JENKINS-18638 Selenium Plugin New Configuration error: config.jelly for class hudson.plugins.selenium.configuration.browser.selenium.IEBrowser I encountered the same problem. I am using Jenkins 1.521. 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] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Slawomir Czarko commented on JENKINS-17974 SVN plugin ignores --depth parameters Is the component here correct? I'm working on a fix for this issue but for subversion-plugin not for svncompat13. 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] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Andreas Scheucher commented on JENKINS-17974 SVN plugin ignores --depth parameters I am not sure about the component anymore. But AFAIK it was the only one related to SVN, hence I choose it. I guess it's wrong. 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] [copyartifact] (JENKINS-18653) Fingerprinting by CopyArtifact plugin should be optional
mwebber updated JENKINS-18653 Fingerprinting by CopyArtifact plugin should be optional Change By: mwebber (08/Jul/13 11:03 AM) Description: TheCopyArtifactpluginalwayscreatesfingerprints.Thisisbydesign,accordingtotheplugindescription:bq.AllartifactscopiedareautomaticallyfingerprintedforyouThefingerprintingshouldbeoptional.Idonotneedthefingerprints,andthereisnopoint sending spending CPUanddiskfornoreason. 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-18650) Updating snapshot view on master fails with Unconnected pipe
Dirk Kuypers commented on JENKINS-18650 Updating snapshot view on master fails with Unconnected pipe Just an update: The provided pre-version works! Many Thanks Vincent for the fast fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-13666) FATAL: Timer already cancelled.
chanti vlad commented on JENKINS-13666 FATAL: Timer already cancelled. Hi, we are also affected by this issue. It happens randomly on our server. Any news 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Sascha Vogt commented on JENKINS-17931 cvs rlog files in /tmp are not deleted I don't see such left-overs on our systems (Debian and RedHat) - which version of the plugin are you using? Do you see any error messages in either Jenkins logs or syslog? 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-18654) DependencyClassLoader#getTransitiveDependencies returns disabled plugins
dogfood commented on JENKINS-18654 DependencyClassLoader#getTransitiveDependencies returns disabled plugins Integrated in jenkins_main_trunk #2695 FIXED JENKINS-18654 exlude disabled plugins from transitive dependency list (Revision a6926e1c51c0650a48dec68cbe402248742dd55c) Result = UNSTABLE Nicolas De Loof : a6926e1c51c0650a48dec68cbe402248742dd55c Files : core/src/main/java/hudson/ClassicPluginStrategy.java 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
sogabe commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button @Jan Did you get a _javascript_ error "Error: TypeError: " ? 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] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Slawomir Czarko commented on JENKINS-17974 SVN plugin ignores --depth parameters Which SVN version are you using? 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-13666) FATAL: Timer already cancelled.
sogabe commented on JENKINS-13666 FATAL: Timer already cancelled. If you have build timeout plugin installed, try to configure time-out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Adrien CLERC commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Thanks for taking care of this. This is an old Hudson instance running on SLES10, that I continuously upgrade until 1.520. CVS plugin is version 2.9, so everything is up-to-date. To be precise, those rlog files are empty. So the problem is occurring when there are more or less 20,000 files, when the index of the directory starts to collapse. Does the plugin use an external library or program? 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] [walldisplay] (JENKINS-18656) Hiding specific jobs from the Wall
Jarno Rantanen created JENKINS-18656 Hiding specific jobs from the Wall Issue Type: New Feature Affects Versions: current Assignee: Christian Pelster Components: walldisplay Created: 08/Jul/13 12:10 PM Description: We have a lot of jobs in our Jenkins installation, and we're only really interested in seeing the status of a few. There is a setting for setting the display name of an individual job for the Wall, so a checkbox for hiding specific ones from there would be really nice to have! Thanks for your good work, Jarno Project: Jenkins Priority: Minor Reporter: Jarno Rantanen 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] [envinject] (JENKINS-18630) EnvInject causes javascript hang when configuring job
John Armenia resolved JENKINS-18630 as Fixed EnvInject causes _javascript_ hang when configuring job Change By: John Armenia (08/Jul/13 12: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 -- 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] [envinject] (JENKINS-18630) EnvInject causes javascript hang when configuring job
John Armenia commented on JENKINS-18630 EnvInject causes _javascript_ hang when configuring job Resolved in 1.522 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] [slave-prerequisites] (JENKINS-15627) Using MacOS slave in 1.487 - Can't connect to window server - not enough permissions
dally soft commented on JENKINS-15627 Using MacOS slave in 1.487 - Cant connect to window server - not enough permissions Thanks for the work around. 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] [role-strategy] (JENKINS-17482) Support folders
cforce edited a comment on JENKINS-17482 Support folders For us its useless that i need to give job specuial names to be able to filter it for rights mangemnt. It feels like a bad work around to manage security/acess aspects via the job name. For multi tenacy i need conatiners(like folder's) inside jenkins i can manage per client the rights for all the jobs inside it, no mater whats in there. It shall also be impossible to access the filesystem outside the workspace of this container. AT the moment every job can access all files accessable by the user who is running jenkins process (on the master), that is npt acceptable from security perspective if you have one master managaging builds from different orgs. It's an overkill to have different jenkins server for different clients. However we need to let different orgs let em manage their jobs (write config) and acceess each other jon's data inside the conatiner. 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] [role-strategy] (JENKINS-17482) Support folders
cforce edited a comment on JENKINS-17482 Support folders For us its useless that i need to give job specuial names to be able to filter it for rights mangemnt. It feels like a bad work around to manage security/acess aspects via the job name. For multi tenacy i need conatiners(like folder's) inside jenkins i can manage per client the rights for all the jobs inside it, no mater whats in there. It shall also be impossible to access the filesystem outside the workspace of this container. AT the moment every job can access all files accessable by the user who is running jenkins process (on the master), that is not acceptable from security perspective if you have one master managaging builds from different orgs. The actuala work around - have different jenkins servers for different clients - It's bad to maintain ! However we need to let different orgs let em manage their jobs (write config) and acceess each other jon's data inside the conatiner. 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] [dry] (JENKINS-3129) Show duplicate as a diff view
Ulli Hafner assigned JENKINS-3129 to Ulli Hafner Show duplicate as a diff view Change By: Ulli Hafner (08/Jul/13 12:57 PM) Assignee: MihailMenev UlliHafner 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] [analysis-core] (JENKINS-17196) Add an action that allows to reset the reference build
Ulli Hafner assigned JENKINS-17196 to Ulli Hafner Add an action that allows to reset the reference build Change By: Ulli Hafner (08/Jul/13 12:57 PM) Assignee: tatura UlliHafner 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] [warnings] (JENKINS-17075) Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors
Ulli Hafner resolved JENKINS-17075 as Fixed Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors Change By: Ulli Hafner (08/Jul/13 12:56 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] [analysis-core] (JENKINS-17169) Add navigation support using the context menu
Ulli Hafner assigned JENKINS-17169 to Ulli Hafner Add navigation support using the context menu Change By: Ulli Hafner (08/Jul/13 12:57 PM) Assignee: tatura UlliHafner 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] [warnings] (JENKINS-17309) XML escaping (or lack thereof)
Ulli Hafner assigned JENKINS-17309 to Ulli Hafner XML escaping (or lack thereof) Change By: Ulli Hafner (08/Jul/13 12:57 PM) Assignee: tatura UlliHafner 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] [analysis-core] (JENKINS-17167) Add search box support
Ulli Hafner assigned JENKINS-17167 to Ulli Hafner Add search box support Change By: Ulli Hafner (08/Jul/13 12:58 PM) Assignee: SebastianSeidl UlliHafner 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] [analysis-core] (JENKINS-9066) Aggregation of downstream project reports for static analysis reports
Ulli Hafner assigned JENKINS-9066 to Ulli Hafner Aggregation of downstream project reports for static analysis reports Change By: Ulli Hafner (08/Jul/13 12:58 PM) Assignee: SebastianHansbauer UlliHafner 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] [analysis-core] (JENKINS-15246) Analysis plugins should have quiet mode
Ulli Hafner resolved JENKINS-15246 as Fixed Analysis plugins should have quiet mode Change By: Ulli Hafner (08/Jul/13 12:58 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-17974) SVN plugin ignores --depth parameters
kutzi updated JENKINS-17974 SVN plugin ignores --depth parameters Change By: kutzi (08/Jul/13 1:04 PM) Component/s: subversion Component/s: svncompat13 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-17974) SVN plugin ignores --depth parameters
kutzi commented on JENKINS-17974 SVN plugin ignores --depth parameters So, actually it doesn't 'ignore' the depth option, but overwrites it in any case, right? I'm not terribly in favor of this feature as it basically sounds to me like you are working around the fact that your SVN repository is not organised optimally. However, since this would - according to the pull request (http://svnkit.com/javadoc/org/tmatesoft/svn/core/SVNDepth.html) - only require a single new value in an existing drop-down menu, I could live with 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] [analysis-core] (JENKINS-18657) Ability to show absolute date instead of relative
Vladimir Ryabtsev created JENKINS-18657 Ability to show absolute date instead of relative Issue Type: Improvement Affects Versions: current Assignee: Ulli Hafner Components: analysis-core Created: 08/Jul/13 1:25 PM Description: Jenkins' job list needs the ability of customization of "Last Success" and "Last Failure" columns. Special option is nedded to choose what type of date should be shown: relative (like now - e.g. "3 days, 6 hours") or absolute (just date and time). Second variant is more informative in several cases. Or plugin is needed with this functionality. Project: Jenkins Priority: Minor Reporter: Vladimir Ryabtsev 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] [role-strategy] (JENKINS-17482) Support folders
Daniel Beck commented on JENKINS-17482 Support folders Please also note that 'folders' has a specific meaning in this context and does not refer to file system directories: http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/folder.html https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Free+Enterprise+Plugins#CloudBeesFreeEnterprisePlugins-FoldersPlugin 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] [role-strategy] (JENKINS-17482) Support folders
Daniel Beck commented on JENKINS-17482 Support folders cforce: If you don't like the design of Role Strategy plugin, don't use it. It sounds like project-based matrix auth or the commercial Jenkins Enterprise plugin Role Based Access Control is a better fit for your needs. Besides, this has nothing to do with this issue or this plugin maybe ask the jenkins-users mailing list for help instead? Larger Jenkins instances also usually don't allow running any jobs on the master node. Just set up separate build nodes and only use the main Jenkins server as fancy UI and data storage. Then no builds have direct access to Jenkins config and data by escaping their $WORKSPACE. Regarding isolation, Jenkins Enterprise offers some solutions here (e.g. Folders/Folders Plus plugins that allows restricting build nodes (slaves) to certain authorized project folders, so you can have org1-slave and org2-slave, and nobody configuring org1 jobs can get them to execute on org2-slave, isolating temporary workspaces). 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Walter Kacynski created JENKINS-18659 NPE during Deleteing of Jobs Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 08/Jul/13 2:01 PM Description: I'm trying to delete all of my generated jobs but the process fails partway thru with a NPE: noformat java.lang.NullPointerException at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:617) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobFromPreviousBuild(GeneratorRun.java:647) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJob(GeneratorRun.java:637) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobs(GeneratorRun.java:584) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.deleteJobs(GeneratorRun.java:598) at org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl.doRun(GeneratorRun.java:250) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1575) at org.jenkinsci.plugins.jobgenerator.GeneratorRun.run(GeneratorRun.java:229) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) noformat Project: Jenkins Priority: Major Reporter: Walter Kacynski 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
[JIRA] [core] (JENKINS-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive
stephenconnolly created JENKINS-18660 10,000+ jobs tied to a label make Node index page unusably unresponsive Issue Type: Bug Assignee: stephenconnolly Components: core Created: 08/Jul/13 2:17 PM Description: When using an authorization strategy other than Unsecured or FullControlOncedoggedIn if there are 10,000+ jobs tied to labels, the tag cloud makes rendering the individual node screens seriously unresponsive as there are repeated access checks of read permission when counting the number of jobs with which to scale the tag cloud. It is not necessary to run the permission checks in order to return the count of jobs, and additionally it is not necessary to build a list of all jobs and then sort the list before filtering and then throwing away the list and retaining the count. A specialized count function with a denormalized loop should provide more usable performance... additionally it is questionable whether the tag cloud provides much utility for very large installations. Project: Jenkins Priority: Minor Reporter: 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-18657) Ability to show absolute date instead of relative
Ulli Hafner updated JENKINS-18657 Ability to show absolute date instead of relative Change By: Ulli Hafner (08/Jul/13 2:17 PM) Assignee: UlliHafner Component/s: core Component/s: analysis-core 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] [envinject] (JENKINS-18051) EnvInject - prepare environment to run - allow for environment variables in file path names
Geoffroy Jabouley
commented on JENKINS-18051
EnvInject - prepare environment to run - allow for environment variables in file path names
This works fine using Jenkins v1.520 and EnvInject v1.85.
Syntax is:
"${SCRIPTDIR}\job1-properties"
Be aware that:
1) If the file does not exist in the given path, EnvInject does not expand environment variables in the error message and will display something like "EnvInject - ERROR - The given properties file path '${SCRIPTDIR}\job1-properties' doesn't exist."
2) EnvInject seems to be sensible to casing of variable names. In your example, configuring the file path to "${scriptdir}\job1-properties" will result in an error (see 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] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
Walter Kacynski updated JENKINS-18377 Performance problem when listing many jobs Change By: Walter Kacynski (08/Jul/13 2:00 PM) Priority: Major Blocker 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] [concurrent-build] (JENKINS-13972) Concurrent matrix builds abort
Sarah Woodall edited a comment on JENKINS-13972 Concurrent matrix builds abort I am seeing this issue for the first time today after upgrading to Jenkins 1.509.1 from the previous LTS version. I have a matrix job which runs four different flavours of build on each of three platforms (Mac, Linux and Windows). My job configuration has not changed (and in fact no code has been checked in at all since the last good build I just started this build manually today to test Jenkins after the upgrade). Our master is on Windows, and there are two Windows executors on the same machine. There are two Mac executors on a Mac slave, and two Linux executors on a Linux slave. All of the builds in fact complete successfully, but the master reports that all four of the Windows builds "appear to be cancelled" and then that they "completed with result ABORTED". UPDATE: I have seen similar behaviour for other matrix jobs, including some that do not run on the slaves at all. I think it is a matrix job issue, not a master/slave issue. Changing the job configuration to make the builds run serially rather than in parallel appears to work round the problem. UPDATE: I believe this problem is Windows only. On my Windows installation, I had to configure all my matrix jobs to run serially, so as to work round this bug. I have now moved my Jenkins master to a Mac, and I have changed all my jobs again so that they do not run serially. So far, I have not seen the problem occur even once on the Mac. (On the Mac I have Jenkins 1.509.2 installed, but I don't think there is a fix for anything like this between 1.509.1 and 1.509.2, so it's more likely to be the change of platform that has caused the improvement.) 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] [role-strategy] (JENKINS-18377) Performance problem when listing many jobs
Walter Kacynski commented on JENKINS-18377 Performance problem when listing many jobs I linked JENKINS-17122 to see if it has any bearing on this 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] [core] (JENKINS-18571) clicking on build now button fires build twice for specific jobs
Jesse Glick updated JENKINS-18571 clicking on build now button fires build twice for specific jobs Change By: Jesse Glick (08/Jul/13 2:37 PM) Component/s: core Component/s: active-directory 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-18654) DependencyClassLoader#getTransitiveDependencies returns disabled plugins
dogfood commented on JENKINS-18654 DependencyClassLoader#getTransitiveDependencies returns disabled plugins Integrated in jenkins_main_trunk #2698 JENKINS-18654 document unit test (Revision bd87d70b3aa6cd8d13dbeae56b3c09fc425e2442) Result = SUCCESS Nicolas De Loof : bd87d70b3aa6cd8d13dbeae56b3c09fc425e2442 Files : test/src/test/java/hudson/ClassicPluginStrategyTest.java 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-18571) clicking on build now button fires build twice for specific jobs
Jesse Glick commented on JENKINS-18571 clicking on build now button fires build twice for specific jobs For what kind of jobs? (Multi-job, freestyle, etc.) 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-11102) Give the possibility to monitor all branches as Git plugin
Jesse Glick resolved JENKINS-11102 as Wont Fix Give the possibility to monitor all branches as Git plugin Have had various discussions with people including @sconnolly and the conclusion is that this is outside the scope of the SCM extension point as currently defined (and that it was a mistake for the Git plugin to try to implement it). Instead, there should be one job per branch, with either manual setup or other plugins being responsible for creating those jobs. Change By: Jesse Glick (08/Jul/13 2:46 PM) Status: InProgress Resolved Assignee: NicolasDeLoof JesseGlick 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] [mercurial] (JENKINS-13774) Provide option for cloning all branches with Mercurial SCM
Jesse Glick resolved JENKINS-13774 as Wont Fix Provide option for cloning all branches with Mercurial SCM After rereading the original request I think this is out of scope for the Mercurial plugin, which is designed around providing an SCM implementation with a checkout/update of a specific branch and a corresponding trigger/changelog/etc. What is being requested is really a distinct plugin, which may or may not want to depend on mercurial-plugin for some low-level functions: a Trigger combined with something else such as a Publisher which looks for any new changesets in a specified repository and produces a bundle as an artifact. Change By: Jesse Glick (08/Jul/13 2:57 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] [walldisplay] (JENKINS-18656) Hiding specific jobs from the Wall
Christian Pelster commented on JENKINS-18656 Hiding specific jobs from the Wall Hi, the walldisplay also works for individual views. You can create a view with the jobs you want to display the walldisplay link in the navigation on the left side always starts a walldisplay containing the jobs from the view where it's started from. See for example http://myadmin1.pelle.io/jenkins//plugin/jenkinswalldisplay/walldisplay.html?viewName=AlljenkinsUrl=http%3A%2F%2Fmyadmin1.pelle.io%2Fjenkins%2F and http://myadmin1.pelle.io/jenkins/view/Walldisplay%20/ 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-15846) Deadlock during Maven builds Parsing POM step
Jesse Glick resolved JENKINS-15846 as Fixed Deadlock during Maven builds Parsing POM step I guess that should fix the issue, right? Change By: Jesse Glick (08/Jul/13 3:07 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 -- 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] [dashboard-view] (JENKINS-15858) Jenkinks UI slow due to constant build record loading
Jesse Glick commented on JENKINS-15858 Jenkinks UI slow due to constant build record loading @vmassol you can try https://buildhive.cloudbees.com/job/jenkinsci/job/dashboard-view-plugin/18/org.jenkins-ci.plugins$dashboard-view/artifact/org.jenkins-ci.plugins/dashboard-view/2.7-SNAPSHOT/dashboard-view-2.7-SNAPSHOT.hpi if you want to still use the Dashboard View 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] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
Vincent Latombe commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step I have to double-check on my side, but if commons-logging is really fixed, that should be good 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] [cvs] (JENKINS-17931) cvs rlog files in /tmp are not deleted
Sascha Vogt commented on JENKINS-17931 cvs rlog files in /tmp are not deleted Hm, we're on LTS and currently have 1.509.1 on our Jenkins instance together with the latest 2.10-SNAPSHOT (due to 2 other issues we had with 2.9). Also I don't think we have 20k files in a single job (though I didn't count, so it might be possible). Are these files all in one directory? 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-18387) Jenkins sometimes fails to restart successfully
Matt Kraai commented on JENKINS-18387 Jenkins sometimes fails to restart successfully This problem appears to have happened again when I restarted Jenkins after downloading the .war file for 1.522. 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-15355) AdjunctManager: exception upon startup
Matt Kraai commented on JENKINS-15355 AdjunctManager: exception upon startup I see the same exception when starting Jenkins 1.522 if and only if the Maven Integration plugin is disabled. 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-18661) add support for creating Branches after a Release
Florian Rosenauer
created JENKINS-18661
add support for creating Branches after a Release
Issue Type:
New Feature
Assignee:
teilo
Components:
m2release
Created:
08/Jul/13 3:57 PM
Description:
On the create release page please add a checkbox and a new textfield, if both are set add the following strings at the end of the release command line:
release:branch -DbranchName=${textfieldvalue}
It would be great, if the default for the textfield could be "${project.artifactId}-${project.version}_BRANCH" with
all dots replaced by "_" (CVS does not allow dots)
"-SNAPSHOT" removed
Background: In our process we usually create a release for production and then we continue working in HEAD/trunk for the next release.
But usually we need a branch, either as release branch for fixing last minute bugs or as maintenance branch for bugfix releases prior to the next rollout.
So we have on allmost every release the manual work of creating a branch for many many multimodule builds. It would be great include that in the Jenkins release.
Project:
Jenkins
Priority:
Major
Reporter:
Florian Rosenauer
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-18660) 10,000+ jobs tied to a label make Node index page unusably unresponsive
dogfood commented on JENKINS-18660 10,000+ jobs tied to a label make Node index page unusably unresponsive Integrated in jenkins_main_trunk #2699 FIXED JENKINS-18660 Added dedicated denormalized counter function (Revision 5981ac4ed7b4b5c462a71ae186a133f7fe44e1a1) Result = SUCCESS Stephen Connolly : 5981ac4ed7b4b5c462a71ae186a133f7fe44e1a1 Files : core/src/main/java/hudson/model/Node.java core/src/main/java/hudson/model/Label.java 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] [nodeofflinenotification] (JENKINS-18541) Core 1.520 breaks nodeofflinenotification plugin
Ben Golding closed JENKINS-18541 as Fixed Core 1.520 breaks nodeofflinenotification plugin Change By: Ben Golding (08/Jul/13 4: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] [nodeofflinenotification] (JENKINS-18541) Core 1.520 breaks nodeofflinenotification plugin
Ben Golding resolved JENKINS-18541 as Fixed Core 1.520 breaks nodeofflinenotification plugin Resolved with update to: Jenkins 1.522 Ruby Runtime 0.12 Node Offline Notification Plugin still at 1.0.3 Notification functionality was tested working OK Change By: Ben Golding (08/Jul/13 4:26 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-17974) SVN plugin ignores --depth parameters
Andreas Scheucher commented on JENKINS-17974 SVN plugin ignores --depth parameters At time of posting the issue, it was 1.7. Currently 1.8. Yes, it seems to be overwritten. If one does an "svn up" on the command line, svn behaves the excpected way (,like configured during checkout). If it's done with the jenkins job configuration, it behaves like set in the drop-down, ignoring the set values. For sure, I was working around a not optimally set up SVN repository. But I am sure, this will happen to a lot of other users as well. Especially, if you need to set up continuous delivery for legacy projects, with a lot of svn:externals and not optimal repository structure. I am talking of several GB of source and configuration, which was fetched in my case and times of weeks for first attempts in reorganising the repository, to get better separation. 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-17974) SVN plugin ignores --depth parameters
Andreas Scheucher commented on JENKINS-17974 SVN plugin ignores --depth parameters thanks for you effort! 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-11102) Give the possibility to monitor all branches as Git plugin
Mike Wilson commented on JENKINS-11102 Give the possibility to monitor all branches as Git plugin Yes, since my last round looking at this topic I have also switched to the one-job-per-branch camp. This is what is most natural considering job status - different branches may have very little to do with each other and their statuses shouldn't be mixed up. But the topic in this ticket is still very relevant and might be appropriate to address in the generic Jenkins code. Either an offical new "super job" entity that can control automatic creation of other jobs, or some simple "clone this job for all branches" setting on ordinary jobs. Then SCM plugins would be required to report the active branches, which could be done at the same time as checking for new checkins. 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
Andre Winkelmann commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Hi, I am also using the plot plugin and got the same issue even with 1.522 (1.520 is the last one working). I am using Firefox (latest). Could it be that e.up is still not returning any value (at least that is what my short debugging showed). After digging up this site here http://www.redmine.org/issues/1636 maybe e.up should be replaced with Element.up(e, 'form'). Maybe someone with a development setup could try this out. I need to get it all set up first before I can try myself. 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] [copyartifact] (JENKINS-15764) Name of COPYARTIFACT_BUILD_NUMER_ variable is incorrectly documented
Daniel Beck commented on JENKINS-15764 Name of COPYARTIFACT_BUILD_NUMER_ variable is incorrectly documented They're not removed either, sequences of non-alpha characters are collapsed into one underscore. Try with project name abc123, it'll become COPYARTIFACT_BUILD_NUMBER_ABC_ 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] [copyartifact] (JENKINS-15764) Name of COPYARTIFACT_BUILD_NUMER_ variable is incorrectly documented
Daniel Beck edited a comment on JENKINS-15764 Name of COPYARTIFACT_BUILD_NUMER_ variable is incorrectly documented They're not removed either, sequences of non-alpha characters are collapsed into one underscore. Try with project name abc123, it'll become COPYARTIFACT_BUILD_NUMBER_ABC_ Since it says it replaces characters (plural) with underscore (singular) (instead of underscores), one could even say the description is correct 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] [copyartifact] (JENKINS-18662) Add a exclude file(s) field to copy artifacts plugin
Vanessa McCallum created JENKINS-18662 Add a exclude file(s) field to copy artifacts plugin Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: copyartifact Created: 08/Jul/13 5:45 PM Description: I want to be able to exclude certain files when I copy artifacts for example: Artifacts to copy: bin/*.dll Exclude Artifacts: useless.dll Due Date: 15/Jul/13 12:00 AM Fix Versions: current Project: Jenkins Labels: plugin artifact copyartifact Priority: Major Reporter: Vanessa McCallum 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] [copyartifact] (JENKINS-18662) Add a exclude file(s) field to CopyArtifact plugin
Vanessa McCallum updated JENKINS-18662 Add a exclude file(s) field to CopyArtifact plugin Change By: Vanessa McCallum (08/Jul/13 5:46 PM) Summary: Addaexcludefile(s)fieldto copyartifacts CopyArtifact 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Sylvain Benner assigned JENKINS-18659 to Sylvain Benner NPE during Deleteing of Jobs Change By: Sylvain Benner (08/Jul/13 5:54 PM) Assignee: SylvainBenner 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Sylvain Benner commented on JENKINS-18659 NPE during Deleteing of Jobs It it possible to write down your job hierarchy ? The deletion of jobs is not an easy task. Currently it relies on the build history, if it is incomplete or wiped I think it can produce NPEs, I'll check into this. Thank you for the report. 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] [sauce-ondemand] (JENKINS-18000) Sauce on Demand setting incorrect pass/fail status
Scott Argenziano commented on JENKINS-18000 Sauce on Demand setting incorrect pass/fail status Will do. The update hasn't hit CloudBees as of yet. Will let you know as soon as I get it installed. 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Walter Kacynski edited a comment on JENKINS-18659 NPE during Deleteing of Jobs The structure is: SND-Deploy-AA_Generate - (template) SND-Deploy-AA_Template = SND-Deploy-AA_Stream_DO_NOT_RUN and SND-Deploy-[JOBS A, B, C... x 100] Only one the concrete jobs had a job history. The others had never been run. 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] [jobgenerator] (JENKINS-18659) NPE during Deleteing of Jobs
Walter Kacynski commented on JENKINS-18659 NPE during Deleteing of Jobs The structure is: SND-Deploy-AA_Generate (template) SND-Deploy-AA_Template = SND-Deploy-AA_Stream_DO_NOT_RUN and SND-DeployJOBS A, B, C... x 100 Only one the concrete jobs had a job history. The others had never been run. 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-18571) clicking on build now button fires build twice for specific jobs
irfan sayed commented on JENKINS-18571 clicking on build now button fires build twice for specific jobs job type is freestyle all the jobs are configured with parameterized build i have upgraded jenkins to 1.521 and issue seems resolved. however, please verify regards irfan 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.
