[JIRA] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Pärsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Would this be a standalone web service, needing to be hosted outside Jenkins and Perforce? I'm no expert in the inner workings of Perforce so this might be the best solution, but requiring a third piece of software to be hosted is a drawback to me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-20463) Manual build of tag breaks scm poll on trunk for parameterized builds
Title: Message Title Christoph Kuhnke commented on JENKINS-20463 Re: Manual build of tag breaks scm poll on trunk for parameterized builds Hello, we are using Jenkins ver. 1.580.3, Subversion Plug-in 1.54. We have not installed EnvInject Plugin. Greets, Christoph. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-timeout-plugin] (JENKINS-26778) Build-timeout+Plugin global timeout setting
Title: Message Title Vaibhav Dwivedi commented on JENKINS-26778 Re: Build-timeout+Plugin global timeout setting Hi , I recently installed build timeout plugin 1.14 and looking to populate it for all jobs . Can you please explain how the global variable setting can be done and if it will help even if the timeout was not set earlier for a job . I checked out a couple of groovy scripts also to do the same but the constructor used there was depreciated . I am a newbie for groovy usage for modifying configs . Please help me out here. Thanks Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2-plugin] (JENKINS-27601) instance caps incorrectly calculated
Title: Message Title suresh nallamilli commented on JENKINS-27601 Re: instance caps incorrectly calculated Submitted https://github.com/jenkinsci/ec2-plugin/pull/159 for this issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [google-play-android-publisher-plugin] (JENKINS-29887) Required Token Macro plugin was not installed by the Google Play APK upload plugin
Title: Message Title Christopher Orr commented on JENKINS-29887 Re: Required Token Macro plugin was not installed by the Google Play APK upload plugin Sorry about that. I had intended for the Token Macro plugin to be an optional dependency, but didn't test thoroughly enough without it installed. I'll make a new release today. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29871) NullPointerException after parsing error file
Title: Message Title Stefan Roth commented on JENKINS-29871 Re: NullPointerException after parsing error file The build results are stored on a clearcase global dynamic view. Is there a option (or something else) to find out more? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [docker-custom-build-environment-plugin] (JENKINS-29410) Compatibility with Sonar plugin (and possibly other auto installed software)
Title: Message Title Andreas Mandel commented on JENKINS-29410 Re: Compatibility with Sonar plugin (and possibly other auto installed software) My use case is a bit different - I would use the docker container as a isolation sandbox for the different builds, while still maintaining a clean - minimum dependencies environment. Therefore it wold make sense to mount the hosts' tools directory into the docker container (if the tools allow in ro mode). But this would still leave other topics open. Might be my requirement needs a different approach? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink-plugin] (JENKINS-29716) Incorrect Execution Results when using TestNG class name results seeking strategy
Title: Message Title voss qa commented on JENKINS-29716 Re: Incorrect Execution Results when using TestNG class name results seeking strategy Anybody able to assist with this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jira-plugin] (JENKINS-25015) RemoteValidationException when using "Mark JIRA Version as Released"
Title: Message Title Stefan Cordes commented on JENKINS-25015 Re: RemoteValidationException when using "Mark JIRA Version as Released" When receiving "Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden." "Cannot find Jira Project "MAV"" you should check the authorization of the User you specified in Jenkins. (For testing add the user to all groups in your MAV-project). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-sync-configuration-plugin] (JENKINS-26652) SCM Sync fails after deleting a project
Title: Message Title Stefan Schäfer commented on JENKINS-26652 Re: SCM Sync fails after deleting a project I can confirm Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [google-play-android-publisher-plugin] (JENKINS-29887) Required Token Macro plugin was not installed by the Google Play APK upload plugin
Title: Message Title Jonny Bergstrom created an issue Jenkins / JENKINS-29887 Required Token Macro plugin was not installed by the Google Play APK upload plugin Issue Type: Bug Assignee: Christopher Orr Components: google-play-android-publisher-plugin Created: 11/Aug/15 2:47 AM Environment: Jenkins 1.624 OS X 10.10.4 (Yosemite) Priority: Minor Reporter: Jonny Bergstrom I finally got a signed apk uploaded to Google Play as alpha - great. However I got stuck with the error: ERROR: Publisher 'Upload Android APK to Google Play' aborted due to exception: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/MacroEvaluationException for a while. No matter what name I entered into the .apk filename row, the above error turned up. So the reason was the Google Play plugin did not install the required Token Macro plugin. I installed it manually and there I went.
[JIRA] [slack-plugin] (JENKINS-29696) Slack notifications are serialized
Title: Message Title Sam Gleske commented on JENKINS-29696 Re: Slack notifications are serialized https://github.com/jenkinsci/slack-plugin/pull/121 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gitlab-plugin] (JENKINS-24474) gitlab-plugin
Title: Message Title evan giordanella commented on JENKINS-24474 Re: gitlab-plugin I have the same issue. Were you able to resolve it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copyartifact-plugin] (JENKINS-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names
Title: Message Title ikedam started work on JENKINS-18938 Change By: ikedam Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [copyartifact-plugin] (JENKINS-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names
Title: Message Title ikedam assigned an issue to ikedam Created a pull request: https://github.com/jenkinsci/copyartifact-plugin/pull/69 It introduce a field to specify the suffix to be used instead of the project name. Leaving empty have the project name used jest as the current brhavior to keep the backward compatibility. Jenkins / JENKINS-18938 COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names Change By: ikedam Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28690) Deadlock in hudson.model.Executor
Title: Message Title dogfood commented on JENKINS-28690 Re: Deadlock in hudson.model.Executor Integrated in jenkins_main_trunk #4246 JENKINS-28690 Aha! So I believe this will fully resolve any of these kinds of deadlocks (Revision 0ba505b60ca86d6b103b070a690a98ae6fef8c5d) Result = SUCCESS stephen connolly : 0ba505b60ca86d6b103b070a690a98ae6fef8c5d Files : core/src/main/java/hudson/model/Executor.java Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-20463) Manual build of tag breaks scm poll on trunk for parameterized builds
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-20463 Re: Manual build of tag breaks scm poll on trunk for parameterized builds Christoph Kuhnke What versions of Jenkins, Subversion Plugin and EnvInject Plugin are you using? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-20463) Manual build of tag breaks scm poll on trunk for parameterized builds
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-20463 Manual build of tag breaks scm poll on trunk for parameterized builds Change By: Manuel Jesús Recena Soto Assignee: k2nakamura Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jira-issue-updater-plugin] (JENKINS-29540) Jenkins job does not fail when it is not able to make state transition on JIRA issue
Title: Message Title Jayesh Gohil updated an issue Jenkins / JENKINS-29540 Jenkins job does not fail when it is not able to make state transition on JIRA issue Change By: Jayesh Gohil Summary: Jenkins job doe does not fail when it is not able to make state transition on JIRA issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28690) Deadlock in hudson.model.Executor
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28690 Re: Deadlock in hudson.model.Executor Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/0ba505b60ca86d6b103b070a690a98ae6fef8c5d Log: JENKINS-28690 Aha! So I believe this will fully resolve any of these kinds of deadlocks Without this, then it becomes a question of find catch and release for each potential code path that might end up restoring the interrupt flag on the current thread. Since standard Lock support is kind enough to restore the interrupt flag on the current thread when blocked waiting for the lock, that would be a hiding to nothing I welcome others to review my logic detailed in the code comment I am leaving the code comment as this is IMHO too important to assume that somebody will check the git commit history Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [envinject-plugin] (JENKINS-29867) Add options, which allow disabling the Injected variables listings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29867 Re: Add options, which allow disabling the Injected variables listings Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/lib/envinject/EnvInjectAction.java http://jenkins-ci.org/commit/envinject-lib/9ffb2877e3e483b8ce165fad2821144c6e7b928a Log: Merge pull request #6 from oleg-nenashev/JENKINS-29867-hide-envvars JENKINS-29867 - Expose owner runs in the action Compare: https://github.com/jenkinsci/envinject-lib/compare/caf1a25b8890...9ffb2877e3e4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28690) Deadlock in hudson.model.Executor
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28690 Re: Deadlock in hudson.model.Executor Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/model/Executor.java http://jenkins-ci.org/commit/jenkins/a80972307e03a7f67e97dee700720cb80f7f65d8 Log: Merge pull request #1786 from stephenc/jenkins-28690-correct-interrupt-override JENKINS-28690 Aha! So I believe this will fully resolve any of these kinds of deadlocks Compare: https://github.com/jenkinsci/jenkins/compare/7ab816878b16...a80972307e03 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [envinject-plugin] (JENKINS-29867) Add options, which allow disabling the Injected variables listings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29867 Re: Add options, which allow disabling the Injected variables listings Code changed in jenkins User: Oleg Nenashev Path: src/main/java/org/jenkinsci/lib/envinject/EnvInjectAction.java http://jenkins-ci.org/commit/envinject-lib/fa6e1a0a39ab3356a090c253a61379138d821e64 Log: JENKINS-29867 - Expose owner runs in the action This change exposes owner builds in order to allow security checks in EnvInject plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [docker-custom-build-environment-plugin] (JENKINS-29410) Compatibility with Sonar plugin (and possibly other auto installed software)
Title: Message Title Nicolas De Loof commented on JENKINS-29410 Re: Compatibility with Sonar plugin (and possibly other auto installed software) Plugin especially has been designed for such use case, so each team can provide a Dockerfile and define the exact set of tools and version it needs to build. Also, ToolInstallers would then have to run on every build, as the resulting changes in docker container would not be persisted - or have to tweak the toolinstaller so it installs within workspace. That being said, having toolinstallers to work nicely with this plugin makes sense, need to investigate further how to hack the tool installation path. You're welcome to contribute if you want to see this issue fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [pmd-plugin] (JENKINS-29799) pmdResult links doesnt work from the trendDetails graph
Title: Message Title Toto Tutu commented on JENKINS-29799 Re: pmdResult links doesnt work from the trendDetails graph Yes. Without the star part it works. Error message : Problem accessing /job/project_name/pmd/trendDetails/269/pmdResult/NORMAL. Reason: Not Found Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29886) Unable to choose my project within http://jenkins.sys.cigna.com/ after logging in
Title: Message Title Maheswari Sevalaiperumal updated an issue Jenkins / JENKINS-29886 Unable to choose my project within http://jenkins.sys.cigna.com/ after logging in Change By: Maheswari Sevalaiperumal Summary: Unable to login to choose my project within http://jenkins.sys.cigna.com/ after logging in Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29886) Unable to login to http://jenkins.sys.cigna.com/
Title: Message Title Maheswari Sevalaiperumal created an issue Jenkins / JENKINS-29886 Unable to login to http://jenkins.sys.cigna.com/ Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Aug/15 8:48 PM Priority: Major Reporter: Maheswari Sevalaiperumal Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received thi
[JIRA] [htmlpublisher-plugin] (JENKINS-29885) Submit data in a HTML page
Title: Message Title Ciprian Vintea created an issue Jenkins / JENKINS-29885 Submit data in a HTML page Issue Type: New Feature Assignee: mcrooney Components: htmlpublisher-plugin Created: 10/Aug/15 7:49 PM Environment: Jenkins v1.624 HTML Publisher Plugin v1.5 Labels: plugins htmlpublisher Priority: Minor Reporter: Ciprian Vintea I have a job which generates a HTML page (based on a script) with the status for other jobs. This HTML page is uploaded to Jenkins using Publish HTML Report plugin. It would be nice to have the possibility to enter some values in the generated HTML report and, at submit action, the information to be visible in the HTML report from the job. The forms can be available in the HTML page (created by that script). Jenkins will only manage the data sent by these forms.
[JIRA] [workflow-plugin] (JENKINS-29875) Wrong timing actions
Title: Message Title Antonio Muñiz started work on JENKINS-29875 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-29875) Wrong timing actions
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-29875 Wrong timing actions Change By: Antonio Muñiz Assignee: Jesse Glick Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29878) Jenkins forgets about last successful build after restart
Title: Message Title
Steffen Pankratz updated an issue
Jenkins / JENKINS-29878
Jenkins forgets about last successful build after restart
Change By:
Steffen Pankratz
After restarting Jenkins ('sudo /etc/init.d/jenkins restart') after an upgrade and/or plugin upgrade it forgets about the last successful build.This is the output for one of the jobs *before* restarting Jenkins:{code}drwxr-xr-x 12 buildhost buildhost 4.0K Aug 10 10:59 .drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:39 ..drwxr-xr-x 2 buildhost buildhost 4.0K Aug 4 18:39 10drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:27 11drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:45 12drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 18:26 13drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 21:51 14drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:09 15drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:59 16drwxr-xr-x 4 buildhost buildhost 4.0K Jul 31 18:00 6drwxr-xr-x 4 buildhost buildhost 4.0K Aug 2 01:26 8drwxr-xr-x 4 buildhost buildhost 4.0K Aug 4 14:24 9lrwxrwxrwx 1 buildhost buildhost2 Aug 5 01:45 lastFailedBuild -> 12lrwxrwxrwx 1 buildhost buildhost2 Aug 10 10:59 lastStableBuild -> 16lrwxrwxrwx 1 buildhost buildhost2 Aug 10 10:59 lastSuccessfulBuild -> 16lrwxrwxrwx 1 buildhost buildhost2 Aug 1 00:28 lastUnstableBuild -> -1lrwxrwxrwx 1 buildhost buildhost2 Aug 5 01:45 lastUnsuccessfulBuild -> 12-rw-r--r-- 1 buildhost buildhost0 Jul 31 17:30 legacyIds{code}The symbolic link _lastSuccessfulBuild_ points to build 16.This is the output for one of the jobs *after* restarting Jenkins:{code}drwxr-xr-x 12 buildhost buildhost 4.0K Aug 10 10:59 .drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:39 ..drwxr-xr-x 2 buildhost buildhost 4.0K Aug 4 18:39 10drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:27 11drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:45 12drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 18:26 13drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 21:51 14drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:09 15drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:59 16drwxr-xr-x 4 buildhost buildhost 4.0K Jul 31 18:00 6drwxr-xr-x 4 buildhost buildhost 4.0K Aug 2 01:26 8drwxr-xr-x 4 buildhost buildhost 4.0K Aug 4 14:24 9lrwxrwxrwx 1 buildhost buildhost2 Aug 5 01:45 lastFailedBuild -> 12lrwxrwxrwx 1 buildhost buildhost2 Aug 10 10:59 lastStableBuild -> 16 -1 lrwxrwxrwx 1 buildhost buildhost2 Aug 10 10:59 lastSuccessfulBuild -> 16 -1 lrwxrwxrwx 1 buildhost buildhost2 Aug 1 00:28 lastUnstableBuild -> -1lrwxrwxrwx 1 buildhost buildhost2 Aug 5 01:45 lastUnsuccessfulBuild -> 12-rw-r--r-- 1 buildhost buildhost0 Jul 31 17:30 legacyIds{code}The symbolic link _lastSuccessfulBuild_ is a broken symbolic link now, pointing to build -1, which does not exist. As you can see build 16 is still there.If have no idea what is wrong.The problem is reproducible.I don't have a workaround for this issue.
[JIRA] [p4-plugin] (JENKINS-28237) p4-plugin does not provide accurate polling results in workflow job
Title: Message Title Robby Pocase updated an issue Jenkins / JENKINS-28237 p4-plugin does not provide accurate polling results in workflow job Change By: Robby Pocase Labels: p4-plugin workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [metadata-plugin] (JENKINS-29884) Render URL's as hyperlinks in Build Metadata Report
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-29884 Render URL's as hyperlinks in Build Metadata Report Issue Type: Improvement Assignee: rsandell Components: metadata-plugin Created: 10/Aug/15 6:22 PM Labels: user-experience Priority: Minor Reporter: Ioannis Moutsatsos It would be useful to render any URLs used as metadata in the report as hyperlinks, similar to how the Jenkins console represents URLs. This way a user that views the report could easily jump to the hyperlinked URL. Add Comment
[JIRA] [cli] (JENKINS-29883) set-build-description no longer appends descriptions.
Title: Message Title Jason Stanley created an issue Jenkins / JENKINS-29883 set-build-description no longer appends descriptions. Issue Type: Bug Assignee: Unassigned Components: cli Created: 10/Aug/15 5:54 PM Environment: CentOS 6.5 Jenkins 1.615 Labels: set-build-description cli Priority: Major Reporter: Jason Stanley After upgrading from 1.594 to 1.615, if you run the command set-build-description, it will no longer append a new description if an existing description exists. Before the upgrade if I ran the set-build-description command 4 times, each time adding a number, the job description would say: 1 2 3 4 After the upgrade, the job description now looks like this; 4
[JIRA] [assembla-plugin] (JENKINS-29882) Authentication Fails
Title: Message Title Dave Szabo created an issue Jenkins / JENKINS-29882 Authentication Fails Issue Type: Bug Assignee: Unassigned Components: assembla-plugin Created: 10/Aug/15 5:43 PM Priority: Minor Reporter: Dave Szabo I installed the Assembla plugin for Jenkins. Authentication fails when testing my connection on the Jenkins Configuration page after the plugin is enabled. It seems that something has possibly changed with the Assembla login that might be affecting this. Add Comment
[JIRA] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-29881 WorkflowRun.getChangeSets should skip empty changesets Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 10/Aug/15 5:40 PM Priority: Minor Reporter: Jesse Glick AbstractBuild.getChangeSets skips builds with no changes but WorkflowRun does not. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [workflow-plugin] (JENKINS-29880) Honor getJobActions
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-29880 Honor getJobActions Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 10/Aug/15 5:28 PM Priority: Major Reporter: Jesse Glick getJobActions is defined for Job/JobProperty but interpreted by AbstractProject.createTransientActions for whatever reason. Either WorkflowJob should do the same, or a TransientActionFactory> should be defined in core which interprets getJobActions (though this would be slightly incompatible as then AbstractProject.getActions would omit them even though AbstractProject.getAllActions would include them). Add Comment
[JIRA] [workflow-plugin] (JENKINS-29676) Workflow: executing bat through Groovy can loop infinitely.
Title: Message Title Martin Bédard commented on JENKINS-29676 Re: Workflow: executing bat through Groovy can loop infinitely. Due to problem using Maven at my work location, I was unable to build the .hpi of 1.9-beta-1. I normally find the beta hpi in the archives, is there a reason for 1.9-beta-1 to be absent? Also, I noticed the fix it is not present in the most recent release, 1.9 three days ago. As soon as it will be in a most recent version, I'll confirm you it's working, but for now I'm just unable to obtain the 1.9-beta-1 hpi Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [mercurial-plugin] (JENKINS-29879) mercurial branch change log includes every change
Title: Message Title Gedalia Pasternak created an issue Jenkins / JENKINS-29879 mercurial branch change log includes every change Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin, multiple-scms-plugin Created: 10/Aug/15 4:16 PM Environment: Mercurial plugin 1.54 jenkins 1.624 Mercurial 3.5 (seems to happen on older versions as well) Labels: changelog scm mercurial Priority: Major Reporter: Gedalia Pasternak the hg change log that is generated from: hg log --rev branch_name:0 --follow --prune hash_name includes every commit in a repository for me, I've tested this on 3-4 repos with a few different version of hg. it seems to produce the right info with: hg log --rev branch_name --follow --prune hash_name not sure if a problem is that branch name = diguy-13_0-ecosim (but "diguy-13_0-ecosim:0" doesn't behave any differently
[JIRA] [durable-task-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29877 failure when incorrect shell is configured is not clear enough to diagnose root cause. Change By: Jesse Glick Component/s: workflow-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29877 failure when incorrect shell is configured is not clear enough to diagnose root cause. Change By: Jesse Glick Labels: diagnostics workflow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title Jesse Glick commented on JENKINS-29877 Re: failure when incorrect shell is configured is not clear enough to diagnose root cause. In the case of a traditional Shell step, Jenkins is actually trying to launch the bash process from Java, which throws that IOException if it does not exist. In the case of durable BourneShellScript, Jenkins is launching sh on a controller script, which in turn runs your script.sh with a shebang interpreter directive. And I suppose sh is printing this unhelpful message. Configuring a global shell is a very bad idea to begin with. Probably when it is set, BourneShellScript should note its value in a message. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-29877 failure when incorrect shell is configured is not clear enough to diagnose root cause. Change By: Jesse Glick Labels: diagnostics Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title Paul Allen commented on JENKINS-25249 Re: Post-commit hook for P4 plugin I like the POST data idea for change-list details. I may combine [1] and [2], using a web service for Jenkins to subscribe to and then use Perforce triggers to poke the web service. [Perforce][Web Service] [Jenkins] | | | | | <-(subscribe)-- | | | | | (change-commit)---> [ ]| | [ ] (POST change)---> [ ] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-29875) Wrong timing actions
Title: Message Title Jesse Glick commented on JENKINS-29875 Re: Wrong timing actions Probably related to, or a duplicate of, JENKINS-25879. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29878) Jenkins forgets about last successful build after restart
Title: Message Title Steffen Pankratz updated an issue Jenkins / JENKINS-29878 Jenkins forgets about last successful build after restart Change By: Steffen Pankratz Summary: Jenkins forgets about last successful builds build after restart Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29878) Jenkins forgets about last successful builds after restart
Title: Message Title
Steffen Pankratz created an issue
Jenkins / JENKINS-29878
Jenkins forgets about last successful builds after restart
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
10/Aug/15 3:40 PM
Environment:
* Ubuntu 12.04.5 LTS x86 * Jenkins 1.624
Priority:
Major
Reporter:
Steffen Pankratz
After restarting Jenkins ('sudo /etc/init.d/jenkins restart') after an upgrade and/or plugin upgrade it forgets about the last successful build.
This is the output for one of the jobs before restarting Jenkins:
drwxr-xr-x 12 buildhost buildhost 4.0K Aug 10 10:59 .
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:39 ..
drwxr-xr-x 2 buildhost buildhost 4.0K Aug 4 18:39 10
drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:27 11
drwxr-xr-x 2 buildhost buildhost 4.0K Aug 5 01:45 12
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 18:26 13
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 5 21:51 14
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:09 15
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 10 10:59 16
drwxr-xr-x 4 buildhost buildhost 4.0K Jul 31 18:00 6
drwxr-xr-x 4 buildhost buildhost 4.0K Aug 2 01:26 8
drwxr-xr-x 4 buildhost buildhost 4.0
[JIRA] [build-timeout-plugin] (JENKINS-29602) Abort wildly verbose job-runs
Title: Message Title Darrel Vuncannon closed an issue as Won't Fix I'm closing because another plugin seems better suited for this functionality. Jenkins / JENKINS-29602 Abort wildly verbose job-runs Change By: Darrel Vuncannon Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title nyoung02 commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 Hi, This bug is marked as delivered in the changelog for version 2.5.1 of the svn plugin: https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin Can anyone confirm that this does indeed fix the issue for them - because I've tried installing Jenkins 1.623 with Subversion plugin 2.5.1 on a clean environment and I hit exactly this issue when I checkout externals (Windows master and Windows/Linux slaves). Either the fix is not actually contained within the plugin as listed, or I have encountered a different but visually similar problem. I'm not currently blocked because I've reverted to the default svn plugin for now (1.5.4) and this functions perfectly in every way except for svn 1.8 support. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Title: Message Title Will Saxon commented on JENKINS-28034 Re: SCM polling not using correct user credentials We're not using remote polling - we have 'force polling using workspace' enabled. I can't spend any time on this right now but will try to get more details this evening. Maybe it's just something we're doing wrong in our environment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [bitkeeper-plugin] (JENKINS-29788) Bk configuration removed on project change
Title: Message Title A E commented on JENKINS-29788 Re: Bk configuration removed on project change I am also using Multiple SCMs plugin version 0.4 to pull from a mercurial repo for the same job. Looks like the problem is an interaction with that plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Title: Message Title Mark Waite commented on JENKINS-28034 Re: SCM polling not using correct user credentials What you reported doesn't match what I see if my test environment. The remote polling works even with a repository which is completely isolated except for the credential that was added to allow the git plugin access to the repository. Can you provide more details of the steps you take to show the problem so that others can duplicate it? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-plugin] (JENKINS-29787) NPE on stop in GitHubPushTrigger
Title: Message Title Kanstantsin Shautsou resolved as Fixed Jenkins / JENKINS-29787 NPE on stop in GitHubPushTrigger Change By: Kanstantsin Shautsou Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29853) git/NotifyCommit not working
Title: Message Title Mark Waite commented on JENKINS-29853 Re: git/NotifyCommit not working What changed last week? If you revert that change, does the problem resolve itself? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-plugin] (JENKINS-29787) NPE on stop in GitHubPushTrigger
Title: Message Title Kanstantsin Shautsou commented on JENKINS-29787 Re: NPE on stop in GitHubPushTrigger Should be fixed in 1.12.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29853) git/NotifyCommit not working
Title: Message Title Andrian Jardan commented on JENKINS-29853 Re: git/NotifyCommit not working We have a setup where commits to our repos call this URL for repo updates, so Jenkins starts builds based on these updates to the repos, and all this stuff stopped working last week. I am not sure about other versions as we only have one jenkins installation. I updated Jenkins and plugins to all available latest versions, and we still see this issue. What other info can I provide to help ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman closed an issue as Won't Fix Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Change By: Nigel Harniman Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman resolved as Won't Fix Customer fixed permissions issue. Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Change By: Nigel Harniman Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert This fixed the customer's problem - was a permission issue. This can be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-26050) Workflow integration for Parameterized Trigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26050 Re: Workflow integration for Parameterized Trigger Code changed in jenkins User: Sam Van Oort Path: pom.xml src/main/java/hudson/plugins/parameterizedtrigger/BlockableBuildTriggerConfig.java src/main/java/hudson/plugins/parameterizedtrigger/BuildTrigger.java src/main/java/hudson/plugins/parameterizedtrigger/BuildTriggerConfig.java src/main/java/hudson/plugins/parameterizedtrigger/DefaultParameterValuesActionsTransform.java src/main/java/hudson/plugins/parameterizedtrigger/ITransformProjectParametersAction.java src/main/java/hudson/plugins/parameterizedtrigger/ProjectSpecificParameterValuesActionTransform.java src/main/java/hudson/plugins/parameterizedtrigger/ProjectSpecificParametersActionFactory.java src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java src/main/resources/hudson/plugins/parameterizedtrigger/BuildTriggerConfig/config.jelly src/test/java/hudson/plugins/parameterizedtrigger/test/BuildTriggerConfigTest.java src/test/java/hudson/plugins/parameterizedtrigger/test/TriggerBuilderTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/5f0492121b03f68000f85ec04340a853e660ed59 Log: Merge pull request #87 from svanoort/feature-workflow-compatibility JENKINS-26050 Fix Workflow compatibility for Parameterized Trigger Compare: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/df0ee6e4a68b...5f0492121b03 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29877) failure when incorrect shell is configured is not clear enough to diagnose root cause.
Title: Message Title
James Nord created an issue
Jenkins / JENKINS-29877
failure when incorrect shell is configured is not clear enough to diagnose root cause.
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
durable-task-plugin, workflow-plugin
Created:
10/Aug/15 2:03 PM
Environment:
jenkis 1.609.1 workflow 1.9-beta-1
Priority:
Minor
Reporter:
James Nord
If you have a shell configured in "manage jenkins" and that shell is not available on the slave used by a workflow sh step, then the error does not help you diagnose the issue.
e.g.
node ('different_slave') {
sh 'echo hello'
}
produces the following error
[workflow_test] Running shell script
sh: 1: /home/jenkins/slave/workspace/workflow_test/.e59a0d2c/script.sh: not found
this implies an error with Jenkins code and no
[JIRA] [msbuild-plugin] (JENKINS-25841) MSBuild exe in white space path messes up properties on command line
Title: Message Title espenalb commented on JENKINS-25841 Re: MSBuild exe in white space path messes up properties on command line Worked for me too Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-29875) Wrong timing actions
Title: Message Title Antonio Muñiz commented on JENKINS-29875 Re: Wrong timing actions The issue is shown when using the "mail" step also. So I think it could be related to all step executions implementing AbstractSynchronousStepExecution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
UPDATED HOT LIST (8-10-2015)
*Hello Partner,* *This is Phani from Humac Inc.* *Here is the Updated list of available consultants for your requirements.* *Please send requirements to ph...@humacinc.com or call me at 623-748-1724* *Name* *Experience* *Job Title* *Location* *Re Loc.* *Avail* *Visa* *Anushree* *9+Yrs* *Sr.SAS (Clinical)* *Caremore, CA* *Open* *Immediately* *H1B* *Anu* *9+Yrs* *Sr.Hadoop Admin* *Booz Allen Hamilton * *Open* *Immediately* *H1B* *Anushree* *9+Yrs* *Sr. SAS Programmer* *Caremore, CA* *Open* *Immediately* *H1B* *Tripti* *8 Yrs* *Sr. Java UI Developer* *Phoenix , AZ* *Open* *Immediately* *H1B* *Nuthana* *8 Yrs* *Sr.Java developer* *Phoenix , AZ* *AZ* *Immediately* *H1B* *Ruchi* *8+Yrs* *Sr.Cognos BI dev* *OH* *Only NC* *Immediately* *H1B* -- -- Thanks & Regards ……… *?* *Phani * *HUMAC INC* *Technical Recruiter* (623) 748-1724 ph...@humacinc.com Gtalk- phani.humacinc -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Pärsson edited a comment on JENKINS-25249 Re: Post-commit hook for P4 plugin Suggestion Design 1 is similar to what the Subversion plugin does. The To use this with Subversion , the Subversion server is configured with a post-commit hook that makes a request to Jenkins over HTTP. One significant difference from your design is that the request however also includes the changed paths as POST data, removing the need for Jenkins to ask the Subversion server for changes. See the [Subversion plugin's wiki page|https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-Postcommithook] for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [p4-plugin] (JENKINS-25249) Post-commit hook for P4 plugin
Title: Message Title David Pärsson commented on JENKINS-25249 Re: Post-commit hook for P4 plugin Suggestion 1 is similar to what the Subversion plugin does. The Subversion server is configured with a post-commit hook that makes a request to Jenkins over HTTP. One significant difference is that the request however also includes the changed paths as POST data, removing the need for Jenkins to ask the Subversion server for changes. See the Subversion plugin's wiki page for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gallio-plugin] (JENKINS-29821) PermGen space error on converting gallio report
Title: Message Title Alexandre Aubert closed an issue as Fixed this was because of PermSize not set for Jenkins : default value was not enough. Setting -XX:PermSize=512m in jenkins.xml has solved the problem. Jenkins / JENKINS-29821 PermGen space error on converting gallio report Change By: Alexandre Aubert Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29876) NPE when triggering downstream job (again)
Title: Message Title
Marek Lemanczyk updated an issue
Jenkins / JENKINS-29876
NPE when triggering downstream job (again)
Change By:
Marek Lemanczyk
We've some jobs which does do some generic jobs tasks . On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.Instead of triggering all the downstream jobs they fire this NPE:{quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredTriggering a new build of .OUR PROJECT NAME...FATAL: nulljava.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687) at hudson.model.Build$BuildExecution.cleanUp(Build.java:200) at hudson.model.Run.execute(Run.java:1788) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You re
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title
Marek Lemanczyk updated an issue
Jenkins / JENKINS-29876
NPE when triggering downstream job (again)
Change By:
Marek Lemanczyk
We've some jobs which check for repo changes only without any build step does some generic jobs . They On success they are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.Instead of triggering all the downstream jobs they fire this NPE:{quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredTriggering a new build of .OUR PROJECT NAME...FATAL: nulljava.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687) at hudson.model.Build$BuildExecution.cleanUp(Build.java:200) at hudson.model.Run.execute(Run.java:1788) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title
Marek Lemanczyk updated an issue
Jenkins / JENKINS-29876
NPE when triggering downstream job (again)
Change By:
Marek Lemanczyk
We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs. This is similar to JENKINS-25758, but its resolution didn't help. Downgrade to 1.620 fixed the problem.There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best.Instead of triggering the all the downstream jobs they fire this NPE:{quote}Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggeredTriggering a new build of .OUR PROJECT NAME...FATAL: nulljava.lang.NullPointerException at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:111) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:84) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:141) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:245) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:687) at hudson.model.Build$BuildExecution.cleanUp(Build.java:200) at hudson.model.Run.execute(Run.java:1788) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381){quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Marek Lemanczyk created an issue Jenkins / JENKINS-29876 NPE when triggering downstream job (again) Issue Type: Bug Assignee: Unassigned Components: core Created: 10/Aug/15 12:05 PM Environment: Jenkins 1.621+ Windows 2003 Labels: dependencies permissions trigger Priority: Major Reporter: Marek Lemanczyk We've some jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs. This is similar to JENKINS-25758 , but its resolution didn't help. Downgrade to 1.620 fixed the problem. There are 2 downstream jobs configured. Starting with 1.621 only the first downstream job gets started after successful build, at best. Instead of triggering the all the downstream jobs they fire this NPE:
[JIRA] [workflow-plugin] (JENKINS-29875) Wrong timing actions
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-29875 Wrong timing actions Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 10/Aug/15 11:57 AM Environment: Workflow master branch (1.10-SNAPSHOT) Launched with hpi:run Priority: Major Reporter: Antonio Muñiz This workflow script is generating wrong timing actions (timing action values taken from build/N/workflow/*.xml): Step TimingAction value echo logged time start=new Date()
[JIRA] [active-directory-plugin] (JENKINS-29860) SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider
Title: Message Title Kenneth Baltrinic edited a comment on JENKINS-29860 Re: SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider A little more information on this issue: * Apparently when this issue occurs it only affects the given user. Our tests show that other users having configured ssh keys are able to continue to use the CLI with ssh auth.* This is only affecting SSH Auth, the affected user is able to use the CLI if we switch to username/password auth.* We have tried various things short of restarting the service in order to resolve this issue (removing and re-assigning the publish public SSH key for the user in Jenkins, Disabling disabling and re-enabling AD auth in Jenkins, etc.) None of that seems to work. A 'soft' restart (a restart initiated from the plugin-update page) does work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-29860) SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider
Title: Message Title Kenneth Baltrinic edited a comment on JENKINS-29860 Re: SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider A little more information on this issue: * Apparently when this issue occurs it only affects the given user. Our tests show that other users having configured ssh keys are able to continue to use the CLI with ssh auth.* This is only affecting SSH Auth, the affected user is able to use the CLI if we switch to username/password auth.* We have tried various things short of starting restarting the service in order to resolve this issue (removing and re-assigning the publish SSH key for the user in Jenkins, Disabling and re-enabling AD auth in Jenkins, etc.) None of that seems to work. A 'soft' restart (a restart initiated from the plugin-update page) does work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-29860) SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider
Title: Message Title Kenneth Baltrinic commented on JENKINS-29860 Re: SSH Auth Breaks with "No Password" error from ActiveDirectoryUnixAuthenticationProvider A little more information on this issue: Apparently when this issue occurs it only affects the given user. Our tests show that other users having configured ssh keys are able to continue to use the CLI with ssh auth. This is only affecting SSH Auth, the affected user is able to use the CLI if we switch to username/password auth. We have tried various things short of starting the service in order to resolve this issue (removing and re-assigning the publish SSH key for the user in Jenkins, Disabling and re-enabling AD auth in Jenkins, etc.) None of that seems to work. A 'soft' restart (a restart initiated from the plugin-update page) does work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [android-lint-plugin] (JENKINS-29870) Make Android Lint Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-29870 Re: Make Android Lint Plugin compatible with Workflow A PR has been sent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title simon werling commented on JENKINS-29422 Re: Cannot run program "groovy" What is quite common is that you have e.g. NFS drive with various tools and mount the disk when you create the slave machine or start the slave ... Since we want to avoid network influenced false negatives in the testing area, i need to avoid this aproach. =( At least directly accessing the tool chain over network can be workaround by copying these tools locally, before the slave starts. Hope you find a proper windows testing machine soon =) thanks!simon Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-plugin] (JENKINS-29787) NPE on stop in GitHubPushTrigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29787 Re: NPE on stop in GitHubPushTrigger Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java http://jenkins-ci.org/commit/github-plugin/18aca714ac992d6c08fa4999fd09cd0e396ff50b Log: [FIXED JENKINS-29787] Fix NPE for race condition. See JENKINS-29794 for details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [github-plugin] (JENKINS-29787) NPE on stop in GitHubPushTrigger
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29787 Re: NPE on stop in GitHubPushTrigger Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java http://jenkins-ci.org/commit/github-plugin/cc84ef4e58d846e01b121639be012c336c73fcef Log: Merge pull request #67 from KostyaSha/fixNPE JENKINS-29787 Fix NPE for race condition. Compare: https://github.com/jenkinsci/github-plugin/compare/a8dca515...cc84ef4e58d8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29794) race conditions in Triggers
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29794 Re: race conditions in Triggers Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java http://jenkins-ci.org/commit/github-plugin/18aca714ac992d6c08fa4999fd09cd0e396ff50b Log: [FIXED JENKINS-29787] Fix NPE for race condition. See JENKINS-29794 for details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27329) WorkspaceCleanupThread deletes Matrix project workspaces
Title: Message Title mwebber assigned an issue to Daniel Beck Daniel knows about this area, so assigning to him for comment (sorry, Daniel!) Jenkins / JENKINS-27329 WorkspaceCleanupThread deletes Matrix project workspaces Change By: mwebber Assignee: Daniel Beck Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-27329) WorkspaceCleanupThread deletes Matrix project workspaces
Title: Message Title mwebber commented on JENKINS-27329 Re: WorkspaceCleanupThread deletes Matrix project workspaces >> Jenkins silently and erroneously deletes workspaces on slaves for matrix projects that are not old We just hit this problem (or what appears to be this problem) as well. An extract from $JENKINS_HOME/Workspace clean-up.log: Deleting /Users/dlshudson/jenkins_slave/workspace/dials_distribute on dials-mac-mini Deleting /scratch/jenkins_slave/workspace/dials_distribute on dials-ws133 Deleting /scratch/jenkins_slave/workspace/dials_distribute on dials-ws154 side-note: it's a shame those log lines are not time-stamped The 3 mentioned workspaces are from a matrix project, and all workspaces had been accessed recently. Presumably there is a bug in the workspace cleanup code that means it does not handle matrix projects correctly. Note that the job configuration specifies 4 slaves: 1 by label, and 3 by individual nodes. The workspaces that were deleted were those on the 3 slaves that were specified as individual notes, but the workspace on the slave that was specified by label was not deleted. Possibly a clue o the bug? The workaround is to set hudson.model.WorkspaceCleanupThread.disabled=true. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program "groovy" as for groovy_default_and_PATH_variable_not_working.png - it seems to be some Windows specific issue, I need to look on it (i.e. find some windows machine), on Linux works fine as for some_workaround.png - in case you have already a groovy installation on local machine, you can un-check "Install automatically" field in global Jenkins configuration and set a path to the installation. It can be arbitrary directory and adding it to the PATH shouldn't be needed. What is quite common is that you have e.g. NFS drive with various tools and mount the disk when you create the slave machine or start the slave ... maybe there can be again some windows specific issues, but AFAIK should work (at least my colleagues who run some groovy scripts on windows have never complained ) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [findbugs-plugin] (JENKINS-29489) Fix "How to use" in the wiki
Title: Message Title Ulli Hafner resolved as Not A Defect The tag still is required for findbugs 2.x. If you are interested, please update the wiki on your own with a section for findbugs 2.x and 3.x. The wiki is accessible for everyone... Jenkins / JENKINS-29489 Fix "How to use" in the wiki Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [pmd-plugin] (JENKINS-29799) pmdResult links doesnt work from the trendDetails graph
Title: Message Title Ulli Hafner commented on JENKINS-29799 Re: pmdResult links doesnt work from the trendDetails graph Can you please wrap the error in a noformat tag? Is the star part of the URL? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29871) NullPointerException after parsing error file
Title: Message Title Ulli Hafner edited a comment on JENKINS-29871 Re: NullPointerException after parsing error file Seems that the directory storing the build results is not available anymore, or the file is missing. Do you have a cleanup script somewhere? Is it possible that the reference build has been deleted? Are the build results stored on another partition that might be not mounted? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29871) NullPointerException after parsing error file
Title: Message Title Ulli Hafner commented on JENKINS-29871 Re: NullPointerException after parsing error file Seems that the directory storing the build results is not available anymore. Do you have a cleanup script somewhere? Is it possible that the reference build has been deleted? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-29871) NullPointerException after parsing error file
Title: Message Title Ulli Hafner edited a comment on JENKINS-29871 Re: NullPointerException after parsing error file Seems that the directory storing the build results is not available anymore , or the file is missing . Do you have a cleanup script somewhere? Is it possible that the reference build has been deleted? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-4501) WorkspaceCleanupThread deletes Matrix project workspaces
Title: Message Title mwebber commented on JENKINS-4501 Re: WorkspaceCleanupThread deletes Matrix project workspaces See new issue JENKINS-27329 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-dsl-plugin] (JENKINS-29874) copyArtifacts deprecated call broke passing env vars to `buildNumber`
Title: Message Title
Pedro Algarvio created an issue
Jenkins / JENKINS-29874
copyArtifacts deprecated call broke passing env vars to `buildNumber`
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
10/Aug/15 10:23 AM
Priority:
Major
Reporter:
Pedro Algarvio
Recently copyArtifacts 2 argument call was deprecated in favor of explicitly passing buildNumber(), however, buildNumber() expects an integer which breaks doing something like:
buildNumber('${CLONE_BUILD_ID}')
Add Comment
[JIRA] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title simon werling commented on JENKINS-29422 Re: Cannot run program "groovy" Hi, i have some workaround to avoid the automatic groovy package installation AND to get the groovy plugin working. see the attached image some_workaround Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title simon werling updated an issue Jenkins / JENKINS-29422 Cannot run program "groovy" Change By: simon werling Attachment: some_workaround.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-29807) NullPointerException when triggering dependent builds
Title: Message Title sseidel commented on JENKINS-29807 Re: NullPointerException when triggering dependent builds Problem seemed to be a disabled project which still had the failing project as upstream dependency. After deleting the disabled project all downstream triggers executed without NPE on 1.624. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title simon werling updated an issue Jenkins / JENKINS-29422 Cannot run program "groovy" Change By: simon werling Attachment: groovy_default_and_PATH_variable_not_working.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title simon werling commented on JENKINS-29422 Re: Cannot run program "groovy" Ok, I guess i got it. So it seems that the PATH variable is not correctly interpreted by the running java slave process? see the attachment : groovy_default_and_PATH_variable_not_working.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-plugin] (JENKINS-3547) On Windows Vista slave: svn: No buffer space available
Title: Message Title Nico Mommaerts commented on JENKINS-3547 Re: On Windows Vista slave: svn: No buffer space available We are regularly seeing this on Jenkins ver. 1.580.2.1 (Jenkins Enterprise by CloudBees 14.11) with Subversion 2.4.3 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-29422) Cannot run program "groovy"
Title: Message Title vjuranek commented on JENKINS-29422 Re: Cannot run program "groovy" Wouldn´t it make sense to call 'groovy' without any prefix-path specification? yes, this is exactly how it works. If you setup groovy installation, it uses full path to the installation, but (Default) call simply groovy without any prefix path, so e.g. on Linux is used the first groovy binary found on paths set in PATH environment variable - but doesn't do any auto installation and if groovy is not the PATH, it fails with an error. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [zentimestamp-plugin] (JENKINS-29873) Zentimestamp should set BUILD_TIMESTAMP variable in any case
Title: Message Title Michael Rentschler created an issue Jenkins / JENKINS-29873 Zentimestamp should set BUILD_TIMESTAMP variable in any case Issue Type: Bug Assignee: Steven Christou Components: zentimestamp-plugin Created: 10/Aug/15 8:30 AM Priority: Major Reporter: Michael Rentschler With Jenkins 1.597, the environment variable BUILD_ID was changed from timestamp to the build number. The zentimestamp plugin can not alter the content of BUILD_ID anymore. A new environment variable should be introduced, like BUILD_TIMESTAMP. This can be modified by the plugin then. Add Comment
[JIRA] [zentimestamp-plugin] (JENKINS-29873) Zentimestamp should set BUILD_TIMESTAMP variable in any case
Title: Message Title
Michael Rentschler updated an issue
Jenkins / JENKINS-29873
Zentimestamp should set BUILD_TIMESTAMP variable in any case
Change By:
Michael Rentschler
With older Jenkins 1.597 versions , the timestamp environment variable {{ (formerly BUILD_ID }} ) was changed from timestamp already set to the build number. The {{zentimestamp}} default timestamp format by the Jenkins core and was only modified by the Zen Timestamp plugin can not alter if the content of {{BUILD_ID}} anymore option "Change date pattern" was checked (inside the job or node configuration) and a different format was selected . A The new environment variable should Zen plugin must be introduced, like {{ fixed to set the BUILD_TIMESTAMP }} variable in any case, even if there was no format defined inside the job or node configuration, by using the default timestamp format . This can must be modified done by the plugin then now, since BUILD_TIMESTAMP is not set by the core anymore .
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-29807) NullPointerException when triggering dependent builds
Title: Message Title sseidel edited a comment on JENKINS-29807 Re: NullPointerException when triggering dependent builds Having the same problem. This is a major problem for us because the whole CI chain fails - downstream projects are not triggered hence tests are not run and automated deployment does not happen. Last version which works is 1.620. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
