[JIRA] (JENKINS-55549) CppCheck Cannot load sidepanel.jelly
Title: Message Title Simon M commented on JENKINS-55549 Re: CppCheck Cannot load sidepanel.jelly Same issue here CentOS Jenkins 2.150.1 Cppcheck plugin 1.24 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55720) ec2-plugin 1.42 doesn't work well with ec2 spot instances
Title: Message Title Ruslan Bondarau created an issue Jenkins / JENKINS-55720 ec2-plugin 1.42 doesn't work well with ec2 spot instances Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-01-22 07:25 Priority: Minor Reporter: Ruslan Bondarau ec2-plugin 1.42 Creates a lot of spot instances and does not use it 1.41 - works great Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55719) Allow to configure the git blame command to suppress whitespace changes
Title: Message Title Till Steinbach created an issue Jenkins / JENKINS-55719 Allow to configure the git blame command to suppress whitespace changes Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-22 06:58 Priority: Minor Reporter: Till Steinbach Sometimes the git blame command does not find the right person as there were whitespace changes (e.g. due to formatting) or code was moved. In this case it is possible to use "git blame -w -M" to suppress commits that only contain those changes and get better results I suggest to make the used git blame command configurable. There are two possible places: in the global configuration. in the warnings step itself. As the implementation in the global settings is much easier I guess it could be done there. The only reason not to have it there would be to have different settings for different parsers (e.g. if you have one parser in the job that would be sensitive to whitespace changes). Add Comment
[JIRA] (JENKINS-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Raviteja A commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously After increasing the 'Max connections to Kubernetes API' parameter, it didn't resolved the issue. We had to restart master.After that things started working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53022) Cannot disable a job from Blue Ocean UI
Title: Message Title Craig Rodrigues commented on JENKINS-53022 Re: Cannot disable a job from Blue Ocean UI Michael Neale The Classic UI has a button Disable Project See: https://i.ytimg.com/vi/1qDsZLtbYQ8/maxresdefault.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env
Title: Message Title Roy Lu created an issue Jenkins / JENKINS-55718 Support ALM15SSO/Make sure the login process could work in some problematic ALM env Issue Type: Improvement Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-01-22 05:26 Priority: Trivial Reporter: Roy Lu Authentication process enhancement. First we're going to support ALM15SSO. Second, some customer's ALM env always got wrong authentication point. We gonna make sure the Jenkins won't be blocked by this ALM issue. Add Comment
[JIRA] (JENKINS-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env
Title: Message Title Roy Lu assigned an issue to Roy Lu Jenkins / JENKINS-55718 Support ALM15SSO/Make sure the login process could work in some problematic ALM env Change By: Roy Lu Assignee: Daniel Gront Roy Lu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55276) HP ALM Plugin - when job is branched only branch appear in HP ALM
Title: Message Title Roy Lu commented on JENKINS-55276 Re: HP ALM Plugin - when job is branched only branch appear in HP ALM Can you show me how you configure the uploadResultToALM pipeline job? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53022) Cannot disable a job from Blue Ocean UI
Title: Message Title Michael Neale commented on JENKINS-53022 Re: Cannot disable a job from Blue Ocean UI Is it possible to disable a job NOT via blue ocean? ie is this a blue ocean only thing or is it more in the design of pipeline? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55717) Testing registration page
Title: Message Title oleksiy kasyanchuk created an issue Jenkins / JENKINS-55717 Testing registration page Issue Type: Bug Assignee: Technical Support Components: absint-a3-plugin Created: 2019-01-22 04:47 Priority: Minor Reporter: oleksiy kasyanchuk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Brian Speagle edited a comment on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I have the the same issue :( I have a pipeline job that is pulled from a Github repo and the script includes the following: parameters { { string(name: 'S3_BUCKET', description: 'Which bucket should we store files in?') } After I save the pipeline initially I am able to go back into the config and set the default value for my param. I then run the job once and everything runs great but when I access my pipeline again the default value I set in the UI for the param is gone. This happens every time I set the default value for the param in the UI and then run the job. Thanks in advance. *FIXED! - I had some other issues with pipelines not registering webhooks for 'GitHub hook trigger for GITScm polling'. I have one pipeline that does save parameters and works with webhook registering so I compared the pipelines and noticed that I wrote them differently. I then rewrote one of my pipelines to match the structure of the one that does work and now it seems that I am able to save parameters after a build!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job
Title: Message Title
Brian Speagle commented on JENKINS-43758
Re: Parameters disappear from pipeline job after running the job
I have the the same issue I have a pipeline job that is pulled from a Github repo and the script includes the following: parameters { string(name: 'S3_BUCKET', description: 'Which bucket should we store files in?') } After I save the pipeline initially I am able to go back into the config and set the default value for my param. I then run the job once and everything runs great but when I access my pipeline again the default value I set in the UI for the param is gone. This happens every time I set the default value for the param in the UI and then run the job. Thanks in advance.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel commented on JENKINS-55527 Re: Builds fail randomly when running sh in container Awesome thank you Andy Powell for tracking this down. We have disabled it and saw the error count drop significantly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin updated an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Change By:
Chris Baldwin
{{ Using declarative pipeline jenkinsfile I have the following: }} xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']], thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')], tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)] The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page.The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: }}{{ at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8) {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ {{ [[ATTACHMENT|/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/screenshots/test/default-e2e-tests_FAILED_Jan-21-2019-145635-GMT-0800.png]] {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ }} Once xUnit transforms the file the resulting XML file contains the following transformed snippet: }}{{ }} {{ }} {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ }} This results in the following error in the build log file: INFO: Processing Custom Tool INFO: [Custom Tool] - 2 test report file(s) were found with the pattern 'test/e2e/reports/**/*.xml' relative to '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ' for the testing framework 'Custom Tool'. WARNING: The converted file for the input file '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/CHROME_71.0.3578.80_XP_test.xml' doesnt match the JUnit format. WARNING: At line 18 of [file:/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:|file:///var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:] Element 'testcase' cannot have character [children], because the type's content type is element-only. ERROR: cvc-complex-type.2.3: Element 'testcase' cannot have character [children], because the type's content type is element-only. This
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin updated an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Change By:
Chris Baldwin
{{Using declarative pipeline jenkinsfile I have the following:}} xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']], thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')], tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)] The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page.The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: {{ {{ }}{{ at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8)}} }} {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ {{ [[ATTACHMENT|/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/screenshots/test/default-e2e-tests_FAILED_Jan-21-2019-145635-GMT-0800.png]]}} }} {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ }} Once xUnit transforms the file the resulting XML file contains the following transformed snippet:{{ {{ }}{{ }} {{ }} {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{ }} This results in the following error in the build log file: INFO: Processing Custom Tool INFO: [Custom Tool] - 2 test report file(s) were found with the pattern 'test/e2e/reports/**/*.xml' relative to '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ' for the testing framework 'Custom Tool'. WARNING: The converted file for the input file '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/CHROME_71.0.3578.80_XP_test.xml' doesnt match the JUnit format. WARNING: At line 18 of [file:/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:|file:///var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:] Element 'testcase' cannot have character [children], because the type's content type is element-only. ERROR: cvc-complex-type.2.3: Element 'testcase' cannot have character [children], because the type's content type is element-only. This
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin updated an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Change By:
Chris Baldwin
{{Using declarative pipeline jenkinsfile I have the following:}} xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']], thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')], tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)] The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page.The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: {{}}{{ at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8)}}at at process._tickCallback (internal/process/next_tick.js:189:7) {{[[ATTACHMENT|/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/screenshots/test/default-e2e-tests_FAILED_Jan-21-2019-145635-GMT-0800.png]]}} at at process._tickCallback (internal/process/next_tick.js:189:7) Once xUnit transforms the file the resulting XML file contains the following transformed snippet:{{}}{{ { { at at process._tickCallback (internal/process/next_tick.js:189:7) This results in the following error in the build log file: INFO: Processing Custom Tool INFO: [Custom Tool] - 2 test report file(s) were found with the pattern 'test/e2e/reports/**/*.xml' relative to '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ' for the testing framework 'Custom Tool'. WARNING: The converted file for the input file '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/CHROME_71.0.3578.80_XP_test.xml' doesnt match the JUnit format. WARNING: At line 18 of [file:/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:|file:///var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:] Element 'testcase' cannot have character [children], because the type's content type is element-only. ERROR: cvc-complex-type.2.3: Element 'testcase' cannot have character [children], because the type's content type is element-only. This error appears to be caused by the transform not properly removing the second instance of a
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin updated an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Change By:
Chris Baldwin
{{Using declarative pipeline jenkinsfile I have the following:}} xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']], thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')],tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)] The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page.The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: {{}}{{ at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8)}} \{{ at }} \{{ at process._tickCallback (internal/process/next_tick.js:189:7) }} {{[[ATTACHMENT|/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/screenshots/test/default-e2e-tests_FAILED_Jan-21-2019-145635-GMT-0800.png]]}} {{ at }} \{{ at process._tickCallback (internal/process/next_tick.js:189:7) }} \{{ }} Once xUnit transforms the file the resulting XML file contains the following transformed snippet:{{}}{{ }} { { }} \ { { at }} \{{ at process._tickCallback (internal/process/next_tick.js:189:7) }} \{{ }} This results in the following error in the build log file: INFO: Processing Custom Tool INFO: [Custom Tool] - 2 test report file(s) were found with the pattern 'test/e2e/reports/**/*.xml' relative to '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ' for the testing framework 'Custom Tool'. WARNING: The converted file for the input file '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/CHROME_71.0.3578.80_XP_test.xml' doesnt match the JUnit format. WARNING: At line 18 of [file:/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:|file:///var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:] Element 'testcase' cannot have character [children], because the type's content type is element-only. ERROR: cvc-complex-type.2.3: Element 'testcase' cannot have character [children], because the type's content type is element-only. This error
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin updated an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Change By:
Chris Baldwin
{{Using declarative pipeline jenkinsfile I have the following:}} {{ xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']], }} {{ thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')], }} {{ tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)] }} The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page.The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: {{}}{{ < .user-dropdown > to be present for 1 milliseconds. - expected" visible " but got:" not found " " > at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8)}} \ {{ at< anonymous > }} \ {{ at process._tickCallback (internal/process/next_tick.js:189:7)}}{{[[ATTACHMENT|/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/screenshots/test/default-e2e-tests_FAILED_Jan-21-2019-145635-GMT-0800.png]]}}{{ at< anonymous > }} \ {{ at process._tickCallback (internal/process/next_tick.js:189:7)}} \ {{ }} Once xUnit transforms the file the resulting XML file contains the following transformed snippet:{{}}{{ < .user-dropdown > to be present for 1 milliseconds. - expected" visible " but got:" not found " " >}}{{ }} \ {{ at< anonymous > }} \ {{ at process._tickCallback (internal/process/next_tick.js:189:7)}} \ {{ }} This results in the following error in the build log file: INFO: Processing Custom ToolINFO: [Custom Tool] - 2 test report file(s) were found with the pattern 'test/e2e/reports/**/*.xml' relative to '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ' for the testing framework 'Custom Tool'.WARNING: The converted file for the input file '/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/reports/CHROME_71.0.3578.80_XP_test.xml' doesnt match the JUnit format.WARNING: At line 18 of [ file:/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/generatedJUnitFiles/8d717da3-a72e-4782-abb7-2a76fbdcd9b2/Custom%20Tool/TEST-f653ef00-1ca8-402f-a18e-1008b363542e.xml:cvc-complex-type.2.3:
[JIRA] (JENKINS-55716) xUnit Custom XSL not Transforming Files properly
Title: Message Title
Chris Baldwin created an issue
Jenkins / JENKINS-55716
xUnit Custom XSL not Transforming Files properly
Issue Type:
Bug
Assignee:
Nikolas Falco
Components:
xunit-plugin
Created:
2019-01-21 23:50
Environment:
Jenkins ver. 2.150.1 xUnit plugin 2.3.2 Ubuntu 16.04.5 LTS Project Using Nightwatch 1.0.18
Labels:
plugin xunit XML xsl
Priority:
Major
Reporter:
Chris Baldwin
Using declarative pipeline jenkinsfile I have the following: {{ xunit testDataPublishers: [[$class: 'AutomateTestDataPublisher']],}} {{ thresholds: [failed(failureNewThreshold: '0', failureThreshold: '0', unstableNewThreshold: '0', unstableThreshold: '0')],}} {{ tools: [Custom(customXSL: 'test/e2e/custom-to-junit.xsl', deleteOutputFiles: true, failIfNotNew: true, pattern: 'test/e2e/reports/**/*.xml', skipNoTestFiles: false, stopProcessingIfError: true)]}} The custom-to-junit.xsl file contains the recommended XSL from here [^custom-to-junit.xsl] as linked to form the plugin wiki page. The project under test is using Nightwatch for e2e front end testing. The XML report file generated by Night watch contains the following snippet: at Object.defaultE2eTests [as default e2e tests] (/var/lib/jenkins/workspace/infra-sms-ui_browserstack-ZV4ZESG7HBLPJAFOXOTRI7VWSYQOL2FCXEE7I66MFQZVXY4TAFDQ/test/e2e/specs/test.js:19:8) {{ at }} {{ at process._tickCallback (internal/process/next_tick.js:189:7)}}
[JIRA] (JENKINS-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Bruno P. Kinoshita commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Never got the time to actually work on CCM Plugin since my last comment. But am currently in a conference, with some hotel time. Would you have - or be able to produce - a CCM file that I could use, please Alex Gray? I am on Linux, without CCM. But having an XML I can at least force the plugin to read it, even on Linux (if I remember well, I did that in the past while developing it). If it is something simple, it might be doable to release a version by the end of this week (once conference is over). Cheers Bruno Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22526) Health threshold rebaseline command
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-22526 Health threshold rebaseline command Change By: Ulli Hafner jjHealth Health thresholds are based (delta) by comparing against some previous build.When, for an existing job, you add a new checker, or make an existing checker more strict, you typically cause all the health thresholds to be violated.In large, legacy code bases, its never realistic to expect to burn those down by any appreciable amount in any finite time.But, you can however, expect to attempt to contain growth of the newly identified and tracked technical debt.Is it possible to have some sort of UI option, command, whatever to say, "accept this build as the baseline to compare against"The current scenarios to effect this without the option are fairly ugly.Unless I'm missing something, the options as I see them are1. delete the job and recreate it whenever you add or make more strict a checker. This will establish the baseline at build 0 but loose all the trending and historical data2. raise/disable the health threshold gate (e.g from 0 new normal to 10'000 new normal), run a build so you have a new 'stable' base, then drop the limit back down. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Dylan H commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan I am seeing the same issue with Perforce Stream multibranch scanning. Restarting Jenkins seems to resolve it for us, but it is certainly a less than elegant workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55715) TagList parser should present files as file names, not classes.
Title: Message Title Jason Faust created an issue Jenkins / JENKINS-55715 TagList parser should present files as file names, not classes. Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-21 21:59 Priority: Minor Reporter: Jason Faust The TagList Maven Plugin reports class names as the file names. While this is fine for the analysis-model library, the full warnings plugin should make an attempt to translate these to *.java files. Add Comment This
[JIRA] (JENKINS-48802) Possibility to add/change the path that used to display source files
Title: Message Title Jason Faust commented on JENKINS-48802 Re: Possibility to add/change the path that used to display source files As a additional add to this request, can the possible path prefixes to check be a collection? For example, The TagList parser reports hits in source files, without indicating if they in the main directory or the test directory, and letting the file name resolution part look in many spots would be useful to solving this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Carlos Sanchez closed an issue as Not A Defect Thanks for figuring it out Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Change By: Carlos Sanchez Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55714) Git plugin scm polling trigger not working on first build
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55714 Git plugin scm polling trigger not working on first build Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Baptiste Mathus commented on JENKINS-55356 Re: Some workflow jobs fail after restart on Java 11 server > repeat less frequently on a Java 11 environment running on a larger computer Triggered a thought Mark Waite: would you be able to run that test inside a Docker container with memory constraints? I can help with that if that's something you've never played with before. But basically passing like -m 1G will limit the memory available inside the container to 1GB of RAM, which is possibly going to trigger that behavior more immediately, if that is actually related to some memory settings . Cheers! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55714) Git plugin scm polling trigger not working on first build
Title: Message Title Kevin Phillips commented on JENKINS-55714 Re: Git plugin scm polling trigger not working on first build Here is some sample output from some of our Git polling logs that seemed relevant. Each one of our builds that hit this problem have output that looks something like this: [poll] Latest remote head revision on refs/heads/master is: c3da10753cc0860f500df626fdb0721897ec5b05 no polling baseline in /home/path/to/builds/IHNK35RKEDZLNTXWNWBKYMUY4CX6G6J764MFFEOAMVC574ZGNUAA on build-agent-35 Using strategy: Default Each affected build has the same message. The same refspec in each case. The same Git commit hash in each case. So even though build #1 obviously checks out that repo at that revision and built it, build #2 seems to miss that fact and thus it thinks the revision is new. This fact is corroberated by this other snippet from the polling log that appears at the very end of each polling operation: [poll] Latest remote head revision on refs/heads/master is: c3da10753cc0860f500df626fdb0721897ec5b05 Done. Took 15 sec Changes found However, that being said we do have examples where builds that hit this problem have several Git repos each being checked out in the same way, but sometimes certain repos/branches do seem to detect when previous builds have used them. Usually the log output from the polling operation looks something like this: [poll] Latest remote head revision on refs/heads/master is: 3e04a485962dd3b3539ab8b5f214e9b8c52f9108 - already built by 2 Using strategy: Default So I am at a loss why sometimes the Git plugin can successfully resolve when a specific revision has been built before and when it hasn't. Sometimes we get different repos that work fairly consistently while others don't, but we also have cases where specific branches in a repo seem to detect changes properly while other branches don't. It's all very inconsistent. If anyone has any suggestions on how to narrow down the potential causes for this problem further do let me know. Add
[JIRA] (JENKINS-55714) Git plugin scm polling trigger not working on first build
Title: Message Title
Kevin Phillips created an issue
Jenkins / JENKINS-55714
Git plugin scm polling trigger not working on first build
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-01-21 19:48
Environment:
Jenkins v2.148 Git plugin v3.9.1
Priority:
Minor
Reporter:
Kevin Phillips
We have an odd problem with Git SCM polling on some of our jenkins projects. The projects in question only seem to be affected when they are built for the first time. These projects are of type "pipeline" and they always have multiple Git repositories being checked out. The build configurations are somewhat complex, but here are the variables that I think are contributing to the problem. First off, we have multiple stages for these builds, each of which checks out several of the same git repos. Further, to ensure that each stage checks out the same copy / revision of these repos we first check out the head revision from a given refspec on the first stage and then cache the revision / hash from that checkout, and then use that hash when checking out subsequent copies. In pseudo-code, the mechanics look something like this:
def cached_rev = ''
stage ("stage 1") {
node {
checkout (scm: [class: '$GitSCM', branches: 'master'...)
cached_rev = sh(returnStdout: true, script: 'git rev-parse HEAD').trim()
// do some build stuff
}
}
stage ("stage 2") {
node {
checkout (scm: [class: '$GitSCM', branches: cached_rev...])
// do more build stuff
}
}
[JIRA] (JENKINS-42632) CCM Plugin Not Creating Trend Graph
Title: Message Title Alex Gray commented on JENKINS-42632 Re: CCM Plugin Not Creating Trend Graph Is there a workaround for this? Just curious if there is one. Maybe another plugin that can consume CCM metrics and plot them over time? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55698) SSO + CRSF causes 403 errors
Title: Message Title Peter Nordquist commented on JENKINS-55698 Re: SSO + CRSF causes 403 errors In my instance with kerberos-sso 1.2, the incompatibility with SECURITY-901 manifests as a redirect loop. I've been unable to upgrade to 1.4 due to JENKINS-44484 but I'll test it on a separate instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Andy Powell commented on JENKINS-55527 Re: Builds fail randomly when running sh in container yes it was Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55713) No agents created when using google compute engine and missing instance template entry
Title: Message Title
L Powers created an issue
Jenkins / JENKINS-55713
No agents created when using google compute engine and missing instance template entry
Issue Type:
Bug
Assignee:
Evan Brown
Components:
google-compute-engine-plugin
Created:
2019-01-21 18:51
Environment:
Jenkins ver. 2.150.2, google compute engine plugin1.0.8, using Bitnami installer from google marketplace.
Labels:
plugin user-experience
Priority:
Minor
Reporter:
L Powers
Ran into an issue where after updating the Google Compute Engine Plugin 1.0.8 cloud environment module for the latest security updates, not having an Instance Template in google cloud causes jobs to queue up with no agents being built. The logs show
Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@50d1bc17 for excess workload of 1 units of label 'proj1'
Jan 19, 2019 1:01:52 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacityFound capacity for 8 nodes in cloud gce
Jan 19, 2019 1:01:52 AM WARNING com.google.jenkins.plugins.computeengine.ComputeEngineCloud provisionError provisioning node
com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
{
"code" : 400,
"errors" : [ {
"domain" : "global",
"message" : "Invalid value for field 'sourceInstanceTemplate': ''. The URL is malformed.",
"reason" : "invalid"
} ],
[JIRA] (JENKINS-55713) No agents created when using google compute engine and missing instance template entry
Title: Message Title
L Powers created an issue
Jenkins / JENKINS-55713
No agents created when using google compute engine and missing instance template entry
Issue Type:
Bug
Assignee:
Evan Brown
Components:
google-compute-engine-plugin
Created:
2019-01-21 18:51
Environment:
Jenkins ver. 2.150.2, google compute engine plugin1.0.8, using Bitnami installer from google marketplace.
Labels:
plugin user-experience
Priority:
Minor
Reporter:
L Powers
Ran into an issue where after updating the Google Compute Engine Plugin 1.0.8 cloud environment module for the latest security updates, not having an Instance Template in google cloud causes jobs to queue up with no agents being built. The logs show
Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@50d1bc17 for excess workload of 1 units of label 'proj1'
Jan 19, 2019 1:01:52 AM INFO com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacityFound capacity for 8 nodes in cloud gce
Jan 19, 2019 1:01:52 AM WARNING com.google.jenkins.plugins.computeengine.ComputeEngineCloud provisionError provisioning node
com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
{
"code" : 400,
"errors" : [ {
"domain" : "global",
"message" : "Invalid value for field 'sourceInstanceTemplate': ''. The URL is malformed.",
"reason" : "invalid"
} ],
[JIRA] (JENKINS-41983) Tests duration are 0 at class level in test results recorded from trx file
Title: Message Title Renato Chencinski edited a comment on JENKINS-41983 Re: Tests duration are 0 at class level in test results recorded from trx file +1Using Just found out the problem in my scenario. I had a custom xsl file for formatting the result, used by the xUnit plugin (userContent\xUnit\MSTest\mstest- to process -junit . trx files generated by vstest.console.exe xsl), which was causing the problem ( equivalent to mstest probably got there around 2014, when it might have been needed ). Anyone had any luck troubleshooting I just removed the file and class duration started appearing again.Hopefully this issue? info helps someone else. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel commented on JENKINS-55527 Re: Builds fail randomly when running sh in container Go it. We have a very similar setup here. Feel free not to comment but was this 3rd party tool Twistlock by any chance? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41983) Tests duration are 0 at class level in test results recorded from trx file
Title: Message Title Renato Chencinski commented on JENKINS-41983 Re: Tests duration are 0 at class level in test results recorded from trx file +1 Using xUnit plugin to process .trx files generated by vstest.console.exe (equivalent to mstest). Anyone had any luck troubleshooting this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Andy Powell commented on JENKINS-55527 Re: Builds fail randomly when running sh in container Ahmed Kamel it was not GCP, but the 3rd party product that was causing the issue. GKE is running Jenkins after we turned off the 3rd party service. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55712) SocketTimeoutException with kubernetes pipelines
Title: Message Title
Filip Pytloun updated an issue
Jenkins / JENKINS-55712
SocketTimeoutException with kubernetes pipelines
Change By:
Filip Pytloun
We are facing issue with occasional SocketTimeoutException when executing long-running shell commands inside pod containers.We have never seen this happen during short running tasks.*Full traceback:* {{ java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:204) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at okio.Okio$2.read(Okio.java:139) at okio.AsyncTimeout$2.read(AsyncTimeout.java:237) Caused: java.net.SocketTimeoutException: timeout at okio.Okio$4.newTimeoutException(Okio.java:230) at okio.AsyncTimeout.exit(AsyncTimeout.java:285) at okio.AsyncTimeout$2.read(AsyncTimeout.java:241) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345) at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217) at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:212) at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189) at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.BackwardsCompatibilityInterceptor.intercept(BackwardsCompatibilityInterceptor.java:119) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at io.fabric8.kubernetes.client.utils.ImpersonatorInterceptor.intercept(ImpersonatorInterceptor.java:66) at
[JIRA] (JENKINS-55712) SocketTimeoutException with kubernetes pipelines
Title: Message Title Filip Pytloun created an issue Jenkins / JENKINS-55712 SocketTimeoutException with kubernetes pipelines Issue Type: Bug Assignee: Ioannis Canellos Components: kubernetes-pipeline-plugin Created: 2019-01-21 17:42 Priority: Minor Reporter: Filip Pytloun We are facing issue with occasional SocketTimeoutException when executing long-running shell commands inside pod containers. We have never seen this happen during short running tasks. Full traceback: java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:204) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:940) at sun.security.ssl.AppInputStream.read(AppInputStream.java:105) at okio.Okio$2.read(Okio.java:139) at okio.AsyncTimeout$2.read(AsyncTimeout.java:237) Caused: java.net.SocketTimeoutException: timeout at okio.Okio$4.newTimeoutException(Okio.java:230) at okio.AsyncTimeout.exit(AsyncTimeout.java:285) at okio.AsyncTimeout$2.read(AsyncTimeout.java:241) at okio.RealBufferedSource.indexOf(RealBufferedSource.java:345) at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:217) at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:212) at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189) at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147) at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121) at
[JIRA] (JENKINS-51913) Post-build action "Archive the artifacts" prints exception to console when no artifacts found
Title: Message Title Paul Holden commented on JENKINS-51913 Re: Post-build action "Archive the artifacts" prints exception to console when no artifacts found Just a follow up to state that the suggestion by Jesse Glick to: Try a more specific file pattern. Has resolved this for us: we no longer get the exception in job logs when no artifacts are found; and artifacts are successfully archived when they do exist Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55356
Some workflow jobs fail after restart on Java 11 server
Change By:
Mark Waite
While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a {code}jenkins-url/safeRestart{code} will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs.Build log output from the failed builds has included messages like (seems to be more common in windows, but visible in Linux agents as well):{noformat}07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTestResuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’Ready to run at Fri Dec 28 07:48:49 MST 201807:48:49 Timeout set to expire in 17 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // node[Pipeline] }07:48:50 Failed in branch windows-8-2.150.1[Pipeline] // parallel[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: missing workspace C:\J\S\workspace\der_git-client-pipeline_beta-3.0 on coleen-pc2-ssh{noformat}and this (seems to fail on Windows and on Linux):{noformat}08:48:33 [INFO] [ hpi ]-Resuming build at Fri Dec 28 08:51:46 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ??Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Ready to run at Fri Dec 28 08:52:07 MST 201808:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // timeout[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // node[Pipeline] // timeout[Pipeline] }08:52:08 Failed in branch windows-8[Pipeline] }[Pipeline] // node[Pipeline] }08:52:08 Failed in branch windows-8-2.150.108:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-3af9d572[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }08:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-1ba13955[Pipeline] // node[Pipeline] }08:57:14 Failed in branch linux-8[Pipeline] }[Pipeline] //
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55356
Some workflow jobs fail after restart on Java 11 server
Change By:
Mark Waite
While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a {code}jenkins-url/safeRestart{code} will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs.Build log output from the failed builds has included messages like (seems to be more common in windows, but visible in Linux agents as well):{noformat}07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTestResuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’Ready to run at Fri Dec 28 07:48:49 MST 201807:48:49 Timeout set to expire in 17 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // node[Pipeline] }07:48:50 Failed in branch windows-8-2.150.1[Pipeline] // parallel[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: missing workspace C:\J\S\workspace\der_git-client-pipeline_beta-3.0 on coleen-pc2-ssh{noformat}and this (seems to fail on Windows and on Linux):{noformat}08:48:33 [INFO] [ hpi ]-Resuming build at Fri Dec 28 08:51:46 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ??Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Ready to run at Fri Dec 28 08:52:07 MST 201808:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // timeout[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // node[Pipeline] // timeout[Pipeline] }08:52:08 Failed in branch windows-8[Pipeline] }[Pipeline] // node[Pipeline] }08:52:08 Failed in branch windows-8-2.150.108:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-3af9d572[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }08:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-1ba13955[Pipeline] // node[Pipeline] }08:57:14 Failed in branch linux-8[Pipeline] }[Pipeline] //
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55356
Some workflow jobs fail after restart on Java 11 server
Change By:
Mark Waite
While running Java 11 based Jenkins in a docker container using a pre-release of the workflow support plugin which includes the fix for the null pointer exception, a {code}jenkins-url/safeRestart{code} will cause several of the Pipeline jobs that were running to fail when Jenkins tries to resume the jobs.Build log output from the failed builds has included messages like (seems to be more common in windows specific , but visible in Linux agents as well ):{noformat}07:40:50 [INFO] Running org.jenkinsci.plugins.gitclient.PushTestResuming build at Fri Dec 28 07:48:06 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #6: Waiting for next available executor on ‘coleen-pc2-ssh’Ready to run at Fri Dec 28 07:48:49 MST 201807:48:49 Timeout set to expire in 17 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // node[Pipeline] }07:48:50 Failed in branch windows-8-2.150.1[Pipeline] // parallel[Pipeline] }[Pipeline] // timestamps[Pipeline] End of PipelineERROR: missing workspace C:\J\S\workspace\der_git-client-pipeline_beta-3.0 on coleen-pc2-ssh{noformat}and this (seems to fail on Windows and on Linux):{noformat}08:48:33 [INFO] [ hpi ]-Resuming build at Fri Dec 28 08:51:46 MST 2018 after Jenkins restartWaiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ??Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Waiting to resume part of Git Client Plugin Folder » Git Client Branches - Jenkinsfile » beta-3.0 #7: ???Ready to run at Fri Dec 28 08:52:07 MST 201808:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min08:52:07 Timeout set to expire in 54 min[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // stage[Pipeline] // withEnv[Pipeline] }[Pipeline] }[Pipeline] // timeout[Pipeline] // stage[Pipeline] }[Pipeline] }[Pipeline] // node[Pipeline] // timeout[Pipeline] }08:52:08 Failed in branch windows-8[Pipeline] }[Pipeline] // node[Pipeline] }08:52:08 Failed in branch windows-8-2.150.108:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-3af9d572[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }08:57:14 process apparently never started in /home/mwaite/testing-a.markwaite.net-agent/workspace/der_git-client-pipeline_beta-3.0@tmp/durable-1ba13955[Pipeline] // node[Pipeline] }08:57:14 Failed in branch linux-8[Pipeline]
[JIRA] (JENKINS-55500) Warnings per project portlet
Title: Message Title Ulli Hafner commented on JENKINS-55500 Re: Warnings per project portlet You don't need to uninstall the old one. It is called 'Static analysis issues per tool and job'. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Justin Pierce assigned an issue to Gabe Montero Jenkins / JENKINS-55711 java.io.FileNotFoundException with tmp file Change By: Justin Pierce Assignee: Justin Pierce Gabe Montero Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55711) java.io.FileNotFoundException with tmp file
Title: Message Title Valéry FREBOURG created an issue Jenkins / JENKINS-55711 java.io.FileNotFoundException with tmp file Issue Type: Bug Assignee: Justin Pierce Attachments: bug_openshift_client_plugin.txt Components: openshift-client-plugin Created: 2019-01-21 17:11 Environment: Jenkins v2.150.2 Openshift-client-plugin v1.0.23 Agent: linux/windows Master: windows Labels: plugin openshift Priority: Major Reporter: Valéry FREBOURG Hello, i use the openshift-client-plugin in a script pipeline and the bug appears with any call on 'openshift' object, on windows/linux agent. i have on linux agent, this following stackstrace : java.io.FileNotFoundException: \data[agent name]\tmp\ocstdout8170191368802961838.txt (The system cannot find the path specified) on windows Agent: the stacktrace is different : Caused: java.io.IOException: Unable to delete 'C:\Windows\TEMP\ocstderr2250675330396309751.txt'. Tried 3 times (of a maximum of 3) waiting 0,1 sec between attempts. This bug is not reproduce with the precedent version : Openshift-client-plugin v1.0.22 In attachment, i append the full stack strace
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55356 Some workflow jobs fail after restart on Java 11 server Change By: Baptiste Mathus Labels: java11-compatibility scrub triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55710) Sidebar-Link plugin file upload blocked by CSRF protection
Title: Message Title Bradley Herrin created an issue Jenkins / JENKINS-55710 Sidebar-Link plugin file upload blocked by CSRF protection Issue Type: Bug Assignee: Unassigned Components: sidebar-link-plugin Created: 2019-01-21 16:40 Environment: Ubuntu 18 Kubernetes 1.11 Jenkins version 2.150.1 sidebar-link-plugin 1.10 Chrome Version 71.0.3578.98 (Official Build) (64-bit) Labels: plugin csrf Priority: Minor Reporter: Bradley Herrin When on the /configure page when trying to upload a new image to /userContent using the sidebar-link plugin the following error is generated. HTTP ERROR 403 Problem accessing /plugin/sidebar-link/upload. Reason: No valid crumb was included in the request Powered by Jetty:// 9.4.z-SNAPSHOT The result of this error is due to CSRF protection in Jenkins 2.x. The current workaround is for a user to complete the following steps: Visit /configureSecurity page Disable Prevent Cross Site Request Forgery exploits ** temporarily Visit /configure upload the image desired
[JIRA] (JENKINS-41194) Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.
Title: Message Title Dmitriy Korovkin updated an issue Jenkins / JENKINS-41194 Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job. Change By: Dmitriy Korovkin Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Stefan Maurer assigned an issue to Stefan Maurer Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Stefan Maurer Assignee: Stefan Maurer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53735) Parallel sequential stages not showing Triggered Builds while Processing
Title: Message Title Stefan Maurer assigned an issue to Unassigned Jenkins / JENKINS-53735 Parallel sequential stages not showing Triggered Builds while Processing Change By: Stefan Maurer Assignee: Stefan Maurer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55709) Add support for certificate authentication
Title: Message Title Ryan Fox created an issue Jenkins / JENKINS-55709 Add support for certificate authentication Issue Type: New Feature Assignee: Janario Oliveira Components: http-request-plugin Created: 2019-01-21 16:10 Priority: Minor Reporter: Ryan Fox Please add support for certificate authentication. My environment uses 2-way SSL for all requests and I would love for the httpRequest plugin to support a certificate. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-55708) google-login-plugin not working, constant 403 redirects
Title: Message Title Vitaly Gorodetsky created an issue Jenkins / JENKINS-55708 google-login-plugin not working, constant 403 redirects Issue Type: Bug Assignee: Ryan Campbell Components: google-login-plugin Created: 2019-01-21 16:01 Priority: Major Reporter: Vitaly Gorodetsky Starting with version 2.160 google-login-plugin no longer works. There is a constant loop of 403 redirects. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55704) Run jenkinsci/usage-in-plugins on JAXB usages
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55704 Run jenkinsci/usage-in-plugins on JAXB usages Change By: Baptiste Mathus [~danielbeck] suggested using https://github.com/ jenkinsci jenkins-infra /usage-in-plugins to analyze existing plugins from the Update Center.It could provide a complementary interesting perspective on the JAXB usage amongst actual plugins hosted at the Jenkins Update center.h3. Acceptance Criteria* list the main (all?) classes of JAXB* run the modified version (See with Baptiste or Daniel for the existing patch) to get a report of the usages of these classes inside the hosted plugins* Attach the report here, and write up a simple analysis of the content (i.e. is there a lot of usages, easy fix, proposals about what to test more given the outcome, etc.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55703) Add option to support exposing Build workspaces in JFR
Title: Message Title Oleg Nenashev updated JENKINS-55703 Jenkins / JENKINS-55703 Add option to support exposing Build workspaces in JFR Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55703) Add option to support exposing Build workspaces in JFR
Title: Message Title Oleg Nenashev commented on JENKINS-55703 Re: Add option to support exposing Build workspaces in JFR https://github.com/jenkinsci/jenkinsfile-runner/pull/60 https://github.com/jenkinsci/jenkinsfile-runner/pull/59 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-54807 Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run Change By: Ramon Leon In order to run mvn hpi:run with Java 11, we need to get JAXB and JAF modules activated. See [https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/#java-11] for examples.To simplify the development, it would be great if it happens automatically for mvn hpi:run somehowWe can check to make it in pom itself and if it doesn't work, try changing in hpi plugin.h3. Acceptance criteria * The build hpi:run runs fine on Java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54807) Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-54807 Maven HPI Plugin or Plugin POM should automatically set up Java 11 environment for hpi:run Change By: Ramon Leon In order to run mvn hpi:run with Java 11, we need to get JAXB and JAF modules activated. See [https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/#java-11] for examples.To simplify the development, it would be great if it happens automatically for mvn hpi:run somehow We can check to make it in pom itself and if it doesn't work, try changing in hpi plugin.h3. Acceptance criteria* The build runs fine on Java11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46523) FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection
Title: Message Title timur suleimanov commented on JENKINS-46523 Re: FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection I have the same issue with java 11. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55500) Warnings per project portlet
Title: Message Title Robin Jansohn commented on JENKINS-55500 Re: Warnings per project portlet I'm trying to test the new portlet but I cannot find it in the portlet dropdown menu after upgrading to warnings-ng 2.1.0. Under which name should I be able to find the new portlet? Do I need to uninstall the "old" warnings plugin? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41020) CloudBees Docker Build and Publish - Environment Variables
Title: Message Title Carlos Sanchez commented on JENKINS-41020 Re: CloudBees Docker Build and Publish - Environment Variables The workaround (and common usage these days IMHO) is to run docker login, build and push with the sh step Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41020) CloudBees Docker Build and Publish - Environment Variables
Title: Message Title Carlos Sanchez assigned an issue to Unassigned Jenkins / JENKINS-41020 CloudBees Docker Build and Publish - Environment Variables Change By: Carlos Sanchez Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55541) PCT on git plugin with JDK11 fails because of old powermock versions and xstream library dependencies
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55541 PCT on git plugin with JDK11 fails because of old powermock versions and xstream library dependencies Change By: Baptiste Mathus Labels: java11 java11-devtools-compatibility scrub triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55698) SSO + CRSF causes 403 errors
Title: Message Title Koen Dierckx commented on JENKINS-55698 Re: SSO + CRSF causes 403 errors https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+the+SECURITY-901+fix This is the cause, by adding the jenkins.security.seed.UserSeedProperty.disableUserSeed to true, everything works again. Hopefully this helps in updating the plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55707) SpotBug: Unknown bug pattern
Title: Message Title Mykhailo Oleksiuk created an issue Jenkins / JENKINS-55707 SpotBug: Unknown bug pattern Issue Type: Bug Assignee: Ulli Hafner Attachments: Screen Shot 2019-01-21 at 16.44.36.png Components: warnings-ng-plugin Created: 2019-01-21 14:53 Environment: Jenkins ver. 2.138.2 Warning-ng 2.0.0 Priority: Major Reporter: Mykhailo Oleksiuk In our java project we have spotbug plugin. We configured warning-ng plugin to display this warnings in Jenkins, but all warnings generated by spotbug are treated by warning-ng as "Unknown". I suppose "warning-ng" should have some mappings for this but does'nt. Maybe I'm wrong and should fire a ticket on spotbug side. Add Comment
[JIRA] (JENKINS-52716) Allow selecting subnetworks different than "default" for the default VPC
Title: Message Title Moritz do Rio Schulze commented on JENKINS-52716 Re: Allow selecting subnetworks different than "default" for the default VPC Neat, thanks a lot! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52716) Allow selecting subnetworks different than "default" for the default VPC
Title: Message Title Moritz do Rio Schulze updated JENKINS-52716 Jenkins / JENKINS-52716 Allow selecting subnetworks different than "default" for the default VPC Change By: Moritz do Rio Schulze Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55693) Joda time recommends using java.time in Java 8 and later
Title: Message Title Mark Waite updated JENKINS-55693 Jenkins / JENKINS-55693 Joda time recommends using java.time in Java 8 and later Change By: Mark Waite Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55706) Capture Play Recap as exit codes
Title: Message Title Nuno Costa created an issue Jenkins / JENKINS-55706 Capture Play Recap as exit codes Issue Type: New Feature Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 2019-01-21 14:29 Priority: Minor Reporter: Nuno Costa It would be very useful to capture the values from play recap, so we could use to have some conditions, depending the the recap output. For example, if the change value is zero, do some action or stop the pipeline. The only way I found to do this is to parse ansible output with regex. If someone has a better solution please let me know Add Comment
[JIRA] (JENKINS-55674) Warnings-NG does not honor the number of entries to show
Title: Message Title Ulli Hafner updated JENKINS-55674 Jenkins / JENKINS-55674 Warnings-NG does not honor the number of entries to show Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54239) jobDSL for warnings column in view
Title: Message Title Ulli Hafner updated JENKINS-54239 Jenkins / JENKINS-54239 jobDSL for warnings column in view Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55564) issue count selector not respected after page reload
Title: Message Title Ulli Hafner updated JENKINS-55564 Jenkins / JENKINS-55564 issue count selector not respected after page reload Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55500) Warnings per project portlet
Title: Message Title Ulli Hafner updated JENKINS-55500 Jenkins / JENKINS-55500 Warnings per project portlet Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52755) Add view columns that show the number of issues
Title: Message Title Ulli Hafner updated JENKINS-52755 Jenkins / JENKINS-52755 Add view columns that show the number of issues Change By: Ulli Hafner Status: Fixed but Unreleased Resolved Released As: warnings-ng 2.1.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54846) RAW HTML is shown in cron column since 2.138.2
Title: Message Title David Aldrich commented on JENKINS-54846 Re: RAW HTML is shown in cron column since 2.138.2 Thanks, I will try it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54524) Improper Encoding of Sync Status
Title: Message Title Tim Foster commented on JENKINS-54524 Re: Improper Encoding of Sync Status Craig Rodrigues why is this a Won't Fix? There are half a dozen complaints here about this, and there are other users in my organization that are experiencing this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54846) RAW HTML is shown in cron column since 2.138.2
Title: Message Title benoit guerin commented on JENKINS-54846 Re: RAW HTML is shown in cron column since 2.138.2 I fixed this issue, I think. See the linked pull request. You can download the hpi here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55148) Is this plugin abandoned?
Title: Message Title Baptiste Mathus closed an issue as Not A Defect I understand you've been trying to ping the maintainer by many means, but we generally do not use JIRA for such requests . Jenkins / JENKINS-55148 Is this plugin abandoned? Change By: Baptiste Mathus Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54846) RAW HTML is shown in cron column since 2.138.2
Title: Message Title David Aldrich commented on JENKINS-54846 Re: RAW HTML is shown in cron column since 2.138.2 Please can this issue be progressed? It makes the dashboard untidy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55703) Add option to support exposing Build workspaces in JFR
Title: Message Title Oleg Nenashev started work on JENKINS-55703 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55703) Add option to support exposing Build workspaces in JFR
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55703 Add option to support exposing Build workspaces in JFR Change By: Oleg Nenashev Currently Jenkinsfile Runner starts internal builds in random places defined by the TemporaryDirectoryAllocator. It had some sense when JFR was inheriting from JTH/JUnit, but now it is no longer needed.I propose the following changes: * Keep a random TMP_DIR allocator in JFR by default, so that it can run in non-Docker mode. But change the path to make the usages of JFR explicit * Allow passing a custom workspace. Now it can be done via "-Djenkins.model.Jenkins.workspacesDir=/workspace/build", but it would be nice to have an option to automate it * Update Docker images to use the fixed Workspace path by default, add volume Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55705) Display link to downstream job in Blue Ocean
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-55705 Display link to downstream job in Blue Ocean Issue Type: New Feature Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2019-01-21 13:53 Priority: Minor Reporter: Timo Sand It would be really useful if the output included a link to the downstream job in Blue Ocean instead of the textual representation to the job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55704) Run jenkinsci/usage-in-plugins on JAXB usages
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55704 Run jenkinsci/usage-in-plugins on JAXB usages Issue Type: Task Assignee: Unassigned Components: core Created: 2019-01-21 13:52 Labels: java11 Priority: Major Reporter: Baptiste Mathus Daniel Beck suggested using https://github.com/jenkinsci/usage-in-plugins to analyze existing plugins from the Update Center. It could provide a complementary interesting perspective on the JAXB usage amongst actual plugins hosted at the Jenkins Update center. Acceptance Criteria list the main (all?) classes of JAXB run the modified version (See with Baptiste or Daniel for the existing patch) to get a report of the usages of these classes inside the hosted plugins Attach the report here, and write up a simple analysis of the content (i.e. is there a lot of usages, easy fix, proposals about what to test more given the outcome, etc.)
[JIRA] (JENKINS-55703) Add option to support exposing Build workspaces in JFR
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-55703 Add option to support exposing Build workspaces in JFR Issue Type: Improvement Assignee: Oleg Nenashev Components: custom-war-packager, jenkinsfile-runner Created: 2019-01-21 13:44 Priority: Minor Reporter: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55702) Missing ellipsis or other indication of abbreviation on artifacts shortlist
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-55702
Missing ellipsis or other indication of abbreviation on artifacts shortlist
Change By:
Craig Ringer
*If Jenkins abbreviates an artifact path on the main job page where it shows the artifacts summary, it should add an ellipsis to the start of the path to make it less confusing.*e.g. if the real path is foo/bar/baz/bop/myfile.so, Jenkins may currently display "bop/myfile.so" in the abbreviated list, and in the full list may display just the path "foo/bar/baz/bop" to browse. Instead it should use the path "*…*/bop/myfile.so" in the abbreviated list, and preferably tooltip-display the full path on hover over the file link.*Example/rationale:*When displaying a job's results, the artifacts summary shown directly on the build results page under the "Build Artifacts" header collapses and hides common subdirectories. That is useful, but it's misleading because there's no indication the abbreviation was performed on the paths.So a user will see e.g.!artifacts-abbrev.png!when viewing a job, then when they go to the /artifact/ page they'll see !artifacts.png! Note that different paths were abbreviated at different depths in the first output. The true listing is{ \ {$ unzip -L archive.zip }}{{Archive: archive.zip}} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test.log }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/package-list.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/pg_controldata.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/pgbench.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/package-list.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pg_controldata.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pgbench-init.txt }} \ {{ inflating: archive/tpa-bdr-simple/tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pgbench.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test.log }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/killjoy/package-list.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/killjoy/pg_controldata.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/killjoy/pgbench.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/quahaug/package-list.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/quahaug/pg_controldata.txt }} \ {{ inflating: archive/tpa-camo-2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/quahaug/pgbench-init.txt }} \ {{ inflating:
[JIRA] (JENKINS-55702) Missing ellipsis or other indication of abbreviation on artifacts shortlist
Title: Message Title
Craig Ringer updated an issue
Jenkins / JENKINS-55702
Missing ellipsis or other indication of abbreviation on artifacts shortlist
Change By:
Craig Ringer
*If Jenkins abbreviates an artifact path on the main job page where it shows the artifacts summary, it should add an ellipsis to the start of the path to make it less confusing.*e.g. if the real path is foo/bar/baz/bop/myfile.so, Jenkins may currently display "bop/myfile.so" in the abbreviated list, and in the full list may display just the path "foo/bar/baz/bop" to browse. Instead it should use the path "*…*/bop/myfile.so" in the abbreviated list, and preferably tooltip-display the full path on hover over the file link.*Example/rationale:*When displaying a job's results, the artifacts summary shown directly on the build results page under the "Build Artifacts" header collapses and hides common subdirectories. That is useful, but it's misleading because there's no indication the abbreviation was performed on the paths.So a user will see e.g.!artifacts-abbrev.png!when viewing a job, then when they go to the /artifact/ page they'll see !artifacts.png! Note that different paths were abbreviated at different depths in the first output. The true listing is{{$ unzip - l ~/Downloads/ L archive.zip }}{{Archive: /home/craig/Downloads/ archive.zip}}{{ Length Date Time Name}}{{- -- - }}{{ 11194 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test.log}}{{ 1906124 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/package-list.txt}}{{ 2281 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/pg_controldata.txt}}{{ 329 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kinkier/pgbench.txt}}{{ 1906131 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/package-list.txt}}{{ 2281 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pg_controldata.txt}}{{ 1 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pgbench-init.txt}}{{ 329 01-21-2019 11 inflating : 28 archive/tpa- BDR bdr - Simple simple /tpa-test/bdr-simple/results/tpaexec-test/1548066249/kismet/pgbench.txt}}{{ 11265 01-21-2019 11 inflating : 28 archive/tpa- CAMO camo -2x2/tpa-test/camo2x2/results/tpaexec-test.log}}{{ 1906129 01-21-2019 11 inflating : 28 archive/tpa- CAMO camo -2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/killjoy/package-list.txt}}{{ 2281 01-21-2019 11 inflating : 28 archive/tpa- CAMO camo -2x2/tpa-test/camo2x2/results/tpaexec-test/1548066249/killjoy/pg_controldata.txt}}{{ 329 01-21-2019 11 inflating : 28
[JIRA] (JENKINS-55702) Missing ellipsis or other indication of abbreviation on artifacts shortlist
Title: Message Title Craig Ringer created an issue Jenkins / JENKINS-55702 Missing ellipsis or other indication of abbreviation on artifacts shortlist Issue Type: Bug Assignee: Unassigned Attachments: artifacts-abbrev.png, artifacts.png Components: core Created: 2019-01-21 13:41 Environment: 2.150.2 Labels: usability user-experience UI Priority: Trivial Reporter: Craig Ringer If Jenkins abbreviates an artifact path on the main job page where it shows the artifacts summary, it should add an ellipsis to the start of the path to make it less confusing. e.g. if the real path is foo/bar/baz/bop/myfile.so, Jenkins may currently display "bop/myfile.so" in the abbreviated list, and in the full list may display just the path "foo/bar/baz/bop" to browse. Instead it should use the path "…/bop/myfile.so" in the abbreviated list, and preferably tooltip-display the full path on hover over the file link. Example/rationale: When displaying a job's results, the artifacts summary shown directly on the build results page under the "Build Artifacts" header collapses and hides common subdirectories. That is useful, but it's misleading because there's no indication the abbreviation was performed on the paths. So a user will see e.g. when viewing a job, then when they go to the /artifact/ page they'll see Note that different paths were abbreviated at different depths in the
[JIRA] (JENKINS-53882) Text ERROR and HTTP 404 when validating input parameter
Title: Message Title Jonas Lindström commented on JENKINS-53882 Re: Text ERROR and HTTP 404 when validating input parameter Still reproducible with Jenkins 2.150.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55701) readProperties does not interpolate some vars
Title: Message Title
jlpinardon commented on JENKINS-55701
Re: readProperties does not interpolate some vars
Let's assume I have something initialized with myVar=${instanceGlobalVar} in the property file, myVar is used as '${instanceGlobalVar}' not interpolated in the Jenkinsfile. But if I set : myVar="${instanceGlobalVar}" in an environment {...} block, myVar has its awaited value, i.e. the one contained in "${instanceGlobalVar}. Worst is probably that this is not systematic in the property file.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55701) readProperties does not interpolate some vars
Title: Message Title
jlpinardon created an issue
Jenkins / JENKINS-55701
readProperties does not interpolate some vars
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2019-01-21 12:30
Environment:
Master and Slave run each on a centOS VM Jenkins 2.121.3 Pipeline-Utility-Steps : 2.2.0
Priority:
Critical
Reporter:
jlpinardon
I have created a property files with vars either initialized to a constant value or to another var coming from the Jenkins instance global properties. Then, I create a Jenkinsfile starting with a node block which reads the property file :
def myEnv
node {
myEnv=
readProperties( file:fileName, interpolate:true )
}
pipeline {
...
}
Most of vars are correctly set as far as I can check that their value. But few of them are not interpolated. Those I am concerned with are initialized with a global jenkins variable which is either initialized itself as a constant value or using another global variable. But some others initialized the same are correctly interpolated. So... I am a bit lost. Additionally, I tried with interpolate:false ... and surpringly the results was not worst ! It means that variables are interpolated... unless the few that are not.
[JIRA] (JENKINS-55700) deadlock remoting TCP agent connection handler
Title: Message Title
Alexander Moiseenko updated an issue
Jenkins / JENKINS-55700
deadlock remoting TCP agent connection handler
Change By:
Alexander Moiseenko
{noformat}Found one Java-level deadlock:="TCP agent connection handler #159021 with /10.116.113.11:54776": waiting for ownable synchronizer 0x0002ce4a6770, (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), which is held by "IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.116.241.122:8181 remote=10.116.113.11/10.116.113.11:54776]] / Computer.threadPoolForRemoting [#12366]""IOHub#1: Worker[channel:java.nio.channels.SocketChannel[connected local=/10.116.241.122:8181 remote=10.116.113.11/10.116.113.11:54776]] / Computer.threadPoolForRemoting [#12366]": waiting to lock monitor 0x7f75cc5900f8 (object 0x0002ce4de778, a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer), which is held by "TCP agent connection handler #159021 with /10.116.113.11:54776"Java stack information for the threads listed above:==="TCP agent connection handler #159021 with /10.116.113.11:54776": at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x0002ce4a6770> (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:967) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1283) at java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:727) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.getNextSend(ProtocolStack.java:857) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:686) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processWrite(SSLEngineFilterLayer.java:518) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.processQueuedWrites(SSLEngineFilterLayer.java:248) - locked <0x0002ce4a6800> (a java.lang.Object) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.doSend(SSLEngineFilterLayer.java:200) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:692) at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.doSend(ConnectionHeadersFilterLayer.java:497) - locked <0x0002ce4de778> (a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:692) at org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.start(ChannelApplicationLayer.java:230) at org.jenkinsci.remoting.protocol.ProtocolStack.init(ProtocolStack.java:201) at
[JIRA] (JENKINS-55700) deadlock remoting TCP agent connection handler
Title: Message Title Alexander Moiseenko created an issue Jenkins / JENKINS-55700 deadlock remoting TCP agent connection handler Issue Type: Bug Assignee: Jeff Thompson Attachments: jenkins.tdump Components: remoting Created: 2019-01-21 12:27 Environment: Server: Jenkins 2.138.2 Remoting: 3.25 Java: 1.8.181 Labels: deadlock remoting Priority: Minor Reporter: Alexander Moiseenko Add Comment
[JIRA] (JENKINS-55699) Pipeline script documentation does not show
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-55699 Pipeline script documentation does not show Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-01-21 12:11 Environment: CloudBees Jenkins Enterprise 2.138.2.2-rolling Labels: script library Priority: Minor Reporter: davidkarlsen I have pipeline libraries in vars/myscript.groovy - but documentation in vars/myscript.txt does not show in the UI. https://groups.google.com/forum/?nomobile=true#!topic/jenkinsci-users/qyEv2MhOt10 Add Comment
[JIRA] (JENKINS-55698) SSO + CRSF causes 403 errors
Title: Message Title Koen Dierckx created an issue Jenkins / JENKINS-55698 SSO + CRSF causes 403 errors Issue Type: Bug Assignee: Tomas Westling Components: kerberos-sso-plugin Created: 2019-01-21 11:54 Environment: Jenkins 2.160 Kerberos SSO plugin 1.4 Labels: SSO CSRF Priority: Minor Reporter: Koen Dierckx We are running jenkins behind an apache proxy Since the latest update, the kerberos sso plugin will cause issues related to the CSRF security policy that is enabled by default. If we only disable the Kerberos SSO, and log in manually using LDAP credentials, everything works as expected. If we only disable the CSRF Protection, and login using SSO, everything works as expected (besides a remote API call, that requires CSRF to be enabled) But when both CSRF and SSO are enabled, the automatic login works perfectly. But the moment you try to do a form submit, like starting a job, we will get a 403 - Forbidden error. This has been working perfectly for a few years. So a recent update broke this. Perhaps the SSO plugin needs an update, related to another recent change in how CSRF is handled ?
[JIRA] (JENKINS-55683) Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication
Title: Message Title Stephen Connolly assigned an issue to Wadeck Follonier Jenkins / JENKINS-55683 Endless loop on login when using OpenID plugin after upgrading to 2.160 / 2.150.2, preventing user authentication Change By: Stephen Connolly Assignee: Stephen Connolly Wadeck Follonier Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55682) Portlet view for warnings-ng doesn't get styled properly
Title: Message Title Lübbe Onken commented on JENKINS-55682 Re: Portlet view for warnings-ng doesn't get styled properly Yes, that's why I asked on gitter where to place this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55350) Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException
Title: Message Title Lübbe Onken commented on JENKINS-55350 Re: Open Tasks Scanner throws java.nio.charset.UnmappableCharacterException Nowadays UTF-8 would probably be a good fallback (unless you have to deal with a legacy code base, but even some up to date source code from github contains UTF-8 and is saved in ANSI). Alternatively, the system default encoding could be used as fallback. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44675) We are trying to configure the ALM Octane CI server in Jenkin server. while giving details like CI String and CI secret code, it is giving error that authorization failure. plea
Title: Message Title Pranjal Gohain commented on JENKINS-44675 Re: We are trying to configure the ALM Octane CI server in Jenkin server. while giving details like CI String and CI secret code, it is giving error that authorization failure. please help in configuring CI servers. Hi Kiran Kasu i had this problem but i was able to solve this. You might need to give your octane server ip in the no proxy tab in the advance tab where we configure proxy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34273) Extend quantity configuration to Pipeline lock step
Title: Message Title Janos Feher edited a comment on JENKINS-34273 Re: Extend quantity configuration to Pipeline lock step [~rbjorklin], [~tstibbs]: did you figure it out? I added quantity manually need to copy the config file instance multiple times and group them by label. So you create- resource1 , but the value vanishes after I save the global config form label: my_resource- resource2, label: my_resource- resource3, label: my_resource- resource4, label: my_resource- resource5, label: my_resourceNow you have my_resource with a quantity of 5 . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
