[JIRA] [gerrit-trigger] (JENKINS-20098) GitClient.getRepository deprecated and broken
kevincai commented on JENKINS-20098 GitClient.getRepository deprecated and broken This issue completely broke my Jenkins system integration with gerrit review. I have to build snapshot version of gerrit plugin from source code (2.12 branch) to make things work. Don't know why not release new version of gerrit plugin to address this issue with high priority. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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
Jeff Burke commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I'm on windows as my previous comment elaborated on. I thought it worthwhile to mention that I no longer have this issue. The disappearance, for me, might be related to increasing my jvm memory and jvm permgen memory. I had noticed in my jenkins.err.log files, I was getting perm gen space and another out of memory error. It is possible that increasing those values has alleviated the symptoms for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
Randall Wood commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX Installing something so that it is writable only as root does not, in any way, imply that that software has root privileges, it in fact, reduces the privalegs that software has. I never said I wanted Jenkins to have more permissions (i.e. run as root), I said I wanted the jenkins service account to not be able to replace Jenkins with arbitrary software (i.e. Jenkins must be installed by a user other than the jenkins service account, who can assume root privileges to do so, but the jenkins service account does not get those privileges). I am fully aware of the limits of physical protection, and I am aware that there are basic minimum good security practices for the physical protection of computing assets, but also know that there is a difference between completely ignoring security concerns, protocols, and regulations as a software provider, or placing the burden of making a decision to operate a computer in an unsafe manner on the user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21166) Environment variables are NOT passed further build steps when using "Block until the triggered projects finish their builds"
ikedam commented on JENKINS-21166 Environment variables are NOT passed further build steps when using "Block until the triggered projects finish their builds" They are available in further build steps, not in downstream builds. For example, think the following case project1 triggers project2. project1: Build Steps: Trigger/Call builds on another project (Block until the triggered projects finish their builds): project2 [A] Run Shell script project2: Build Steps: [B] Run Shell script In this case, TRIGGERED_ will be available in A, not in B. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
cowwoc commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Randall First rule of security: anyone with physical access to a computer can subvert any protection you put in (they can remove the HD and probe it using an external Linux/OSX installation). I don't think it makes sense to protect against such a case. I can't believe you'd want to give Jenkins more permissions than it need (root privileges) because when it inevitably gets exploited (Jenkins is not the most secure software in the world) your entire OS just got exploited as well. I'd much rather run Jenkins under a normal (non-admin) user account. @Sami Tikka: I'm trying to run the iOS simulator under a Jenkins slave under OSX. As far as I know, this requires us to install Jenkins under ~/LaunchAgents. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman updated JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! The zup file contains directory related to the new build jobs Change By: Grigoriy Milman (11/Jan/14 2:16 AM) Attachment: TOOLS.BUILD-JenkinsMSEI.GetBuildResults_TEST.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman edited a comment on JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue? With PTC plugin v1.20 I have disabled the current build job and create then new one based on the config of disabled and started build of new job manually. After that new job was started by an SCM change after each polling interval again, the same as original job. Polling log shows Polling Log This page captures the polling log that triggered this build. Started on Jan 10, 2014 5:06:37 PM Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Preparing to execute si viewproject for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Project contains changes a total of 59 changes! Done. Took 39 sec Changes found By the way, it is not clear what that 59 changes are! It is not file changes! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman edited a comment on JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue? With PTC plugin v1.20 I have disabled the current build job and create then new one based on the config of disabled and started build of new job manually. After that new job was started by an SCM change after each polling interval again. Polling log shows Polling Log This page captures the polling log that triggered this build. Started on Jan 10, 2014 5:06:37 PM Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Preparing to execute si viewproject for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Project contains changes a total of 59 changes! Done. Took 39 sec Changes found By the way, it is not clear what that 59 changes are! It is not file changes! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21260) PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman commented on JENKINS-21260 PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue? With PTC plugin v1.20 I have disabled the current build job and create then new one based on the config of disabled and started build of new job manually. After that new job was started by an SCM change after each polling interval again. Polling log shows Polling Log View as plain text This page captures the polling log that triggered this build. Started on Jan 10, 2014 5:06:37 PM Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Preparing to execute si viewproject for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj Project contains changes a total of 59 changes! Done. Took 39 sec Changes found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-14494) Need to be able to use Flexible Publish in matrix job post-build actions
ikedam closed JENKINS-14494 as Fixed Need to be able to use Flexible Publish in matrix job post-build actions Subversion Tagging Plugin does not support running on matrix parents. Even without Flexible Publisher plugin, your job should not run as expected. Flexible Publisher plugin does not make a publisher who does not support matrix projects support them. Anyway, Create a new ticket. Change By: ikedam (11/Jan/14 1:52 AM) Status: Reopened Closed 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-18394) IncompatibleClassChangeError after upgrade to 1.519
Indra Gunawan commented on JENKINS-18394 IncompatibleClassChangeError after upgrade to 1.519 I am getting same error with most recent Jenkins LTS version 1.509.4 and 1.532.1 Both run: FindBugs Jenkins plugin version 4.10 findbugs maven plugin version 2.5.3 : http://mojo.codehaus.org/findbugs-maven-plugin-2.5.3/ Findbugs version 2.0.2 [INFO] Done FindBugs Analysis java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) 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:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.LinkageError: Failed to load edu.umd.cs.findbugs.detect.TestASM$1 at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:723) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:763) at sun.reflect.GeneratedMethodAccessor38.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) 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:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IncompatibleClassChangeError: Implementing class at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:698) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1068) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at org.apache.tools.ant.AntClassLoader.defineClassFromData(AntClassLoader.java:1128) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:698) at org.apache.tools.ant.AntClassLoader.getClassFromStream(AntClassLoader.java:1299) at org.apache.tools.ant.AntClassLoader.findClassInComponents(AntClassLoader.java:1355) at org.apache.tools.ant.AntClassLoader.findClass(AntClassLoader.java:1315) at org.apache.tools.ant.AntCl
[JIRA] [core] (JENKINS-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Randall: OK, so it can be done, but is it well documented and supported by Xcode? If it's not, lots of programmers are going to try building their iOS projects on Jenkins and will be unhappy. If it just works, then we should be good with the existing installer that sets up a launch daemon. Apparently there are complications because there used to be lots of people asking how to get signing to work when building under Jenkins. (There might still be but I have been away from Jenkins community for a while.) Well, there's the iOS simulator... What do we do about 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] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Josh Santangelo commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows You know, you're right. I was misinterpreting that number. This should work fine for my needs. The issue with explorer not following the links by default is real, though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Jesse Glick commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows lastFailedBuild [-1] lastStableBuild [162] looks right to me. There are no failed builds, which the bogus target -1 indicates. The last stable build is #162, so lastStableBuild links to that (which is itself a symlink to the actual build directory, 2014-01-10_12-58-51). Whether or not the Explorer GUI allows (valid) symlinks to be traversed is a secondary consideration, so long as Jenkins code can read the symlink target. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21094) NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178)
Gregory Boissinot commented on JENKINS-21094 NullPointerException at org.jenkinsci.plugins.xunit.XUnitPublisher.performTests(XUnitPublisher.java:178) Please test with 1.78. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21336) ADMINISTER should not imply RUN_SCRIPTS
Jesse Glick updated JENKINS-21336 ADMINISTER should not imply RUN_SCRIPTS Change By: Jesse Glick (10/Jan/14 10:50 PM) Summary: Confused status of ADMINISTER should not imply RUN_SCRIPTS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21336) Confused status of RUN_SCRIPTS
Jesse Glick created JENKINS-21336 Confused status of RUN_SCRIPTS Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Jan/14 10:47 PM Description: Anyone with RUN_SCRIPTS can go to /script and immediately grant themselves other permissions (or disable security altogether, or worse), so it is strictly more powerful than anything else, including ADMINISTER. Yet the impliedBy link normally grants RUN_SCRIPTS automatically to anyone with ADMINISTER, which is backward. Less obviously, with UPLOAD_PLUGINS you could do much the same, if you spent a moment writing a custom plugin with a malicious initializer and building an hpi file, then installing it dynamically. This leaves a bit more of an audit trail, but only barely. (Maybe SecurityListener should be notified whenever a script is run or a custom plugin uploaded, and by whom?) If (as is common) all these permissions are granted together to administrators and not at all to other users, there is no problem, but the illogical impliedBy relationship together with the relatively innocuous-sounding permission descriptions combine to make even many experienced Jenkins administrators unaware of the risks. At a minimum, the descriptions of these three permissions must clearly state what they allow users to do and the implications. Next, ADMINISTER should no longer be taken to imply RUN_SCRIPTS or UPLOAD_PLUGINS, since such implications give the misleading impression that these are weaker permissions. They should need to be explicitly granted. (There is an unfortunate settings compatibility issue, that authorization strategy configurations which previously granted ADMINISTER explicitly to a user with the expectation that RUN_SCRIPTS would be granted implicitly would after such an update no longer grant RUN_SCRIPTS, since existing strategies typically serialize only granted permissions and make no mention of denied permissions. If popular strategies were fixed to distinguish implicitly from explicitly granted permissions, perhaps they could perform a one-time settings upgrade in which RUN_SCRIPTS were assumed granted to users previously having ADMINISTER.) Possibly RUN_SCRIPTS and UPLOAD_PLUGINS should even be made to imply ADMINISTER, as in effect they do. Note that it is possible to configure a customized system whereby some users get ADMINISTER but not either of the two other permissions mentioned here, as for example *.ci.cloudbees.com does. One of the changes needed is for the authorization strategy to ignore impliedBy for these cases. With CONFIGURE_UPDATECENTER you could perhaps trick someone with ADMINISTER into installing a "trojan horse" the next time they updated something, though you might be stymied by the signature check. There are other permissions which could be used to compromise a stock system, such as Computer.CONFIGURE (with CommandLauncher), or simply having nonzero executors on the master, so such a lockdown has to extend beyond the ACL unless various other operations in Jenkins are made to perform stricter checks. Project: Jenkins Labels: security 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, s
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Josh Santangelo commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows Expanding on the above directory listing, note how the links to build numbers show the target, but the "last*" ones don't. 01/10/2014 02:25 PM . 01/10/2014 02:25 PM .. 01/09/2014 02:09 PM 152 [2014-01-09_14-08-58] 01/09/2014 03:24 PM 153 [2014-01-09_15-24-00] 01/09/2014 03:29 PM 154 [2014-01-09_15-29-22] 01/09/2014 03:44 PM 155 [2014-01-09_15-44-02] 01/09/2014 04:09 PM 156 [2014-01-09_16-09-01] 01/09/2014 05:19 PM 157 [2014-01-09_17-19-02] 01/09/2014 06:29 PM 158 [2014-01-09_18-28-59] 01/10/2014 11:09 AM 159 [2014-01-10_11-09-02] 01/10/2014 12:31 PM 160 [2014-01-10_12-31-32] 01/10/2014 12:49 PM 161 [2014-01-10_12-48-59] 01/10/2014 12:58 PM 162 [2014-01-10_12-58-51] 01/09/2014 02:12 PM 2014-01-09_14-08-58 01/09/2014 03:27 PM 2014-01-09_15-24-00 01/09/2014 03:33 PM 2014-01-09_15-29-22 01/09/2014 03:47 PM 2014-01-09_15-44-02 01/09/2014 04:12 PM 2014-01-09_16-09-01 01/09/2014 05:22 PM 2014-01-09_17-19-02 01/09/2014 06:32 PM 2014-01-09_18-28-59 01/10/2014 11:13 AM 2014-01-10_11-09-02 01/10/2014 12:35 PM 2014-01-10_12-31-32 01/10/2014 12:52 PM 2014-01-10_12-48-59 01/10/2014 01:02 PM 2014-01-10_12-58-51 01/08/2014 10:24 PM archive 01/09/2014 05:22 PM lastFailedBuild [-1] 01/10/2014 01:02 PM lastStableBuild [162] 01/10/2014 01:02 PM lastSuccessfulBuild [162] 01/05/2014 03:14 PM lastUnstableBuild [-1] 01/09/2014 05:22 PM lastUnsuccessfulBuild [-1] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17681) LastSuccessful and LastStable symlinks are invalid under Windows
Josh Santangelo commented on JENKINS-17681 LastSuccessful and LastStable symlinks are invalid under Windows @jesse @joe – My apologies, I'm pretty new to Jenkins and I don't really know how Maven fits in. I'm not specifically doing anything with Maven, but maybe it's involved in all builds? The behavior that I'm seeing is that these symlinks can't be followed in the Windows Explorer GUI without applying that fsutil command above. Further, if I look at them from a command line, I see this: 01/09/2014 05:22 PM lastFailedBuild [-1] 01/10/2014 01:02 PM lastStableBuild [162] 01/10/2014 01:02 PM lastSuccessfulBuild [162] 01/05/2014 03:14 PM lastUnstableBuild [-1] 01/09/2014 05:22 PM lastUnsuccessfulBuild [-1] A regular symlink would show the target of the link instead of a numeric code. I am trying to parse the target in a deployment script. If I should enter this bug elsewhere, let me know. Thanks for responding. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat resolved JENKINS-20935 as Fixed Provide separate monitoring pages for each slave node The PR is merged (except a link) in Subversion at: https://svn.jenkins-ci.org/trunk/hudson/plugins/monitoring, revision 41066 This improves previous UI, with actions in a new page. Change By: evernat (10/Jan/14 10:09 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] [testflight] (JENKINS-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" in the log (using Flexible Publish plugin) that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file containing environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" >TestFlightChanges
echo "\\" >>TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash >>TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" >TestFlightChanges
fi
echo "\\" >>TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" >>TestFlightChanges
echo "TestFlightChangeCount=$i" >> TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits, which are not important for testers.
Note that this relies on the existence of the Jenkins-LastTestFlight tag, so you will need to add the initial tag yourself.
I use the TestFlightChangeCount variable as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
Then just put ${TestFlightChangeLog} in your build notes box for TestFlight and turn off the standar broken change log.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-with-parameters] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker created JENKINS-21335 Forward slashes in a File Parameter's file location cause parameter download links to break Issue Type: Bug Assignee: Unassigned Attachments: testfile.txt Components: build-with-parameters, parameters Created: 10/Jan/14 10:00 PM Description: When a 'File Parameter' is given a 'File Location' with forward slashes to use a subdirectory of the workspace (ex: subfolder/input.txt), the file cannot be downloaded from the build's Parameters page. A blank page appears when the links are clicked. If there are no slashes in the 'File Location' the file will download fine. To Reproduce: - Create New Build Check 'This Build is Parameterized' Add 'File Parameter' with 'file location' = "subfolder/input.txt" Save Run Build using a text file named 'testfile.txt' as parameter. On that Build's info page Click Parameters Try and download using the link Result: --- URL like: http://JenkinsBox/job/fileParameterBuild/1/parameters/parameter/subdir%2Finput.txt/testfile.txt Leading to blank white Page Expected Result: Specified File Downloads Additional Notes: - The file DOES exist on the server: C:\BUILD\.jenkins\jobs\fileParameterBuild\builds\2014-01-10_16-52-47\fileParameters\subdir\input.txt Environment: Jenkins ver. 1.532.1 on apache-tomcat-7.0.39 on Windows 7 Project: Jenkins Labels: jenkins file-parameter parameter parameter-download Priority: Major Reporter: Eric Anker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" >TestFlightChanges
echo "\\" >>TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash >>TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" >TestFlightChanges
fi
echo "\\" >>TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" >>TestFlightChanges
echo "TestFlightChangeCount=$i" >> TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
Note that this relies on the existence of the tag, so you will need to add the initial tag yourself.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-20503) Appending changlog says no changes if a build failed
Dale King
edited a comment on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:\\" >TestFlightChanges
echo "\\" >>TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log -1 "--format=format:$i. %s - %an\n" $hash >>TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build\\" >TestFlightChanges
fi
echo "\\" >>TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" >>TestFlightChanges
echo "TestFlightChangeCount=$i" >> TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-20503) Appending changlog says no changes if a build failed
Dale King
commented on JENKINS-20503
Appending changlog says no changes if a build failed
I have a complicated workaround that I am using:
I have a Conditional Post Build Task that tags the last successful testflight push that is conditional on the presence of the text "Testflight Configuration Link:" that runs this script to tag the last build:
/usr/bin/git tag -f "Jenkins-LastTestFlight"
/usr/bin/git push -f ${GIT_URL} "Jenkins-LastTestFlight"
I have a build step that creates a property file to build up to inject as environment variables that contains the changes since that tag and is injected using the EnvInject plugin in a following step. That script looks like this:
echo "TestFlightChangeLog:Code Changes:" >TestFlightChanges
echo "" >>TestFlightChanges
i=0
for hash in `git log Jenkins-LastTestFlight..HEAD --pretty=format:%H`
do
shopt -s nocasematch
if [[ ! `git log -1 --pretty=format:%B $hash` =~ @NoTestFlight ]]
then
i=$[i+1];
git log 1 "-format=format:$i. %s - %an\n" $hash >>TestFlightChanges
fi
done
if [ $i == 0 ]
then
echo "TestFlightChangeLog:No Significant Code Changes Since Previous Build" >TestFlightChanges
fi
echo "" >>TestFlightChanges
echo "Built from git commit ${GIT_COMMIT}" >>TestFlightChanges
echo "TestFlightChangeCount=$i" >> TestFlightChanges
This creates a file called TestFlightChanges which I load with envinject plugin. Note I have a flag that can be added to a commit comment @NoTestFlight which will exclude the comment from being included in the TestFlight log. This is used for things like refactoring commits.
I use the TestFlightChangeCount as a condition for running the TestFlight post build step. So it only uploads to TestFlight if there are significant changes.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [openid] (JENKINS-14843) OpenID SSO should use POST to submit details to google apps endpoint
John Engelman commented on JENKINS-14843 OpenID SSO should use POST to submit details to google apps endpoint Just tried to disable using the property and there is a missing '.' in the code that looks up the property. Using the malformed -Dhudson.plugins.openid.impl.TeamsExtensiondisable=true does work though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith resolved JENKINS-21184 as Fixed SSO Appears to be Broken See my comment. id10t error. Change By: Jared Griffith (10/Jan/14 9:38 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Kanstantsin Shautsou commented on JENKINS-21184 SSO Appears to be Broken Thanks, part of code related to SSO now more optional. I'will add note to changelog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Jared Griffith commented on JENKINS-21184 SSO Appears to be Broken Oh man, I guess I didn't have the SSO check box clicked. Nevermind, it's working fine now. My bad. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-20871) Unable to login with plugin v1.6
Kanstantsin Shautsou edited a comment on JENKINS-20871 Unable to login with plugin v1.6 Could you try remove group entries and login? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-21184) SSO Appears to be Broken
Kanstantsin Shautsou commented on JENKINS-21184 SSO Appears to be Broken Does "test connection" in jenkins configuration success? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-20871) Unable to login with plugin v1.6
Kanstantsin Shautsou commented on JENKINS-20871 Unable to login with plugin v1.6 Could you try remove group entries and try login? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
Randall Wood commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX @Sami Tikka: The only need addressed by running Jenkins in a GUI login session is running automated tests in the iOS simulator. Code signing for iOS and OS X builds can be done entirely from the CLI, even remotely over SSH. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
Randall Wood commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX All login plist/hooks can be disabled when accessing the console of a OS X system that is being restarted. I know that a number of users of Jenkins on OS X are using Jenkins on systems that may be installed in areas not under the administrator's physical control. This is a real concern for many OS X developers who are not completely independent. Software that exists in a user's directory is always easier to exploit than software installed using root privileges. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX We might want to gather some requirements or user stories for the Jenkins Mac installer. My humble opinion is the only people who want to run Jenkins on Mac are iOS developers. (And Mac developers but there are few of those and their needs might be very similar to iOS developers.) People who do cross-platform development and need to build their software for multiple platforms need to set up Windows, Mac and Linux build servers. They will probably run Jenkins master either on Windows or Linux and run a slave on Mac. Thus we do not need to worry about these people. The iOS developers have some special needs (which I do not know exactly because I haven't done any real development for iOS so feel free to add to the list or set me straight.) Builds must be codesigned. The developer certificate resides in the developer's keychain. The keychain is only accessible within the developer's GUI login session. Automated tests need to execute iOS simulator which is a GUI app. GUI apps can only run in GUI login session. It seems to me the most common use cases for Jenkins master on Mac require that Jenkins has access to GUI login session. This means Jenkins master must be executed either as a launch agent (which are meant for background processes) or within a context of a GUI app wrapper (if we want something visible in Dock or menu bar.) The security aspect of having a Jenkins master with a logged-in user with a GUI session must be addressed separately. I do not believe we can provide a solution that fits everyone's needs. Maybe we can just give hints on how to solve it: put the Mac in a locked room, set up screensaver with short timeout or the trick mentioned above in the ticket description or maybe something else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21313) Anonymous users can configure and delete PrioritySorter JobGroups
Magnus Sandberg commented on JENKINS-21313 Anonymous users can configure and delete PrioritySorter JobGroups Yes it does - I'm also considering defining custom permissions for this do you think that would make sense? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21237) Jenkins should use LaunchAgents under OSX
Sami Tikka commented on JENKINS-21237 Jenkins should use LaunchAgents under OSX When the user requests the Installer to install something for all users, it prompts the user for admin password and elevates permissions to root, making it possible to install Jenkins as a launch daemon. But this is only relevant if we want to keep the possibility of installing as launch daemon. But like I said, I do not look forward to tweaking PackageMaker to achieve many different ways of installing Jenkins to suite everyone's needs. IMHO the PackageMaker based installer is only suitable for one kind of installation with no options at all. (The current Installer has a few options but I'm sure no-one has found them or uses those.) If a more customizable installer is required, it must be based on something else. My favorite is a simple AppleScript application. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Marko Macek edited a comment on JENKINS-12480 Build step that runs multiple jobs in parallel, and blocks until all are complete Currently, one can run parallel jobs when specifying them in a single build step/"Projects to build". But this requires them to have the same parameters (except factory ones). But when specifying multiple "Projects to build" within a single build step, there's no option "Block until the triggered projects finish their builds" that would wait for all jobs of this build step. I'll be trying "File Generator Parameter Factory" now Doesn't work for me, because in many cases I need to run different 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] [testng] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Gavin Gray commented on JENKINS-20985 TestNG plugin should has a possibility to use thresholds for failed tests In our case, we have several thousand functional tests and an engineering organization of roughly 150 people that contribute to them. That said, we ocasionally have a an intermittent failure or two that we'd like to deal with in isolation, but we don't want the build to fail for hours while the fix is on its way. We're okay with tolerating roughly 1% of failures, but really nothing more. Obviously, this is an opt-in feature, so I'm not sure how it could do anything but benefit others who have a similar use case as us. Fundamentally I agree with you that we might not want to ignore a certain percentage of failures, but each organization is different, so shouldn't we let them make that decision? This feature works similarly to the xUnit-plugin and we could use that instead, but it currently doesn't have TestNG support. We'd prefer to continue to use the TestNG plugin instead of extending xUnit to support TestNG. Finally, I think that the health extension a la emma is good, but it's not as valuable for our purposes as success vs. unstable vs. failure. Thanks for responding. Before I move forward, I'll let Nikolay share his experiences too (he originally filed the feature request). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-12480) Build step that runs multiple jobs in parallel, and blocks until all are complete
Marko Macek commented on JENKINS-12480 Build step that runs multiple jobs in parallel, and blocks until all are complete Currently, one can run parallel jobs when specifying them in a single build step/"Projects to build". But this requires them to have the same parameters (except factory ones). But when specifying multiple "Projects to build" within a single build step, there's no option "Block until the triggered projects finish their builds" that would wait for all jobs of this build step. I'll be trying "File Generator Parameter Factory" now... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testng] (JENKINS-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Nalin Makar commented on JENKINS-20985 TestNG plugin should has a possibility to use thresholds for failed tests I am not really sold on this feature. It's not right to mark a build as successful based on a percentage as it could mislead the user. E.g. If the threshold is set at 95% and if 96% tests pass, the build would be marked success, but the failing 4% tests could be the most important tests of the regression. Do you have a concrete use case in mind? What is the issue with a build being marked unstable? IMO, implementing JENKINS-9838, in some ways similar to how Emma Coverage Report plugin works would be better. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
G. Ann Campbell commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction' After upgrading to 2.5 I see 1) old data warnings 2) loss of build badges This happens on all freestyle jobs I checked. (I don't have any Maven jobs). I roll back to 2.4 & both conditions reverse. I'm on Jenkins ver. 1.513, on CentOS. I'm not using Build Trigger Badge Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21334) Groovy html template failing on this line: def junitResultList = it.JUnitTestResult
Marcus Mosttler created JENKINS-21334 Groovy html template failing on this line: def junitResultList = it.JUnitTestResult Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 10/Jan/14 5:50 PM Description: After updating to email-ext 2.37 from 2.27.1 the groovy html template sent at the end of our builds started failing, not sending. Using the Test Email Template feature I tested the template and found that it failed with msg on the page of [object Object] and nothing in the logs. Removing the it.JUnitTestResult portion of the line (def junitResultList = it.JUnitTestResult) allowed the email to render successfully. Environment: Windows XP, Jenkins 1.546, email-ext 2.37 Project: Jenkins Priority: Major Reporter: Marcus Mosttler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21221) Add option for backing up of plugin archives, as well as arbitrary files
Thomas Fürer commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files UNSTABLE: Integrated in thinBackup #91 JENKINS-21221: Add option for backing up of plugin archives, as well as arbitrary files. (pmatignon: e33602363860377849015bbb1939f604304813a9) src/main/webapp/help/help-backupAdditionalFiles.html src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java src/main/webapp/help/help-backupPlugins.html src/main/resources/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink/backupsettings.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21314) Stack trace displayed on web page when attempting to configure PrioritySorter plugin
Magnus Sandberg commented on JENKINS-21314 Stack trace displayed on web page when attempting to configure PrioritySorter plugin The problem is this part of the xml: true 0 Where the strategy list has one empty item. Replace this section with: false Now it should load. I'm trying to reproduce this xml being created but failed so far let me know if this happens again ... I will investigate further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21221) Add option for backing up of plugin archives, as well as arbitrary files
SCM/JIRA link daemon commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files Code changed in jenkins User: Patrice Matignon Path: src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/resources/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink/backupsettings.jelly src/main/webapp/help/help-backupAdditionalFiles.html src/main/webapp/help/help-backupPlugins.html http://jenkins-ci.org/commit/thin-backup-plugin/e33602363860377849015bbb1939f604304813a9 Log: JENKINS-21221: Add option for backing up of plugin archives, as well as arbitrary files. Proposed implementation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-21221) Add option for backing up of plugin archives, as well as arbitrary files
SCM/JIRA link daemon commented on JENKINS-21221 Add option for backing up of plugin archives, as well as arbitrary files Code changed in jenkins User: Thomas Fuerer Path: src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/resources/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink/backupsettings.jelly src/main/webapp/help/help-backupAdditionalFiles.html src/main/webapp/help/help-backupPlugins.html http://jenkins-ci.org/commit/thin-backup-plugin/728bc2534097c71a7b398de99808dd1d820ec7cc Log: Merge pull request #4 from patricematignon/master JENKINS-21221: Add option for backing up of plugin archives, as well arbitrary files Compare: https://github.com/jenkinsci/thin-backup-plugin/compare/0900a7ba03c0...728bc2534097 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-21327) Offering access to users with RUN_SCRIPTS is redundant
Dominik Bartholdi commented on JENKINS-21327 Offering access to users with RUN_SCRIPTS is redundant If you'r right and RUN_SCRIPTS has more power then ADMINISTRATOR, then I must say that RUN_SCRIPT is not well documented and a very very misleading name. But anyway - I guess if you say so, then you probably are right and sure this must be changed/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] [rich-text-publisher] (JENKINS-21333) Variable injected with EnvInject not supported
herve martin created JENKINS-21333 Variable injected with EnvInject not supported Issue Type: Bug Assignee: Unassigned Components: rich-text-publisher Created: 10/Jan/14 5:23 PM Description: It looks like variables injected with EnvInject plugin are not resolved by the rich-text-publisher Project: Jenkins Priority: Major Reporter: herve martin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fortify360] (JENKINS-21332) Fortify Upload does not work in Jenkins >= 1.519
Martin Kutter commented on JENKINS-21332 Fortify Upload does not work in Jenkins >= 1.519 I forgot to mention: I reproduced the issue with Jenkins 1.532.1 LTS fortify360-plugin 2.4 fortify360-plugin 3.8 fortify360-plugin 3.9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fortify360] (JENKINS-21332) Fortify Upload does not work in Jenkins >= 1.519
Martin Kutter created JENKINS-21332 Fortify Upload does not work in Jenkins >= 1.519 Issue Type: Bug Assignee: samngms Components: fortify360 Created: 10/Jan/14 5:05 PM Description: On uploading a FPR to a fortify 360 server, the plugin writes the following error message into the buildlog: Error uploading to F360 Server: https://fortify...de/ssc java.lang.ClassNotFoundException: org.jvnet.hudson.plugins.fortify360.fortifyclient.FortifyClient at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1484) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1329) at org.jvnet.hudson.plugins.fortify360.FortifyClientClassLoader.findClass(FortifyClientClassLoader.java:196) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:760) at java.lang.ClassLoader.loadClass(ClassLoader.java:737) at java.lang.ClassLoader.loadClass(ClassLoader.java:707) at org.jvnet.hudson.plugins.fortify360.FPRPublisher.invokeFortifyClient(FPRPublisher.java:266) at org.jvnet.hudson.plugins.fortify360.FPRPublisher.perform(FPRPublisher.java:178) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:224) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:166) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.model.Run.run(Run.java:1612) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:111) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) This is probably the same as https://github.com/hudson3-plugins/fortify360-plugin/issues/1 , though the linked report does not explain the error. I think the error is due to this change https://github.com/jenkinsci/maven-plugin/commit/97b452ecc95a5546c471198126834f770a63a249 implemented in Jenkins-1.519 due to https://issues.jenkins-ci.org/browse/JENKINS-15120. As a result of this change, the plugin's resources are no longer exploded into WEB-INF/classes, but kept in a classes.jar in the plugin's WEB-INF/lib directory. Thus, the FortifyClientClassloader creates a URL similar to jar:file:/var/lib/jenkins/plugins/fortify360/WEB-INF/lib/classes.jar!/fortifyclient-2.6.5.jar and adds it to it's URL list. On loading the class, the FortifyClientClassLoader uses the methods from the default Java Classloader - which does not support nested jars. This results in the above error message. I think the strategy described here could resolve the issue: http://www.ibm.com/developerworks/library/j-onejar/ Project: Jenkins Priority: Blocker Reporter: Martin Kutter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21182) EC2 Plugin: EC2 instance starts but waits forever
Mark Fink commented on JENKINS-21182 EC2 Plugin: EC2 instance starts but waits forever I have setup a EC2 machine at us-east-1 region with EC2-Classic. Jenkins now can ssh into the machine without any problems. I can't wait for this patch to be released. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-20985) TestNG plugin should has a possibility to use thresholds for failed tests
Gavin Gray updated JENKINS-20985 TestNG plugin should has a possibility to use thresholds for failed tests I have a working implementation. See attached screenshot. Just need to add some validation and I'll submit a pull request. Change By: Gavin Gray (10/Jan/14 5:02 PM) Assignee: Nalin Makar Gavin Gray Attachment: Screen Shot 2014-01-10 at 12.00.38 PM.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] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Eric Long commented on JENKINS-15128 Renaming job doesn't work with Git Thanks Frédéric. I will try this shortly. I appreciate your help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-21331) Improve usage of github permissions to be able to assign individual permissions to users or teams
Leandro Lucarella created JENKINS-21331 Improve usage of github permissions to be able to assign individual permissions to users or teams Issue Type: New Feature Affects Versions: current Assignee: Sam Kottler Components: github-oauth Created: 10/Jan/14 4:04 PM Description: Permissions granularity when using the plugin is extremely limited when using the plugin. It would be nice if the plugin could also provide some kind of matrix to set permissions to individual users or github teams (ideally). Also it would be extremely useful if you could link any job to a github project and map github permissions to job permissions. Users with pull access should only see the results, users with push access should also be able to execute the job and users with admin access should be able to edit the job's configuration. Project: Jenkins Labels: github permissions Priority: Major Reporter: Leandro Lucarella This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18137) null value for project workspace location
Antoine Beaupre commented on JENKINS-18137 null value for project workspace location I can reproduce with version 0.19 of the plugin as well. This is Jenkins 1.546 on Debian Wheezy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18137) null value for project workspace location
Antoine Beaupre started work on JENKINS-18137 null value for project workspace location Change By: Antoine Beaupre (10/Jan/14 3:50 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-18137) null value for project workspace location
Antoine Beaupre stopped work on JENKINS-18137 null value for project workspace location Change By: Antoine Beaupre (10/Jan/14 3:50 PM) Status: In Progress 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] [ws-cleanup] (JENKINS-18137) null value for project workspace location
Antoine Beaupre commented on JENKINS-18137 null value for project workspace location I also see this, using version 0.15 of the workspace cleanup plugin. I'll try to update to see if there will be some changes. (sorry for the noise) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Greg Huber created JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 10/Jan/14 3:38 PM Description: Hello, On the latest version 1.546 for a maven build I get this error: Started by user anonymous ln builds/lastSuccessfulBuild /home/dev/.jenkins/jobs/MyBuild/lastSuccessful failed java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:241) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1116) at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.Util.createSymlinkJava7(Util.java:1146) at hudson.Util.createSymlink(Util.java:1064) at hudson.model.Run.createSymlink(Run.java:1783) at hudson.model.Run.updateSymlinks(Run.java:1764) at hudson.model.Run.execute(Run.java:1676) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ln builds/lastStableBuild /home/dev/.jenkins/jobs/MyBuild/lastStable failed java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastStable at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:241) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1116) at sun.reflect.GeneratedMethodAccessor313.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.Util.createSymlinkJava7(Util.java:1146) at hudson.Util.createSymlink(Util.java:1064) at hudson.model.Run.createSymlink(Run.java:1783) at hudson.model.Run.updateSymlinks(Run.java:1765) at hudson.model.Run.execute(Run.java:1676) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Building in workspace /home/dev/.jenkins/jobs/MyBuild/workspace Updating svn://myweb.com/repos/Events/trunk at revision '2014-01-10T15:06:09.745 +' At revision 1974 WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior. no change for svn://myweb.com/repos/Events/trunk since the previous build Parsing POMs It does not seem to get the latest update from the svn. Switching back to 1.544 fixed the issue. Cheers Greg Environment: tomcat/centos Project: Jenkins Priority: Major Reporter: Greg Huber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit ht
[JIRA] [email-ext] (JENKINS-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport
Alex Earl commented on JENKINS-21308 java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport Yeah, it's possible its the same issue. Not sure what is going on yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Daniel Beck resolved JENKINS-20898 as Cannot Reproduce SVN post commit hook not working after update to 1.542 Change By: Daniel Beck (10/Jan/14 3:28 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [batch-task] (JENKINS-21329) Can't do git commands in Jenkins
pedro reis created JENKINS-21329 Can't do git commands in Jenkins Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: batch-task Created: 10/Jan/14 3:27 PM Description: Have Jenkins v1.532.1. Jenkins master service is running on a Linux and the master of the job (where it fails) is a Windows that has a Jenkins slave service configured to log on with the same user account that works ok when running directly on the PC. This occurs with "windows batch command" or using the source code management git (plugin v2.01). I've inserted a ping to prove that it is not a DNS issue: " Started by user anonymous Building remotely on Windows_vs100_slave in workspace c:\h\workspace\GIT_test [GIT_test] $ cmd /c call C:\DOCUME~1\user\LOCALS~1\Temp\hudson354076269384288705.bat c:\h\workspace\GIT_test>ping host Pinging host [192.168.1.43] with 32 bytes of data: Reply from 192.168.1.43: bytes=32 time<1ms TTL=64 Reply from 192.168.1.43: bytes=32 time<1ms TTL=64 Reply from 192.168.1.43: bytes=32 time<1ms TTL=64 Reply from 192.168.1.43: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.43: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms c:\h\workspace\GIT_test>cd c:\h\workspace\GIT_test c:\h\workspace\GIT_test>REM make sure nothing is hidden c:\h\workspace\GIT_test>attrib -H /S File not found - C:\h\workspace\GIT_test*.* c:\h\workspace\GIT_test>REM recursively remove child folders c:\h\workspace\GIT_test>for / %X in (.) do rd /s /q "%X" c:\h\workspace\GIT_test>REM delete files in root folder c:\h\workspace\GIT_test>del /q /f * c:\h\workspace\GIT_test>REM get the source c:\h\workspace\GIT_test>git clone git@host:/opt/git/common/mde.git Cloning into 'mde'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. c:\h\workspace\GIT_test>exit 128 Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE " Environment: Jenkins Master service at Linux. Jenkins Slave services at windows. Project: Jenkins Priority: Blocker Reporter: pedro reis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
André Schramm commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Sorry for kicking in late. I meanwhile updated to Jenkins 1.546 and everything works fine, so this issue can be closed I guess. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21308) java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport
Tomasz Uss commented on JENKINS-21308 java.lang.NoClassDefFoundError: hudson/maven/reporters/SurefireAggregatedReport Is it possible to result from JENKINS-21326? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco commented on JENKINS-9031 Performance plugin lock out Jenkins while running Performance Trend You are right, I didn't realize that your patch was done with git-diff. Merged: https://github.com/jenkinsci/performance-plugin/commits/master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
Manuel Carrasco resolved JENKINS-9031 as Fixed Performance plugin lock out Jenkins while running Performance Trend Fixed in git Change By: Manuel Carrasco (10/Jan/14 3:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21328) Support for StabilityTestDataPublisher plugin
Kenny Moens
created JENKINS-21328
Support for StabilityTestDataPublisher plugin
Issue Type:
Bug
Assignee:
Justin Ryan
Components:
job-dsl-plugin
Created:
10/Jan/14 3:15 PM
Description:
Please provide support to intregrate the StabilityTestDataPublisher plugin. It provides an overview of the JUnit results.
I've used this custom extension to the DSL to integrate it:
PublisherContext.metaClass.junit = { String pattern, boolean testStability = true,
boolean retainLongStdout = true, boolean allowClaimingOfFailedTests = false, boolean publishTestAttachments = false ->
def nodeBuilder = new NodeBuilder()
Node archiverNode = nodeBuilder.'hudson.tasks.junit.JUnitResultArchiver' {
testResults pattern
keepLongStdio retainLongStdout ? 'true' : 'false'
testDataPublishers {
if (allowClaimingOfFailedTests) {
'hudson.plugins.claim.ClaimTestDataPublisher' ''
}
if (publishTestAttachments) {
'hudson.plugins.junitattachments.AttachmentPublisher' ''
}
if (testStability) {
'de.esailors.jenkins.teststability.StabilityTestDataPublisher' ''
}
}
}
publisherNodes << archiverNode
}
Project:
Jenkins
Priority:
Major
Reporter:
Kenny Moens
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-21327) Offering access to users with RUN_SCRIPTS is redundant
Jesse Glick commented on JENKINS-21327 Offering access to users with RUN_SCRIPTS is redundant Or Checking this option, allows users who have the 'RunScript' permission to change a scriptler scripts before executing it. A user can seriously harm your system and compromise your security! which makes no sense, since a user with RUN_SCRIPTS can trivially compromise any kind of security without any help from the Scriptler plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-21327) Offering access to users with RUN_SCRIPTS is redundant
Jesse Glick created JENKINS-21327 Offering access to users with RUN_SCRIPTS is redundant Issue Type: Bug Assignee: Dominik Bartholdi Components: scriptler Created: 10/Jan/14 3:06 PM Description: From my reading of the UI and wiki, Scriptler seems to allow people with ADMINISTER to always run scripts, and those with RUN_SCRIPTS to do so only if additionally authorized. If true, this is backwards, as RUN_SCRIPTS is strictly more powerful than ADMINISTER. (And for Scriptler to be useful in a large secured installation, someone with RUN_SCRIPTS needs to be able to offer scripts for use by users who lack either permission.) Is this really true, or does the UI just give this false impression? For example Allow execution by user with 'RunScripts' permission Project: Jenkins Labels: security 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] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Uh oh. Based on this log, it does indeed look like Jenkins is constantly trying to restart the VM. Let me investigate further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-16352) Add ability to specify parameters in the crontab
James Wilson commented on JENKINS-16352 Add ability to specify parameters in the crontab Here's a first pass at solving this. I have the approach that most additions should be plugins. When I looked at the Trigger extension point I was sceptical that this should be a plugin. The CronTab and CronTabList classes did not want to cooperate. Then there is the is the configuration. In order to make the parameterized schedule enabled only for projects with parameters I seem to have forced the user to re-enter the config screen after setting parameters. This does not flow well. Now that I've implemented it as a plugin, I suspect it should be in core. Else the Trigger extension point needs some refactoring to support different kinds of triggers. It's my opinion that the Trigger was nearly already in need of refactoring. This is evidenced by Trigger.getSpec(), checkTriggers is static but other Trigger implementations may not be the least bit interested in CronTabList. For my part, I needed to extend CronTab to support parameters stored with each. I'm interested to hear the opinion of others closer to, with more experience in, the jenkins-core. https://github.com/jwmach1/parameterized-scheduler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Daniel Beck commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Looks like the pattern to detect this is still too restrictive. FWIW I didn't know the tool ever is called just look. https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/hudson/scm/SubversionRepositoryStatus.java#L98 André Schramm: Please consider responding to the comments asking for more information, as we're unable to 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] [performance-plugin] (JENKINS-9031) Performance plugin lock out Jenkins while running Performance Trend
SCM/JIRA link daemon commented on JENKINS-9031 Performance plugin lock out Jenkins while running Performance Trend Code changed in jenkins User: Michel Marti Path: src/main/java/hudson/plugins/performance/HttpSample.java src/main/java/hudson/plugins/performance/JMeterParser.java src/main/java/hudson/plugins/performance/PerformanceReport.java src/main/java/hudson/plugins/performance/UriReport.java http://jenkins-ci.org/commit/performance-plugin/be7401b0284466b9f10815d5215e01d33771528f Log: Cache preprocessed JMeter Reports (JENKINS-9031) Instead of parsing all available JTL results upon each request, we now save the parsed report as a serialized Java object for later reuse. The file will be next to the JTL file with a '.serialized' suffix. Additionally the report also gets added to a in-memory cache with a maximum capacity of 100 reports. This considerably speeds up the performance trend display. Signed-off-by: Michel Marti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github-oauth] (JENKINS-20845) Github Authorization Settings, users in "Participant in Organization" not given READ
Leandro Lucarella commented on JENKINS-20845 Github Authorization Settings, users in "Participant in Organization" not given READ Oh, so THAT was the problem! All the members in my organization are not public, once I changed them to be public it worked as expected! So I'm not experiencing this issue anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition help says separator spaces are used, commas are required
Mark Waite updated JENKINS-21305 elastic axis definition help says separator spaces are used, commas are required Change By: Mark Waite (10/Jan/14 2:01 PM) Description: If I want to run a multi-configuration job on all windows machines (as identified by the NodeLabeler plugin), elastic axis makes that work very well. All machines with that label are used to execute the job.If I want to run a multi-configuration job on all Debian machines (as identified by the NodeLabeler plugin), elastic axis makes that work very well. All machines with that label are used to execute the job.If I want to run a multi-configuration job on all Debian machines and on all windows machines (as identified by the NodeLabeler plugin), the plugin help suggests I can place a space separated list of labels. When I place "Debian windows" in the list of labels, no nodes are selected.It appears the space separated list of labels is not being evaluated. The source code expects a comma to separate labels in a list of labels. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21326) email-ext.jar might need to be rebuilt in email-ext 2.37
Tomasz Uss created JENKINS-21326 email-ext.jar might need to be rebuilt in email-ext 2.37 Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 10/Jan/14 1:58 PM Description: After upgrading jenkins and updating plugins to the latest versions in my jenkins log I see: WARNING: Failed to scout hudson.plugins.emailext.JellyTemplateConfig$JellyTemplateConfigProvider java.lang.InstantiationException: /home/jenkins/.jenkins/plugins/email-ext/WEB-INF/lib/email-ext.jar might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.emailext.JellyTemplateConfig$JellyTemplateConfigProvider at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:310) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:309) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.getComponents(ExtensionList.java:149) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsIterator(ExpressionSupport.java:101) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:89) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.App
[JIRA] [flexible-publish] (JENKINS-14494) Need to be able to use Flexible Publish in matrix job post-build actions
WH reopened JENKINS-14494 Need to be able to use Flexible Publish in matrix job post-build actions Jenkins LTS 1.532.1 Flexible publisher plugin 0.12 Jenkins Subversion Tagging Plugin 1.16 I have a matrix job with 2 labels and the flexible publisher as post build action. I checked the check butten "Condition for matrix aggregation", set "Run on parent?" to "Always" and set "Perform subversion tagging on successful build" as action. Result: The matrix parent job performs no tagging! The parent jobs console output even shows no output from the flexible publisher plugin. Originally I hoped the new matrix support will solve this problem: https://issues.jenkins-ci.org/browse/JENKINS-9683 Change By: WH (10/Jan/14 2:01 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21137) git fetch does not have support for "--progress" option in 1.7.x version of git client binary
dev @ doxo.com commented on JENKINS-21137 git fetch does not have support for "--progress" option in 1.7.x version of git client binary That is precisely our situation. We are using Ubuntu 10.04 LTS, and therefore are still using Git 1.7.0.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [external-resource-dispatcher] (JENKINS-17444) NoopExternalResourceManager fails to timeout reservations of resources on the master build node
SCM/JIRA link daemon commented on JENKINS-17444 NoopExternalResourceManager fails to timeout reservations of resources on the master build node Code changed in jenkins User: arleyristar Path: src/main/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/cli/ErCliUtils.java src/test/java/com/sonyericsson/jenkins/plugins/externalresource/dispatcher/utils/NoopExternalResourceManagerJenkinsTest.java http://jenkins-ci.org/commit/external-resource-dispatcher-plugin/4686f2e8dabae23b29fd7f0bcd9e1f984dc55ead Log: Fixing reservation in master. Related to the Issue JENKINS-17444. Added a Test Case too. "WARNING: Failed to timeout a reservation of 1234 on node !" was caused by trying to access the master node with his name. getNodeName() in master, returns "" and cannot be found with Hudson.getInstance().getNode(nodeName); This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21325) Strange "Disk Usage" message.
Tom Brus commented on JENKINS-21325 Strange "Disk Usage" message. using jenkins 1.546 BTW This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21325) Strange "Disk Usage" message.
Tom Brus created JENKINS-21325 Strange "Disk Usage" message. Issue Type: Bug Affects Versions: current Assignee: Lucie Votypkova Attachments: Screen_Shot_2014-01-10_at_14_32_55-2.png Components: disk-usage Created: 10/Jan/14 1:39 PM Description: The disk usage message is too long and uses #bytes instead of human readable numbers (k/M/G). The long message messes up the rest of the page. See included screenshot. (using plugin version 0.23) Project: Jenkins Priority: Major Reporter: Tom Brus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition help says separator spaces are used, commas are required
Mark Waite updated JENKINS-21305 elastic axis definition help says separator spaces are used, commas are required Change By: Mark Waite (10/Jan/14 1:33 PM) Summary: elastic axis definition multiple labels are separated by commas, though helps help says separator spaces are used , commas are required This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17570) not copying artfacts from another job using specifc build number passed by environment variable.
Alexis Morelle commented on JENKINS-17570 not copying artfacts from another job using specifc build number passed by environment variable. You can pass it as a job parameter. For example you'd have a String parameter for the job named "BUILD_NUMBER" and in the specific build number field you reuse that with "$BUILD_NUMBER". Varaibles are expanded so I don't see why it wouldn't work with envinject. From what I see, inject a variable named "DOWNSTREAM_JOB_BUILD_NUMBER1" and affect it with "$DOWNSTREAM_JOB_BUILD_NUMBER". [EnvInject] - Injecting as environment variables the properties content DOWNSTREAM_JOB_BUILD_NUMBER1=$DOWNSTREAM_JOB_BUILD_NUMBER So the variable can be expanded in "$DOWNSTREAM_JOB_BUILD_NUMBER1" which is not a build number. Moreover, if you only injected this, there's no "$DOWNSTREAM_JOB_BUILD_NUMBER" variable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition multiple labels are separated by commas, though helps says separator spaces are used
Mark Waite updated JENKINS-21305 elastic axis definition multiple labels are separated by commas, though helps says separator spaces are used Change By: Mark Waite (10/Jan/14 1:31 PM) Summary: elastic axis definition cannot contain multiple labels are separated by commas , though helps says that is allowed separator spaces are used This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition cannot contain multiple labels, though helps says that is allowed
Mark Waite edited a comment on JENKINS-21305 elastic axis definition cannot contain multiple labels, though helps says that is allowed Help text is incorrect. Multiple labels should be separated by commas. The help text might also be improved by additional examples like the availability of the "not" operator (exclamation point). I wanted to build on all nodes except my raspberrypi. I entered !raspberrypi as the label definition and it correctly added all nodes which are not labeled "raspberrypi". Pull request has been submitted to update the help text to match the implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-12869) Maven Build fails when integration/system test executed with failsafe fails.
puce commented on JENKINS-12869 Maven Build fails when integration/system test executed with failsafe fails. +1 Any news on this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition cannot contain multiple labels, though helps says that is allowed
Mark Waite edited a comment on JENKINS-21305 elastic axis definition cannot contain multiple labels, though helps says that is allowed Help text is incorrect. Multiple labels should be separated by commas. The help text might also be improved by additional examples like the availability of the "not" operator (exclamation point). I wanted to build on all nodes except my raspberrypi. I entered !raspberrypi as the label definition and it correctly added all nodes which are not labeled "raspberrypi". Pull request 1 has been submitted to update the help text to match the implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [elastic-axis] (JENKINS-21305) elastic axis definition cannot contain multiple labels, though helps says that is allowed
Mark Waite resolved JENKINS-21305 as Fixed elastic axis definition cannot contain multiple labels, though helps says that is allowed Help text is incorrect. Multiple labels should be separated by commas. The help text might also be improved by additional examples like the availability of the "not" operator (exclamation point). I wanted to build on all nodes except my raspberrypi. I entered !raspberrypi as the label definition and it correctly added all nodes which are not labeled "raspberrypi". Pull request has been submitted to update the help text to match the implementation. Change By: Mark Waite (10/Jan/14 1:28 PM) Status: In Progress 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] [elastic-axis] (JENKINS-21305) elastic axis definition cannot contain multiple labels, though helps says that is allowed
Mark Waite started work on JENKINS-21305 elastic axis definition cannot contain multiple labels, though helps says that is allowed Change By: Mark Waite (10/Jan/14 1:11 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21324) Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart
peter ducai commented on JENKINS-21324 Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart are you suggesting that you 'cannot close browser while uploading of plugins (or any other task) is going on' ? Isn't all work done on backend (jenkins itself) ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21324) Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart
Oleg Nenashev commented on JENKINS-21324 Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart "Failed to write to client" usually means that somebody has closed the page without waiting for its full load. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21324) Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart
peter ducai created JENKINS-21324 Jenkins 1.532.1 (LTS) on Ubuntu 12.04, getting org.apache.commons.jelly.JellyTagException after updating plugins without restart Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.log Components: core Created: 10/Jan/14 10:50 AM Description: not able to manage jenkins after update of plugins without restart, instead just getting many JellyTagException Due Date: 10/Jan/14 12:00 AM Environment: NAME="Ubuntu" VERSION="12.04.3 LTS, Precise Pangolin" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu precise (12.04.3 LTS)" VERSION_ID="12.04" java -version java version "1.6.0_27" OpenJDK Runtime Environment (IcedTea6 1.12.6) (6b27-1.12.6-1ubuntu0.12.04.4) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) Project: Jenkins Priority: Major Reporter: peter ducai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21299) SVN post commit hook not triggering any jobs
er gt resolved JENKINS-21299 as Not A Defect SVN post commit hook not triggering any jobs it was an error in the post-commit hook. 'svnlook' command could not be found. Change By: er gt (10/Jan/14 10:48 AM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
er gt commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 The error was that the 'svnlook' command could not be found. So I changed the post-commit hook to 'app/subversion/csvn/bin/svnlook'. Now it's working! Thanks, a lot! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-858) Aborting a multimodule build can leave the sub projects in a bad state.
teilo resolved JENKINS-858 as Duplicate Aborting a multimodule build can leave the sub projects in a bad state. fixed in the duplicate JENKINS-19801 Change By: teilo (10/Jan/14 10:40 AM) Status: In Progress Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21323) Global default maven settings providers not working
Florian Zschocke created JENKINS-21323 Global default maven settings providers not working Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: MavenConfig.png Components: core Created: 10/Jan/14 10:37 AM Description: Changing the default setting provider under /configure -> Maven Configuration has no effect. No matter what either the local or global setting provider is set to, Maven always uses the defaults, i.e. the setting files of the user and the Maven installation. Executing Maven: -B -f w:\Devenv\Jenkins\config-file-provider-plugin\work\jobs\test_maven\workspace\pom.xml help:effective-settings Environment: Jenkins 1.539 Both Linux and Windows versions affected. Project: Jenkins Priority: Major Reporter: Florian Zschocke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20898) SVN post commit hook not working after update to 1.542
Yoichi Nakayama commented on JENKINS-20898 SVN post commit hook not working after update to 1.542 Following part seems wrong (should be output of svnlook command): "[look changed --revision 12594 /app/subversion/csvn/data/repositories/project']" Please check the content of your post-commit hook. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build I think thats not working because "Failed" triggers every time it fails, so "Failed" and "Still Failing" are triggered for following commits... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
pedro reis commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) It seems this problem occurs also using windows batch at Jenkins v1.532.1. If I run this batch locally, the problem doesn't occur!: Started by user Pedro Reis Building remotely on Windows_vs100_slave in workspace c:\h\workspace\GIT_test [GIT_test] $ cmd /c call C:\DOCUME~1\user\LOCALS~1\Temp\hudson3319679789711969196.bat c:\h\workspace\GIT_test>REM make sure nothing is hidden c:\h\workspace\GIT_test>attrib -H /S File not found - C:\h\workspace\GIT_test*.* c:\h\workspace\GIT_test>REM recursively remove child folders c:\h\workspace\GIT_test>REM for /d %X in (.) do rd /s /q "%X" c:\h\workspace\GIT_test>REM delete files in root folder c:\h\workspace\GIT_test>REM del /q /f * c:\h\workspace\GIT_test>REM get the source c:\h\workspace\GIT_test>git clone ssh://git@host/opt/git/common/mde.git Cloning into 'mde'... fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. c:\h\workspace\GIT_test>exit 128 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
