[JIRA] [core] (JENKINS-20913) [jar caching] - winp.x64.dll access conflicts
Oleg Nenashev commented on JENKINS-20913 [jar caching] - winp.x64.dll access conflicts Created a PR, which allows to disable JAR caching via the CLI option https://github.com/jenkinsci/remoting/pull/21 BTW, it is just a workaround. The complete resolution requires some tweaks in the caching procedures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-18058) NegativeArraySizeException when trying to enable a job using Jenkins CLI
Vlad Aginsky commented on JENKINS-18058 NegativeArraySizeException when trying to enable a job using Jenkins CLI I see this in my setup, v 1.550: java -jar /var/lib/jenkins/jenkins-cli.jar -s http://10.7.0.182:8080/ set-build-description some_txt 980 'GIT: e4e1681511df4548ac6365adad064b2818280833' --username name --password 'word' Exception in thread "main" java.lang.NegativeArraySizeException at hudson.cli.Connection.readByteArray(Connection.java:131) at hudson.cli.CLI.connectViaCliPort(CLI.java:243) at hudson.cli.CLI.init(CLI.java:134) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:384) Build step 'Execute shell' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-22177) Crash in Jenkins CLI when updating build result
Vlad Aginsky commented on JENKINS-22177 Crash in Jenkins CLI when updating build result I see this in my setup, v 1.550: java -jar /var/lib/jenkins/jenkins-cli.jar -s http://10.7.0.182:8080/ set-build-description some_txt 980 'GIT: e4e1681511df4548ac6365adad064b2818280833' --username name --password 'word' Exception in thread "main" java.lang.NegativeArraySizeException at hudson.cli.Connection.readByteArray(Connection.java:131) at hudson.cli.CLI.connectViaCliPort(CLI.java:243) at hudson.cli.CLI.init(CLI.java:134) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:384) Build step 'Execute shell' marked build as failure This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too
Sven Appenrodt commented on JENKINS-2 Extend name pattern to use dots too Thanks for asking. I assume there is no guideline but asking doesn't cost anything than a little time In that case - can we make a compromise that you continue checking the names but display the result (if any) as warning? Maybe many users will missinterpret your "error", but a warning like "use bash like names a-zA-Z_-, there might be problems with using this parameter in actions" or something like this might be better. It's just to warn the user using that kind of name, not to forbid it. 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/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build To use hudson.upstreamCulprits I think I'll start with that. To write a groovy script to extract upstream developers. It is available at JENKINS-17742 I'm new at Groovy scripts. Where should I put it, maybe as "Run Groovy Script" postbuild action? What happens, when I run this downstream job on it's own, then this Groovy script won't mess all up? To request a new feature to email-ext. The same problem would happen with native Jenkins e-mailing post build action I guess. How "Email-Ext" can solve it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21398) Skip build if Verified label is automatically copied to patch set
rin_ne commented on JENKINS-21398 Skip build if Verified label is automatically copied to patch set Please provide sample event provided by stream-events. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21398) Skip build if Verified label is automatically copied to patch set
Orgad Shaneh updated JENKINS-21398 Skip build if Verified label is automatically copied to patch set Well, it doesn't appear in the event. I filed a feature request: https://code.google.com/p/gerrit/issues/detail?id=2559 Can you maybe somehow query gerrit? Change By: Orgad Shaneh (18/Mar/14 8:51 AM) Attachment: patchset-created.json This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup] (JENKINS-22239) Doesn't create root folder when installing JNLP Windows Service
Markus KARG created JENKINS-22239 Doesnt create root folder when installing JNLP Windows Service Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 18/Mar/14 9:01 AM Description: After JNLP Slave started successfully, I clicked on "File Install as a service". The reaction was a message sayinig "Root folder 'C:\.jenkins' does not exist on slave node.". I then created that folder manually, and tried again which correctly installed the windows service. It seems there is a bug: The JNLP slave does not try to create that folder. Environment: LTS 1.532.2; Win7 Pro SP1 64 Bit; JDK 7u51 Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21989) ReverseProxySetupMonitor broken in Jenkins release 1.552
René Charbonneau commented on JENKINS-21989 ReverseProxySetupMonitor broken in Jenkins release 1.552 This also happens with (on Debian Wheezy) with Apache + AJP + build in Servlet Engine (winestone?!). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21989) ReverseProxySetupMonitor broken in Jenkins release 1.552
René Charbonneau edited a comment on JENKINS-21989 ReverseProxySetupMonitor broken in Jenkins release 1.552 This also happens with (on Debian Wheezy) with Apache + AJP + build in servlet engine (winestone?!). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-21536) GIT_BRANCH should not change after merge
Achim Staebler commented on JENKINS-21536 GIT_BRANCH should not change after merge I just hit the same issue with feature branch builds that merge the integration branch before the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-22240) Workspace folder not renamed/deleted when renaming job
Anders Hammar created JENKINS-22240 Workspace folder not renamed/deleted when renaming job Issue Type: Bug Assignee: Unassigned Components: subversion Created: 18/Mar/14 9:28 AM Description: When renaming a (Maven) job, the old workspace folder on disk is left unchanged. On the next build a new workspace folder (with the new job name) is created, leaving the old one as a leftover which has to be removed manually by logging onto the server. I think that the workspace folder should be renamed as well, or deleted (and then re-created on the next build). Environment: Jenkins LTS 1.532.2 with Svn plugin 2.2 Windows Server 2008 SR2 with Oracle JDK 1.7.0_25 Project: Jenkins Priority: Minor Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [notification] (JENKINS-22014) Notification hangs, does not time out
SCM/JIRA link daemon commented on JENKINS-22014 Notification hangs, does not time out Code changed in jenkins User: Wannes Sels Path: src/main/java/com/tikal/hudson/plugins/notification/Endpoint.java src/main/java/com/tikal/hudson/plugins/notification/Phase.java src/main/java/com/tikal/hudson/plugins/notification/Protocol.java src/main/resources/com/tikal/hudson/plugins/notification/HudsonNotificationProperty/config.jelly src/main/resources/com/tikal/hudson/plugins/notification/HudsonNotificationProperty/help-timeout.html src/test/java/com/tikal/hudson/plugins/notification/ProtocolTest.java http://jenkins-ci.org/commit/notification-plugin/ed88bd744181f5c9d3b3311411638702832505cf Log: added optional timeout, defaults to 30 seconds FIXED JENKINS-22014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [notification] (JENKINS-22014) Notification hangs, does not time out
SCM/JIRA link daemon resolved JENKINS-22014 as Fixed Notification hangs, does not time out Change By: SCM/JIRA link daemon (18/Mar/14 9:36 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs (=)
Shyamendra Singh commented on JENKINS-21160 Jenkins CLI cannot handle arguments with equals signs (=) Any help for an alternate fix for this, till we get issue to be in resolved status. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [extensible-choice-parameter] (JENKINS-22222) Extend name pattern to use dots too
ikedam commented on JENKINS-2 Extend name pattern to use dots too I'm not sure now. I know I can take one of follewing ways: Not check names at all. Check, but dispay only as a warning. (as your suggest) Check and display as a error. But never forbid it actually (as current implemantation). Let me have time to consider which is the best way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
ikedam commented on JENKINS-22212 No e-mail sent after failed build triggered from another build This page would be better to understand how to extract upstream developers with a groovy script: http://stackoverflow.com/questions/14541617/how-can-jenkins-downstream-job-send-email-notification-to-upstream-git-committer The same problem would happen with native Jenkins e-mailing post build action I guess. How "Email-Ext" can solve it? As I mentioned, it's not a bug but a designated behavior of Jenkins. Parameterized trigger does nothing for that. If you want both built-in mailer and email-ext extract upstream developers, you can post requests of new features to both of them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-15359) Adding a second data series and saving it results in error
Dmytro Makhno commented on JENKINS-15359 Adding a second data series and saving it results in error This is keep reproducing for me on 1.7. And seems UI only issue. Here is preliminary steps: 1. Add Plot 2. Add Several Data Series with xpath, set result as node. 3. Apply = Everything fine 4. Refresh page = https://www.dropbox.com/s/vlt4lmuzfpxdh5j/Screenshot%202014-03-18%2012.58.16.png Actual: You can find that for first data series settings are not shown Expected: All settings are visible (this is first strange thing) 5. Press on all settings = Settings are shown 6. Set all to Numbers 7. Press apply = https://www.dropbox.com/s/h2exl81qstsmawe/Screenshot%202014-03-18%2013.03.37.png Actual: Two radio boxes dissapered (second strange things) Expected: All radio are on place 8. Try to set back to node = https://www.dropbox.com/s/yf60e7uacohz0q5/Screenshot%202014-03-18%2013.05.42.png Actual: Radio button near number stays Expected: All Radios stays on node 9. Try to apply = https://www.dropbox.com/s/b5n4j5uq4n6kams/Screenshot%202014-03-18%2013.07.57.png Actual: Error, and only refresh helps to make job useful Expected: No chaos in radios I cannot find in logs anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-api] (JENKINS-21007) Add method to get parent revision
stephenconnolly commented on JENKINS-21007 Add method to get parent revision There are a number of issues with such an API enhancement: 1. There are going to be SCM implementations that cannot resolve such a concept (e.g. CVS for one) 2. What you are trying to get to is the previous relevant build... which with the multi-branch project type is almost always the previous build on the branch... so JENKINS-13056 is actually solved by multi-branch project type. 3. The previous commit may not have a build associated with it... so then the API would need to give you a means to keep walking up previous commits... which need not be a single path However I will see if there is something that can be added to resolve such concepts even if they are flawed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [recipe] (JENKINS-22241) Recipe export does not properly quote non-ASCII characters in the job description field
Markus Strand created JENKINS-22241 Recipe export does not properly quote non-ASCII characters in the job description field Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: recipe Created: 18/Mar/14 11:35 AM Description: The job description field can have any HTML text. eg that looks like the The export works fine, but the import of the recipe fails with " Exception: Invalid byte 1 of 1-byte UTF-8 sequence. Stacktrace: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence. at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.invalidByte(Unknown Source) at com.sun.org.apache.xerces.internal.impl.io.UTF8Reader.read(Unknown Source) ... " Project: Jenkins Priority: Major Reporter: Markus Strand This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api] (JENKINS-22242) Add MultiBranchProperty support
stephenconnolly created JENKINS-22242 Add MultiBranchProperty support Issue Type: New Feature Assignee: stephenconnolly Components: branch-api Created: 18/Mar/14 11:47 AM Description: Some concepts in Jenkins require a multi-branch property to store the properties that apply to the entire multibranch project as a whole... The current BranchProperty only applies to a single branch or a set of branches Project: Jenkins Priority: Major Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api] (JENKINS-22243) Add support property to hold project based access control settings for multi-branch property
stephenconnolly created JENKINS-22243 Add support property to hold project based access control settings for multi-branch property Issue Type: New Feature Assignee: stephenconnolly Components: branch-api Created: 18/Mar/14 11:48 AM Project: Jenkins Priority: Minor Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api] (JENKINS-22242) Add MultiBranchProperty support
SCM/JIRA link daemon commented on JENKINS-22242 Add MultiBranchProperty support Code changed in jenkins User: Stephen Connolly Path: src/main/resources/jenkins/branch/MultiBranchProject/configure.jelly http://jenkins-ci.org/commit/branch-api-plugin/d269396e18ed93487996e789361d4e1bb1c913fc Log: FIXED JENKINS-21399 Job Properties should not be exposed for MultiBranchProject instances as MultiBranchProject does not inherit from Job... A side effect is that we need a MultiBranchProperty that is distinct from the BranchProperty (i.e. JENKINS-22242) A second side effect is that we need a concrete version of that class that implements the Project Based Access Control functionality (i.e. JENKINS-22243) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [literate] (JENKINS-21399) Unable to enable project based security in configuration for literate build
SCM/JIRA link daemon commented on JENKINS-21399 Unable to enable project based security in configuration for literate build Code changed in jenkins User: Stephen Connolly Path: src/main/resources/jenkins/branch/MultiBranchProject/configure.jelly http://jenkins-ci.org/commit/branch-api-plugin/d269396e18ed93487996e789361d4e1bb1c913fc Log: FIXED JENKINS-21399 Job Properties should not be exposed for MultiBranchProject instances as MultiBranchProject does not inherit from Job... A side effect is that we need a MultiBranchProperty that is distinct from the BranchProperty (i.e. JENKINS-22242) A second side effect is that we need a concrete version of that class that implements the Project Based Access Control functionality (i.e. JENKINS-22243) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api] (JENKINS-22243) Add support property to hold project based access control settings for multi-branch property
SCM/JIRA link daemon commented on JENKINS-22243 Add support property to hold project based access control settings for multi-branch property Code changed in jenkins User: Stephen Connolly Path: src/main/resources/jenkins/branch/MultiBranchProject/configure.jelly http://jenkins-ci.org/commit/branch-api-plugin/d269396e18ed93487996e789361d4e1bb1c913fc Log: FIXED JENKINS-21399 Job Properties should not be exposed for MultiBranchProject instances as MultiBranchProject does not inherit from Job... A side effect is that we need a MultiBranchProperty that is distinct from the BranchProperty (i.e. JENKINS-22242) A second side effect is that we need a concrete version of that class that implements the Project Based Access Control functionality (i.e. JENKINS-22243) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [literate] (JENKINS-21399) Unable to enable project based security in configuration for literate build
stephenconnolly resolved JENKINS-21399 as Fixed Unable to enable project based security in configuration for literate build Removed the code that was pulling in the non-existant properties Change By: stephenconnolly (18/Mar/14 11:53 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
swapnil soor created JENKINS-22244 javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 18/Mar/14 11:51 AM Description: I am not able to create any job using jenkins UI, it redirects me to below error OOPS page. Stack trace javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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:727) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) 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:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408) at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne started work on JENKINS-21547 Add information to console log when a job is aborted by gerrit Change By: rin_ne (18/Mar/14 11:53 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne updated JENKINS-21547 Add information to console log when a job is aborted by gerrit Change By: rin_ne (18/Mar/14 11:53 AM) Assignee: rsandell rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne assigned JENKINS-21547 to Unassigned Add information to console log when a job is aborted by gerrit Change By: rin_ne (18/Mar/14 11:54 AM) Assignee: rin_ne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-21547) Add information to console log when a job is aborted by gerrit
rin_ne stopped work on JENKINS-21547 Add information to console log when a job is aborted by gerrit Change By: rin_ne (18/Mar/14 11:54 AM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [literate] (JENKINS-20592) Literate plugin needs an email feature
stephenconnolly commented on JENKINS-20592 Literate plugin needs an email feature Firstly, do you really want the email stuff in the README.md? Secondly, this is something that should really be considered more Jenkins specific... So as a result you should handle it with the .jenkins/ directory in SCM and just add the Mailer's XML descriptor... or better yet define a more literate style descriptor parser for mailing config. You may want to turn off/ignore emails from specific branches, all that points to the .jenkins folder handling logic (i.e. branch profiles, etc) There is also the question of whether you should be storing email addresses in SCM... given that you might have to re-activate an old branch which triggers emails to people that are no longer working on the project, etc... (but that is not a new question) I would point to the https://github.com/jenkinsci/literate-plugin/blob/master/src/main/java/org/cloudbees/literate/jenkins/publishers/Agent.java class as the extension point where this would be easiest addressed. An EmailerAgent could parse a simple plain text format descriptor and construct the EmailPublisher instance to be used by each branch that would give the nice plain text support and allow people to disable the agent for e.g. pull request branches, etc If you don't create a custom format (e.g. like what I did with the two example Agents for JUnit and artifact archiving) then the default XML agent will pick up and XML file for emailer publisher config if present... So the literate plugin does actually have email feature right now... you just have to write it in XML This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [literate] (JENKINS-19766) 'Agents' for builders
stephenconnolly commented on JENKINS-19766 Agents for builders Actually the way I see the Maven integration working is by decorating the environment-label mapping providers. An environment-label mapper could take environment names like `maven-3.2.1`, `maven-3.0.4` and map them to tool installers for the corresponding version of Maven. This makes it easy to have a convention for Maven version without forcing people to name their tool installers following the convention. When picking up such a mapping, it will actually inject a different PATH from that constructed by the ToolInstaller. On this different path will be a hook script that wraps `mvn` or `mvn.bat` such that the execution has an extra Maven extension that records the build operations that were executed and injects the settings configuration. The hook script is required because somebody may well have a literate command along the lines of MAVEN_OPTS=-Xmx512M mvn clean verify -P+extra-tests So we cannot rely on injecting MAVEN_OPTS into the environment and hoping that the person writing the command knows how to not clobber us. Similarly we need to support somebody building with Maven and requiring their own extensions be registered This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
swapnil soor commented on JENKINS-22244 javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 I am using the latest Jenkins version 1.555. Upgraded today expecting that might solve 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/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
swapnil soor edited a comment on JENKINS-22244 javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 I am using the latest Jenkins version 1.555. Upgraded today expecting that might solve the problem but no luck . I believe this must be some basic issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21288) Build with Poll SCM trigger proceeds even though no SCM change
stephenconnolly updated JENKINS-21288 Build with Poll SCM trigger proceeds even though no SCM change Change By: stephenconnolly (18/Mar/14 12:31 PM) Component/s: scm-api This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-19762) Would like to be able to clean AFTER build as well as during setup
stephenconnolly updated JENKINS-19762 Would like to be able to clean AFTER build as well as during setup Change By: stephenconnolly (18/Mar/14 12:31 PM) Component/s: scm-api This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
Mark Waite commented on JENKINS-22244 javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 The Java 8 pre-release is not supported with Jenkins and is known to not work. Please install either Oracle JDK 7 or OpenJDK 7 for use with Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Meta Stable commented on JENKINS-21518 Error while using SSH credentials to fetch git repository. I am currently running Jenkins 1.537, with the following plugins: Credentials plugin: 1.9.4 SSH Credentials Plugin: 1.6 SSH Slaves Plugin: 1.5 Strictly speaking, I'm not sure any are required other than "SSH Credentials Plugin". I see that new version(s) are available, both for Jenkins as well as some of these plugins, so I will update and check. But I am still facing this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
Mark Waite resolved JENKINS-22244 as Not A Defect javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 Java 8 is not supported with Jenkins. Java 8 is not yet released and the pre-release versions are known to not work with Jenkins. Change By: Mark Waite (18/Mar/14 12:44 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Mark Waite commented on JENKINS-21518 Error while using SSH credentials to fetch git repository. The Credentials plugin is required with the git-plugin and the git-client-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/d/optout.
[JIRA] [core] (JENKINS-13135) Very large console logs will cause Jenkins to crash or behave erratically
evernat resolved JENKINS-13135 as Incomplete Very large console logs will cause Jenkins to crash or behave erratically No response from the reporter, so resolving as incomplete. Change By: evernat (18/Mar/14 1:06 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-21848) CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration
Yasuyuki Saito commented on JENKINS-21848 CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration Is it possible to check the value of CyclomaticComplexity of Metrics.xml ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Sam Gleske commented on JENKINS-20941 Stored git credentials not used when submodule is updated I figured out the root cause of this in my installation. The problem is that the initial checkout is using the credentials plugin but the submodule checkout is using the default user credentials defined in `/.ssh/config`. If there is not `config` then SSH by default will look for `/.ssh/id_rsa` as the private key for the connection. My jenkins system user has default credentials in `~/.ssh/id_rsa` and so I had to give the user using those credentials access to the submodule project with read permissions. Hopefully that was clear. Essentially, the git plugin claims it is reusing credentials plugin for the submodule check out but it is actually not using it at all. I'll try to dig through the source to point out where it is doing 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/d/optout.
[JIRA] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs (=)
Shyamendra Singh commented on JENKINS-21160 Jenkins CLI cannot handle arguments with equals signs (=) seems this issue is fixed https://github.com/jenkinsci/jenkins/pull/776 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Sam Gleske updated JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Sam Gleske (18/Mar/14 1:28 PM) Environment: Windows78slavesCannotreproduceonMacslave ReproducedonRHELLinux6.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Sam Gleske edited a comment on JENKINS-20941 Stored git credentials not used when submodule is updated I figured out the root cause of this in my installation. The problem is that the initial checkout is using the credentials plugin but the submodule checkout is using the default user credentials defined in `/.ssh/config`. If there is not `config` then SSH by default will look for `~/.ssh/id_rsa` as the private key for the connection. My jenkins system user has default credentials in `/.ssh/id_rsa` and so I had to give the user using those credentials access to the submodule project with read permissions. Hopefully that was clear. Essentially, the git plugin claims it is reusing credentials plugin for the submodule check out but it is actually not using it at all. I'll try to dig through the source to point out where it is doing 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/d/optout.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Sam Gleske edited a comment on JENKINS-20941 Stored git credentials not used when submodule is updated I figured out the root cause of this in my installation. The problem is that the initial checkout is using the credentials plugin but the submodule checkout is using the default user credentials defined in `/.ssh/config`. If there is not `config` then SSH by default will look for `/.ssh/id_rsa` as the private key for the connection. My jenkins system user has default credentials in `/.ssh/id_rsa` and so I had to give the user using those credentials access to the submodule project with read permissions. Hopefully that was clear. Essentially, the git plugin claims it is reusing credentials plugin for the submodule check out but it is actually not using it at all. I'll try to dig through the source to point out where it is doing this. This behavior was observed by viewing the SSH logs on the git server while Jenkins was checking out the submodules. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Patrik Boström closed JENKINS-22211 as Fixed Parallel stages display distorted Released in 0.7.2 Change By: Patrik Boström (18/Mar/14 1:35 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Roy Miller commented on JENKINS-22211 Parallel stages display distorted Thanks, Patrik. I sent you a couple emails with lots of details about how to reproduce the bug, but I'm not sure if you got them. I replace to the emails I got when you made comments on this Jenkins ticket. The email address for you looked legit. Glad this is fixed. Does it a take a little while for Jenkins to tell me there's an update for the plugin to version 0.7.2? I haven't seen the "upgrades available" message 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/d/optout.
[JIRA] [core] (JENKINS-13135) Very large console logs will cause Jenkins to crash or behave erratically
Danny Staple commented on JENKINS-13135 Very large console logs will cause Jenkins to crash or behave erratically We no longer reproduce this as we worked around it by redirecting the output somewhere. It is far less likely we will see it as we've internalised this as a standard thing - we only allow small bits of glue code output to the main log, and archive the redirected output. Where there are non-concurrent jobs, this also means it can be observed in the workspace. Where we allow concurrent jobs and slave node labels, we have placed apache servers pointing at the workspace directories so we can easily view the in progress logs, and write the link to them out in the main console log when it starts up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-22244) javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1
swapnil soor commented on JENKINS-22244 javax.servlet.ServletException: java.lang.ArrayIndexOutOfBoundsException: -1 Thanks Mark. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22210) On restarting broken build in pipeline, dashboard should update accordingly
Patrice Matignon commented on JENKINS-22210 On restarting broken build in pipeline, dashboard should update accordingly I am interested in having a fix for when using the "Rebuild" plugin. Is it the same root cause essentially (i.e. the upstream cause is not present/preserved) ? I think the combo (pipeline + rebuild plugins) is powerful and adds a lot of value. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich commented on JENKINS-22212 No e-mail sent after failed build triggered from another build I've added -Dhudson.upstreamCulprits=true. Let's see how it will go. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich edited a comment on JENKINS-22212 No e-mail sent after failed build triggered from another build I've added -Dhudson.upstreamCulprits=true. Let's see how it will go. Thanks for 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/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22212) No e-mail sent after failed build triggered from another build
Alexander Obuhovich resolved JENKINS-22212 as Not A Defect No e-mail sent after failed build triggered from another build Change By: Alexander Obuhovich (18/Mar/14 2:20 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
recampbell created JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand Created: 18/Mar/14 2:22 PM Description: If your main view has the SauceBadgeColumn, a saucelabs.com outage will cause a Jenkins outage. As of Tue Mar 18 14:20:31 UTC 2014, saucelabs.com is not responding (seems well-hung). This causes Jenkins to hang. An easy fix is to add a read timeout and handle that failure gracefully. Thread dump: 2014-03-18_14:09:48.10898 "Handling GET / : http-8084-3" daemon prio=10 tid=0x7fbac404b800 nid=0x1986 runnable 0x7fbad53b 2014-03-18_14:09:48.10899java.lang.Thread.State: RUNNABLE 2014-03-18_14:09:48.10900 at java.net.SocketInputStream.socketRead0(Native Method) 2014-03-18_14:09:48.10900 at java.net.SocketInputStream.read(Unknown Source) 2014-03-18_14:09:48.10901 at java.net.SocketInputStream.read(Unknown Source) 2014-03-18_14:09:48.10902 at sun.security.ssl.InputRecord.readFully(Unknown Source) 2014-03-18_14:09:48.10902 at sun.security.ssl.InputRecord.read(Unknown Source) 2014-03-18_14:09:48.10903 at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) 2014-03-18_14:09:48.10903 - locked 0xfcb17420 (a java.lang.Object) 2014-03-18_14:09:48.10904 at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source) 2014-03-18_14:09:48.10904 at sun.security.ssl.AppInputStream.read(Unknown Source) 2014-03-18_14:09:48.10905 - locked 0xfcb256a8 (a sun.security.ssl.AppInputStream) 2014-03-18_14:09:48.10905 at java.io.BufferedInputStream.fill(Unknown Source) 2014-03-18_14:09:48.10906 at java.io.BufferedInputStream.read1(Unknown Source) 2014-03-18_14:09:48.10906 at java.io.BufferedInputStream.read(Unknown Source) 2014-03-18_14:09:48.10907 - locked 0xfcba7340 (a java.io.BufferedInputStream) 2014-03-18_14:09:48.10908 at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source) 2014-03-18_14:09:48.10909 at sun.net.www.http.HttpClient.parseHTTP(Unknown Source) 2014-03-18_14:09:48.10909 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) 2014-03-18_14:09:48.10910 - locked 0xfcb13910 (a sun.net.www.protocol.https.DelegateHttpsURLConnection) 2014-03-18_14:09:48.10910 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(Unknown Source) 2014-03-18_14:09:48.10911 - locked 0xfcb13890 (a sun.net.www.protocol.https.HttpsURLConnectionImpl) 2014-03-18_14:09:48.10911 at com.saucelabs.saucerest.SauceREST.retrieveResults(SauceREST.java:140) 2014-03-18_14:09:48.10912 at com.saucelabs.saucerest.SauceREST.retrieveResults(SauceREST.java:117) 2014-03-18_14:09:48.10912 at hudson.plugins.sauce_ondemand.SauceBadgeColumn.getSauceUser(SauceBadgeColumn.java:59) 2014-03-18_14:09:48.10913 at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) 2014-03-18_14:09:48.10913 at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 2014-03-18_14:09:48.10914 at java.lang.reflect.Method.invoke(Unknown Source) Project: Jenkins Priority: Critical Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the
[JIRA] [audit-trail] (JENKINS-22246) Audit Trail Plugin should record system changes
Mr Cinquero created JENKINS-22246 Audit Trail Plugin should record system changes Issue Type: Improvement Assignee: Alan Harder Components: audit-trail Created: 18/Mar/14 2:31 PM Description: It would be extremely useful to have a protocol when the build system environment changed and in which way. Things to get started: Jenkins boot (including server version) and shutdown. Plugin installations, removals, upgrades and downgrades (including versions). Project: Jenkins Priority: Major Reporter: Mr Cinquero This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
stephenconnolly created JENKINS-22247 Provide an extension point to define user id case sensitivity contract Issue Type: New Feature Assignee: Unassigned Components: core Created: 18/Mar/14 2:33 PM Description: The current core implementation does not define a proper contract for case insensitivity leading to all sorts of bugs, e.g. JENKINS-22057 JENKINS-12607 JENKINS-3218 JENKINS-9771 JENKINS-6377 JENKINS-20125 JENKINS-18009 Also there are a lot of issues showing a fundamental misunderstanding of why Jenkins originally used a semi-case insensitive username... (hint the real reason is because windows filesystem is case insensitive) People seem to think that user ids are case insensitive... despite unix logins being case sensitive email addresses being case sensitive (yes they are allowed to be... read the RFC... the destination server is allowed to treat them as case sensitive... though the RFC does say a polite version of "only a fool would actually do that" it is allowed by the spec, so you cannot assume that f...@acme.org is the same person as f...@acme.org... you can however assume that f...@acme.org and f...@acme.org are the same person as is f...@acme.org because domain names are not case sensitive) As such, without a plugable strategy the case sensitive/insensitivity of Jenkins is fundamentally broken. Project: Jenkins Priority: Major Reporter: stephenconnolly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [audit-trail] (JENKINS-22246) Audit Trail Plugin should record system changes
Mr Cinquero updated JENKINS-22246 Audit Trail Plugin should record system changes Change By: Mr Cinquero (18/Mar/14 2:32 PM) Description: Itwouldbeextremelyusefultohaveaprotocol when aboutchangesin thebuildsystemenvironment changedandinwhichway .Thingstogetstarted:Jenkinsboot(includingserverversion)andshutdown.Plugininstallations,removals,upgradesanddowngrades(includingversions). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
stephenconnolly commented on JENKINS-22247 Provide an extension point to define user id case sensitivity contract https://github.com/jenkinsci/jenkins/pull/1161 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish] (JENKINS-22188) Multiple capability (as conditional steps plugin as single and multiple)
pedro reis commented on JENKINS-22188 Multiple capability (as conditional steps plugin as single and multiple) Sorry, did a search before searching and didn't found 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/d/optout.
[JIRA] [flexible-publish] (JENKINS-22188) Multiple capability (as conditional steps plugin as single and multiple)
pedro reis edited a comment on JENKINS-22188 Multiple capability (as conditional steps plugin as single and multiple) Sorry, did a search before posting and didn't found 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/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
recampbell commented on JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn A related pull request which would migate this problem: https://github.com/saucelabs/saucerest-java/pull/8 Unfortunately, if saucelabs.com goes down, most people would still pin the blame on Jenkins if they didn't look at the stack trace. So I think this badge really needs to be asynchronous, perhaps loaded as an image from an action hanging off the build vs. calling saucelabs.com when rendering the html. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13135) Very large console logs will cause Jenkins to crash or behave erratically
evernat commented on JENKINS-13135 Very large console logs will cause Jenkins to crash or behave erratically ok, thanks for those ideas. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22247) Provide an extension point to define user id case sensitivity contract
Jesse Glick updated JENKINS-22247 Provide an extension point to define user id case sensitivity contract Change By: Jesse Glick (18/Mar/14 3:39 PM) Labels: api This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida edited a comment on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I had to close the browser/reboot, so expected the cookie to be deleted. It was, so I was logged out. Logged into Jenkins again: new cookie good for 14 days from today. We'll see how it goes this time... LATER: No problem the rest of that day. I'll repost the next time Jenkins logs me out WITHOUT closing the browser. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-20065) Retain original build causes
Alex Gray commented on JENKINS-20065 Retain original build causes This bug has a side of effect of blocking: https://issues.jenkins-ci.org/browse/JENKINS-22210 Here is the summary of that JIRA: = Let's say you have a pipeline: A - B - C And B fails for whatever reason. "B" is automatically restarted via the "naginator" plugin and the build passes, it would be since to have the build pipeline reflect this. = We display the build pipeline plugin on our TV dashboards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
Jesse Glick updated JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn Change By: Jesse Glick (18/Mar/14 4:55 PM) Labels: performance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
Jesse Glick assigned JENKINS-22245 to Unassigned Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn Change By: Jesse Glick (18/Mar/14 4:55 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-22245) Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn
Jesse Glick commented on JENKINS-22245 Saucelabs.com outage causes Jenkins outage when using SauceBadgeColumn Indeed no code should be making a network request in the course of page rendering. Currently seems to use cached results for five minutes, but should not ever do this calculation synchronously. By the way loading an image asynchronously would not suffice as the user name is used also in a hyperlink; would need to use l:renderOnDemand (with l:ajax) or similar. Also it seems inappropriate for PluginImpl.disableStatusColumn to default to false. Would be more polite for SauceBadgeColumn.DescriptorImpl.shownByDefault to simply be false, where users would add the column to whichever views they wanted to see it on; this is how most plugin-contributed columns work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task] (JENKINS-22248) Support multiple launches per workspace
Jesse Glick created JENKINS-22248 Support multiple launches per workspace Issue Type: Bug Assignee: Jesse Glick Components: durable-task Created: 18/Mar/14 5:30 PM Description: FileMonitoringTask currently assumes that the caller of the task owns an exclusive lock on the workspace. For some purposes this is not a safe assumption, so it should instead generate distinct tracker files for each concurrent invocation. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick created JENKINS-22249 Record process ID of spawned process Issue Type: Bug Assignee: Jesse Glick Components: durable-task Created: 18/Mar/14 5:34 PM Description: Currently BourneShellScript does not try to track the PID of the external process; it assumes that it runs to completion (successfully or not) and then writes the status file. But if the wrapping shell script is killed, or the machine rebooted, this might never occur and the task would hang. Better to record $$ from the outer sh process and override exitStatus in case no such process still exists. Implies some use of native code. (TBD whether an analogous fix can be done for Windows as well.) Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap] (JENKINS-22250) fail the build if no test results are present option doesn't fail the job.
Brendan Mannix created JENKINS-22250 fail the build if no test results are present option doesnt fail the job. Issue Type: Bug Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 18/Mar/14 6:05 PM Description: The "fail the build if no test results are present" option doesn't fail the job. The tap results file exists and contains a single string (not test results). TAP Reports Processing: START Looking for TAP results report in workspace using pattern: js_unittest_results.txt Saving reports... Processing '/var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt' Parsing TAP test result [/var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt]. TAP Reports Processing: FINISH Finished: SUCCESS [bmannix@glados ~]$ cat /var/lib/jenkins/jobs/testing/builds/2014-03-18_13-04-29/tap-master-files/js_unittest_results.txt object EXPECTED BEHAVIOR: The build fails based on not finding any tap test results. Environment: Jenkins: 1.551 Tap: 1.18 Project: Jenkins Priority: Minor Reporter: Brendan Mannix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-22251) Executing tf using the TFS Plugin throws an IO exception
Renu Chudamani created JENKINS-22251 Executing tf using the TFS Plugin throws an IO exception Issue Type: Bug Assignee: redsolo Components: tfs Created: 18/Mar/14 6:21 PM Description: When executing the TFS Plugin from a Linux master to a Windows 7 slave I am getting the following error: 17:00:52 EnvInject - Loading node environment variables. 17:00:53 Building remotely on VMWAYQA09 in workspace C:\jenkins-slave\workspace\AUT-Geb-Demo 17:00:53 AUT-Geb-Demo $ tf workspaces -format:brief -server:http://server:8080/tfs/2x 17:00:53 java.io.IOException: Cannot run program "tf" (in directory "C:\jenkins-slave\workspace\AUT-Geb-Demo"): CreateProcess error=2, The system cannot find the file specified 17:00:53 at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) 17:00:53 at hudson.Proc$LocalProc.init(Proc.java:244) 17:00:53 at hudson.Proc$LocalProc.init(Proc.java:216) 17:00:53 at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) 17:00:53 at hudson.Launcher$ProcStarter.start(Launcher.java:353) 17:00:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:998) 17:00:53 at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:965) 17:00:53 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 17:00:53 at hudson.remoting.UserRequest.perform(UserRequest.java:48) 17:00:53 at hudson.remoting.Request$2.run(Request.java:328) 17:00:53 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 17:00:53 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 17:00:53 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 17:00:53 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 17:00:53 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 17:00:53 at hudson.remoting.Engine$1$1.run(Engine.java:63) 17:00:53 at java.lang.Thread.run(Thread.java:662) 17:00:53 Caused by: java.io.IOException: CreateProcess error=2, The system cannot find the file specified 17:00:53 at java.lang.ProcessImpl.create(Native Method) 17:00:53 at java.lang.ProcessImpl.init(ProcessImpl.java:81) 17:00:53 at java.lang.ProcessImpl.start(ProcessImpl.java:30) 17:00:53 at java.lang.ProcessBuilder.start(ProcessBuilder.java:453) 17:00:53 ... 16 more 17:00:53 Finished: FAILURE Project: Jenkins Priority: Critical Reporter: Renu Chudamani This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-22251) Executing tf using the TFS Plugin throws an IO exception
Renu Chudamani
updated JENKINS-22251
Executing tf using the TFS Plugin throws an IO exception
Change By:
Renu Chudamani
(18/Mar/14 6:29 PM)
Environment:
JenkinsmasterisLinux.SlavenodeisWindows7machine.
Description:
WhenexecutingtheTFSPluginfromaLinuxmastertoaWindows7slaveIamgettingthefollowingerror:
bq.
17:00:52[EnvInject]-Loadingnodeenvironmentvariables.17:00:53BuildingremotelyonVMWAYQA09inworkspaceC:\jenkins-slave\workspace\AUT-Geb-Demo17:00:53[AUT-Geb-Demo]$tfworkspaces-format:brief-server:http://server:8080/tfs/2x
{color:red}
17:00:53java.io.IOException:Cannotrunprogramtf(indirectoryC:\jenkins-slave\workspace\AUT-Geb-Demo):CreateProcesserror=2,Thesystemcannotfindthefilespecified
{color:red}
17:00:53 atjava.lang.ProcessBuilder.start(ProcessBuilder.java:460)17:00:53 athudson.Proc$LocalProc.init(Proc.java:244)17:00:53 athudson.Proc$LocalProc.init(Proc.java:216)17:00:53 athudson.Launcher$LocalLauncher.launch(Launcher.java:773)17:00:53 athudson.Launcher$ProcStarter.start(Launcher.java:353)17:00:53 athudson.Launcher$RemoteLaunchCallable.call(Launcher.java:998)17:00:53 athudson.Launcher$RemoteLaunchCallable.call(Launcher.java:965)17:00:53 athudson.remoting.UserRequest.perform(UserRequest.java:118)17:00:53 athudson.remoting.UserRequest.perform(UserRequest.java:48)17:00:53 athudson.remoting.Request$2.run(Request.java:328)17:00:53 athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)17:00:53 atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)17:00:53 atjava.util.concurrent.FutureTask.run(FutureTask.java:138)17:00:53 atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)17:00:53 atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)17:00:53 athudson.remoting.Engine$1$1.run(Engine.java:63)17:00:53 atjava.lang.Thread.run(Thread.java:662)17:00:53Causedby:java.io.IOException:CreateProcesserror=2,Thesystemcannotfindthefilespecified17:00:53 atjava.lang.ProcessImpl.create(NativeMethod)17:00:53 atjava.lang.ProcessImpl.init(ProcessImpl.java:81)17:00:53 atjava.lang.ProcessImpl.start(ProcessImpl.java:30)17:00:53 atjava.lang.ProcessBuilder.start(ProcessBuilder.java:453)17:00:53 ...16more17:00:53Finished:FAILURE
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs] (JENKINS-22251) Executing tf using the TFS Plugin throws an IO exception
Renu Chudamani
commented on JENKINS-22251
Executing tf using the TFS Plugin throws an IO exception
Also - needs to be mentioned that we have tried the following and they are successful. Hence, the hunch is that an issue with the plugin.
1. Executing the tf command by configuring a job as a Windows batch command on the slave works successfully.
2. Exceuting the tf command using the script console like this works successfully:
Process p = "cmd /c tf".execute()
println "${p.text}"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22224) one job configuration change results in three Job Config History entries
Marc Günther
updated JENKINS-4
one job configuration change results in three Job Config History entries
Change By:
Marc Günther
(18/Mar/14 6:37 PM)
Description:
EverytimeImakeaconfigurationchangetoajob,IgetthreeentriesintheJobConfigHistoryview:#removaloftheconfigfor{{disk-usage}}plugin#actualchangeImade#additionoftheconfigof{{disk-usage}}againTheremovedandre-addedlinelookslikethis:{code}hudson.plugins.disk__usage.DiskUsagePropertyplugin=disk-usage@0.23/{code}Expected:1.and3.shouldnothappen..
EDIT:Ihavenowalsoseenacasewhere1.and2.arecombinedintoonechange,and3.isthesecondchange.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to SCMTrigger if a build is run because of a source code change
SCM/JIRA link daemon commented on JENKINS-21955 Set BUILD_USER to SCMTrigger if a build is run because of a source code change Code changed in jenkins User: Clifford Sanders Path: src/main/java/org/jenkinsci/plugins/builduser/BuildUser.java src/main/java/org/jenkinsci/plugins/builduser/varsetter/impl/SCMTriggerCauseDeterminant.java http://jenkins-ci.org/commit/build-user-vars-plugin/e2e328e8bc71412d24b8ec366fbba4d6d3fa52e1 Log: Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change - fixes JENKINS-21955 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
Anders Hammar commented on JENKINS-20753 Remove unused Append Hudson Build Number option Could this be applied please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [naginator] (JENKINS-20065) Retain original build causes
Patrik Boström commented on JENKINS-20065 Retain original build causes Created a pull request with a fix for this issue: https://github.com/jenkinsci/naginator-plugin/pull/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/d/optout.
[JIRA] [analysis-core] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Jesse Glick created JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Issue Type: Bug Assignee: Ulli Hafner Attachments: config.xml Components: analysis-core, maven, tasks-plugin Created: 18/Mar/14 7:39 PM Description: If in the above environment you run the attached job, you will get [TASKS] Scanning folder '.../workspace' for files matching the pattern '**/*.java' - excludes: [TASKS] Found 2 files to scan for tasks Found 0 open tasks. [TASKS] File encoding has not been set in pom.xml, using platform encoding UTF-8, i.e. build is platform dependent (see a href=""Maven FAQ/a). java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy7.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:201) at hudson.plugins.analysis.core.HealthAwareReporter.registerResultsOnMaster(HealthAwareReporter.java:326) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:317) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:628) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:610) at hudson.maven.Maven3Builder$JenkinsEventSpy.onEvent(Maven3Builder.java:306) at org.apache.maven.eventspy.internal.EventSpyDispatcher.onEvent(EventSpyDispatcher.java:108) at org.apache.maven.eventspy.internal.EventSpyExecutionListener.mojoSucceeded(EventSpyExecutionListener.java:131) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:227) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155) at org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) 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:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[JIRA] [core] (JENKINS-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Peter Eisentraut
updated JENKINS-21985
java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
updated stack strace
Change By:
Peter Eisentraut
(18/Mar/14 7:51 PM)
Description:
Imadeajobthatjustdoes{noformat}echofoofoo.txt{noformat}andissettoarchive*.txt.ThenIboundthatjobtoaslavewithalabel.Thebuildfailswith{noformat}+echofooArchivingartifactsERROR:Failedtoarchiveartifacts:*.txtjava.io.IOException:java.util.concurrent.ExecutionException:java.lang.NoClassDefFoundError:jnr/posix/POSIXHandler athudson.FilePath.copyRecursiveTo(FilePath.java:2016) atjenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) athudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) athudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) athudson.model.Run.execute(Run.java:1703) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:231)
Causedby:java.util.concurrent.ExecutionException:java.lang.NoClassDefFoundError:jnr/posix/POSIXHandler athudson.remoting.Channel$3.adapt(Channel.java:755) athudson.remoting.Channel$3.adapt(Channel.java:750) athudson.remoting.FutureAdapter.get(FutureAdapter.java:55) athudson.FilePath.copyRecursiveTo(FilePath.java:2014) ...11moreCausedby:java.lang.NoClassDefFoundError:jnr/posix/POSIXHandler athudson.util.IOUtils.mode(IOUtils.java:125) athudson.util.io.TarArchiver.visit(TarArchiver.java:101) athudson.util.DirScanner.scanSingle(DirScanner.java:49) athudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2540) athudson.FilePath.writeToTar(FilePath.java:2052) athudson.FilePath.access$1000(FilePath.java:172) athudson.FilePath$41.invoke(FilePath.java:1993) athudson.FilePath$41.invoke(FilePath.java:1989) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:328) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:701)Causedby:java.lang.ClassNotFoundException:jnr.posix.POSIXHandler(WebAppClassLoader=Jenkinsv1.546@49f4bcf7didnotfindclassfile) athudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch2(RemoteClassLoader.java:727) athudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:777) athudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:784) atsun.reflect.GeneratedMethodAccessor1893.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) atjava.lang.reflect.Method.invoke(Method.java:616) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299) athudson.remoting.Request$2.run(Request.java:328) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) atjava.util.concurrent.FutureTask.run(FutureTask.java:166) atjava.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) atjava.lang.Thread.run(Thread.java:679)
{noformat}IfIrunthejobonthemaster,itworksfine.Somehow,thejnr-posixstuffisntmadeavailableontheslave.(seemsrelatedtoJENKINS-18682,whichwasclausedbecauseofinactivity)
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Jesse Glick updated JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap Change By: Jesse Glick (18/Mar/14 7:53 PM) Assignee: UlliHafner Component/s: tasks-plugin Component/s: analysis-core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Jesse Glick commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap AbstractMapBasedMultimap was introduced in Guava 14 (bundled in Maven 3.2.1); AbstractMultimap is present in the Guava 11 used by Jenkins core. So presumably the Maven plugin is allowing Guava 11 to “leak through” from core into the effective classpath for the Maven agent. Then when AbstractMapBasedMultimap is loaded from 14, parent-first delegation causes it to look for its superclass in the wrong class loader. I think this is a bug in the Maven plugin: for Guava at least it should delegate to Maven’s lib/*.jar preferentially. (There is no general rule that I can think of, because some other libraries bundled with core may well be needed from plugins loading code in the Maven build agent.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to SCMTrigger if a build is run because of a source code change
Clifford Sanders resolved JENKINS-21955 as Fixed Set BUILD_USER to SCMTrigger if a build is run because of a source code change Change By: Clifford Sanders (18/Mar/14 8:04 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22210) On restarting broken build in pipeline, dashboard should update accordingly
Patrik Boström commented on JENKINS-22210 On restarting broken build in pipeline, dashboard should update accordingly I tried the Rebuild plugin 1.21 and it retain the original build cause. So the Delivery Pipeline Plugin picks up the rebuild attempt. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22211) Parallel stages display distorted
Patrik Boström commented on JENKINS-22211 Parallel stages display distorted It usually takes a couple of hour until Jenkins picks up new plugin releases, but you should be able to see the new version by now. I hope that my fix has resolved the issue. Please report back the result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) M2 Release Plugin Widget not appearing on Jenkins View
Anders Hammar assigned JENKINS-20027 to Anders Hammar M2 Release Plugin Widget not appearing on Jenkins View Change By: Anders Hammar (18/Mar/14 8:49 PM) Assignee: teilo AndersHammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
Anders Hammar updated JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Adjusted summary to reflect issue better. Change By: Anders Hammar (18/Mar/14 8:51 PM) Summary: M2ReleasePluginWidgetnotappearingonJenkins ExceptionthrownwhenDashboard View pluginisnotinstalled This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
Anders Hammar commented on JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Details on working with option deps: https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins#Dependenciesamongplugins-Optionaldependencies This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
Anders Hammar commented on JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Pull request sent: https://github.com/jenkinsci/m2release-plugin/pull/23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion
František Novotný commented on JENKINS-22199 Jenkins throwing errors in SCM Polling and Updates with Subversion I have the same problem after update jenkins from 1.549 to 1.554 and subversion plugin from 2.0 to 2.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion
kutzi commented on JENKINS-22199 Jenkins throwing errors in SCM Polling and Updates with Subversion Note: likely caused by https://github.com/jenkinsci/subversion-plugin/commit/ec606ac7557772cb07e72f00c084203810ebd815 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-import] (JENKINS-22159) Cannot create jobs when running on Java 1.8
Jesse Glick resolved JENKINS-22159 as Duplicate Cannot create jobs when running on Java 1.8 Change By: Jesse Glick (18/Mar/14 9:30 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20764) Failing upgrade from 1.533 to 1.541
Jesse Glick resolved JENKINS-20764 as Duplicate Failing upgrade from 1.533 to 1.541 Change By: Jesse Glick (18/Mar/14 9:31 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
SCM/JIRA link daemon commented on JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Code changed in jenkins User: jtnord Path: src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java http://jenkins-ci.org/commit/m2release-plugin/7ee2284e0515ae0aeb784188c670de34c3b1f0c6 Log: Merge pull request #23 from andham/JENKINS-20027 FIXED JENKINS-20027 Exception thrown when Dashboard View plugin is not... Compare: https://github.com/jenkinsci/m2release-plugin/compare/50bdcffd3dd2...7ee2284e0515 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
SCM/JIRA link daemon resolved JENKINS-20027 as Fixed Exception thrown when Dashboard View plugin is not installed Change By: SCM/JIRA link daemon (18/Mar/14 9:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [m2release] (JENKINS-20027) Exception thrown when Dashboard View plugin is not installed
SCM/JIRA link daemon commented on JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Code changed in jenkins User: Anders Hammar Path: src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java http://jenkins-ci.org/commit/m2release-plugin/6458233425d9f6f1231cdb1817b26fb06075fc3e Log: FIXED JENKINS-20027 Exception thrown when Dashboard View plugin is not installed Signed-off-by: Anders Hammar and...@hammar.net This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to SCMTrigger if a build is run because of a source code change
Clifford Sanders closed JENKINS-21955 as Fixed Set BUILD_USER to SCMTrigger if a build is run because of a source code change Change By: Clifford Sanders (18/Mar/14 10:00 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
