[JIRA] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
Stefan Thurnherr commented on JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 FYI: Working on migrating the jira plugin from SOAP to REST over here: https://github.com/stefanthurnherr/jira-plugin Planning to migrate to the credentials plugin at the same time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [translation] (JENKINS-22419) Basic review of Polish translation (language errors, wrong translation, inconsistency, poor quality)
Hubert Gajewski created JENKINS-22419 Basic review of Polish translation (language errors, wrong translation, inconsistency, poor quality) Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: basic_review_of_polish_translation.patch Components: translation Created: 30/Mar/14 3:33 PM Description: I am involved in localisation and QA (mainly in Mozilla projects, also GNU/Linux projects in the past) for about 10 years and I use Jenkins for about 3 years. Usually my browser locale is set up on en-US or en-GB but sometime I set up it on pl-PL. Then Jenkins automatically switches to use Polish translation. Unfortunately Polish translation is one of the worst I've ever seen. I decided to do fast, basic review all properties files with Polish translation. Usually I submit separate bug for each change or/and component but in this case number of issue was too high so I decided to submit everything in single bug. I focused on: language errors (many, many) wrong translation (translator did not understand English version, there were a few only) inconsistency (there was about 7, maybe more translations for word "build" - eg. build, task, execution, running, job, probably because there is no one good Polish word in this case, people usually use English word. I used "kompilacja"- it is some kind of compromise. The same issue exists with "failure" and few others.) poor quality (in a few places it looked like written by someone without elementary education) Some of my changes are not perfect, some could be discussed and improved but generally it improves overall quality. Feel free to take all the changes or only some of them. Fix Versions: current Project: Jenkins Priority: Minor Reporter: Hubert Gajewski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [brakeman] (JENKINS-22420) Post-Build Action not available (freestyle or multi-config)
Jim Yanko created JENKINS-22420 Post-Build Action not available (freestyle or multi-config) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: brakeman Created: 30/Mar/14 5:03 PM Description: Brakeman Plugin v0.7 is noted as installed currently, yet the Post-Build Action for Brakeman does not appear in the select menu of jobs for either job type supported by my jenkins instance. project_freestyle_SAMPLE project_multiconfig_SAMPLE Currently I am seeing this in Jenkins v1.554 Project: Jenkins Priority: Major Reporter: Jim Yanko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
Michal Turek started work on JENKINS-22303 Should have option to not care about build failure status Change By: Michal Turek (30/Mar/14 5:12 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
SCM/JIRA link daemon commented on JENKINS-22303 Should have option to not care about build failure status Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountPublisher.java src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly http://jenkins-ci.org/commit/sloccount-plugin/38eedb0848fd345f84f8a0294c2111e4ed4b446f Log: JENKINS-22303 Should have option to not care about build failure status Option to try to process the report files even if the build is not successful added to job configuration. If no file is matching the input pattern, no data are stored and the build is marked as failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
Michal Turek resolved JENKINS-22303 as Fixed Should have option to not care about build failure status Fixed, will be released in version 1.17. Change By: Michal Turek (30/Mar/14 5:36 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
SCM/JIRA link daemon commented on JENKINS-22303 Should have option to not care about build failure status Code changed in jenkins User: Michal Turek Path: src/main/java/hudson/plugins/sloccount/SloccountPublisher.java src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly http://jenkins-ci.org/commit/sloccount-plugin/2d9956629d6b1b2f2ce479af14369807468b56cb Log: Merge pull request #39 from mixalturek/master JENKINS-22303 Should have option to not care about build failure status Compare: https://github.com/jenkinsci/sloccount-plugin/compare/4f30bbf5c058...2d9956629d6b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
Michal Turek edited a comment on JENKINS-22303 Should have option to not care about build failure status Implemented, will be released in version 1.17. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
Michal Turek closed JENKINS-22303 as Fixed Should have option to not care about build failure status Change By: Michal Turek (30/Mar/14 5:39 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] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
SCM/JIRA link daemon resolved JENKINS-20753 as Fixed Remove unused Append Hudson Build Number option Change By: SCM/JIRA link daemon (30/Mar/14 5:41 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-21063) Indicate in icon (or tooltip) if a release build failed
SCM/JIRA link daemon commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Code changed in jenkins User: Anders Hammar Path: pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction/badge.jelly src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeActionTest.java src/test/resources/org/jvnet/hudson/plugins/m2release/maven3-failing-project.zip http://jenkins-ci.org/commit/m2release-plugin/32529b14eec921c0f2baea34ca6bd6548246a9a3 Log: JENKINS-21063 Badge now retrieves dryRun, version, and failedBuild info from build instead of storing it. As a side effect, variables in M2ReleaseBadgeAction were removed which will affect builds persisted with older versions of the plugin. Also, required version of Jenkins was bumped to 1.509.3. 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] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
SCM/JIRA link daemon commented on JENKINS-20753 Remove unused Append Hudson Build Number option Code changed in jenkins User: imod Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly http://jenkins-ci.org/commit/m2release-plugin/9eddf086dc875f765a9308244bac29dbaca1a964 Log: Merge branch 'JENKINS-20753' of https://github.com/andham/m2release-plugin into andham-JENKINS-20753 Compare: https://github.com/jenkinsci/m2release-plugin/compare/7ee2284e0515...9eddf086dc87 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21063) Indicate in icon (or tooltip) if a release build failed
SCM/JIRA link daemon commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Code changed in jenkins User: imod Path: pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction/badge.jelly src/main/webapp/img/new-package.png src/main/webapp/img/releasebadge-dryrun.png src/main/webapp/img/releasebadge-failure.png src/main/webapp/img/releasebadge.png src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeActionTest.java src/test/resources/org/jvnet/hudson/plugins/m2release/maven3-failing-project.zip http://jenkins-ci.org/commit/m2release-plugin/aaba60e7307eea50ebc377403562364896f3d968 Log: Merge branch 'JENKINS-21063' of https://github.com/andham/m2release-plugin into andham-JENKINS-21063 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-20983) Improve help text for Preselect append Jenkins username option
SCM/JIRA link daemon commented on JENKINS-20983 Improve help text for Preselect append Jenkins username option Code changed in jenkins User: Anders Hammar Path: pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly src/main/webapp/help-projectConfig-numberOfReleaseBuildsToKeep.html src/main/webapp/help-projectConfig-selectAppendHudsonUsername.html http://jenkins-ci.org/commit/m2release-plugin/35d201a67b2e32850b68b75621aeb488cfe4c9df Log: Merge remote-tracking branch 'upstream/master' into JENKINS-21063 upstream/master: ReleasesCauses are now userIdCause - so update RSS appropriatly. maven-release-plugin prepare for next development iteration maven-release-plugin prepare release m2release-0.13.0 Fixed a few UI text items in the project configuration dialog to align with text items in release dialog. FIXED JENKINS-20983 Improve help text for "Preselect append Jenkins username" option FIXED JENKINS-21060 Improve help text of "Number of successful release builds to keep" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21063) Indicate in icon (or tooltip) if a release build failed
SCM/JIRA link daemon commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Code changed in jenkins User: Anders Hammar Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction.java src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction/badge.jelly src/main/webapp/img/new-package.png src/main/webapp/img/releasebadge-dryrun.png src/main/webapp/img/releasebadge-failure.png src/main/webapp/img/releasebadge.png http://jenkins-ci.org/commit/m2release-plugin/8a166ef54883fdaf1e244cbd046d2e0908ee1adf Log: JENKINS-21063 Indicate in icon (or tooltip) if a release build failed. Failed release build is now indicated in badge/icon as well as tooltip. Also reworked dryrun badge to align. 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] [m2release] (JENKINS-20753) Remove unused Append Hudson Build Number option
SCM/JIRA link daemon commented on JENKINS-20753 Remove unused Append Hudson Build Number option Code changed in jenkins User: Anders Hammar Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseAction/index.jelly http://jenkins-ci.org/commit/m2release-plugin/bb0f1f20eb911d321f2281ea9a4f597b0a0702c1 Log: FIXED JENKINS-20753 Remove unused "Append Hudson Build Number" option 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] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
SCM/JIRA link daemon commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Code changed in jenkins User: Anders Hammar Path: pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly src/main/webapp/help-projectConfig-numberOfReleaseBuildsToKeep.html src/main/webapp/help-projectConfig-selectAppendHudsonUsername.html http://jenkins-ci.org/commit/m2release-plugin/35d201a67b2e32850b68b75621aeb488cfe4c9df Log: Merge remote-tracking branch 'upstream/master' into JENKINS-21063 upstream/master: ReleasesCauses are now userIdCause - so update RSS appropriatly. maven-release-plugin prepare for next development iteration maven-release-plugin prepare release m2release-0.13.0 Fixed a few UI text items in the project configuration dialog to align with text items in release dialog. FIXED JENKINS-20983 Improve help text for "Preselect append Jenkins username" option FIXED JENKINS-21060 Improve help text of "Number of successful release builds to keep" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21060) Improve help text of Number of successful release builds to keep
SCM/JIRA link daemon commented on JENKINS-21060 Improve help text of Number of successful release builds to keep Code changed in jenkins User: Anders Hammar Path: pom.xml src/main/java/org/jvnet/hudson/plugins/m2release/dashboard/RecentReleasesPortlet.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBuildWrapper/config.jelly src/main/webapp/help-projectConfig-numberOfReleaseBuildsToKeep.html src/main/webapp/help-projectConfig-selectAppendHudsonUsername.html http://jenkins-ci.org/commit/m2release-plugin/35d201a67b2e32850b68b75621aeb488cfe4c9df Log: Merge remote-tracking branch 'upstream/master' into JENKINS-21063 upstream/master: ReleasesCauses are now userIdCause - so update RSS appropriatly. maven-release-plugin prepare for next development iteration maven-release-plugin prepare release m2release-0.13.0 Fixed a few UI text items in the project configuration dialog to align with text items in release dialog. FIXED JENKINS-20983 Improve help text for "Preselect append Jenkins username" option FIXED JENKINS-21060 Improve help text of "Number of successful release builds to keep" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21063) Indicate in icon (or tooltip) if a release build failed
SCM/JIRA link daemon commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Code changed in jenkins User: Anders Hammar Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction.java src/main/resources/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeAction/badge.jelly src/main/webapp/img/releasebadge-failure.png src/test/java/org/jvnet/hudson/plugins/m2release/M2ReleaseBadgeActionTest.java http://jenkins-ci.org/commit/m2release-plugin/1f8dc39b7b325c2be9b33a2640826ed0bb2a65e8 Log: JENKINS-21063 Changed failed badge to indicate uncertainty wrt release and fixed backwards campatibility for builds by old versions of plugin. 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
SCM/JIRA link daemon commented on JENKINS-22303 Should have option to not care about build failure status Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly http://jenkins-ci.org/commit/sloccount-plugin/105324d6263140d03989d02995c588e988cd5365 Log: Merge pull request #40 from mixalturek/master JENKINS-22303 Should have option to not care about build failure statu... Compare: https://github.com/jenkinsci/sloccount-plugin/compare/2d9956629d6b...105324d62631 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [sloccount] (JENKINS-22303) Should have option to not care about build failure status
SCM/JIRA link daemon commented on JENKINS-22303 Should have option to not care about build failure status Code changed in jenkins User: Michal Turek Path: src/main/resources/hudson/plugins/sloccount/SloccountPublisher/config.jelly http://jenkins-ci.org/commit/sloccount-plugin/2c8d46aec8f9f32b2358611d454ac2184f1933fb Log: JENKINS-22303 Should have option to not care about build failure status Regression found by injected unit test fixed. label for="" shouldn't be used because it doesn't work when the configuration item is repeated. Use label class="attach-previous" to have your label attach to the previous DOM node instead. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities How can I get more detailed log info? The jenkins logging page is a little touch for me to parse given the fact that they don't give me target systems to log. (hudson.? org.jenkinsci.plugins?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Sorry needed a weekend (p.s. Soren, thanks so much for your help in the first place) I just upgraded to 1.556 and your binary of the github oauth plugin. When I $ curl --user [masked username]:[masked api key] --data "" [jenkins api endpoint] I get (with a lot of html formatting removed) Error 401 Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@94008f0a: Username:[masked username]; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: 127.0.0.1; SessionId: null; Not granted any authorities How can I get more detailed log info? The jenkins logging page is a little tough for me to parse given the fact that they don't give me target systems to log. (hudson.? org.jenkinsci.plugins?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access
Soren Hansen commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I was really hoping for relevant parts of the server side log file (for me it's located in /var/log/jenkins/jenkins.log). Any chance you can dig that up for me? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22421) File descriptor leak - changelog.xml
recampbell created JENKINS-22421 File descriptor leak - changelog.xml Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/14 9:12 PM Description: Jenkins is occasionally failing to load the index page and complains about "Too many open files". Looking at the open files, I see around 7000 such as this one: //jenkins/jenkins_home/jobs//jobs/messages/builds/2012-08-16_03-38-51/changelog.xml This is a rather large public Jenkins instance which is no doubt crawled by search engines. Environment: 1.532.2 Project: Jenkins Priority: Major 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 Google Groups Jenkins Issues group. To unsubscribe from this 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-19822) A first time git clone on a slave produce an error
Guy Rozendorn commented on JENKINS-19822 A first time git clone on a slave produce an error still happens in our environment, running: Jenkins 1.553 Git plugin 2.0.4 Git Client plug-in 1.6.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] [git] (JENKINS-19822) A first time git clone on a slave produce an error
Guy Rozendorn commented on JENKINS-19822 A first time git clone on a slave produce an error scratch that, traceback comes from a different place This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Still symptom, different traceback: java.io.IOException: remote file operation failed: C:\Jenkins\workspace\integration-tests at hudson.remoting.Channel@3e89cfcb:host-ci73 at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:565) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:557) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: Remote call on host-ci73 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:903) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.gitclient.GitClient at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(CliGitAPIImpl.java:110) at hudson.plugins.git.GitAPI.init(GitAPI.java:43) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Retrying after 10 seconds java.io.IOException: remote file operation failed: C:\Jenkins\workspace\integration-tests at hudson.remoting.Channel@3e89cfcb:host-ci73 at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:565) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:557) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: Remote call on host-ci73 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:903) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.gitclient.GitClient at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(CliGitAPIImpl.java:110) at hudson.plugins.git.GitAPI.init(GitAPI.java:43) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at
[JIRA] [startup-trigger-plugin] (JENKINS-22422) Make the name of the node that trigger the startup job available
Andrew Sumner
created JENKINS-22422
Make the name of the node that trigger the startup job available
Issue Type:
Improvement
Affects Versions:
current
Assignee:
ashlux
Components:
startup-trigger-plugin
Created:
30/Mar/14 10:44 PM
Description:
I’m working on a slave reboot task that would take a node offline, wait for any running jobs to complete and then restart the computer. Once restarted and reconnected I need to bring the node back online which is where I’d like to have a job that is triggered by a node startup (using this plugin) and will run a groovy script via the "Execute Groovy Script" build step:
jenkins = Hudson.instance
def node = jenkins.nodes.getNode("node name").getComputer()
if (node.isTemporarilyOffline())
{
node.setTemporarilyOffline(false, node.getOfflineCause())
}
The two issues I have are:
1. The plugin does not appear to provide the name of the node that triggered the job – a solution would be for the plugin to provide an environment variable that I could read within the groovy script.
2. The "Restricted node Label" to does not support wild cards – it would be nice if there was some way I could say “run this for all nodes”, possibly by putting a * in the node label field although a work around for this would be to give all nodes a label of ONLINE which would give the desired result as long as it doesn’t break the existing label the slaves have
The first issue is definitely the most desired, the second nice to have.
Project:
Jenkins
Priority:
Major
Reporter:
Andrew Sumner
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-21933) PermGen leaks
Zachary Young commented on JENKINS-21933 PermGen leaks Does RTC stand for "Rational Team Concert"? Using just the default/core SCM plugin, but just got this error: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8090-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.550.jar!/lib/layout/layout.jelly:75:72: st:include java.lang.OutOfMemoryError: PermGen space at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) Is this like the error you got? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-9952) Subversion revision not passed along to all downstream jobs
ikedam resolved JENKINS-9952 as Not A Defect Subversion revision not passed along to all downstream jobs Change By: ikedam (30/Mar/14 11:04 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] [parameterized-trigger] (JENKINS-12686) Predefined parameters on a post-join build are evaluated by a child job rather than parent
ikedam resolved JENKINS-12686 as Cannot Reproduce Predefined parameters on a post-join build are evaluated by a child job rather than parent Cannot test the bahavior without a detailed report even it does not always reproduce. Please reopen the ticket if you can report details to reproduce. Change By: ikedam (30/Mar/14 11:16 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22282) Extensible choice parameter greyed out in Internet Explorer
ikedam commented on JENKINS-22282 Extensible choice parameter greyed out in Internet Explorer It never reproduces in my environment without setting the document mode. It may be for Windows 8. Can you let me know the behavior for each document mode in your environment? It can be set in Tools F12 Developer Tools Emulation (the most down icon) in IE11 (IE10 should also provide an alike tool). In my environment: Document mode gray out Edge (Default) not reproduce 10 not reproduce 9 not reproduce 8 not reproduce 7 reproduce 5 reproduce And it may be caused by combination with another plugin. Can you test the behavior with a new instance of Jenkins? You can launch Jenkins locally without install it to the system. Download jenkins.war (from the "Latest and greatest" link in http://jenkins-ci.org/) Launch command line, and type following command: java -jar jenkins.war Now you can access new Jenkins in http://localhost:8080/ If you want to shutdown Jenkins, press Ctrl+C on the command line window. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
ikedam commented on JENKINS-12732 Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs It looks not related with fingerprinting, but just a problem of file permissions. When it reproduces, please check and report the permission of the file to be overwritten. It is easy to attach output of ls -laR. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-13463) Upgraded to 1.21 and now cannot copy from Matrix Builds
ikedam resolved JENKINS-13463 as Cannot Reproduce Upgraded to 1.21 and now cannot copy from Matrix Builds It may be a permission problem as the output says. Please see https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact for details. Change By: ikedam (31/Mar/14 12:53 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-20112) Can't access artifacts of upstream matrix jobs
ikedam resolved JENKINS-20112 as Fixed Cant access artifacts of upstream matrix jobs See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact for details. Change By: ikedam (31/Mar/14 12:57 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] [copyartifact] (JENKINS-19132) Copy Artifact Plugin with parameterized project name incompatible with Github Authorization Settings
ikedam resolved JENKINS-19132 as Fixed Copy Artifact Plugin with parameterized project name incompatible with Github Authorization Settings See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact for details. Change By: ikedam (31/Mar/14 12:57 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] [copyartifact] (JENKINS-16185) CopyArtifact plugin can't copy from not anonymous redeable jobs
ikedam resolved JENKINS-16185 as Fixed CopyArtifact plugin cant copy from not anonymous redeable jobs See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact for details. Change By: ikedam (31/Mar/14 1:03 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] [copyartifact] (JENKINS-14654) fails to copy artifact from matrix to matrix with label as parameter
ikedam resolved JENKINS-14654 as Fixed fails to copy artifact from matrix to matrix with label as parameter See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact for details. Change By: ikedam (31/Mar/14 1:05 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] [msbuild] (JENKINS-15427) Incompatibility of MSBuild and Copy Artifact Plugins
ikedam updated JENKINS-15427 Incompatibility of MSBuild and Copy Artifact Plugins This looks parameter-escaping issue of msbuild-plugin. Change By: ikedam (31/Mar/14 1:09 AM) Assignee: kdsweeney Component/s: copyartifact This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
Patrice Matignon commented on JENKINS-22211 Parallel stages display distorted This is still not working for me, with version 0.7.2. I have multiple pipelines representing multiple maintenance branches of the same codebase, and each pipeline has the same stage names and step names. They are all using different projects though (all projects are duplicated for each branch/pipeline). What happens is that the top pipeline has the proper arrows in the view, and the bottom one has all the arrows from the first stage going all the way up to the second stage of the top pipeline (the remaining stages on the bottom pipeline just aren't part of the graph). All pipelines in between the top and bottom ones have no arrow/lines. If I add a completely different pipeline at the bottom, then it won't have any lines/arrows at all, but it won't point t the top pipeline, so I think it's related to the fact that I'm using the same stage/step names. This is a regression, it was working fine before version 0.7.1 (which had only the top pipeline displayed) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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
Patrice Matignon commented on JENKINS-22211 Parallel stages display distorted Then again, I have no parallel stages, so this is not the proper JIRA, my apologies This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22423) Pipelines are mixed up when same stage/step names are used
Patrice Matignon created JENKINS-22423 Pipelines are mixed up when same stage/step names are used Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: delivery-pipeline Created: 31/Mar/14 2:22 AM Description: I have multiple pipelines representing multiple maintenance branches of the same codebase, and each pipeline has the same stage names and step names. They are all using different projects though (all projects are duplicated for each branch/pipeline). What happens is that the top pipeline has the proper arrows in the view, and the bottom one has all the arrows from the first stage going all the way up to the second stage of the top pipeline (the remaining stages on the bottom pipeline just have no arrow/lines). All pipelines in between the top and bottom ones have no arrow/lines. If I add a completely different pipeline at the bottom, then it won't have any lines/arrows at all, but it won't point to the top pipeline, so I think it's related to the fact that I'm using the same stage/step names. This is a regression, it was working fine before version 0.7.1 (which had only the top pipeline displayed) Environment: Linux SLES 11.2 Jenkins 1.543 Project: Jenkins Priority: Major Reporter: Patrice Matignon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [all-changes] (JENKINS-21808) Error on Save Projet Modification
Bai Zhiping commented on JENKINS-21808 Error on Save Projet Modification Hello, I am facing the same problem for all the jobs on the CI. Even I reset a new instance, I am still have this problem. Exception: net.sf.json.JSONException: Unquotted string 'Test' Stacktrace: javax.servlet.ServletException: net.sf.json.JSONException: Unquotted string 'Win8_64_DI_5.1' at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at
[JIRA] [all-changes] (JENKINS-21808) Error on Save Projet Modification
Bai Zhiping edited a comment on JENKINS-21808 Error on Save Projet Modification Hello, I am facing the same problem for all the jobs on the CI. Even I reset a new instance, I am still have this problem. Exception: net.sf.json.JSONException: Unquotted string 'Test' Stacktrace: javax.servlet.ServletException: net.sf.json.JSONException: Unquotted string 'Test' at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at
[JIRA] [all-changes] (JENKINS-21808) Error on Save Projet Modification
Bai Zhiping edited a comment on JENKINS-21808 Error on Save Projet Modification Hello, I am facing the same problem for all the jobs on the CI. Even I reset a new instance, I am still have this problem. Exception: net.sf.json.JSONException: Unquotted string 'Test' Stacktrace: javax.servlet.ServletException: net.sf.json.JSONException: Unquotted string 'Test' at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:63) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at
[JIRA] [versionnumber] (JENKINS-22424) versionnumber/displayName not working
Jose Medaglia created JENKINS-22424 versionnumber/displayName not working Issue Type: Bug Assignee: Unassigned Components: versionnumber Created: 31/Mar/14 3:15 AM Description: I need to retrieve the generated version number of latest build: .../lastSuccessfulBuild/versionnumber/displayName, however versionnumber/displayName is not working, it redirects to build status page. I would expect it to behave similarly to .../lastSuccessfulBuild/buildNumber Project: Jenkins Priority: Major Reporter: Jose Medaglia This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22423) Pipelines are mixed up when same stage/step names are used
Patrice Matignon updated JENKINS-22423 Pipelines are mixed up when same stage/step names are used Change By: Patrice Matignon (31/Mar/14 4:47 AM) Attachment: Pipelines-for-Multiple-Branches.png.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
