[JIRA] [configurationslicing-plugin] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Ninian resolved JENKINS-21556 as Fixed Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build Stack trace indicates this is happening when updating a matrix item directly. Should be fixed in v1.40 of the configurationslicing-plugin. Change By: Ninian (16/Nov/14 9:07 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] [configurationslicing-plugin] (JENKINS-20082) UnsupportedoperationException trying to slice logrotationbuilds
Ninian resolved JENKINS-20082 as Fixed UnsupportedoperationException trying to slice logrotationbuilds Stack trace indicates this is happening when updating a matrix item directly. Should be fixed in v1.40 of the configurationslicing-plugin. Change By: Ninian (16/Nov/14 9:06 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] [configurationslicing-plugin] (JENKINS-23776) Matrix axes are sometimes treated as jobs
Ninian resolved JENKINS-23776 as Fixed Matrix axes are sometimes treated as jobs Should be fixed in v1.40 of the configurationslicing-plugin. Change By: Ninian (16/Nov/14 9:10 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Ulli Hafner commented on JENKINS-25511 Checkstyle double-escapes content I understand. You are not referring to the UI, you are referring to the persisted values and the API. Seems that Jenkins serialization process also escapes the values. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Alexander Obuhovich commented on JENKINS-25511 Checkstyle double-escapes content As you can see Jenkins already does double escaping when job publishes it's Checkstyle.xml report (the message node in jenkins_checkstyle.xml). If that will be fixed, then I guess all should be ok. However if API xml request doesn't escape content considering that published checkstyle xml file already was escaped then this might be problematic. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-with-parameters-plugin] (JENKINS-24008) Jobs stuck while waiting for an executor (and executors are available)
Andrew P commented on JENKINS-24008 Jobs stuck while waiting for an executor (and executors are available) PS: Removing the "This build is parameterized" tick will remove the unwanted behavior This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-token-root-plugin] (JENKINS-25637) Add CrumbExclusion for buildByToken URL
kflorian created JENKINS-25637 Add CrumbExclusion for buildByToken URL Issue Type: Bug Assignee: Jesse Glick Components: build-token-root-plugin Created: 16/Nov/14 12:18 PM Description: Just like similar plugins, (e.g. GitHub and GitLab), the Build Token Root Plugin does not play nice whith CSRF protection enabled. The root cause seems to be JENKINS-22474 (documented by Jesse Glick), but until that is fixed, the Build Token Root Plugin should probably add a CrumbExclusion for the URL it is listening on. See JENKINS-20140 for a similar issue in the GitHub Plugin, that has been resolved. Project: Jenkins Labels: plugin csrf Priority: Minor Reporter: kflorian This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Shane Gannon commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source I was able to resolve this by downgrading from JDK 8 to JDK 7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [email-ext-plugin] (JENKINS-18693) Add support for periodic spamming rather than all or nothing
Alex Earl commented on JENKINS-18693 Add support for periodic spamming rather than all or nothing I think you could probably achieve this with the script trigger now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Daniel Beck updated JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Workaround present, so reducing priority. Change By: Daniel Beck (16/Nov/14 2:26 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [email-ext-plugin] (JENKINS-21672) Need Pre-send Script to support classpath options
Alex Earl resolved JENKINS-21672 as Fixed Need Pre-send Script to support classpath options Code merged for 2.39 Change By: Alex Earl (16/Nov/14 2:38 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template-plugin] (JENKINS-23866) Templates are not saved to disk after an edit
Alex Earl resolved JENKINS-23866 as Fixed Templates are not saved to disk after an edit This is a simple fix, sorry it took so long, just needed to add a call to save() after the template is updated in memory. Should be fixed in 0.3 Change By: Alex Earl (16/Nov/14 5:37 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] [emailext-template-plugin] (JENKINS-23866) Templates are not saved to disk after an edit
SCM/JIRA link daemon commented on JENKINS-23866 Templates are not saved to disk after an edit Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/org/jenkinsci/plugins/emailext_template/ExtEmailTemplateManagement.java src/main/resources/org/jenkinsci/plugins/emailext_template/ExtendedEmailTemplatePublisher/config.groovy src/test/java/org/jeninsci/plugins/emailext_plugin/ExtendedEmailTemplatePublisherTest.java http://jenkins-ci.org/commit/emailext-template-plugin/f913d9213d24830625f3eeb63bd768d230dbb4e8 Log: Fix JENKINS-23866 Added call to descriptor.save() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [emailext-template-plugin] (JENKINS-22933) Incorect template name being displayed
SCM/JIRA link daemon commented on JENKINS-22933 Incorect template name being displayed Code changed in jenkins User: Alex Earl Path: src/main/resources/org/jenkinsci/plugins/emailext_template/ExtendedEmailTemplatePublisher/config.groovy http://jenkins-ci.org/commit/emailext-template-plugin/292b9a01e1244e98d8578641d96c5a6a3e04 Log: Fix JENKINS-22933 Fixed logic that loads the templates for saved jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emailext-template-plugin] (JENKINS-22933) Incorect template name being displayed
Alex Earl resolved JENKINS-22933 as Fixed Incorect template name being displayed Fixed in 0.3 Change By: Alex Earl (16/Nov/14 6:00 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] [cli] (JENKINS-25606) PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source
Shane Gannon commented on JENKINS-25606 PrivateKeyProviderTest (in Jenkins.CLI) fails when doing Maven build of Jenkins source Probably should mention that I'm getting a new build error but now in Jenkins Core instead CLI. Failed tests: SecretRewriterTest.recursionDetection:100 assert 6==sw.rewriteRecursive(t, st) 5 hudson.util.StreamTaskListener@3fa56a3e C:\Development\jenkins\core\target\junit4899974716784858398\t hudson.util.SecretRewriter@4e22d17 false Tests in error: RunTest.testParseTimestampFromBuildDir:109 ╗ InvalidDirectoryName Invalid dire... DefaultConfidentialStoreTest.roundtrip:52 ╗ IO javax.crypto.BadPaddingExceptio... But progress is progress - I guess This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage-plugin] (JENKINS-22721) Project page has broken layout on smaller screens
Michal Turek commented on JENKINS-22721 Project page has broken layout on smaller screens Hi, it's here https://github.com/jenkinsci/disk-usage-plugin/pull/20. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-24296) Drop dependency to jQuery-UI
Patrik Boström closed JENKINS-24296 as Fixed Drop dependency to jQuery-UI Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:09 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25279) Loading animation has old size
Patrik Boström closed JENKINS-25279 as Fixed Loading animation has old size Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:10 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-24644) NPE when View is configured with a non existing firstJob
Patrik Boström closed JENKINS-24644 as Fixed NPE when View is configured with a non existing firstJob Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:09 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed
Patrik Boström closed JENKINS-25607 as Fixed Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed Change By: Patrik Boström (16/Nov/14 9:11 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25361) Manual triggered reexecuting jobs which has failed dont show up as status queued
Patrik Boström resolved JENKINS-25361 as Fixed Manual triggered reexecuting jobs which has failed dont show up as status queued Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:10 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] [delivery-pipeline-plugin] (JENKINS-25256) MalformedUrlException fills up logs
Patrik Boström closed JENKINS-25256 as Fixed MalformedUrlException fills up logs Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:09 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25361) Manual triggered reexecuting jobs which has failed dont show up as status queued
Patrik Boström closed JENKINS-25361 as Fixed Manual triggered reexecuting jobs which has failed dont show up as status queued Change By: Patrik Boström (16/Nov/14 9:10 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25607) Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed
Patrik Boström resolved JENKINS-25607 as Fixed Unable to trigger manual jobs when build-pipeline-plugin 1.4.4 is installed Released in 0.8.7 Change By: Patrik Boström (16/Nov/14 9:10 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
SCM/JIRA link daemon commented on JENKINS-25511 Checkstyle double-escapes content Code changed in jenkins User: Ulli Hafner Path: .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_core_1_66.xml analysis-collector checkstyle compile.sh warnings http://jenkins-ci.org/commit/analysis-suite-plugin/479368313b7a76b448f13dcf4cc9dce8fcd51a9d Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/analysis-suite-plugin/compare/db92e5d8fbfa...479368313b7a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-17309) XML escaping (or lack thereof)
SCM/JIRA link daemon commented on JENKINS-17309 XML escaping (or lack thereof) Code changed in jenkins User: Ulli Hafner Path: .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_core_1_66.xml analysis-collector checkstyle compile.sh warnings http://jenkins-ci.org/commit/analysis-suite-plugin/479368313b7a76b448f13dcf4cc9dce8fcd51a9d Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/analysis-suite-plugin/compare/db92e5d8fbfa...479368313b7a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
SCM/JIRA link daemon commented on JENKINS-25511 Checkstyle double-escapes content Code changed in jenkins User: Ulli Hafner Path: checkstyle.iml pom.xml src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java http://jenkins-ci.org/commit/checkstyle-plugin/067654f75120c548ba24ddf20b574e00e1c5056b Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-17309) XML escaping (or lack thereof)
SCM/JIRA link daemon commented on JENKINS-17309 XML escaping (or lack thereof) Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/warnings/parser/AbstractWarningsParser.java src/main/java/hudson/plugins/warnings/parser/GccParser.java src/test/java/hudson/plugins/warnings/parser/GccParserTest.java src/test/java/hudson/plugins/warnings/parser/ParserTester.java src/test/resources/hudson/plugins/warnings/parser/issue17309.txt warnings.iml http://jenkins-ci.org/commit/warnings-plugin/7af227eb669868a09d1fe09e19c8a025118983dc Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/warnings-plugin/compare/a811a92cfee0...7af227eb6698 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-17309) XML escaping (or lack thereof)
SCM/JIRA link daemon commented on JENKINS-17309 XML escaping (or lack thereof) Code changed in jenkins User: Ulli Hafner Path: checkstyle.iml pom.xml src/test/java/hudson/plugins/checkstyle/parser/CheckStyleParserTest.java http://jenkins-ci.org/commit/checkstyle-plugin/067654f75120c548ba24ddf20b574e00e1c5056b Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
SCM/JIRA link daemon commented on JENKINS-25511 Checkstyle double-escapes content Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/warnings/parser/AbstractWarningsParser.java src/main/java/hudson/plugins/warnings/parser/GccParser.java src/test/java/hudson/plugins/warnings/parser/GccParserTest.java src/test/java/hudson/plugins/warnings/parser/ParserTester.java src/test/resources/hudson/plugins/warnings/parser/issue17309.txt warnings.iml http://jenkins-ci.org/commit/warnings-plugin/7af227eb669868a09d1fe09e19c8a025118983dc Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/warnings-plugin/compare/a811a92cfee0...7af227eb6698 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-17309) XML escaping (or lack thereof)
SCM/JIRA link daemon commented on JENKINS-17309 XML escaping (or lack thereof) Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/util/AbstractPackageDetector.java src/main/java/hudson/plugins/analysis/util/EncodingValidator.java src/main/java/hudson/plugins/analysis/util/JavaPackageDetector.java src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java src/test/java/hudson/plugins/analysis/util/model/AbstractAnnotationTest.java http://jenkins-ci.org/commit/analysis-core-plugin/e001040655c1b7018019a3179ed346b9f855c438 Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/4b695e192cc2...e001040655c1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
SCM/JIRA link daemon commented on JENKINS-25511 Checkstyle double-escapes content Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/util/AbstractPackageDetector.java src/main/java/hudson/plugins/analysis/util/EncodingValidator.java src/main/java/hudson/plugins/analysis/util/JavaPackageDetector.java src/main/java/hudson/plugins/analysis/util/model/AbstractAnnotation.java src/test/java/hudson/plugins/analysis/util/model/AbstractAnnotationTest.java http://jenkins-ci.org/commit/analysis-core-plugin/e001040655c1b7018019a3179ed346b9f855c438 Log: FIXED JENKINS-25511 JENKINS-17309 Reverted XML escaping of message. Revert of fix for JENKINS-17309. Previous solution was too aggressive, it makes sense to escape only messages from parsers that parse non-XML files. XML parsers should not escape entities at all. AbstractAnnotation never escapes entities now, only GCC parser escapes and invokes constructor with escaped message. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/4b695e192cc2...e001040655c1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [checkstyle-plugin] (JENKINS-25511) Checkstyle double-escapes content
Ulli Hafner resolved JENKINS-25511 as Fixed Checkstyle double-escapes content Change By: Ulli Hafner (16/Nov/14 9:51 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] [analysis-core-plugin] (JENKINS-25560) Multi-line messages shall be displayed with line breaks
Ulli Hafner resolved JENKINS-25560 as Fixed Multi-line messages shall be displayed with line breaks With fix for JENKINS-25551 you should now be able to insert XML line breaks into your message. Change By: Ulli Hafner (16/Nov/14 9:50 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] [analysis-core-plugin] (JENKINS-25560) Multi-line messages shall be displayed with line breaks
Ulli Hafner edited a comment on JENKINS-25560 Multi-line messages shall be displayed with line breaks With fix for JENKINS-25511 you should now be able to insert XML line breaks into your message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-22043) Hyperlinks on the Details - pane do not work any more
Ulli Hafner resolved JENKINS-22043 as Fixed Hyperlinks on the Details - pane do not work any more Should be fixed with JENKINS-25511. Change By: Ulli Hafner (16/Nov/14 9:52 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] [lockable-resources-plugin] (JENKINS-25569) Lockable resource multi-configuration job stuck at default is still in the queue: Waiting for resources [my_resource]
Jonathan Strickland updated JENKINS-25569 Lockable resource multi-configuration job stuck at default is still in the queue: Waiting for resources [my_resource] Change By: Jonathan Strickland (17/Nov/14 1:21 AM) Summary: Lockableresource multi-configuration jobstuckatdefaultisstillinthequeue:Waitingforresources[my_resource] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [lockable-resources-plugin] (JENKINS-25569) Lockable resource multi-configuration job stuck at default is still in the queue: Waiting for resources [my_resource]
Jonathan Strickland commented on JENKINS-25569 Lockable resource multi-configuration job stuck at default is still in the queue: Waiting for resources [my_resource] Seems to be only related to multi-configuration jobs. Captured some debugs: First task called is hudson.matrix.MatrixProject, then multiple hudson.matrix.MatrixConfiguration task. All initiate QueueTaskDispatcher, causing some eventual problems as seen with exhaustion of resources. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Mark Waite commented on JENKINS-24133 GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL Proposed fix has been merged for inclusion in the first versions after git plugin 2.3 and git plugin 2.2.8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Mark Waite resolved JENKINS-24133 as Fixed GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL Change By: Mark Waite (17/Nov/14 2:18 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] [build-pipeline-plugin] (JENKINS-25638) Cannot prevent concurrent build pipelines
Bruce Fraser created JENKINS-25638 Cannot prevent concurrent build pipelines Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 17/Nov/14 3:15 AM Description: There is no way to inhibit a subsequent instance of a build pipeline from starting while another is in progress. I've created a Test job that takes the workspace of the upstream job as a parameter so that it can be equally applied to Gerrit check ins, master updates, and release builds. It's fine to have different pipelines running because they operate in separate workspaces. But when a second instance of a particular pipeline begins before the first has finished, it may remove files that the test relies upon. As a result, I see frequent failures of downstream jobs. As a workaround, I've reduced the number of executors to one, and set the priority of downstream jobs to be higher than upstream jobs, but this is still not a guarantee. And it's definitely not ideal because some upstream jobs take a long time and having more executors allows faster jobs to complete. Environment: Jenkins 1.588 Build-Pipeline-Plugin: 1.4.4 Project: Jenkins Labels: concurrent-build Priority: Major Reporter: Bruce Fraser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Arpit Nagar commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive It is blocker for us, have you find any solution for this ?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-24481) Could not deleting files/folder in workspace
Arpit Nagar reopened JENKINS-24481 Could not deleting files/folder in workspace It has been still not fixed. Change By: Arpit Nagar (17/Nov/14 5:13 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-24481) Could not deleting files/folder in workspace
Arpit Nagar edited a comment on JENKINS-24481 Could not deleting files/folder in workspace It has been still not fixed. Allure tries to delete file but it says, some files are still in use. It is not because of Antivirus, firewall or such. Can we introduce any type of mechanism to unlock the folder before deleting files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
tsondergaard commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive The problem appears to be eliminated or at least significantly reduced by disabling the "Windows Search" indexing service. Also look out for anti-virus programs causing problems. http://www.pcmag.com/slideshow_viewer/0,3253,l=251692a=251692po=4,00.asp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [jacoco-plugin] (JENKINS-23708) Unable to view JaCoCo report and history graph
Muralidhar Gupta commented on JENKINS-23708 Unable to view JaCoCo report and history graph We are also facing this issue. The report got missing after couple of days. Do we have official fix available for this ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [allure-plugin] (JENKINS-24481) Could not deleting files/folder in workspace
Daniel Beck resolved JENKINS-24481 as Duplicate Could not deleting files/folder in workspace Arpit Nagar: Nobody claimed it is. It's resolved as duplicate after review by the plugin maintainer, since there's no point in keeping multiple copies of the same issue around. Change By: Daniel Beck (17/Nov/14 6:50 AM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-25608) Intermittent gerrit trigger NPE on Jenkins restart
rin_ne commented on JENKINS-25608 Intermittent gerrit trigger NPE on Jenkins restart Maybe this was fixed in 2.12.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
