[JIRA] [core] (JENKINS-14189) Discover permission gives Status Code 500 and Stacktrace
Roland Gruber commented on JENKINS-14189 Discover permission gives Status Code 500 and Stacktrace Any chance this gets fixed? At the moment, no deep links are 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] [core] (JENKINS-18169) Deadlock when running multiple delete
Marcus Jacobsson
created JENKINS-18169
Deadlock when running multiple delete
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
03/Jun/13 6:58 AM
Description:
Tried to remove ~20 builds in parallel with 30 days of build logs (a lot of files) and this resulted in a deadlock and we needed to restart the server.
JavaMelody listed the doDelete threads as deadlocked and showed
1 x hudson.model.Job.delete(Job.java:587)
17 x hudson.model.Project.getPublishersList(Project.java:114)
as a result of the deadlock we can't edit builds anymore
/configSubmit : http-bio-8080-exec-3552 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3503 yes 5 BLOCKED hudson.model.Project.getPublishersList(Project.java:114)
/doDelete : http-bio-8080-exec-3543 yes 5 BLOCKED hudson.model.Job.delete(Job.java:587)
Looking in project.java it looks like a deprecated method is used
/**
* @deprecated as of 1.463 We will be soon removing the restriction that
* only one instance of publisher is allowed per type. Use
* {@link #getPublishersList()} instead.
*/
public MapDescriptorPublisher,Publisher getPublishers() {
return publishers.toMap();
}
Environment:
Jenkins 1.509.1 running on Ubuntu 12.04 with JDK 1.7
Project:
Jenkins
Priority:
Major
Reporter:
Marcus Jacobsson
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving 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-18169) Deadlock when running multiple delete
kutzi commented on JENKINS-18169 Deadlock when running multiple delete Please attach the full thread dump! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18170) Remove issues on Github or stop using Jenkins Jira
Ole Christian Langfjæran created JENKINS-18170 Remove issues on Github or stop using Jenkins Jira Issue Type: Task Affects Versions: current Assignee: Unassigned Components: build-pipeline Created: 03/Jun/13 7:47 AM Description: It is confusing using when there's an Issues tab on Github, but issues are maintained here at Jenkins Jira That said I think many, many prefer Github Issues over Jira, so is it worth considering moving again? It would also do contributions and closing issues a whole lot easier. Fix Versions: current Project: Jenkins Priority: Minor Reporter: Ole Christian Langfjæran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-16455) Build Environment section mission from build-flow job configuration page
William Zhang commented on JENKINS-16455 Build Environment section mission from build-flow job configuration page fix this and “Set Build Name”( https://wiki.jenkins-ci.org/display/JENKINS/Build+Name+Setter+Plugin )is very usable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18170) Remove issues on Github or stop using Jenkins Jira
Ole Christian Langfjæran commented on JENKINS-18170 Remove issues on Github or stop using Jenkins Jira That said I would gladly help moving issues over to Github. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects Have you tried using the 1.3.4-SNAPSHOT version? We are using it just to make Manual Parameterized builds available. Bugs on rerun, but otherwise works. Haven't tested on Parameterized downstream project though. But I would much like that a 1.3.4 version was commited with current code all the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [versionnumber] (JENKINS-18171) Version Number plugin doesn't increment build numbers after an unstable build
Mikolaj Leszczynski created JENKINS-18171 Version Number plugin doesnt increment build numbers after an unstable build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: versionnumber Created: 03/Jun/13 8:28 AM Description: When the option 'Don't increment builds today/ this month/ this year/ all time after a failed build' is selected, the plugin doesn't increment build numbers for unstable builds as well. This makes it tedious to get a correct version number if one or two tests tend to be unstable. Environment: Debian x64 Project: Jenkins Labels: plugin Priority: Major Reporter: Mikolaj Leszczynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema edited a comment on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I have tried it, but considering I'm working on a production server with 30 projects (plus the 120 duplicates), I was hesitant to commit more time investigating, considering the Run button is bugged with the 1.3.4-SNAPSHOT. Don't know if it fixes it, but it's unusable just the same. This is a rather big issue for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I have tried it, but considering I'm working on a production server with 30 projects, I was hesitant to commit more time investigating, considering the Run button is bugged with the 1.3.4-SNAPSHOT. Don't know if it fixes it, but it's unusable just the same. This is a rather big issue for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [accurev] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
Frank Malsbenden commented on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset Same problem occurs frequently with different versions of Jenkins, actual Version is 1.514 All jobs stopped with the same error. May this be a problem with the SVN client? SVN checkout is the first action inside all Jobs. Console output of job Started by upstream project "std-trunk" build number 132 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on gs3-compile-x64 in workspace d:\jenkins\workspace\rt-trunk BuildAndDeploy FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:893) at hudson.FilePath.act(FilePath.java:877) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:67) at hudson.model.Run.execute(Run.java:1575) at hudson.model.Run.run(Run.java:1521) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:60) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:185) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) 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] [release] (JENKINS-18172) Release on SSH slave broken (svn not found)
Michael Pailloncy created JENKINS-18172 Release on SSH slave broken (svn not found) Issue Type: Bug Assignee: Peter Hayes Components: release, ssh-slaves Created: 03/Jun/13 9:00 AM Description: We want to use 'ssh-slave' capabilities. During tests, we've made a release and an error occurred : ... INFO BUILD FAILURE INFO INFO Total time: 4.850s INFO Finished at: Mon Jun 03 10:34:06 CEST 2013 INFO Final Memory: 10M/24M INFO ERROR Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.2.1:prepare (default-cli) on project myjob: Unable to check for local modifications ERROR Provider message: ERROR The svn command failed. ERROR Command output: ERROR /bin/sh: svn: not found ERROR - Help 1 ERROR ERROR To see the full stack trace of the errors, re-run Maven with the -e switch. ERROR Re-run Maven using the -X switch to enable full debug logging. ERROR ERROR For more information about the errors and possible solutions, please read the following articles: ERROR Help 1 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException The main build is a maven type build and works well if I launch a classic build. If I rollback to JNLP strategy to connect slaves, the release is OK. Thanks Environment: Jenkins 1.504 - SVN 1.6 - Maven release using https://wiki.jenkins-ci.org/display/JENKINS/Release+Plugin Project: Jenkins Priority: Major Reporter: Michael Pailloncy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9271) AdjunctManager is not installed for this application upon failed boot
Barthélémy von Haller commented on JENKINS-9271 AdjunctManager is not installed for this application upon failed boot I have just got it with 1.517 on RHEL 6. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
Mikolaj Leszczynski commented on JENKINS-17592 Testflight uploader plugin doesnt allow to upload multiple files This works nicely, thanks for your hard work guys! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [accurev] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
framal edited a comment on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset Same problem occured with Jenkins Version 1.514, running on Ubuntu. All jobs stopped with the same error. May this be a problem with the SVN client? SVN checkout is the first action inside all Jobs. The connection to the clients were still up. Console output of job, running on windows slave Started by upstream project "std-trunk" build number 132 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on gs3-compile-x64 in workspace d:\jenkins\workspace\rt-trunk BuildAndDeploy FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:672) at hudson.FilePath.act(FilePath.java:893) at hudson.FilePath.act(FilePath.java:877) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1369) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:67) at hudson.model.Run.execute(Run.java:1575) at hudson.model.Run.run(Run.java:1521) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:60) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:732) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:185) at java.io.FilterInputStream.read(FilterInputStream.java:133) at java.io.BufferedInputStream.fill(BufferedInputStream.java:235) at java.io.BufferedInputStream.read(BufferedInputStream.java:254) at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2265) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2558) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2568) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) 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] [jclouds-jenkins] (JENKINS-18173) JClouds fails accessing OpenStack-nova
Jaroslav Henner created JENKINS-18173 JClouds fails accessing OpenStack-nova Issue Type: Bug Assignee: Unassigned Components: jclouds-jenkins Created: 03/Jun/13 11:43 AM Description: I filled all the fields available in the configuration, including the endpoint url pointing to my Keystone: http://MY_JENKINS_IP:5000/v2.0/ When clicking on the Test, I am getting: Cannot connect to specified cloud, please check the identity and credentials: java.lang.NullPointerException: tenant Obviously there should be one more field to fill the tenant, as in openstack, user should specify which tenant (aka project) he is going to work with. Project: Jenkins Labels: plugin Priority: Major Reporter: Jaroslav Henner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-18173) JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant)
Jaroslav Henner updated JENKINS-18173 JClouds fails accessing OpenStack-nova (java.lang.NullPointerException: tenant) Change By: Jaroslav Henner (03/Jun/13 11:44 AM) Summary: JCloudsfailsaccessingOpenStack-nova (java.lang.NullPointerException:tenant) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-12076) m2 Release Plugin lock builds
Maciej Matys commented on JENKINS-12076 m2 Release Plugin lock builds How does it work, now I see 'Number of successful release builds to keep' with default value 0, moreover latest release build is NOT locked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18174) Checking of unique Build Parameter names has a hole and only works within a single context
Andrew Harmel-Law created JENKINS-18174 Checking of unique Build Parameter names has a hole and only works within a single context Issue Type: Bug Assignee: Justin Ryan Components: job-dsl-plugin Created: 03/Jun/13 12:07 PM Description: In https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/BuildParametersContextHelper.groovy the buildParameterNodes.containsKey(parameterName) won't help if someone calls parameters a few times, since that check only works within a single Context. Ideally we should queue up all the buildParameterNodes and then replay only at the very end. See: https://github.com/jenkinsci/job-dsl-plugin/pull/50 Environment: Development Project: Jenkins Priority: Minor Reporter: Andrew Harmel-Law This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-18175) dSYM filename
Valerio Mazzeo created JENKINS-18175 dSYM filename Issue Type: Improvement Assignee: Unassigned Components: testflight Created: 03/Jun/13 12:18 PM Description: Allows the plugin to search also for ".dSYM.zip" files instead that only for "-dSYM.zip" This will make the integration with xcoder smoother: https://github.com/rayh/xcoder/issues/68 Project: Jenkins Priority: Minor Reporter: Valerio Mazzeo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [memory-map] (JENKINS-18176) Environment variables can not be used in filepaths
Bue Petersen
created JENKINS-18176
Environment variables can not be used in filepaths
Issue Type:
Bug
Affects Versions:
current
Assignee:
Praqma Support
Components:
memory-map
Created:
03/Jun/13 12:43 PM
Description:
For example using the following path for in the Linker Command File: ${GIT_CLONE_DIR}/${cmdfile}-${BCONF}.cmd
... can't be found.
Using the same path in for example Archive Artifacts will work, thus the env. vars. are available in the post-build step.
Environment:
Master and slaves on Linux, Jenkins 1.491
Project:
Jenkins
Priority:
Major
Reporter:
Bue Petersen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [memory-map] (JENKINS-18176) Environment variables can not be used in filepaths (Praqma case 9430)
Bue Petersen updated JENKINS-18176 Environment variables can not be used in filepaths (Praqma case 9430) Change By: Bue Petersen (03/Jun/13 12:46 PM) Summary: Environmentvariablescannotbeusedinfilepaths (Praqmacase9430) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-13567) NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end
Jesse Glick updated JENKINS-13567 NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end Change By: Jesse Glick (03/Jun/13 12:49 PM) URL: https://github.com/jenkinsci/violations-plugin/pull/30 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-16374) BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE
kutzi reopened JENKINS-16374 BuildStepMonitor.STEP makes concurrent builds wait, could be changed to BuildStepMonitor.NONE Reopening it as no one has answered my previous comment and I still think this can produce wrong result number trends. Change By: kutzi (03/Jun/13 1:15 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] [violations] (JENKINS-13567) NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end
SCM/JIRA link daemon commented on JENKINS-13567 NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end Code changed in jenkins User: peterkittreilly Path: src/main/java/hudson/plugins/violations/hudson/maven/ViolationsMavenReporter.java http://jenkins-ci.org/commit/violations-plugin/2f0a405468f87b974847de14be5d7f02d39b51f5 Log: Merge pull request #30 from jglick/JENKINS-13567-diag JENKINS-13567 Diagnosis for an NPE. Compare: https://github.com/jenkinsci/violations-plugin/compare/5e0b1f06ebd2...2f0a405468f8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [violations] (JENKINS-13567) NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end
SCM/JIRA link daemon commented on JENKINS-13567 NullPointerException on hudson.plugins.violations.hudson.maven.ViolationsMavenReporter.end Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/violations/hudson/maven/ViolationsMavenReporter.java http://jenkins-ci.org/commit/violations-plugin/a11c253f3065fc0b9ebf6fe6d7f3257c39c69265 Log: JENKINS-13567 Diagnosis for an NPE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
jon cage commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Same here running on Windows XP host for Jenkins and viewing through chrome. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
jon cage edited a comment on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity Same here running on Windows XP host (as a service) and viewing no client machines using Chrome / FF. Closing the tab and opening a new one appears to fix 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] [maven] (JENKINS-15846) Deadlock during Maven builds Parsing POM step
Tony Bridges commented on JENKINS-15846 Deadlock during Maven builds Parsing POM step Are all the pieces in place ? Is this expected in a release any time soon ? I'm hitting this issue a lot more often than now and then - about twice a day. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-18177) Allow to cancel both the flow and all running builds
Nicolas De Loof created JENKINS-18177 Allow to cancel both the flow and all running builds Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 03/Jun/13 2:08 PM Description: Provide an additional option to cancel both the flow (don't trigger new jobs) but also cancel all active builds. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Benny Bottema commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity We're running this in a project with 5 teams of about 2/3 developers per team and we all experience this issue. Simple refresh doesn't work (even with cache turned off under Chrome), but a ctrl-F5 seems to have some effect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
Georg Sash created JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven2 Created: 03/Jun/13 2:29 PM Description: All our Jenkins builds using Maven2 are failing after upgrade to 1.517. Reverting back to 1.516 solves the issue. Our Maven 3 based builds are not affected. INFO ERROR FATAL ERROR INFO INFO org/apache/commons/codec/digest/DigestUtils.md5Hex(Ljava/io/InputStream;)Ljava/lang/String; INFO INFO Trace java.lang.NoSuchMethodError: org/apache/commons/codec/digest/DigestUtils.md5Hex(Ljava/io/InputStream;)Ljava/lang/String; at hudson.Util.getDigestOf(Util.java:557) at hudson.maven.reporters.MavenArtifactArchiver.postBuild(MavenArtifactArchiver.java:101) at hudson.maven.Maven2Builder.postModule(Maven2Builder.java:129) at hudson.maven.MavenBuilder$Adapter.fireLeaveModule(MavenBuilder.java:354) at hudson.maven.MavenBuilder$Adapter.postBuild(MavenBuilder.java:308) at org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:68) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at hudson.maven.agent.Main.launch(Main.java:185) at hudson.maven.MavenBuilder.call(MavenBuilder.java:154) at hudson.maven.Maven2Builder.call(Maven2Builder.java:79) at hudson.maven.Maven2Builder.call(Maven2Builder.java:55) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:314) at java.util.concurrent.FutureTask.run(FutureTask.java:149) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:897) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:919) at java.lang.Thread.run(Thread.java:738) INFO INFO Total time: 8 seconds INFO Finished at: Mon Jun 03 15:26:42 CEST 2013 INFO Final Memory: 49M/125M INFO channel stopped Finished: FAILURE Environment: Linux, IBM JDK6 and Sun JDK6 Project: Jenkins Priority: Blocker Reporter: Georg Sash This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups
[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 It seems that kohsuke’s f8014d974c6eb9f30098851bd7c1edd1928f was overly optimistic; while in Java 7 Path.toRealPath correctly follows Windows symlinks, File.getCanonicalFile does not. That means that it is normal on Windows when using Java 6 for existing build records using symlinks (e.g. created when Jenkins was running on Java 7?) to display this error. The questions are 1. Why this is seen as a fatal error. Code up the call stack should catch the exception, print it, and ignore it, continuing the load the actual build directories. 2. How Jenkins running on Windows on Java 6 can safely ignore links. Maybe it should just quietly ignore anything named lastSomething or a number, without trying to determine if it is a link or not; and only report one-line warnings for directory entries with other (unexpected) names. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 @ramicenzic: yes it is preferable to run Jenkins on Java 7 rather than 6, but we support 6 (and even 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] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick updated JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Change By: Jesse Glick (03/Jun/13 2:52 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick started work on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Change By: Jesse Glick (03/Jun/13 2:52 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick assigned JENKINS-15587 to Jesse Glick Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Change By: Jesse Glick (03/Jun/13 2:52 PM) Assignee: KohsukeKawaguchi 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] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Jesse Glick updated JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Change By: Jesse Glick (03/Jun/13 2:52 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18042) Jobs not loading after changing 'Build Record Root Directory' under 'Manage Jenkins' page
Sam Wrankmore updated JENKINS-18042 Jobs not loading after changing Build Record Root Directory under Manage Jenkins page Change By: Sam Wrankmore (03/Jun/13 3:21 PM) Component/s: core Component/s: build-flow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jesse Glick commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException @walterk82 indeed -Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true really only turns off the specialized error reporting, not the filter as a whole. For that you need to use -Dorg.kohsuke.stapler.jelly.DefaultScriptInvoker.compress=false from what I can tell. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-poll-action] (JENKINS-17076) Poll SCM brings up a window complaining about submitting a POST
Kevin Phillips commented on JENKINS-17076 Poll SCM brings up a window complaining about submitting a POST I am encountering this error as well. I could be mistaken, but I think this feature was working at one point on our Jenkins configuration so I suspect this error may be indirectly related to some recent configuration changes that we've made. For example, we just recently enabled the "Project-based Matrix Authorization Strategy" in the security configuration area so maybe this has somehow affected the behavior of the polling mechanism. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
kutzi resolved JENKINS-17526 as Duplicate Broken CSS when reloading Jenkins after a time of inactivity Change By: kutzi (03/Jun/13 5:13 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] [cvs] (JENKINS-16314) cvs plugin removes sticky branch tag
Adriano Andrulis commented on JENKINS-16314 cvs plugin removes sticky branch tag Hi Michael, do you know when the next version will be release? Thanks in advance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jesse Glick commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Looking around for alternate implementations of GZIPOutputStream. JZlib looks most promising. Swapping this in for the native JRE implementation (zlib) should be trivial enough, but I need someone who is able to reproduce this bug and is willing to build Jenkins from sources (or give me a target Jenkins release version that I can build an alternate binary of) and compare the JZlib performance, so see if the hypothesis is valid that a bug in zlib is causing this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
jon cage commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity FYI, I've just upgraded to v1.517 and have not as yet seen the issue re-appear. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17526) Broken CSS when reloading Jenkins after a time of inactivity
Christopher Orr commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity The fix for this should be in 1.518, so you may well still see this problem occur in 1.517. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16276) NPE cause dead thread slave
SCM/JIRA link daemon commented on JENKINS-16276 NPE cause dead thread slave Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/matrix/MatrixBuild.java http://jenkins-ci.org/commit/jenkins/fc45c84551f9955960752038209749be453aab19 Log: Merge pull request #746 from saschpe/master-jenkins-16276 JENKINS-16276 and various fixes for related exceptions Compare: https://github.com/jenkinsci/jenkins/compare/c8a6dac2f908...fc45c84551f9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17728) NPE from MatrixConfiguration.newBuild
Jesse Glick commented on JENKINS-17728 NPE from MatrixConfiguration.newBuild https://github.com/jenkinsci/jenkins/commit/1c00d3f65b0aea70df1c6d64c60bf9541eb4454f fixes a probably related stack trace: java.lang.NullPointerException at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:371) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-18179) Allow Build Hiding in Build History
kevin ran created JENKINS-18179 Allow Build Hiding in Build History Issue Type: Improvement Assignee: Nicolas De Loof Components: build-flow, logaction, logging Created: 03/Jun/13 6:22 PM Description: Right now if we limit the number of builds to keep to 1 for a particular job, its runs still show up in the build history. Is it possible to completely hide a build from the build history? Project: Jenkins Priority: Trivial Reporter: kevin ran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Jesse Glick commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Created http://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-war/1.513.JENKINS-14362-jzlib/jenkins-war-1.513.JENKINS-14362-jzlib.war based on 1.513 if anyone wants to give it a whirl. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [file-leak-detector] (JENKINS-18180) File Leak Detector Plugin does not work if JENKINS_HOME has a space in it
Kevin Ormbrek created JENKINS-18180 File Leak Detector Plugin does not work if JENKINS_HOME has a space in it Issue Type: Bug Assignee: Unassigned Components: file-leak-detector Created: 03/Jun/13 6:47 PM Description: Exception in thread "main" com.sun.tools.attach.AgentLoadException: Agent JAR not found or no Agent-Class attribute In the stack trace you can see in the path to the file leak detector jar, the space is being "percent-encoded" e.g. C:\Program%20Files\Jenkins... Moving the Jenkins folder so that JENKINS_HOME did not have a space in it resolved the issue. Project: Jenkins Priority: Minor Reporter: Kevin Ormbrek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-18181) INFOPLIST_FILE with Environment Variable breaks IPA Packaging
Heath Borders created JENKINS-18181 INFOPLIST_FILE with Environment Variable breaks IPA Packaging Issue Type: Bug Assignee: Unassigned Components: xcode Created: 03/Jun/13 6:47 PM Description: In my project.pbxproj file, I had the following INFOPLIST_FILE setting: INFOPLIST_FILE = "$(SRCROOT)/jive-ipad/jive-ipad-Info.plist"; Which yielded the following weird output: Fetching marketing version number (CFBundleShortVersionString) from project. [jive-pkg-ipad_develop] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): $(SRCROOT)/jive-ipad/jive-ipad-Info.plist 0.5.3. Marketing version (CFBundleShortVersionString) found in project configuration: $(SRCROOT)/jive-ipad/jive-ipad-Info.plist 0.5.3. Fetching technical version number (CFBundleVersion) from project. [jive-pkg-ipad_develop] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: $(SRCROOT)/jive-ipad/jive-ipad-Info.plist 0.5.3 I switched it to this setting: INFOPLIST_FILE = "jive-ipad/jive-ipad-Info.plist"; And everything worked fine: Fetching marketing version number (CFBundleShortVersionString) from project. [jive-pkg-ipad_develop] $ /usr/bin/agvtool mvers -terse1 Found marketing version (CFBundleShortVersionString): 0.5.3. Marketing version (CFBundleShortVersionString) found in project configuration: 0.5.3. Fetching technical version number (CFBundleVersion) from project. [jive-pkg-ipad_develop] $ /usr/bin/agvtool vers -terse No marketing version found (CFBundleVersion) Technical version (CFBundleVersion) found in project configuration: . Marketing version (CFBundleShortVersionString) used by Jenkins to produce the IPA: 0.5.3 This is easy to workaround, but if you don't support environment variables in the INFOPLIST_FILE setting, you should emit an error message. Project: Jenkins Priority: Minor Reporter: Heath Borders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-13131) SSH may stale for 15 minutes after slave restart
Guy Rozendorn commented on JENKINS-13131 SSH may stale for 15 minutes after slave restart more than a year later, and we're still dealing daily with this issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-13237) Unsuccessful SSH slave start do not timeout and cannot be retry, even manually
Guy Rozendorn commented on JENKINS-13237 Unsuccessful SSH slave start do not timeout and cannot be retry, even manually Looks related to JENKINS-13131, did you try waiting for 15 minutes and see if your slaves reconnect? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Leo Li commented on JENKINS-15769 Provide way to allow build icons without anonymous access. Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18182) Stacktrace on project save
Jon Skarpeteig
created JENKINS-18182
Stacktrace on project save
Issue Type:
Bug
Assignee:
Unassigned
Components:
gui
Created:
03/Jun/13 7:45 PM
Description:
Error
Failed to parse form data. Please report this problem as a bug
JSON={"name":"arc-internal","description":"img type=\"image/svg+xml\" height=\"300\" src="" width=\"500\"\/img\nimg type=\"image/svg+xml\" height=\"300\" src="" width=\"500\"\/img","":img type=\image/svg+xml\ height=\300\ src="" width=\500\\/img\nimg type=\image/svg+xml\ height=\300\ src="" width=\500\\/img,0,"logrotate":true,"buildDiscarder":{"stapler-class":"hudson.tasks.LogRotator","daysToKeepStr":"","numToKeepStr":"50","artifactDaysToKeepStr":"","artifactNumToKeepStr":""},"properties":{"stapler-class-bag":"true","hudson-security-AuthorizationMatrixProperty":{},"hudson-model-ParametersDefinitionProperty":{}},"displayNameOrNull":"","scm":{"value":"2","userRemoteConfigs":{"url":"g...@gitorious.armed.us:arc/arc.git","name":"","refspec":""},"branches":{"name":"next"},"includedRegions":"","excludedRegions":"","excludedUsers":"","localBranch":"","relativeTargetDir":"","reference":"","scmName":"","gitConfigName":"","gitConfigEmail":"","pruneBranches":false,"skipTag":false,"clean":false,"remotePoll":false,"disableSubmodules":false,"recursiveSubmodules":false,"authorOrCommitter":false,"wipeOutWorkspace":false,"ignoreNotifyCommit":false,"useShallowClone":false,"":hudson.plugins.git.util.DefaultBuildChooser,auto,"buildChooser":{"stapler-class":"hudson.plugins.git.util.DefaultBuildChooser"},"gitTool":"Default"},"hudson-triggers-SCMTrigger":{"scmpoll_spec":"* * * * *","ignorePostCommitHooks":false},"hudson-plugins-ansicolor-AnsiColorBuildWrapper":{"colorMapName":"xterm"},"builder":{"targets":"build-internal","buildFile":"","properties":"","antOpts":"","stapler-class":"hudson.tasks.Ant","kind":"hudson.tasks.Ant"},"publisher":[{"pattern":"build/logs/checkstyle.xml","canRunOnFailed":true,"shouldDetectModules":false,"healthy":"1","unHealthy":"1","thresholdLimit":"low","unstableTotalAll":"1","unstableTotalHigh":"1","unstableTotalNormal":"1","unstableTotalLow":"1","failedTotalAll":"1","failedTotalHigh":"1","failedTotalNormal":"1","failedTotalLow":"1","canComputeNew":{"unstableNewAll":"1","unstableNewHigh":"1","unstableNewNormal":"1","unstableNewLow":"1","failedNewAll":"1","failedNewHigh":"1","failedNewNormal":"1","failedNewLow":"1","useDeltaValues":false,"useStableBuildAsReference":false},"defaultEncoding":"","stapler-class":"hudson.plugins.checkstyle.CheckStylePublisher","kind":"hudson.plugins.checkstyle.CheckStylePublisher"},{"pattern":"build/logs/pmd.xml","canRunOnFailed":true,"shouldDetectModules":false,"healthy":"1","unHealthy":"1","thresholdLimit":"low","unstableTotalAll":"0","unstableTotalHigh":"0","unstableTotalNormal":"0","unstableTotalLow":"0","failedTotalAll":"0","failedTotalHigh":"0","failedTotalNormal":"0","failedTotalLow":"0","canComputeNew":{"unstableNewAll":"0","unstableNewHigh":"0","unstableNewNormal":"0","unstableNewLow":"0","failedNewAll":"0","failedNewHigh":"0","failedNewNormal":"0","failedNewLow":"0","useDeltaValues":false,"useStableBuildAsReference":false},"defaultEncoding":"","stapler-class":"hudson.plugins.pmd.PmdPublisher","kind":"hudson.plugins.pmd.PmdPublisher"},{"pattern":"build/logs/pmd-cpd.xml","highThreshold":"50","normalThreshold":"25","canRunOnFailed":true,"shouldDetectModules":false,"healthy":"","unHealthy":"","thresholdLimit":"low","unstableTotalAll":"","unstableTotalHigh":"","unstableTotalNormal":"","unstableTotalLow":"","failedTotalAll":"","failedTotalHigh":"","failedTotalNormal":"","failedTotalLow":"","canComputeNew":{"unstableNewAll":"","unstableNewHigh":"","unstableNewNormal":"","unstableNewLow":"","failedNewAll":"","failedNewHigh":"","failedNewNormal":"","failedNewLow":"","useDeltaValues":false,"useStableBuildAsReference":false},"defaultEncoding":"","stapler-class":"hudson.plugins.dry.DryPublisher","kind":"hudson.plugins.dry.DryPublisher"},{"plots":{csvFileName:123.csv,group:phploc,title:A - Lines of code,numBuilds:100,yaxis:Lines of
[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.5.15, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
David Barber created JENKINS-18183 After upgrading from jenkins 1.513 to 1.5.15, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 03/Jun/13 7:56 PM Description: After upgrading Jenkins from version 1.513 to 1.515, I cannot save the field Settings file to "Settings file in filesystem" which is pointed to a local settings.xml file for the maven (Invoke top-level Maven target) prebuild step. It will let me enter all the information and save it but it is not permanently saved in the job's config.xml file. When I reconfigure the job, the Settings file defaults back to "use default maven settings". The workaround is to the "-s" parameter to the Goals field. This is annoying because have many jenkins jobs that use "Invoke top-level Maven target" as a prebuild step. Environment: Jenkins 1.515 in Centos 6. Project: Jenkins Priority: Major Reporter: David Barber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.5.15, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
David Barber updated JENKINS-18183 After upgrading from jenkins 1.513 to 1.5.15, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. Change By: David Barber (03/Jun/13 7:57 PM) Description: AfterupgradingJenkinsfromversion1.513to1.515,IcannotsavethefieldSettingsfiletoSettingsfileinfilesystemwhichispointedtoalocalsettings.xmlfileforthemaven(Invoketop-levelMaventarget)prebuildstep.Itwillletmeenteralltheinformationandsaveitbutitisnotpermanentlysavedinthejobsconfig.xmlfile.WhenIreconfigurethejob,theSettingsfiledefaultsbacktousedefaultmavensettings.Theworkaroundistothe-sparametertotheGoalsfield.Thisisannoyingbecause we havemanyjenkinsjobsthatuseInvoketop-levelMaventargetasaprebuildstep. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18183) After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
David Barber updated JENKINS-18183 After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. Change By: David Barber (03/Jun/13 7:57 PM) Summary: Afterupgradingfromjenkins1.513to1. 5.15 515 ,IcannotuseSettingsfile(Settingsfileinfilesystem)fieldinamavenprebuildstepforamavenproject. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [file-leak-detector] (JENKINS-18180) File Leak Detector Plugin does not work if JENKINS_HOME has a space in it
Kevin Ormbrek updated JENKINS-18180 File Leak Detector Plugin does not work if JENKINS_HOME has a space in it Change By: Kevin Ormbrek (03/Jun/13 8:20 PM) Attachment: StackTrace.txt Description: Exceptioninthreadmaincom.sun.tools.attach.AgentLoadException:AgentJARnotfoundornoAgent-ClassattributeInthestacktraceyoucanseeinthepathtothefileleakdetectorjar,thespaceisbeingpercent-encodede.g.C:\Program%20Files\Jenkins...MovingtheJenkinsfoldersothatJENKINS_HOMEdidnothaveaspaceinitresolvedtheissue. Response(stacktrace)whenattemptingtoactivatethefileleakdetectorisattached. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18184) Polling should initiate build when tied slave is online but workspace had been deleted
Jesse Glick created JENKINS-18184 Polling should initiate build when tied slave is online but workspace had been deleted Issue Type: Bug Assignee: Unassigned Components: core Created: 03/Jun/13 8:53 PM Description: After a job's workspace was deleted, probably by the workspace cleanup thread due to a period of inactivity, polling from Git (without Fast Remote Polling enabled) failed: No workspace is available, so can't check for updates. Done. Took 84 ms No changes In AbstractProject._poll, if requiresWorkspaceForPolling and there is no workspace and there is a self label, then building is skipped: if the build is fixed on a node, then attempting a build will do us no good. We should just wait for the slave to come back. which makes sense if the workspace is unavailable because the slave is offline, but not if the slave is online and the workspace has simply been deleted. Environment: 1.480.3 Project: Jenkins Labels: workspace polling Priority: Minor 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] [rake] (JENKINS-7530) Rake plugin fails when Job configured to use (Default) Rake installation.
vikram jani commented on JENKINS-7530 Rake plugin fails when Job configured to use (Default) Rake installation. I am using Rake Plugin 1.7.7 and see this issue. I only have rake and ruby avialable on my slave (windows) machine. Any clue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17675) Allow the Pre-send script to be a file or call a scriptler script
Kavita Tiwari commented on JENKINS-17675 Allow the Pre-send script to be a file or call a scriptler script Great! Thanks Alex! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
George Marchin commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 See this: https://github.com/jenkinsci/xunit-plugin/compare/xunit-1.58...xunit-1.59 I would appear that the JUnit model validator was silently changed from 4 to 5. JUnit 4 and JUnit 5 should be added as seperate xunit file types in the 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] [xcode] (JENKINS-15708) Xcode Plugin not expanding $(SRCROOT) variable
Nick Amundsen
commented on JENKINS-15708
Xcode Plugin not expanding $(SRCROOT) variable
I believe this is still an issue.
The issue seems to be exactly as described in the title in that the Xcode Plugin is not expanding the SRCROOT variable as it should.
While the comments above describe a workaround, providing the relative path to the info.plist is not always sufficient. It would be nice to be able to include a variable in the path of the info.plist and to have the plugin evaluate that variable to find the full path.
Another note here is that if you are using variables in your paths, the more appropriate syntax is "${SRCROOT}" rather than "$(SRCROOT)".
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15708) Xcode Plugin not expanding $(SRCROOT) variable
Nick Amundsen reopened JENKINS-15708 Xcode Plugin not expanding $(SRCROOT) variable Change By: Nick Amundsen (03/Jun/13 9:37 PM) Resolution: NotADefect 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] [embeddable-build-status] (JENKINS-15769) Provide way to allow build icons without anonymous access.
Leo Li edited a comment on JENKINS-15769 Provide way to allow build icons without anonymous access. Is this fixed by https://issues.jenkins-ci.org/browse/JENKINS-17798 ? EDIT: I think it did, at least provided a workaround good enough to close this ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Peter Becker edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification We are using Mercurial as well, having normal looking commits on that end. Jenkins 1.506 adds underscores to some but not all email addresses. In one build two out of three email addresses failed. They all look the same in hg, the one big different is that the two failing ones belong to users with Jenkins accounts, the one that works belongs to a user that never created a Jenkins account. The user profiles in the Jenkins installation look fine, the addresses in there seem to be ok. The person that gets the build notification does not have a profile at all. One thing we noticed is that there are two additional user profiles in the file system that follow the pattern FirstName LastName email@address as folder names. These are about a month old now and belong to other users, both of which have a normal profile as well. I don't know if that is related somehow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Peter Becker commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Upgrading to 1.509.1 seems to have resolved this issue for us. The one thing we did notice while looking at this is that it was not actually just adding underscores to the email addresses, it was using the whole Mercurial username with the lesser than/greater than symbols replaced. For example Peter Becker pbec...@example.com should have turned into pbec...@example.com but resulted in Peter Becker pbec...@example.com being used as email address. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
Luis Cardozo commented on JENKINS-17986 CloudTest plug-in does not work on Windows This bug it's open since 16/may, more than half a month, is there any date for its resolution? It's anyone monitoring open issues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
msolnit commented on JENKINS-17986 CloudTest plug-in does not work on Windows Hi Luis. Yes, we do, and I apologize for the delay. I plan to have a fix for this in the next day or two. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
