[JIRA] [git-client] (JENKINS-20684) Support for .netrc file limited by strict file format requirement
SCM/JIRA link daemon resolved JENKINS-20684 as Fixed Support for .netrc file limited by strict file format requirement Change By: SCM/JIRA link daemon (26/Nov/13 8:24 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] [git-client] (JENKINS-20684) Support for .netrc file limited by strict file format requirement
SCM/JIRA link daemon commented on JENKINS-20684 Support for .netrc file limited by strict file format requirement Code changed in jenkins User: Florian Zschocke Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java src/main/java/org/jenkinsci/plugins/gitclient/Netrc.java src/test/java/org/jenkinsci/plugins/gitclient/NetrcTest.java src/test/resources/netrc_1.in src/test/resources/netrc_1a.in src/test/resources/netrc_2.in http://jenkins-ci.org/commit/git-client-plugin/3430d9270beeabedfab130e5d987bcf26c336748 Log: FIXED JENKINS-20684 Parser for .netrc file format This path implements a parser for the .netrc file supporting various formats. It is not restricted to having a machine definition on a single line but can parse any valid format. The one exception is that it does not cope with `macdef` definitions. handle `macdef` definitons in the netrc file to the parser. Anything following a `macdef` keyword will be ignored up to the next empty line. This message is automatically generated by JIRA. 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] [thinBackup] (JENKINS-20761) Trigger Jenkins job after backup
Kristofer Hansson Aspman created JENKINS-20761 Trigger Jenkins job after backup Issue Type: New Feature Assignee: Thomas Fürer Components: thinBackup Created: 26/Nov/13 8:39 AM Description: Personally, I think it would be really handy if there was an option to trigger a Jenkins job when backups are done. For instance, let's say that I want to create a report and archive this together with the created backup-files to some other server. Currently, I do this in a job that is scheduled to run 30 minutes after ThinBackup is scheduled. In short, I think it would be nicer if the job could be linked to ThinBackup explicitly Project: Jenkins Priority: Minor Reporter: Kristofer Hansson Aspman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20677) HTTP URLs with variables are not supported when using credentials
Florian Zschocke commented on JENKINS-20677 HTTP URLs with variables are not supported when using credentials I have a fix for this in my local copy but haven't refined it more. When you have some time, you could have a look at it and let me know if you think it would be enough to create a pull request for it. https://github.com/fzs/git-client-plugin/compare/1.4.x...url-with-variable This message is automatically generated by JIRA. 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-20640) Jenkins become very slow and had 'proxy error'
Chris Z commented on JENKINS-20640 Jenkins become very slow and had proxy error Hi, I've got similar issue. In monitoring you can see peeks of active threads. When I get screenshoot (when jenkins unfreez) i will attach 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] [git] (JENKINS-19994) Unable to delete workspace
Michael Glauche commented on JENKINS-19994 Unable to delete workspace Same problem here, with windows 2008 r2 server, git plugin 2.0 with JGit implementation. This message is automatically generated by JIRA. 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] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
Janne Enberg commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction I have this same issue, I migrated jobs from our old build server running 1.527 to a new server running 1.539 by copying the jobs folders over. Then I proceeded to check which of the plugins were really in use and installed a handful of those, and eventually managed to get all of the old data warnings to disappear. Then a while later, these warnings started to appear. It doesn't seem to cause any issues, nor can I find a fix for it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1
Onno van der Straaten commented on JENKINS-11933 Subversion plugin doesnt probably work correctly with svn server version 1.7.1 Marked it as fixed why don't ya. This things is not fixed. It just doesn't work. When I logon to Jenkins server as Jenkins I can do svn ls svn+ssh://myuser@myhost/somerepos/somepathinrepos. No problem. When we add that url to jenkins it will fail with above message. Support for Subversion isn't what it used to be. Maybe we need to switch to Git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jacoco] (JENKINS-20754) Jacoco coverage reports built from Jenkins are inconsistent.
Joel Costigliola commented on JENKINS-20754 Jacoco coverage reports built from Jenkins are inconsistent. Hi Ogi, Jenkins JaCoCo plugin version was 1.0.14 Joel This message is automatically generated by JIRA. 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] [build-flow] (JENKINS-20762) Build-Flow graph don't show when using buildgraph-view plug-in
Saran Niyakit created JENKINS-20762 Build-Flow graph dont show when using buildgraph-view plug-in Issue Type: Bug Assignee: berthelot nicolas Components: build-flow Created: 26/Nov/13 11:17 AM Description: For lasted version 0.10 which has dependency “buildgraph-view” plug-in I install buildgraph-view then trigged run jobs. Jobs run fine except graph don't show. Project: Jenkins Priority: Major Reporter: Saran Niyakit This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Paul Grove commented on JENKINS-20630 Jenkins fails to start I have tried running Jenkins 1.541 on Windows 8.1 with Java 7 (b45) and it crashes Java. I then tried to deploy inside Tomcat 7, Tomcat starts but when I drop the jenkins war into tomcat it again causes Java to crash, strange thing is Java was not core dumping. To see if this was a Java 7 issue I tried on a different Windows machine running Windows 7 and Java 6. But Java crashed again at least this time Java 6 gave a core dump, which I have attached. I then tried the latest LTS version and this works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Paul Grove updated JENKINS-20630 Jenkins fails to start Java core dump from Jenkins start crash Change By: Paul Grove (26/Nov/13 11:27 AM) Attachment: hs_err_pid35184.log This message is automatically generated by JIRA. 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] [build-flow] (JENKINS-20763) Build-Flow graph disappeared
Saran Niyakit created JENKINS-20763 Build-Flow graph disappeared Issue Type: Bug Assignee: berthelot nicolas Components: build-flow Created: 26/Nov/13 11:29 AM Description: From Issue JENKINS-20762 I downgrade to previous version 0.8 everything work fine including graph when jobs is running. When I come back to previous jobs that finished the graph disappeared. In the case I’m not sure about how long build flow plug-in keeps the graph. Project: Jenkins Priority: Major Reporter: Saran Niyakit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20619) multijob started disabled plugins
André Söderlind resolved JENKINS-20619 as Fixed multijob started disabled plugins Bugfix implemented: Put back check if the future value is null do not add sub-job. @Plugin owners: please review code modification (only 5 lines of code ) Bugfix committed to the branch: https://github.com/andresoderlind/tikal-multijob-plugin/tree/ISSUE-J-20619 Change By: André Söderlind (26/Nov/13 12:09 PM) Status: Open Resolved Assignee: AndréSöderlind 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-20764) Failing upgrade from 1.533 to 1.541
Peter Miklosko created JENKINS-20764 Failing upgrade from 1.533 to 1.541 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 26/Nov/13 12:30 PM Description: I did system update to get jenkins upgraded `sudo apt-get upgrade jenkins sudo service jenkins stop sudo service jenkins start` Which resulted in (stacktrace bellow) looking at config file I seen that version field value did not changed from 1.533 to 1.541 ( I tried manually overwrite it but without success jenkins will fail again on start-up) hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.WebAppMain$3.run(WebAppMain.java:234) Caused by: org.jvnet.hudson.reactor.ReactorException: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:907) at jenkins.model.Jenkins.init(Jenkins.java:806) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: java.io.IOException: Unable to read /var/lib/jenkins/config.xml at hudson.XmlFile.unmarshal(XmlFile.java:169) at jenkins.model.Jenkins$17.run(Jenkins.java:2541) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:896) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: com.thoughtworks.xstream.converters.ConversionException: -1 : -1 Debugging information message : -1 cause-exception : java.lang.ArrayIndexOutOfBoundsException cause-message : -1 class : hudson.model.Hudson required-type : hudson.model.Hudson converter-type : hudson.util.RobustReflectionConverter path: /hudson/disabledAdministrativeMonitors line number : 3 version : not available --- 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 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 hudson.XmlFile.unmarshal(XmlFile.java:165) ... 9 more Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77) at java.util.HashMap.putMapEntries(HashMap.java:511) at java.util.HashMap.putAll(HashMap.java:784) at com.thoughtworks.xstream.core.util.OrderRetainingMap.init(OrderRetainingMap.java:36) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldOrNull(FieldDictionary.java:113) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.getFieldOrNull(PureJavaReflectionProvider.java:186) at hudson.util.RobustReflectionConverter.fieldDefinedInClass(RobustReflectionConverter.java:328) at
[JIRA] [core] (JENKINS-20739) UI elements listing descriptor-based items need to apply DescriptorVisibilityFilter
Oleg Nenashev commented on JENKINS-20739 UI elements listing descriptor-based items need to apply DescriptorVisibilityFilter +1. I suppose it will be a very useful feature together with Extension Filter Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-11933) Subversion plugin doesn't probably work correctly with svn server version 1.7.1
centic commented on JENKINS-11933 Subversion plugin doesnt probably work correctly with svn server version 1.7.1 hmm, it seems to work for many people, and works for me also with svn+ssh, so I would suggest you create a new bug-entry together with information about which version of Jenkins and which version of Subversion Plugin you are using and also add some logfile of jenkins output, ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-20765) Jenkins 1.541 make java hangs on windows
yann collette created JENKINS-20765 Jenkins 1.541 make java hangs on windows Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 26/Nov/13 1:12 PM Description: I upgraded from jenkins 1.538 to 1.541 and when Jenkins restarted, java hangs. Their is no more informations than a windows popup saying that java.exe has hanged. Each time I restart jenkins, the same hangs happen. Environment: Windows Server 2007 SP1 Project: Jenkins Priority: Major Reporter: yann collette This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-20765) Jenkins 1.541 make java hangs on windows
Hal Deadman commented on JENKINS-20765 Jenkins 1.541 make java hangs on windows Are you sure it is hung or did it crash/core dump? - This is probably a duplicate of JENKINS-20630 This message is automatically generated by JIRA. 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-17695) error 500 after Delete Project
Jeff smith commented on JENKINS-17695 error 500 after Delete Project FWIW, we are seeing this error with Windows version 1.466.2, and do not have the Build Pipeline 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] [ec2] (JENKINS-20766) Support new EC2 instance types
Daniel Spilker created JENKINS-20766 Support new EC2 instance types Issue Type: Improvement Affects Versions: current Assignee: Daniel Spilker Components: ec2 Created: 26/Nov/13 1:23 PM Description: It is not possible to launch C3 instances. See http://aws.amazon.com/about-aws/whats-new/2013/11/14/announcing-new-amazon-ec2-compute-optimized-instances/ for details about new instance types. Project: Jenkins Labels: plugin Priority: Major Reporter: Daniel Spilker This message is automatically generated by JIRA. 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] [ec2] (JENKINS-20766) Support new EC2 instance types
Daniel Spilker commented on JENKINS-20766 Support new EC2 instance types Pull request: https://github.com/jenkinsci/ec2-plugin/pull/70 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Mac Cer
commented on JENKINS-14508
Default pre-send script in Jenkins Configuration
Hey, is it intended behavior to have the $DEFAULT_PRESEND_SCRIPT be expanded after a Job that had it included in its configuration ran?
Cause that's what happens with my Jenkins 1.509.4 and Version 2.36 of this plugin.
I find this a little inconvenient. What if I want to make changes to my script? Every Job that I have set up with "$DEFAULT_PRESEND_SCRIPT" in its configuration would have the old version of that script expanded in its configuration after it ran at least once. I would have to go through every job config and change it back to "$DEFAULT_PRESEND_SCRIPT" to have to load the newest version of that script.
This expansion happens every time. I tried writing it as $DEFAULT_PRESEND_SCRIPT and ${DEFAULT_PRESEND_SCRIPT}. Both times it gets expanded.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-20765) Jenkins 1.541 make java hangs on windows
yann collette commented on JENKINS-20765 Jenkins 1.541 make java hangs on windows Yes, you're right. I was focused on v1.541 so, I missed this bug report. You can classify my bug report as a duplicate of 20630. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-17929) Fail to run 'groovysh' in CLI due to insufficient permission
Dmitry Danilson commented on JENKINS-17929 Fail to run groovysh in CLI due to insufficient permission I've sent a pull request intended to fix this issue: https://github.com/jenkinsci/jenkins/pull/1035 . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Alex Earl commented on JENKINS-14508 Default pre-send script in Jenkins Configuration Can you post a config.xml before and after? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-14508) Default pre-send script in Jenkins Configuration
Alex Earl commented on JENKINS-14508 Default pre-send script in Jenkins Configuration Also, please file a new issue since the issue you are describing is different from the one this one is describing. This message is automatically generated by JIRA. 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-20767) Git plugin 2.0: Git polling causes builds even if no changes
Roman Prots created JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 26/Nov/13 2:08 PM Description: http://stackoverflow.com/questions/20007854/jenkins-scm-triggering-constant-builds-despite-no-change http://jenkins-ci.361315.n4.nabble.com/git-polling-builds-every-2-minutes-repository-isn-t-changing-why-td4679352.html Project: Jenkins Priority: Critical Reporter: Roman Prots This message is automatically generated by JIRA. 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] [extreme-feedback] (JENKINS-20768) Comparison method violates its general contract exception
Tobias Tobiasen
created JENKINS-20768
Comparison method violates its general contract exception
Issue Type:
Bug
Assignee:
emanuelez
Components:
extreme-feedback
Created:
26/Nov/13 2:09 PM
Description:
It get the stacktrace below sometimes. I have not found a clear pattern in when it happens.
However I have seen similar errors in other code running on JDK 7.
I am running 1.2.2
To me it looks like the selectComparator.compare in XFPanelView is wrong. It contains.
// if build is null, show it on bottom of its class
if ( buildA == null || buildB == null ){
return ( buildA == null ) ? 1 : 0;
}
// if building atm - show build on top of its class
if ( buildA.isBuilding() || buildB.isBuilding() ){
return ( buildA.isBuilding() ) ? 0 : 1;
}
It does not follow the contract that says:
"The implementor must ensure that sgn(compare(x, y)) == -sgn(compare(y, x)) for all x and y. "
It should be changed to:
// if build is null, show it on bottom of its class
if ( buildA == null || buildB == null ){
if (buildA == buildB) {
return 0;
}
return ( buildA == null ) ? 1 : 0;
}
// if building atm - show build on top of its class
if ( buildA.isBuilding() || buildB.isBuilding() ){
if (buildA.isBuilding() == buildB.isBuilding()) {
return 0;
} }
return ( buildA.isBuilding() ) ? 0 : 1;
}
Status Code: 500
Exception: org.apache.commons.jelly.JellyTagException: file:/D:/JenkinsHome/plugins/xfpanel/WEB-INF/classes/maps/hudson/plugin/xfpanel/XFPanelView/maindisplay.jelly:23:53: j:invoke method sort threw exception: Comparison method violates its general contract!
Stacktrace:
javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: file:/D:/JenkinsHome/plugins/xfpanel/WEB-INF/classes/maps/hudson/plugin/xfpanel/XFPanelView/maindisplay.jelly:23:53: j:invoke method sort threw exception: Comparison method violates its general contract!
at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:728)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at
[JIRA] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
Javier Delgado stopped work on JENKINS-20599 Handle several testpoints TAP result file Change By: Javier Delgado (26/Nov/13 2:37 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20770) Default pre-send script variable gets expanded inside the job confguration
Mac Cer
created JENKINS-20770
Default pre-send script variable gets expanded inside the job confguration
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Attachments:
config.xml, config_before_job_is_run.xml
Components:
email-ext
Created:
26/Nov/13 2:38 PM
Description:
I have a groovy script set in the global configuration for this email-ext plugin as a "Default Pre-send Script". Set it up as: ${SCRIPT, template="scan-email.groovy"}
I add this script to my job configurations as: $DEFAULT_PRESEND_SCRIPT in the field "Pre-send Script"
The script will get called at the appropriate time when the job runs. But after the job has run, inside the jobs configuration, there will no longer be the $DEFAULT_PRESEND_SCRIPT I originally entered. That field will contain the scripts contents. Aka, it expanded the $DEFAULT_PRESEND_SCRIPT variable with the content of the script.
Now, a setup like this will still work, but if I happen to edit this script, this job will not get the most recent changes I made to that script as it will just continue to use what is entered in its configuration.
Expected behavior:
I would have expected that $DEFAULT_PRESEND_SCRIPT stays as it is inside the jobs configuration. Pretty much like $DEFAULT_CONTENT does.
Please find attached a sample job configuration and notice the difference before and after that job has run.
Project:
Jenkins
Labels:
plugin
email-ext
Priority:
Minor
Reporter:
Mac Cer
This message is automatically generated by JIRA.
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-20769) Failed to execute command Pipe.EOF
Roman Prots created JENKINS-20769 Failed to execute command Pipe.EOF Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/13 2:37 PM Description: Errors from log, occurs from time to time: Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle SEVERE: Failed to execute command Pipe.EOF(49) (channel qa3) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Nov 26, 2013 4:31:58 PM hudson.remoting.Channel$2 handle SEVERE: This command is created here Command Pipe.EOF(49) created at at hudson.remoting.Command.init(Command.java:67) at hudson.remoting.Command.init(Command.java:50) at hudson.remoting.ProxyWriter$EOF.init(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:101) at java.lang.ref.Finalizer.access$100(Finalizer.java:32) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:190) Project: Jenkins Priority: Major Reporter: Roman Prots This message is automatically generated by JIRA. 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] [extreme-feedback] (JENKINS-20768) Comparison method violates its general contract exception
Tobias Tobiasen commented on JENKINS-20768 Comparison method violates its general contract exception A workaround is to add "-Djava.util.Arrays.useLegacyMergeSort=true" to the JVM at startup. See http://stackoverflow.com/questions/7849539/comparison-method-violates-its-general-contract-java-7-only http://stackoverflow.com/questions/15893487/compile-in-java-6-run-in-7-how-to-specify-uselegacymergesort This message is automatically generated by JIRA. 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-20771) Fresh install of 1.541 on CentOS
Aram Mirzadeh created JENKINS-20771 Fresh install of 1.541 on CentOS Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 26/Nov/13 2:43 PM Description: After a fresh rpm install using yum, starting jenkins and going to Maintenance - Configure None of the options are editable, and on the bottom of the page you get: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.541.jar!/jenkins/model/Jenkins/configure.jelly:59:84: st:include org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.541.jar!/lib/form/section.jelly:48:21: d:invokeBody com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Daniel Beck created JENKINS-20772 Apply error screens dont work Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/13 3:00 PM Description: The error screens shown for invalid configurations after pressing 'Apply' don't work. Steps to reproduce: 1. Create a freestyle job with a unique, valid name 3. Clear the name in the config screen 4. Press 'Apply' Expected result: Error message shown Actual result: Huge, empty dialog with title 'Error' shown (error screen seems to appear, but is immediately removed) Environment: Jenkins 1.509.4 Jenkins 1.532.1 RC1 Firefox 17.0.10 ESR Project: Jenkins Labels: lts-candidate Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20772) 'Apply' error screens don't work
Daniel Beck commented on JENKINS-20772 Apply error screens dont work There are several issues about the errors that (don't) appear in response to some action (JENKINS-17401, JENKINS-13287, JENKINS-19037, possibly others) but none seem to cover the problem that the error screen is completely useless because it doesn't show the error (e.g. stacktrace). This message is automatically generated by JIRA. 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] [ec2] (JENKINS-20766) Support new EC2 instance types
Daniel Spilker assigned JENKINS-20766 to Francis Upton Support new EC2 instance types Change By: Daniel Spilker (26/Nov/13 3:07 PM) Assignee: DanielSpilker FrancisUpton This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Markus Eisenmann commented on JENKINS-20630 Jenkins fails to start In my opinion, all newer releases since 1.540 should be rejected - because, it's a major bug. Okay - as I know - "only" Windows-users are affected; But, as long as this problem exists, further weekly builds should be marked as unstable (or a similiar meaning). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
Hugo Ares commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit This is fixed in 2.11.0 which is not released yet. Robert just created version 2.11.0-beta-11 so I guess we can expect a release soon. 1https://github.com/jenkinsci/gerrit-trigger-plugin/tree/gerrit-trigger-2.11.0-beta-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] [gui] (JENKINS-20773) Config loading takes longer after few days of tomcat restart
rsemburakkiannan created JENKINS-20773 Config loading takes longer after few days of tomcat restart Issue Type: Bug Assignee: Unassigned Components: gui Created: 26/Nov/13 3:16 PM Description: Currently we are using Jenkins 1.539 version and tomcat version - apache-tomcat-7.0.40. If we click configure, it takes atleast 30 secs to 60 secs - few days after tomcat restart. It become worse after a week. So it requires to restart often to make the config loading better. Any inputs? Project: Jenkins Priority: Major Reporter: rsemburakkiannan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-10709) multiple builds are triggered for one change in Gerrit
rsandell commented on JENKINS-10709 multiple builds are triggered for one change in Gerrit Yepp, I just released 2.11.0-beta-1, it should be available in the experimental update center soon. And I am looking for brave beta testers to try it 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] [git] (JENKINS-20774) Git remotes not updated after updating credentials
Daniel Spilker created JENKINS-20774 Git remotes not updated after updating credentials Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 26/Nov/13 3:18 PM Description: We are using git over HTTPS with username/password credentials as introducted with version 2.0 of the Git plugin. After updating passwords, the git remote in the workspace is not updated. This causes any git commands which run from shell steps and interact with remotes to fail. To reproduce this, create a free-style job, use any Git repo with protected HTTPS access and use Jenkins managed credentials. Create a shell step executing 'git remote -v'. Run the job, change the password for the credentials, run the job again and compare the output. The remote has not been updated with the new password. Environment: Jenkins 1.537, Git Plugin 2.0, Git Client Plugin 1.4.6, Credentials Plugin 1.9.3 Project: Jenkins Labels: plugin Priority: Major Reporter: Daniel Spilker This message is automatically generated by JIRA. 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] [delivery-pipeline] (JENKINS-20756) Dont work with Folders plugin
Patrik Boström resolved JENKINS-20756 as Fixed Dont work with Folders plugin Change By: Patrik Boström (26/Nov/13 3:30 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] [core] (JENKINS-20764) Failing upgrade from 1.533 to 1.541
Peter Miklosko commented on JENKINS-20764 Failing upgrade from 1.533 to 1.541 So is there any easy way to fix 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] [matrix-combinations-parameter] (JENKINS-20553) matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME
bayram duezguen updated JENKINS-20553 matrix-job: Slashes (/) not allowed in $P4CLIENT / $JOB_NAME Change By: bayram duezguen (26/Nov/13 4:14 PM) Component/s: matrix-combinations-parameter This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-8597) Deal with matrix builds better
Oleg Nenashev commented on JENKINS-8597 Deal with matrix builds better Hello, there will be a priority-sorter-2.0 soon. So the plugin is being supported now by Magnus Sandberg. So please feel free to submit issues and bugs. Regarding this bug, it is possible to integrate it into the incoming release. Would you like to create a pull request? I can do it as well, but it may take some time due to a big task queue. This message is automatically generated by JIRA. 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] [prioritysorter] (JENKINS-8597) Deal with matrix builds better
Oleg Nenashev edited a comment on JENKINS-8597 Deal with matrix builds better Hello, there will be a priority-sorter-2.0 soon. In the current state the plugin is being supported by Magnus Sandberg. So please feel free to submit issues and bugs. Regarding this bug, it is possible to integrate it into the incoming release. Would you like to create a pull request? I can do it as well, but it may take some time due to a big task queue. This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Stephen Barrett commented on JENKINS-20630 Jenkins fails to start Have same exact issue just had to roll back to 1.534 This message is automatically generated by JIRA. 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] [credentials] (JENKINS-20775) Build Pipeline Parameters - Password text visible
mujtaba mohammed created JENKINS-20775 Build Pipeline Parameters - Password text visible Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: credentials Created: 26/Nov/13 4:33 PM Description: We have used password parameters for some builds. The password parameters are visible in clear text in the pipeline, when we configure a build pipeline and select the following options: Show pipeline parameters in project headers OR Show pipeline parameters in revision box Environment: Windows 7 Project: Jenkins Priority: Major Reporter: mujtaba mohammed This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Stephen Barrett updated JENKINS-20630 Jenkins fails to start Change By: Stephen Barrett (26/Nov/13 4:32 PM) Attachment: hs_err_pid4584.log Attachment: hs_err_pid5660.log Attachment: hs_err_pid5960.log This message is automatically generated by JIRA. 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-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
Kevin Burge commented on JENKINS-20243 Upgrade to Jenkins GIT plugin 2.0 from 1.5 brakes Gerrit triggered builds I'm running in to the same issue. This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2. This is a significant problem for us. I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client). This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Stephen Barrett updated JENKINS-20630 Jenkins fails to start Change By: Stephen Barrett (26/Nov/13 4:34 PM) Environment: MicrosoftWindowsServer2003R2MicrosoftWindows2008serverw/Tomcat WinXP MicrosoftWindowsXP SP3 MicrosoftWindows7x64SP1 This message is automatically generated by JIRA. 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-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
Kevin Burge edited a comment on JENKINS-20243 Upgrade to Jenkins GIT plugin 2.0 from 1.5 brakes Gerrit triggered builds I'm running in to the same issue (integration with Gerrit Trigger). This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2. This is a significant problem for us. I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client). This message is automatically generated by JIRA. 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-20243) Upgrade to 'Jenkins GIT plugin' 2.0 from 1.5 brakes Gerrit triggered builds
Kevin Burge edited a comment on JENKINS-20243 Upgrade to Jenkins GIT plugin 2.0 from 1.5 brakes Gerrit triggered builds I'm running in to the same issue (integration with Gerrit Trigger). This doesn't prevent checkout, it just causes Jenkins to clear the workspace so that my build completely starts over, which can take 45 minutes, when it could take 1 or 2. This is a significant problem for us. I'd rather not downgrade as I would have to reconfigure many jobs to specify the ref location (like I did when I upgraded from the older git client). Fetching changes from the remote Git repository Fetching upstream changes from git://repo.dev.systemware.com/xds Checking out Revision 407f296d95c4626e65647e50573f6a2ad08b0eef (master) ERROR: Unable to retrieve changeset hudson.plugins.git.GitException: Failed to find parent id. at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getFirstParent(GerritTriggerBuildChooser.java:156) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.prevBuildForChangelog(GerritTriggerBuildChooser.java:117) at hudson.plugins.git.GitSCM.computeChangeLog(GitSCM.java:935) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:875) at hudson.model.AbstractProject.checkout(AbstractProject.java:1376) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: java.lang.UnsupportedOperationException at org.jenkinsci.plugins.gitclient.RemoteGitImpl.getRepository(RemoteGitImpl.java:187) at com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser.getFirstParent(GerritTriggerBuildChooser.java:146) ... 11 more Cleaning workspace This message is automatically generated by JIRA. 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] [credentials] (JENKINS-20775) Build Pipeline Parameters - Password text visible
mujtaba mohammed updated JENKINS-20775 Build Pipeline Parameters - Password text visible Change By: mujtaba mohammed (26/Nov/13 4:41 PM) Attachment: example_pipeline.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [xfpanel] (JENKINS-20768) Comparison method violates its general contract exception
emanuelez updated JENKINS-20768 Comparison method violates its general contract exception Change By: emanuelez (26/Nov/13 5:34 PM) Assignee: emanuelez Component/s: xfpanel Component/s: extreme-feedback This message is automatically generated by JIRA. 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] [thinBackup] (JENKINS-20761) Trigger Jenkins job after backup
Thomas Fürer commented on JENKINS-20761 Trigger Jenkins job after backup nice idea, i will think about it for version 2.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-15936) ajax menus not working below chromium
evernat commented on JENKINS-15936 ajax menus not working below chromium Is it reproduced with recent versions of Jenkins and of Chromium? This message is automatically generated by JIRA. 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-20764) Failing upgrade from 1.533 to 1.541
Gemini A commented on JENKINS-20764 Failing upgrade from 1.533 to 1.541 Hi Peter, I think 1.539 works. http://mirrors.jenkins-ci.org/war/1.539/ Try that for now until Jenkins is able to release a working build. This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Gemini A commented on JENKINS-20630 Jenkins fails to start @Markus, if the info on JENKINS-20764 is correct, it says Environment: Ubuntu 13, Java 1.6 then it means that the issue affects both Windows and Linux users. https://issues.jenkins-ci.org/browse/JENKINS-20764 This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Shannon Newbold commented on JENKINS-20630 Jenkins fails to start I tried 1.541 and had the same issues. I rolled back to 1.539 and everything seems to be working again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Diogo Campos commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Still having problems with this in 1.6.5 It seems that the SkipTestException raised is being captured and turned into a (Tunneled)InterruptedException. In this example I'm publishing junit tests (2 files) and boosttest (0 files): [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 2 test report file(s) were found with the pattern 'PATTERN' relative to 'PATH' for the testing framework 'JUnit'. [xUnit] [INFO] - Processing BoostTest-1.x (default) [xUnit] [INFO] - [BoostTest-1.x (default)] - No test report file(s) were found with the pattern 'PATTERN' relative to 'PATH' for the testing framework 'BoostTest-1.x (default)'. Did you enter a pattern relative to the correct directory? Did you generate the result report(s) for 'BoostTest-1.x (default)'? [xUnit] [WARNING] - No test reports found for the metric 'BoostTest' with the resolved pattern 'PATTERN'. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.InterruptedException at hudson.FilePath.act(FilePath.java:908) at hudson.FilePath.act(FilePath.java:890) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:185) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:118) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.FilePath$TunneledInterruptedException at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2427) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:722) Caused by: org.jenkinsci.plugins.xunit.SkipTestException at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:167) at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:38) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2425) ... 10 more Job XML: xunit plugin="xunit@1.65" types JUnitType patternPATTERN/pattern skipNoTestFilesfalse/skipNoTestFiles failIfNotNewfalse/failIfNotNew deleteOutputFilestrue/deleteOutputFiles stopProcessingIfErrortrue/stopProcessingIfError /JUnitType BoostTestJunitHudsonTestType patternPATTERN/pattern skipNoTestFilestrue/skipNoTestFiles failIfNotNewfalse/failIfNotNew deleteOutputFilestrue/deleteOutputFiles stopProcessingIfErrortrue/stopProcessingIfError /BoostTestJunitHudsonTestType /types thresholds org.jenkinsci.plugins.xunit.threshold.FailedThreshold unstableThreshold0/unstableThreshold unstableNewThreshold0/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.FailedThreshold /thresholds thresholdMode1/thresholdMode /xunit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Diogo Campos edited a comment on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Still having problems with this in 1.65 It seems that the SkipTestException raised is being captured and turned into a (Tunneled)InterruptedException. In this example I'm publishing junit tests (2 files) and boosttest (0 files): [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 2 test report file(s) were found with the pattern 'PATTERN' relative to 'PATH' for the testing framework 'JUnit'. [xUnit] [INFO] - Processing BoostTest-1.x (default) [xUnit] [INFO] - [BoostTest-1.x (default)] - No test report file(s) were found with the pattern 'PATTERN' relative to 'PATH' for the testing framework 'BoostTest-1.x (default)'. Did you enter a pattern relative to the correct directory? Did you generate the result report(s) for 'BoostTest-1.x (default)'? [xUnit] [WARNING] - No test reports found for the metric 'BoostTest' with the resolved pattern 'PATTERN'. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.InterruptedException at hudson.FilePath.act(FilePath.java:908) at hudson.FilePath.act(FilePath.java:890) at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:185) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:118) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.FilePath$TunneledInterruptedException at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2427) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:722) Caused by: org.jenkinsci.plugins.xunit.SkipTestException at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:167) at com.thalesgroup.hudson.plugins.xunit.service.XUnitTransformer.invoke(XUnitTransformer.java:38) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2425) ... 10 more Job XML: xunit plugin="xunit@1.65" types JUnitType patternPATTERN/pattern skipNoTestFilesfalse/skipNoTestFiles failIfNotNewfalse/failIfNotNew deleteOutputFilestrue/deleteOutputFiles stopProcessingIfErrortrue/stopProcessingIfError /JUnitType BoostTestJunitHudsonTestType patternPATTERN/pattern skipNoTestFilestrue/skipNoTestFiles failIfNotNewfalse/failIfNotNew deleteOutputFilestrue/deleteOutputFiles stopProcessingIfErrortrue/stopProcessingIfError /BoostTestJunitHudsonTestType /types thresholds org.jenkinsci.plugins.xunit.threshold.FailedThreshold unstableThreshold0/unstableThreshold unstableNewThreshold0/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.FailedThreshold /thresholds thresholdMode1/thresholdMode /xunit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on
[JIRA] [gui] (JENKINS-15936) ajax menus not working below chromium
H.-Dirk Schmitt commented on JENKINS-15936 ajax menus not working below chromium Seems to work now This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Matt Kraai commented on JENKINS-20630 Jenkins fails to start I used git bisect to determine that 7d2a3b3f9c96f3ab950d84781da5cf903ca4c4be was the first commit that had 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-20630) Jenkins fails to start
Oleg Nenashev assigned JENKINS-20630 to Kohsuke Kawaguchi Jenkins fails to start Change By: Oleg Nenashev (26/Nov/13 6:39 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Oleg Nenashev commented on JENKINS-20630 Jenkins fails to start Thank you for analysis, Matt You are right, the error has been caused by Kernel32 call in https://github.com/jenkinsci/jenkins/commit/7d2a3b3f9c96f3ab950d84781da5cf903ca4c4be This message is automatically generated by JIRA. 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] [xfpanel] (JENKINS-20749) Some jobs are missing in Available jobs multichoice window
Tobias Tobiasen commented on JENKINS-20749 Some jobs are missing in Available jobs multichoice window I have also seen this in v1.2.2 with jenkins 1.513. This message is automatically generated by JIRA. 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] [xfpanel] (JENKINS-16094) Better Job filtering capabilities - make use of JobViewsFilterPlugin
Tobias Tobiasen edited a comment on JENKINS-16094 Better Job filtering capabilities - make use of JobViewsFilterPlugin Excellent idea. I need this too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xfpanel] (JENKINS-16094) Better Job filtering capabilities - make use of JobViewsFilterPlugin
Tobias Tobiasen commented on JENKINS-16094 Better Job filtering capabilities - make use of JobViewsFilterPlugin Excelent idea. I need this too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Roland Whitley commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Is there a work around for this issue, or is a code release required in order for this to work. I am getting the same error when trying to connect to a repository in a job configuration. This message is automatically generated by JIRA. 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-20757) jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541
Daniel Beck commented on JENKINS-20757 jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541 That stack trace only shows warnings. Is there nothing else? This message is automatically generated by JIRA. 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-20757) jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541
warren brown commented on JENKINS-20757 jenkins startup dies quickly ostensibly due to maven problem in 1.540 and 1.541 Correct. There is nothing else. This message is automatically generated by JIRA. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani commented on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot There does appear to be a pending pull request: JENKINS-17885 This message is automatically generated by JIRA. 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] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Mark Ottaviani edited a comment on JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Looking forward to seeing this fixed. Same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Mark Ottaviani commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. There does appear to be a pending pull request: JENKINS-17885 This message is automatically generated by JIRA. 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] [maven2] (JENKINS-20725) maven build creates files that Windows cannot backup
Joe Knudsen commented on JENKINS-20725 maven build creates files that Windows cannot backup After looking closer I see that the slashes are Unix forward slashes in for the path to the symbolic link. Two directories above is a SYMLINK for lastStable and that uses the back slashes. I am guessing the Maven plugin needs to start using the forward slashes on Windows. I did check and the files exist if I use the back slashes. This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
SCM/JIRA link daemon commented on JENKINS-20630 Jenkins fails to start Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/util/jna/Kernel32Utils.java http://jenkins-ci.org/commit/jenkins/0438e4f7a2142c1d18652aa7bcf8c3d72443f6af Log: FIXED JENKINS-20630 The size is in wchar_t, not in bytes This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
SCM/JIRA link daemon resolved JENKINS-20630 as Fixed Jenkins fails to start Change By: SCM/JIRA link daemon (26/Nov/13 7:38 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] [core] (JENKINS-20630) Jenkins fails to start
Kohsuke Kawaguchi commented on JENKINS-20630 Jenkins fails to start Folks, my sincere apologies. This message is automatically generated by JIRA. 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-20675) Java platform binary has stopped working message appears when starting Jenkins 1.540
Kohsuke Kawaguchi resolved JENKINS-20675 as Duplicate Java platform binary has stopped working message appears when starting Jenkins 1.540 Same issue as JENKINS-20630 Change By: Kohsuke Kawaguchi (26/Nov/13 7:39 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-20765) Jenkins 1.541 make java hangs on windows
Kohsuke Kawaguchi resolved JENKINS-20765 as Duplicate Jenkins 1.541 make java hangs on windows Change By: Kohsuke Kawaguchi (26/Nov/13 7:41 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20630) Jenkins fails to start
Kohsuke Kawaguchi commented on JENKINS-20630 Jenkins fails to start The fix will be in 1.542. This message is automatically generated by JIRA. 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-20630) Jenkins fails to start
Stephen Barrett commented on JENKINS-20630 Jenkins fails to start Thanks for the fix. No hard feelings Kohsuke, everyone makes bugs We should figure out how it got past testing though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-15936) ajax menus not working below chromium
evernat resolved JENKINS-15936 as Fixed ajax menus not working below chromium Ok, thanks. So resolving as fixed. Please reopen if needed. Change By: evernat (26/Nov/13 8:06 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] [update-center] (JENKINS-15921) 1.492 Jenkins Debian packages not found
evernat resolved JENKINS-15921 as Fixed 1.492 Jenkins Debian packages not found When clicking on the link, it works. So resolving as fixed. It may have been a transient issue. Change By: evernat (26/Nov/13 8:08 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] [extension-filter] (JENKINS-20776) Add validation of classnames to global configuration
Oleg Nenashev created JENKINS-20776 Add validation of classnames to global configuration Issue Type: Improvement Assignee: Unassigned Components: extension-filter Created: 26/Nov/13 8:08 PM Description: It would be great to have on-the-flight validation of class names in fqcn field of the form Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. 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-20764) Failing upgrade from 1.533 to 1.541
Peter Miklosko commented on JENKINS-20764 Failing upgrade from 1.533 to 1.541 Thanks Gemini, but I guess I will have to wait for next release since I do not use war but system driven updates This message is automatically generated by JIRA. 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] [maven2] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (26/Nov/13 8:24 PM) Summary: mavenbuildcreates symlinkd filesthatWindows cannotbackup OSdoesnotunderstand This message is automatically generated by JIRA. 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-17314) Rebuild Job using GET method
Kevin Thieling commented on JENKINS-17314 Rebuild Job using GET method Did upgrading the Dashboard View plugin resolve this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xfpanel] (JENKINS-16094) Better Job filtering capabilities - make use of JobViewsFilterPlugin
Oleg Nenashev commented on JENKINS-16094 Better Job filtering capabilities - make use of JobViewsFilterPlugin BTW, you can just copy configs/filtering implementation from ListView class in the core. Then you will automatically get support of existing extensions like "View job filters". This message is automatically generated by JIRA. 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] [job-restrictions] (JENKINS-20281) Add option for restriction of manual build invocation
Oleg Nenashev resolved JENKINS-20281 as Fixed Add option for restriction of manual build invocation Added this feature to job-restrictions-0.2.1 Change By: Oleg Nenashev (26/Nov/13 8:51 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] [job-restrictions] (JENKINS-20281) Add option for restriction of manual build invocation
Oleg Nenashev closed JENKINS-20281 as Fixed Add option for restriction of manual build invocation Change By: Oleg Nenashev (26/Nov/13 8:51 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] [custom-tools] (JENKINS-19177) improper injection of the VERSION variables into the build environment
Oleg Nenashev resolved JENKINS-19177 as Fixed improper injection of the VERSION variables into the build environment Change By: Oleg Nenashev (26/Nov/13 8:53 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] [xfpanel] (JENKINS-20749) Some jobs are missing in Available jobs multichoice window
emanuelez assigned JENKINS-20749 to Julien RENAUT Some jobs are missing in Available jobs multichoice window Change By: emanuelez (26/Nov/13 8:54 PM) Assignee: emanuelez JulienRENAUT This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-18583) [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs
Oleg Nenashev resolved JENKINS-18583 as Fixed [MultipleSCM integration] - Perforce SCM does not work in MultipleSCMs Updated the issue's status Change By: Oleg Nenashev (26/Nov/13 8:59 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] [core] (JENKINS-19776) Deadlock of AsyncFutureImpl.get() during massive submission of distributed jobs
Oleg Nenashev resolved JENKINS-19776 as Cannot Reproduce Deadlock of AsyncFutureImpl.get() during massive submission of distributed jobs I cannot reproduce the issue since update to 1.509.4 If anybody experiences it, please reopen the issue. Change By: Oleg Nenashev (26/Nov/13 9:01 PM) Status: InProgress Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. 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] [mailer] (JENKINS-19433) ownership plugin does not find owner's email - although it's defined in his/her profile
Oleg Nenashev updated JENKINS-19433 ownership plugin does not find owners email - although its defined in his/her profile Reassigned the issue to mailer plugin Change By: Oleg Nenashev (26/Nov/13 9:14 PM) Issue Type: Bug Improvement Component/s: mailer This message is automatically generated by JIRA. 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-20772) 'Apply' error screens don't work
Steven Christou commented on JENKINS-20772 Apply error screens dont work This is also an issue if you rename it to anything other than the original namen and click the apply button. This message is automatically generated by JIRA. 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-15030) Cannot find help file of 'Pattern' field
Oleg Nenashev updated JENKINS-15030 Cannot find help file of Pattern field Change By: Oleg Nenashev (26/Nov/13 9:19 PM) Summary: Cannotfindhelpfileof Patron Pattern field Description: Errorwhenshowinghelpfileofthe Patron Pattern fieldinmanage-rolespageoftheplugin:ERROR:Failedtoloadhelpfile:NotFound This message is automatically generated by JIRA. 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.
