[JIRA] [conditional-buildstep] (JENKINS-20543) error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper
paul hinds commented on JENKINS-20543 error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper +1 Jenkins 1.509.4 conditional-buildstep 1.3.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-20543) error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper
paul hinds commented on JENKINS-20543 error on delete job - java.lang.NoSuchMethodError: org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuildStepHelper Hi, are you saying 1.3.3 fixed the bug? and delte now works or just that after reset the delete happens? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-folder] (JENKINS-20715) dynamically update folder icon using its direct children state
Régis Desgroppes created JENKINS-20715 dynamically update folder icon using its direct children state Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder Created: 22/Nov/13 9:05 AM Description: Hi, Currently the folder icon is static: always blue, not animated. Could you please consider setting it dynamically according to its direct children: color based on worst child build status: red, yellow, "blue" (green with GreenBalls plugin), etc. animated when 1+ child build is running. Thanks in advance. Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20664) radiator-view plugin stop work after upgrade to 1.539
Kamal Mettananda commented on JENKINS-20664 radiator-view plugin stop work after upgrade to 1.539 We do experience the 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] [shiningpanda] (JENKINS-20716) Virtualenv builder fails to create virtualenv
Marius Gedminas created JENKINS-20716 Virtualenv builder fails to create virtualenv Issue Type: Bug Assignee: Unassigned Components: shiningpanda Created: 22/Nov/13 9:26 AM Description: I'm trying to add a build slave to perform Windows builds. I've installed the ShiningPanda plugin (version 0.20) and set up a Virtualenv builder in a job. The build fails with Fetching changes from the remote Git repository Fetching upstream changes from https://github.com/mgedmin/check-manifest.git Checking out Revision 9fc0aaae12f57bdb4ca795ded6c6f0a685dc2cd4 (origin/master) Cleaning workspace Resetting working tree check-manifest-on-windows $ cmd.exe /C '"c:\python27\python.exe c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py --distribute c:\buildslave\shiningpanda\jobs\765322bd\virtualenvs\d41d8cd9 exit %%ERRORLEVEL%%"' PYTHONHOME is set. You must activate the virtualenv before using it New python executable in c:\buildslave\shiningpanda\jobs\765322bd\virtualenvs\d41d8cd9\Scripts\python.exe Installing distribute. Complete output from command c:\buildslave\shinin...9\Scripts\python.exe -c "#!python \"\"\"Bootstra... sys.exit(main()) ": Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.34.tar.gz Extracting in c:\users\mg\appdata\local\temp\3\tmpy3wx2w Traceback (most recent call last): File "string", line 546, in module File "string", line 543, in main File "string", line 77, in _install File "string", line 485, in _extractall File "c:\python27\Lib\tarfile.py", line 2084, in extract self._extract_member(tarinfo, os.path.join(path, tarinfo.name)) File "c:\python27\Lib\tarfile.py", line 2160, in _extract_member self.makefile(tarinfo, targetpath) File "c:\python27\Lib\tarfile.py", line 2201, in makefile copyfileobj(source, target) File "c:\python27\Lib\tarfile.py", line 266, in copyfileobj shutil.copyfileobj(src, dst) File "c:\python27\Lib\shutil.py", line 49, in copyfileobj buf = fsrc.read(length) File "c:\python27\Lib\tarfile.py", line 819, in read buf += self.fileobj.read(size - len(buf)) File "c:\python27\Lib\tarfile.py", line 737, in read return self.readnormal(size) File "c:\python27\Lib\tarfile.py", line 746, in readnormal return self.fileobj.read(size) File "c:\python27\Lib\gzip.py", line 261, in read self._read(readsize) File "c:\python27\Lib\gzip.py", line 308, in _read self._read_eof() File "c:\python27\Lib\gzip.py", line 347, in _read_eof hex(self.crc))) IOError: CRC check failed 0x4b42a280 != 0xec007959L ...Installing distribute...done. Traceback (most recent call last): File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 5016, in module main() File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 3418, in main no_pip=options.no_pip) File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 3527, in create_environment search_dirs=search_dirs, never_download=never_download) File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 3055, in install_distribute search_dirs=search_dirs, never_download=never_download) File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 3022, in _install_req cwd=cwd) File "c:\buildslave\shiningpanda\jobs\765322bd\virtualenv.py", line 3496, in call_subprocess % (cmd_desc, proc.returncode)) OSError: Command c:\buildslave\shinin...9\Scripts\python.exe -c "#!python \"\"\"Bootstra... sys.exit(main()) " failed with error code 1 Build step 'Virtualenv Builder' marked build as failure Environment: Windows Server 2012 build slave Project: Jenkins Labels: plugin windows Priority: Major
[JIRA] [gui] (JENKINS-20698) A lot of JellyTagExceptions in the jenkins.log
Hallvard Nygård commented on JENKINS-20698 A lot of JellyTagExceptions in the jenkins.log Got this exception when a job is running. It appears everywhere in GUI where the build status is (status under the menu on the frontpage, executor status in configure, etc). I think it might be related to the plugin Gerrit trigger that adds information to the build status. Got this exception on both Linux and Windows Jenkins server. Downgraded to 1.502 (From 1.539) on the Windows Jenkins server and the problem seems to have disappeared. On the Linux server it appeared after a upgrade last week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
movavi team commented on JENKINS-20622 In the prompts to enter the password it says something else Jenkins ver. 1.540 - not fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
movavi team reopened JENKINS-20622 In the prompts to enter the password it says something else Change By: movavi team (22/Nov/13 9:45 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20717) Add pipelines to view dymacally with regexp
Andreas Rehn created JENKINS-20717 Add pipelines to view dymacally with regexp Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: delivery-pipeline Created: 22/Nov/13 9:46 AM Description: I propose an alternative dynamic way of adding pipelines to the view by using regexps. E.g. "^Build-(.)-myProject$" would match Build-serviceX-myProject, Build-serviceY-myProject etc, making it easy to add new pipelines without reconfiguring the view. A capturing group (.) could be used to automatically set a decent pipeline name in the view, e.g. serviceX and serviceY. Project: Jenkins Priority: Major Reporter: Andreas Rehn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shiningpanda] (JENKINS-20716) Virtualenv builder fails to create virtualenv
Marius Gedminas commented on JENKINS-20716 Virtualenv builder fails to create virtualenv I see that pip install on this machine (a Rackspace Could VM) also throws hash mismatch errors left and right, but occasionally succeeds. This might be a problem on a lower level. Still, I don't think ShiningPanda should ask for virtualenv --distribute, given that distribute was merged back into upstream setuptools. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-20193) disk usage plugin seems to scan /
Croesus Kall commented on JENKINS-20193 disk usage plugin seems to scan / I am encountering this problem also. Searching through job config files, I see that a great many of them have "/" set as the path. But this only applies to "modules" i.e. the config.xml files that apply to module builds. In addition, this also only applies to very old jobs, that used to run on a slave that no longer exists. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-20698) A lot of JellyTagExceptions in the jenkins.log
Sigbjørn Tvedt commented on JENKINS-20698 A lot of JellyTagExceptions in the jenkins.log It seems that this error only occurs when the browser is using Norwegian as the preferred language and the CI server is building a project. A temporary workaround is to force the browser to use English as the preferred language. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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
Eric Han commented on JENKINS-20630 Jenkins fails to start Same with me, and I tried multiple approaches on windows 7 64, the last works version is 1.539. Is there any workaround for changing the jenkins or JVM settings? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Victor Antonovich commented on JENKINS-20622 In the prompts to enter the password it says something else Please note in 1.540 russian translation has vulgar slang inclusion in project "Status" word translation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Victor Antonovich updated JENKINS-20622 In the prompts to enter the password it says something else Vulgar slang inclusion in russian translation. Change By: Victor Antonovich (22/Nov/13 10:26 AM) Attachment: screenshot_russian.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] [startup-trigger-plugin] (JENKINS-20718) Documentation and help for startup-trigger-plugin missing
Danny Staple created JENKINS-20718 Documentation and help for startup-trigger-plugin missing Issue Type: Improvement Affects Versions: current Assignee: ashlux Components: startup-trigger-plugin Created: 22/Nov/13 10:37 AM Description: There is no documentation for this - no help for the plugin control in the job and no readme on the github folder. It would be great to have some simple docs on its usage, and covering things like what happens with a job not tied to slave node, or when tied to multiple nodes. Useful documentation here (sifted from the comments): "This plugin requires a jenkins restart (it will not work using install without restart)." "A tickbox will appear in the trigger section of each job, tick this to trigger it when the node starts". "When a job is tied to node labels with multiple nodes, it will be triggered when each node is started" (not sure about this - but the correct logic could be put here) Project: Jenkins Priority: Minor Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10540) Maven build aborted without cause
Adam H commented on JENKINS-10540 Maven build aborted without cause Seeing similar error message on Jenkins 1.532 and Maven 3.0.5: Nov 22, 2013 8:29:23 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Channel to Maven [java, -Dmaven.repo.basedir=file:///folder/mvn.repo/, -cp, /jenkins/gotburh08p/WPF.REDHAT.OPTIMIZE/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/usr/local/share/java/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /usr/local/share/java/apache-maven-3.0.5, /jenkins/hostname/servername/.jenkins/war/WEB-INF/lib/remoting-2.32.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar, 41611] java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-20719) groovy.lang.MissingPropertyException Exception evaluating property 'size' for java.util.ArrayList when using IBM Java 6
Gabriel Lopez
created JENKINS-20719
groovy.lang.MissingPropertyException Exception evaluating property size for java.util.ArrayList when using IBM Java 6
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
22/Nov/13 10:53 AM
Description:
When using IBM Java 6, the following error happens when trying to see a build result.
The bug seems to be the following line in hudson.plugins.parameterizedtrigger.BuildInfoExporterAction.sumary.groovy: if (projects.size 0) {
This is related to this: http://jira.codehaus.org/browse/GROOVY-4094 , where it is mentioned that should be size(), not size.
Stack trace:
Caused by: groovy.lang.MissingPropertyException: Exception evaluating property 'size' for java.util.ArrayList, Reason: groovy.lang.MissingPropertyException: No such property: size for class: hudson.model.FreeStyleProject
Possible solutions: name, scm
at org.codehaus.groovy.runtime.DefaultGroovyMethods.getAt(DefaultGroovyMethods.java:6810)
at groovy.lang.MetaClassImpl$7.getProperty(MetaClassImpl.java:1712)
at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.getProperty(GetEffectivePojoPropertySite.java:61)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGetProperty(AbstractCallSite.java:227)
at hudson.plugins.parameterizedtrigger.BuildInfoExporterAction.summary.run(summary.groovy:30)
at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:69)
at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
... 96 more
Project:
Jenkins
Priority:
Major
Reporter:
Gabriel Lopez
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [startup-trigger-plugin] (JENKINS-20718) Add Documentation and help for startup-trigger-plugin
Danny Staple updated JENKINS-20718 Add Documentation and help for startup-trigger-plugin Change By: Danny Staple (22/Nov/13 10:55 AM) Summary: Add Documentationandhelpforstartup-trigger-plugin missing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-10540) Maven build aborted without cause
Adam H edited a comment on JENKINS-10540 Maven build aborted without cause Seeing similar error message on Jenkins 1.532 and Maven 3.0.5: Nov 22, 2013 8:29:23 AM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Channel to Maven [java, -Dmaven.repo.basedir=file:///folder/mvn.repo/, -cp, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.4.jar:/usr/local/share/java/apache-maven-3.0.5/boot/plexus-classworlds-2.4.jar, org.jvnet.hudson.maven3.agent.Maven3Main, /usr/local/share/java/apache-maven-3.0.5, /jenkins/hostname/servername/.jenkins/war/WEB-INF/lib/remoting-2.32.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.4.jar, /jenkins/hostname/servername/.jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar, 41611] java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2596) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1316) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20291) Server configuration cannot be opened if new server name has specific character.
SCM/JIRA link daemon commented on JENKINS-20291 Server configuration cannot be opened if new server name has specific character. Code changed in jenkins User: rinrinne Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java gerrithudsontrigger/src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement/index.jelly http://jenkins-ci.org/commit/gerrit-trigger-plugin/63fe5497798d024b2362f5562108afd87fd1aefa Log: Use encoded string for server name If string including special character for URL (e.g. /,?,#) or multibyte character is given as server name, stapler cannot handle it correctly. This patch provides encoded server name as url string. And jelly has something wrong so fix it. Fix for JENKINS-20291 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodeofflinenotification] (JENKINS-20720) Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin
lata kopalle created JENKINS-20720 Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin Issue Type: Bug Assignee: Unassigned Components: nodeofflinenotification Created: 22/Nov/13 11:46 AM Description: Hi We could connect to our slaves via ssh smoothly, until we installed the nodeofflinenotification plugin. Once the plugin is installed, *the connection is not established, *there is no slave log at $JENKINS_HOME/logs/slaves/ created, *and a spinning wheel when trying to access the slave log from jenkins console, the log is not created anyway. There were a bunch of plugins that were installed on our instance since the last successful slave connect, the new plugin which is causing this failure to connect is the nodeofflinenotification v 1.0.3 https://wiki.jenkins-ci.org/display/JENKINS/Node+Offline+Notification+Plugin I've uninstalled the plugin and restarted our Jenkins, the slaves re-connect smoothly again. I've categorized this as a 'Major' priority not for the functionality of the plugin but for the time and effort it could result in in identifying why the slaves are not connecting via ssh. Thanks Lata Environment: Jenkins Master: Linux x86_64 Jenkins Slave: Linux x86_64 Jenkins Version: 1.509.3 (LTS) nodeofflinenotification Plugin: 1.0.3 java version: jdk1.6.0_32 Project: Jenkins Priority: Major Reporter: lata kopalle This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20721) Triggered by includes culprits
Patrik Boström created JENKINS-20721 Triggered by includes culprits Issue Type: Bug Assignee: Unassigned Components: delivery-pipeline Created: 22/Nov/13 11:53 AM Description: Triggered by includes culprits and not just the people involved in the specific pipeline instance (version). Project: Jenkins Priority: Major Reporter: Patrik Boström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20721) Triggered by includes culprits
Patrik Boström assigned JENKINS-20721 to Patrik Boström Triggered by includes culprits Change By: Patrik Boström (22/Nov/13 11:57 AM) Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20721) Triggered by includes culprits
Patrik Boström resolved JENKINS-20721 as Fixed Triggered by includes culprits Fixed https://github.com/Diabol/delivery-pipeline-plugin/commit/fae77a0e3e6628f84c3fbbfc6b6bdf56c55dc9fb Change By: Patrik Boström (22/Nov/13 12:01 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-20722) Unable to start Jenkins 540 using java7u45x64b
Fernando Rosado Altamirano created JENKINS-20722 Unable to start Jenkins 540 using java7u45x64b Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 22/Nov/13 12:11 PM Description: I have updated the server using : 1.540 and java 1.7u45(x86 and x64) on a windows environment. (validated Windows 7 and 2008 ) After launch jenkins, java runtime finish with a crash message. Environment: Windows x64 (2008 and 7) Project: Jenkins Priority: Critical Reporter: Fernando Rosado Altamirano This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20722) Unable to start Jenkins 540 using java7u45x64b
Fernando Rosado Altamirano commented on JENKINS-20722 Unable to start Jenkins 540 using java7u45x64b Also tested with Java 7 update 40 x86 and Java 7 u 45 x85. Both runtimes also fails Using Jenkins 1.539 works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20599) Handle several testpoints TAP result file
Javier Delgado started work on JENKINS-20599 Handle several testpoints TAP result file Change By: Javier Delgado (22/Nov/13 12:37 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-20590) New batch build step
Javier Delgado stopped work on JENKINS-20590 New batch build step Change By: Javier Delgado (22/Nov/13 12:38 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] [core] (JENKINS-20453) Build History disappear after reload config from disk, restart/start application, and restart managed server
Queenie Chow commented on JENKINS-20453 Build History disappear after reload config from disk, restart/start application, and restart managed server Yes, the build history are on the file system. Jenkins did not removing anything, just not visible from the Jenkins console. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17460) Error occurs viewing build history on some builds
Bruce Coveny updated JENKINS-17460 Error occurs viewing build history on some builds Change By: Bruce Coveny (22/Nov/13 1:16 PM) Environment: JENKINSWARVERSION1.509-1. 529 539 WINDOWSSERVER2008R2ENTERPRISEAMDOPTERON(TM)PROCESSOR61362.4GHZ(2PROCESSORS)4.0GBRAM64-BITOPERATIONSYSTEMWEBSPHEREAPPLICATIONSERVER8.5.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Arne-Christian Blystad commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server Hello, sorry for the late answer. No, the zip could not be extracted manually, I get the following error: jenkins@build:~/Jenkins Backup$ unzip BACKUPSET_2013-10-10_03-00_.zip Archive: BACKUPSET_2013-10-10_03-00_.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of BACKUPSET_2013-10-10_03-00_.zip or BACKUPSET_2013-10-10_03-00_.zip.zip, and cannot find BACKUPSET_2013-10-10_03-00_.zip.ZIP, period. The files are located on the local drive at /var/lib/jenkins/Jenkins Backup/. Would it be possible to provide non-zipped updates? I've installed Sun Java 7 1.7.0_45 on the server and I'll come back with results during next weeks backups. I've uploaded the crash report to: http://pastebin.com/siQCLvwV This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-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 (22/Nov/13 1:20 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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
f v commented on JENKINS-20675 Java platform binary has stopped working message appears when starting Jenkins 1.540 As a newbie spent a while before finding this post. Thanks! went back to previous rev and launches OK. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Mark Waite reopened JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace This was working correctly in Git plugin 1.5.0 so long as the command line implementation was used. It no longer works correctly in Git plugin 2.0, even when the command line implementation is used. Some portion of the Git plugin or Git client plugin seems to be opening a pack file and not closing it. Change By: Mark Waite (22/Nov/13 1:58 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite commented on JENKINS-19994 Unable to delete workspace The bug JENKINS-15103 may be a duplicate of this bug, even though that bug was fixed in 1.5.0, since it has reappeared in 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] [git] (JENKINS-15103) jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace
Mark Waite edited a comment on JENKINS-15103 jenkins slave process does not let go of .git\objects\pack\*.pack file causeing Unable to delete when wiping workspace This was working correctly in Git plugin 1.5.0 so long as the command line implementation was used. It no longer works correctly in Git plugin 2.0, even when the command line implementation is used. Some portion of the Git plugin or Git client plugin seems to be opening a pack file and not closing it. Refer to JENKINS-19994 for a bug which may be a duplicate of this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20723) Add an option to include or exclude disabled jobs in the 'Unstable jobs' widget.
Tim De Backer created JENKINS-20723 Add an option to include or exclude disabled jobs in the Unstable jobs widget. Issue Type: Improvement Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 22/Nov/13 2:08 PM Description: In a situation with many jobs (where the list of unstable jobs is particularly handy) there are often a few disabled jobs as well. The current 'Unstable jobs' widget handles disabled jobs like any other. Disabled jobs are thus included in the list if their last build failed or was unstable. At this moment, the user can already choose to include or exclude the (non-failed) unstable jobs, using a simple checkbox. A similar checkbox should be added to let the user include or exclude (failed/unstable) disabled jobs. Project: Jenkins Priority: Major Reporter: Tim De Backer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Support multi-configuration (matrix) jobs
Marc Abramowitz updated JENKINS-20706 Support multi-configuration (matrix) jobs Change By: Marc Abramowitz (22/Nov/13 2:30 PM) Summary: Supportmulti-configuration (matrix) jobs withuser-definedaxes Labels: matrix multi-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] [other] (JENKINS-20622) In the prompts to enter the password it says something else
Victor Antonovich edited a comment on JENKINS-20622 In the prompts to enter the password it says something else Attached screenshot of vulgar slang inclusion in russian translation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [console-column] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Adam Ocsvari updated JENKINS-20724 MultiJob project console output link is broken if job is opened from a view Change By: Adam Ocsvari (22/Nov/13 2:41 PM) Description: OpenthepageofaMultiJobprojectfromaview.YouwillgetthesamepageinthedifferentURL-s:jenkinsserver:8080/job/My_Jobs_name_MultiJob/ 10/console jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/Butbecauseoftherelativeurls,thelinktotheMultiJob-sconsoleoutputisalsodifferent:jenkinsserver:8080/view/Unit_tests/view/Unit_tests/job/My_Jobs_name_MultiJob/10/consolejenkinsserver:8080/job/My_Jobs_name_MultiJob/10/consoleAsitsshowedabove,thelinkfortheconsoleoutputcontainstheviewnametwice.Thecorrectiscontainstheviewnameonceownotatall:jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/10/consolejenkinsserver:8080/job/My_Jobs_name_MultiJob/10/console This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [console-column] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Adam Ocsvari created JENKINS-20724 MultiJob project console output link is broken if job is opened from a view Issue Type: Bug Affects Versions: current Assignee: jieryn Components: console-column Created: 22/Nov/13 2:40 PM Description: Open the page of a MultiJob project from a view. You will get the same page in the different URL-s: jenkinsserver:8080/job/My_Jobs_name_MultiJob/10/console jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/ But because of the relative urls, the link to the MultiJob-s console output is also different: jenkinsserver:8080/view/Unit_tests/view/Unit_tests/job/My_Jobs_name_MultiJob/10/console jenkinsserver:8080/job/My_Jobs_name_MultiJob/10/console As it's showed above, the link for the console output contains the view name twice. The correct is contains the view name once ow not at all: jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/10/console jenkinsserver:8080/job/My_Jobs_name_MultiJob/10/console Environment: Windows 7, x64, running as a service Project: Jenkins Labels: consoleoutput console Priority: Minor Reporter: Adam Ocsvari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [console-column] (JENKINS-20724) MultiJob project console output link is broken if job is opened from a view
Adam Ocsvari updated JENKINS-20724 MultiJob project console output link is broken if job is opened from a view Change By: Adam Ocsvari (22/Nov/13 2:42 PM) Description: OpenthepageofaMultiJobprojectfromaview.YouwillgetthesamepageinthedifferentURL-s:jenkinsserver:8080/job/My_Jobs_name_MultiJob/jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/Butbecauseoftherelativeurls,thelinktotheMultiJob-sconsoleoutputisalsodifferent:jenkinsserver:8080/view/Unit_tests/view/Unit_tests/job/My_Jobs_name_MultiJob/10/consolejenkinsserver:8080/job/My_Jobs_name_MultiJob/10/consoleAsitsshowedabove,thelinkfortheconsoleoutputcontainstheviewnametwice.Thecorrect iscontains shloudcontain theviewnameonceownotatall:jenkinsserver:8080/view/Unit_tests/job/My_Jobs_name_MultiJob/10/consolejenkinsserver:8080/job/My_Jobs_name_MultiJob/10/console This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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 created JENKINS-20725 maven build creates files that Windows cannot backup Issue Type: Bug Assignee: Unassigned Components: maven2 Created: 22/Nov/13 2:46 PM Description: After upgrading to 1.509.4 our Maven builds create files that Windows cannot backup. The UI seems to working. The files are SYMLINKD one for each module. The none maven builds seem fine. The files are under the jobs/project name/builds/buildnumber or builddate directory. 11/19/2013 04:47 PMSYMLINKD us.mn.state.education.sfin.automation$sfi n-post-processor [../../modules/us.mn.state.education.sfin.automation$sfin-post- processor/builds/2013-11-19_16-40-46] 4 File(s) 3,881,255 bytes 34 Dir(s) 20,236,365,824 bytes free E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56type us.mn.state.education.sfin$confi gs Access is denied. E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56cd us.mn.state.education.sfin$configs The filename, directory name, or volume label syntax is incorrect. E:\jenkins\.jenkins\jobs\SFIN-OB\builds\56 Environment: Windows 2008 R2 Jenkins 1.509.4 Project: Jenkins Priority: Major Reporter: Joe Knudsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20395) Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server
Thomas Fürer commented on JENKINS-20395 Corrupt ZIP backup sets and thinBackup crashing the whole Jenkins server thanks for the update, is the corrupt file a 0 byte file? my own jenkins running on ubuntu 13.10 and jenkins 1.531 is working fine, i will try to test the system with java 1.6.x now. curretnly I cannot reproduce the problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [recipe] (JENKINS-20726) JobIngredient does not handle folders
Jesse Glick created JENKINS-20726 JobIngredient does not handle folders Issue Type: Bug Assignee: Unassigned Components: recipe Created: 22/Nov/13 2:56 PM Description: Uses Job.getName when creating an ingredient, and cook only supports adding the job to Jenkins top level. Project: Jenkins Labels: folders Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [recipe] (JENKINS-20727) Cannot recreate job
Jesse Glick created JENKINS-20727 Cannot recreate job Issue Type: Bug Assignee: Unassigned Components: recipe Created: 22/Nov/13 2:58 PM Description: For JobIngredient, the import wizard just shows an error if you already have a job of that name. (But lets you proceed, and then rewrites the existing job, losing its history.) Should show only a warning, then let you update the configuration in place, retaining history. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [recipe] (JENKINS-20727) Cannot recreate job
Jesse Glick assigned JENKINS-20727 to Jesse Glick Cannot recreate job Change By: Jesse Glick (22/Nov/13 2:58 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [recipe] (JENKINS-20727) Cannot recreate job
Jesse Glick started work on JENKINS-20727 Cannot recreate job Change By: Jesse Glick (22/Nov/13 2:58 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Jeanjean LaGuigne commented on JENKINS-17608 Test Link plugin, show the test results in the category notes Hi Bruno, How are you? Sorry for taking so long before answering, i finished my studies this summer, and i was in holiday. But now I'am back to work ^^ Are you ok to reopen the 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] [cloudbees-folder] (JENKINS-20715) dynamically update folder icon using its direct children state
Jesse Glick assigned JENKINS-20715 to Unassigned dynamically update folder icon using its direct children state If you get Jenkins Enterprise by CloudBees, the Folders Plus plugin offers an Aggregate status of items in the folder option for the folder icon which does just this. Change By: Jesse Glick (22/Nov/13 3:07 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mask-passwords] (JENKINS-20728) Mask-Passwords-Plugin corrupts passwords with IE11
oliver schmidt created JENKINS-20728 Mask-Passwords-Plugin corrupts passwords with IE11 Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: mask-passwords Created: 22/Nov/13 3:10 PM Description: We setup Jenkins with the "Mask Passwords Plugin". We setup jobs with masked password parameters. If we open such a job with IE11, the masked password fields are shown empty. The job//config.xml in the filesystem shows the correct masked entry. A different browser, e.g. IE9/Chrome show a masked password. If a save the job with IE11, a corrupted (shorter) masked password is stored (I checked in the config.xml). If the job is executed, it fails - the password parameter contains an incorrect value. This occurs with IE11, IE10 was fine, IE9 is fine, Chrome 31 is fine. Environment: redhat linux Project: Jenkins Priority: Major Reporter: oliver schmidt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20569) Polling with excluded regions don't prevent job triggered
Nicolas De Loof commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered This happens due to remote polling. This is also the case with 1.x when remote polling is set By nature, remote polling only can compare remote HEAD with last build sha1, not consider commit 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] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Bruno P. Kinoshita commented on JENKINS-17608 Test Link plugin, show the test results in the category notes Hi Jeanjean, I'm fine and you? Are you ok to reopen the issue ? Yup, send it in, and let's see if we can fix it before x-mas Thanks! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20569) Polling with excluded regions don't prevent job triggered
Joe Mihalich commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered I don't understand that. This feature was working fine in the 1.4.0 git plugin. Something must have been broken. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20722) Unable to start Jenkins 540 using java7u45x64b
Fernando Rosado Altamirano edited a comment on JENKINS-20722 Unable to start Jenkins 540 using java7u45x64b Those errors appear that are the same (JENKINS-20630 and JENKINS-20675) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20722) Unable to start Jenkins 540 using java7u45x64b
Fernando Rosado Altamirano closed JENKINS-20722 as Duplicate Unable to start Jenkins 540 using java7u45x64b Duplicated by JENKINS-20630 Change By: Fernando Rosado Altamirano (22/Nov/13 3:37 PM) Status: Open Closed 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
Fernando Rosado Altamirano commented on JENKINS-20630 Jenkins fails to start I rejected JENKINS-20722 because duplicate this. Is this problem related with Java 7? I have tested java versions : 1.7.0.40 x86 - x64 1.7.0.45 x86 - x64 With and without tomcat on windows 2008 and 7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20729) provide Tranfers default settings in SSH Servers configuration
Mathis Dirksen-Thedens
created JENKINS-20729
provide Tranfers default settings in SSH Servers configuration
Issue Type:
Improvement
Assignee:
bap
Components:
publish-over-ssh
Created:
22/Nov/13 3:50 PM
Description:
It would be great if default values for all options in the "Transfers" section (e.g. "Source files", "Exec command") could be provided in the global configuration in a way that would reduce each job's configuration to selecting the server.
I guess it's a common use case to use Jenkins variables like ${JOB_NAME}, and this makes the configuration much the same - save an occasional exception for a legacy project. To reduce duplication of config data, it would be nice to set some defaults for each configured SSH Server and then be able to overwrite them occasionally, but if nothing is configured explicitly the defaults from the SSH Server configuration would be taken.
Project:
Jenkins
Labels:
configuration
Priority:
Major
Reporter:
Mathis Dirksen-Thedens
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
Marc Abramowitz updated JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs Change By: Marc Abramowitz (22/Nov/13 3:57 PM) Summary: Support MakeCoberturaplug-insupport multi-configuration(matrix)jobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cobertura] (JENKINS-20706) Make Cobertura plug-in support multi-configuration (matrix) jobs
Marc Abramowitz commented on JENKINS-20706 Make Cobertura plug-in support multi-configuration (matrix) jobs ssogabe: What do you think? If you don't want to do this, but can give me some pointers in the right direction, I might be able to send a PR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bulk-builder] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Michael Clarke updated JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working. Change By: Michael Clarke (22/Nov/13 4:24 PM) Component/s: cvs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-20632) Conditionally execute Coverity plugin fails during publish.
ikedam assigned JENKINS-20632 to ikedam Conditionally execute Coverity plugin fails during publish. Change By: ikedam (22/Nov/13 4:32 PM) Assignee: bap ikedam This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
Jim Gallagher commented on JENKINS-19888 NPE when running plugin I've analysed the file you've attached - many thanks for that. The error is caused by step definitions in the json output that do not contain an id element, causing a null-pointer exception when trying to generate the step reports for each scenario. That's the cause - the solution is more tricky. I need to investigate the structure of the json output and determine if an id element is mandatory - you'd think it is, but your file indicates otherwise. This is still under investigation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
Jim Gallagher started work on JENKINS-19888 NPE when running plugin Change By: Jim Gallagher (22/Nov/13 4:49 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20730) Wrong log message for out-of-order build record repair
Daniel Beck created JENKINS-20730 Wrong log message for out-of-order build record repair Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Nov/13 5:05 PM Description: Log says: Fixing problems in Foldername » Jobname Renaming /var/lib/jenkins/jobs/Foldername/jobs/Jobname/outOfOrderBuilds - /var/lib/jenkins/jobs/Foldername/jobs/Jobname/outOfOrderBuilds/2013-11-20_16-02-31 Renaming /var/lib/jenkins/Foldername/jobs/Jobname/outOfOrderBuilds - /var/lib/jenkins/jobs/Foldername/jobs/Jobname/outOfOrderBuilds/2013-11-20_16-05-31 The first line each time appears to be wrong, it should be e.g. Renaming /var/lib/jenkins/jobs/Foldername/jobs/Jobname/2013-11-20_16-02-31 Environment: 1.533-SNAPSHOT (CI build just before 1.532.1-rc1) Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20731) Dashboard rendering spends too much time in WeatherColumn
Jesse Glick created JENKINS-20731 Dashboard rendering spends too much time in WeatherColumn Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Nov/13 6:14 PM Description: The Jenkins dashboard was taking a ridiculously long time to render. A number of threads showed stack traces like "Handling GET / : http-8080-2" ... java.lang.Thread.State: RUNNABLE at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) - locked 0xfcb65020 (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(Unknown Source) at java.io.PushbackInputStream.read(Unknown Source) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.getHeader(XmlHeaderAwareReader.java:79) at com.thoughtworks.xstream.core.util.XmlHeaderAwareReader.init(XmlHeaderAwareReader.java:61) at com.thoughtworks.xstream.io.xml.AbstractXppDriver.createReader(AbstractXppDriver.java:65) at hudson.XmlFile.unmarshal(XmlFile.java:166) at hudson.model.Run.reload(Run.java:310) at hudson.model.Run.init(Run.java:299) at hudson.model.AbstractBuild.init(AbstractBuild.java:182) at hudson.maven.AbstractMavenBuild.init(AbstractMavenBuild.java:54) at hudson.maven.MavenBuild.init(MavenBuild.java:113) at sun.reflect.GeneratedConstructorAccessor75.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1129) at hudson.model.AbstractProject$1.create(AbstractProject.java:325) at hudson.model.AbstractProject$1.create(AbstractProject.java:323) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:674) - locked 0xd17b2608 (a hudson.model.RunMap) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:657) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:456) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220) at hudson.tasks.Fingerprinter$FingerprintAction.compact(Fingerprinter.java:356) at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:345) at hudson.model.Run.onLoad(Run.java:323) at hudson.model.RunMap.retrieve(RunMap.java:226) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:674) - locked 0xd17b2608 (a hudson.model.RunMap) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:657) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:456) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1076) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:465) at hudson.maven.MavenModuleSetBuild.computeResult(MavenModuleSetBuild.java:212) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:203) - locked 0xf286c990 (a java.lang.Object) at hudson.model.Run.getIconColor(Run.java:701) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:1035) at hudson.model.Job.getBuildHealthReports(Job.java:1010) at hudson.model.Job.getBuildHealth(Job.java:975) It seems that buildHealth.jelly, called from WeatherColumn/column.jelly, does some potentially rather expensive computations, especially when Maven projects are concerned. This should be done asynchronously, not in the HTTP rendering thread. Project: Jenkins Labels: performance Priority: Major Reporter:
[JIRA] [core] (JENKINS-20732) There should not be a 'Install without Restart' button on the 'Available' (updates) tab in update center
Daniel Beck created JENKINS-20732 There should not be a Install without Restart button on the Available (updates) tab in update center Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Nov/13 6:29 PM Description: Installed plugins cannot be updated without restarting Jenkins. So there shouldn't even be a button 'Install without Restart' button, it just behaves like 'Download now and install after restart' anyway... Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-1616) Support Integrated Windows Authentication
Kohsuke Kawaguchi resolved JENKINS-1616 as Duplicate Support Integrated Windows Authentication JENKINS-3730 has more votes. Consolidating to it. Change By: Kohsuke Kawaguchi (22/Nov/13 7:08 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] [active-directory] (JENKINS-20733) SASL authentication with Active Directory
Kohsuke Kawaguchi created JENKINS-20733 SASL authentication with Active Directory Issue Type: New Feature Assignee: Unassigned Components: active-directory Created: 22/Nov/13 7:12 PM Description: Instead of simple bind, use SASL to provide some degree of data encryption out of the box. MSDN lists various mechanisms that AD supports, and it includes DIGEST-MD5, which works with plain text password Jenkins has received from the browser (via the login form.) SASL is supported by JNDI LDAP implementation(http://docs.oracle.com/javase/tutorial/jndi/ldap/sasl.html) so activating it should be very simple. Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-20733) SASL authentication with Active Directory
Kohsuke Kawaguchi commented on JENKINS-20733 SASL authentication with Active Directory One of the reasons people want JENKINS-3730 is to avoid plain text password on the network caused by simple bind. This will prevent that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gui] (JENKINS-20698) A lot of JellyTagExceptions in the jenkins.log
Hallvard Nygård commented on JENKINS-20698 A lot of JellyTagExceptions in the jenkins.log Good catch! I've been using a browser with Norwegian language settings lately... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit-attachments] (JENKINS-19430) The files are not visible from either the test or the class page
Daniel Hinton commented on JENKINS-19430 The files are not visible from either the test or the class page I'm seeing the same issue: "This image failed to load." Built with: mvn -e clean install -Dtest=QA_Test This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20387) Timeout (10min) on git clone command
David Cummings commented on JENKINS-20387 Timeout (10min) on git clone command I did some digging in the code. The introduction of the timeout corresponds to: commit 1b7fd2b18d626d8ca081933d8a004fd7b2279210 Author: Nicolas De Loof nicolas.del...@gmail.com 2013-10-28 04:23:58 Committer: Nicolas De Loof nicolas.del...@gmail.com 2013-10-28 04:23:58 Parent: ddfde14d27aa6cd802dfc9897506eae4095b4f37 (JENKINS-20189 automatically append .git to repo URL just as git-cli does when base URL don't resolve to a git repo) Child: 8512c51b116475e78b1c1ddd7c84277af0f64904 (FIXED JENKINS-20326 proxy may not require authentication) Branches: origin/1.4.x, origin/gitcredentials If you look into the code, it is designed to be configurable by a system property. Kjell Morgenstern mentioned that didn't work, but it's because the system property was misspelt in his example. The O in timeOut is capitalized. should be java -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=12000 -jar jenkins.war Also, it's in minutes, not seconds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20734) NPE on some operations after restart
Bruno Meneguello created JENKINS-20734 NPE on some operations after restart Issue Type: Bug Affects Versions: current Assignee: Bruno Meneguello Components: ec2 Created: 22/Nov/13 8:58 PM Description: After restart Jenkins, the ec2 slaves forgets is cloud (the cloud attribute becames null) and then, when any operation needs to connect to the cloud, throws a NPE Project: Jenkins Priority: Critical Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20387) Timeout (10min) on git clone command
Mark Waite commented on JENKINS-20387 Timeout (10min) on git clone command Thanks for discovering that! I was mistakenly assuming that the most recent deliveries of the Git client plugin were released from the master branch. It appears they have been released from the 1.4.x branch. I assume that is because there are larger changes on the master branch which are not yet ready for release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-19276) Escape characters such as \ for filepaths are being removed from variables loaded from properties file.
Igor Okulist commented on JENKINS-19276 Escape characters such as \ for filepaths are being removed from variables loaded from properties file. bump! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20735) P4_LABEL variable not set
D Soa
created JENKINS-20735
P4_LABEL variable not set
Issue Type:
Bug
Assignee:
Rob Petti
Components:
perforce
Created:
22/Nov/13 10:45 PM
Description:
Plugin Version 1.3.25
I'm not getting a value for ${P4_LABEL} in a shell script. It looks like from the plugin doc version history that it should be set if building from a label (the P4 Label field in the SCM configuration).
I'm trying to run the following command to create a BOM file in a build step:
/usr/local/bin/p4 files //depot/...@${P4_LABEL} ${WORKSPACE}/p4.bom
Also, could you please add the list of all variables you are setting with this plugin to the documentation? I haven't found a definitive list anywhere.
Thanks.
Environment:
Linux
Project:
Jenkins
Priority:
Major
Reporter:
D Soa
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-20736) Git plugin does not update origin if URL changes
Dale King created JENKINS-20736 Git plugin does not update origin if URL changes Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 22/Nov/13 10:58 PM Description: I ran into a slight issue. Within my job I had a post build step that conditionally adds a tag and pushes it to origin. That was working until we renamed our git repo and thus changing the URL. I changed the URL in the job config, but the pushing of the tag was failing. The reason was that origin was never updated to the new URL because the builds did not do a new clone and the git plugin does not rely on the origin remote. Might be a good idea if the origin remote is updated to reflect the current URL. The workaround is that I need to not rely on origin in my job. Environment: Any Project: Jenkins Priority: Minor Reporter: Dale King This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit-attachments] (JENKINS-20737) Attached files appear in list, but throw a 404 Not Found when attempting to view them
Daniel Hinton created JENKINS-20737 Attached files appear in list, but throw a 404 Not Found when attempting to view them Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: junit-attachments Created: 22/Nov/13 11:13 PM Description: Jenkins: v1.540 JUnit-Attachments: v1.3 The files are displayed correctly, and are available on the server (I can copy them to another machine and view them). However, when clicking on the file, the light box displays the following error: This image failed to load. If I attempt to open the image in a new tab/window, I get a "404 Not Found" exception. I've checked the permissions throughout the Jenkins install and everything seems to be in order (however, this an instance that doesn't use any kind of authentication; everyone is the anonymous user with full permissions). Clicking the "attachments" link to the left yields even more interesting results: http://junit/namespace/test class name/attachments It appears that the link is rather incomplete, and doesn't reference the actual Jenkins instance I'm using. If I've missed anything, or you need additional information, please let me know! Project: Jenkins Priority: Major Reporter: Daniel Hinton This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19794) Prevent password exposure in perforce
Jarek Kapica commented on JENKINS-19794 Prevent password exposure in perforce Wouldn't this change reset job specific setting, rather than merely overriding it. Is that what is really intended? https://github.com/jenkinsci/perforce-plugin/pull/36/files#diff-a6a8e160fa20240410923ec7114cfacfR2711 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-20632) Conditionally execute Coverity plugin fails during publish.
ikedam assigned JENKINS-20632 to Josh Vinson Conditionally execute Coverity plugin fails during publish. Coverity plugin decides a temporary directory to use when that project is configured with Coverity publisher. This is performed in CoverityLauncherDecorator, CoverityTempDir. Used with Flexible Publisher, Coverity plugin fails to know Coverity publisher is configured in that project as it is wrapped by Flexible Publisher. This results no temporary directory is configured, and NPE happens as reported. I pass this issue to Coverity plugin as there is nothing Flexible Publisher can do. I think there are several ways Coverity plugin can do: Does not support Fiexible Publish plugin. Checks CovertyTempDir exists, and create if not exists. Add a special handling for Flexib Publish plugin. Change By: ikedam (22/Nov/13 11:36 PM) Assignee: ikedam JoshVinson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19794) Prevent password exposure in perforce
Jarek Kapica reopened JENKINS-19794 Prevent password exposure in perforce Change By: Jarek Kapica (22/Nov/13 11:38 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-20735) P4_LABEL variable not set
Rob Petti commented on JENKINS-20735 P4_LABEL variable not set I just took a quick glance at the code, and you're right, it doesn't make any sense. It's trying to use the label from the TagAction, which when the build is still running hasn't been tagged yet. I'll also look into listing all the env variables. It's a good thing to have listed somewhere. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Jay Spang commented on JENKINS-19470 Build Graph not displaying Repro'ing for me on Jenkins 1.5.37 (Win2012 Server), BuildFlow 0.10, BuildGraphView 1.1.1. I don't know what event causes the graphs to disappear, but they disappear after a couple of hours whether I've restarted Jenkins or not (I just checked and a build I ran 2h8m ago has already lost its graph). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20493) Plugin send encrypted password, login denied
Jay Spang commented on JENKINS-20493 Plugin send encrypted password, login denied Can you provide a source for the Perforce trigger bug? I'm seeing this issue too (my Perforce ticket is shown on the Console output, so anyone with access to the logs can see the ticket) so I'm keen to get to the bottom of this and resolve it if possible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [plugin] (JENKINS-15255) rvm plugin is not up to date with recent source code at github
Eito Katagiri closed JENKINS-15255 as Fixed rvm plugin is not up to date with recent source code at github In the latest version (0.4), you can use a dot (.) to load project .rvmrc with fairly recent rvm. Change By: Eito Katagiri (23/Nov/13 1:47 AM) Status: Open Closed Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17042) Replace Back to Dashboard link with Back to view name
Yoichi Nakayama commented on JENKINS-17042 Replace Back to Dashboard link with Back to view name FYI, CloudBees Folders Plugin does provide "Up" link to upper ViewGroup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20655) Unable to start the Jenkins applicaiton
Sylvain Benner edited a comment on JENKINS-20655 Unable to start the Jenkins applicaiton Could you be more specific about this issue ? Why did you assigned it to the jobgenerator component ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20655) Unable to start the Jenkins applicaiton
Sylvain Benner commented on JENKINS-20655 Unable to start the Jenkins applicaiton Could be more specific about this issue ? Why did you assigned it to the jobgenerator component ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20493) Plugin send encrypted password, login denied
Rob Petti commented on JENKINS-20493 Plugin send encrypted password, login denied I'm not sure what problem you are referring to, Jay. This ticket describes an issue communicating with perforce, which has been determined to be a configuration problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-19794) Prevent password exposure in perforce
Oleg Nenashev commented on JENKINS-19794 Prevent password exposure in perforce Yes, this change does exactly what I want. It prohibits exposal of P4 passwords in all jobs without ANY possibilities to retrieve or re-enable them from job's 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] [core] (JENKINS-20473) line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification
Dmitry Danilson started work on JENKINS-20473 line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification Change By: Dmitry Danilson (23/Nov/13 5:09 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20473) line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification
Dmitry Danilson commented on JENKINS-20473 line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification Parameters In order to make sure for me (and prove for you and others) that I am getting everything right, let me describe my explanation of the issue you have. So, we have 3 completely independent parameters that influence the issue: OS (either Windows or Linux); Jenkins version (only 2 variants that we have to take into account: either less or equal 1.530 or bigger than that); Line endings of request client (again only 2 variants: either CRLF or LF). Prediction So here is the table of results you are getting together with my prediction based on my understanding of the issue: OS/Version(crlf/non-crlf) =1.530 1.530 Linux Sucess/Success Error 400/JSON parsing error Windows Success/Success Error 400/JSON parsing error Please make sure that everything is as described in the table. Reasons Why it fails for Version1.530 for both OSes According to https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+Security , you should either grant additional permission for anonymous users or use a suggested plugin: Anonymous read access required The preceding instructions require that anonymous users have read access to Jenkins. If you disable overall read access for anonymous users, the Build Token Root Plugin allows use of tokens. Why it works for Version=1.530 for both OSes Among the changes done after 1.530 release (see http://jenkins-ci.org/changelog for reference) there was one called "Use fine-grained permissions for node manipulation via REST API CLI (issue 18485)". It changed the way how permission check works - so you need additional effort. Why for Version1.530 for both OSes it fails with 400 Error and not 403 or 404, which looks more appropriate in case if it is permission issue? I guess it is due to multipart submission. I believe that in case if you use regular call it will return either 403 or 404 Error. Hope it helps. Feel free to post additional info in case if suggested recipe doesn't solve your issue. Until that, I am going to mark it as solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20473) line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification
Dmitry Danilson edited a comment on JENKINS-20473 line-ending mismatch between the Jenkins HTTP server implementation and the HTTP specification Parameters In order to make sure for me (and prove for you and others) that I am getting everything right, let me describe my explanation of the issue you have. So, we have 3 completely independent parameters that influence the issue: OS (either Windows or Linux); Jenkins version (only 2 variants that we have to take into account: either less or equal 1.530 or bigger than that); Line endings of request client (again only 2 variants: either CRLF or LF). Prediction So here is the table of results you are getting together with my prediction based on my understanding of the issue: OS/Version(crlf/non-crlf) =1.530 1.530 Linux Sucess/Success Error 400/JSON parsing error Windows Success/Success Error 400/JSON parsing error Please make sure that everything is as described in the table. Reasons Why it fails for Version1.530 for both OSes According to https://wiki.jenkins-ci.org/display/JENKINS/Quick+and+Simple+Security , you should either grant additional permission for anonymous users or use a suggested plugin: Anonymous read access required The preceding instructions require that anonymous users have read access to Jenkins. If you disable overall read access for anonymous users, the Build Token Root Plugin allows use of tokens. Why it works for Version=1.530 for both OSes Among the changes done after 1.530 release (see http://jenkins-ci.org/changelog for reference) there was one called "Use fine-grained permissions for node manipulation via REST API CLI (issue 18485)". It changed the way how permission check works - so you need additional effort. Why for Version1.530 for both OSes it fails with 400 Error and not 403 or 404, which looks more appropriate in case if it is permission issue? I guess it is due to multipart submission. I believe that in case if you use regular call it will return either 403 or 404 Error. Hope it helps. Feel free to post additional info in case if suggested recipe doesn't solve your issue. Until that, I am going to consider it as solved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
