[JIRA] (JENKINS-49573) Matrix Project Plugin is affected by JEP-200
Title: Message Title
David Gangel updated an issue
Jenkins / JENKINS-49573
Matrix Project Plugin is affected by JEP-200
Change By:
David Gangel
We are not able to run our matrix jobs since we upgraded our Jenkins server to 2.106The issue what is logged in the console: \{code} FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuildjava.lang.UnsupportedOperationException: Refusing to marshal com.google.common.collect.Lists$TransformingRandomAccessList for security reasons; see [https://jenkins.io/redirect/class-filter/] at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize java.util.Collections$UnmodifiableCollection#c for class java.util.Collections$UnmodifiableList at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252)Caused: java.lang.RuntimeException: Failed to serialize hudson.plugins.matrix_configuration_parameter.shortcut.ResultShortcut#resultsToCheck for class hudson.plugins.matrix_configuration_parameter.shortcut.ResultShortcut at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at
[JIRA] (JENKINS-49573) Matrix Project Plugin is affected by JEP-200
Title: Message Title
David Gangel created an issue
Jenkins / JENKINS-49573
Matrix Project Plugin is affected by JEP-200
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
matrix-project-plugin
Created:
2018-02-15 07:46
Labels:
JEP-200
Priority:
Critical
Reporter:
David Gangel
We are not able to run our matrix jobs since we upgraded our Jenkins server to 2.106 The issue what is logged in the console: {code} FATAL: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild java.lang.UnsupportedOperationException: Refusing to marshal com.google.common.collect.Lists$TransformingRandomAccessList for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize java.util.Collections$UnmodifiableCollection#c for class java.util.Collections$UnmodifiableList at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at
[JIRA] (JENKINS-49568) Container template not using correct version of image specified.
Title: Message Title Carlos Sanchez commented on JENKINS-49568 Re: Container template not using correct version of image specified. Use a uuid as label https://github.com/jenkinsci/kubernetes-plugin/blob/master/README.md#pipeline-support Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49572) [SRF] [Tunneling] > settings are missing in create tunnel step
Title: Message Title noam doron created an issue Jenkins / JENKINS-49572 [SRF] [Tunneling] > settings are missing in create tunnel step Issue Type: Bug Assignee: noam doron Components: hp-application-automation-tools-plugin Created: 2018-02-15 07:01 Priority: Critical Reporter: noam doron Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are
[JIRA] (JENKINS-49360) [SRF] Unable to open tests results in case script name contains spaces
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49360 [SRF] Unable to open tests results in case script name contains spaces Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49359) [SRF] No results nor error message when tunnel doest's exist
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49359 [SRF] No results nor error message when tunnel doest's exist Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49358) [SRF] Running scripts which finish in 'completed' status marked as failed tests in jerkins's test results with unavailable script steps
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49358 [SRF] Running scripts which finish in 'completed' status marked as failed tests in jerkins's test results with unavailable script steps Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49356) [SRF] Second execution fails when running 2 tests with different tags and a space after the comma delimiter
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49356 [SRF] Second execution fails when running 2 tests with different tags and a space after the comma delimiter Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49355) [SRF] In case the test is stopped via SRF the Jenkins job continue to run
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49355 [SRF] In case the test is stopped via SRF the Jenkins job continue to run Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49357) [SRF] Description steps are missing for UFT test result
Title: Message Title noam doron resolved as Fixed Jenkins / JENKINS-49357 [SRF] Description steps are missing for UFT test result Change By: noam doron Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48880) Jira rest api connection timeout
Title: Message Title Roshni J commented on JENKINS-48880 Re: Jira rest api connection timeout Yes done. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49571) Post Section not available in Blue-Ocean
Title: Message Title Scott Herrmann created an issue Jenkins / JENKINS-49571 Post Section not available in Blue-Ocean Issue Type: Improvement Assignee: Unassigned Components: blueocean-pipeline-editor-plugin, blueocean-plugin Created: 2018-02-15 06:49 Environment: Jenkins 2.60.3 BlueOcean 1.4.1 Labels: blueocean pipeline Pipeline Priority: Minor Reporter: Scott Herrmann Currently (to my knowledge and searching) there is no way to create a post section in Blue-Ocean for pipelines. Add Comment
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title
Steffen Kötte updated an issue
Jenkins / JENKINS-49495
False positive for LLVM/Clang
Change By:
Steffen Kötte
|{{{color:#808080}01{color} {color:#00}Copying the source file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' f{color}{color:#00}rom the workspace to the build folder {color}{color:#ff6100}'25{color}{color:#99}{color}{color:#00}bd.tmp{color}{color:#ff6100}' o{color}{color:#00}n the Jenkins master failed.{color}}}{{{color:#808080}02{color} {color:#00}Seems that the path is relative, however an absolute path is required when copying the sources.{color}}}{{{color:#808080}03{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' c{color}{color:#00}ontained more than once in your workspace?{color}}}{{{color:#808080}04{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' a {color}{color:#00}valid filename?{color}}}{{{color:#808080}05{color} {color:#00}If you are building on a slave: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}{{{color:#808080}06{color} {color:#00}If you are building on the master: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/workspace/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}| Follow up for [https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333=1515495766539#app-switcher] The part of the log which is producing the issue is this:{noformat}Test Case '-[AuthenticationTests test_mockError]' started.2018-02-12 01:40:47.179785+0100 App[94246:19282931] ERROR: Error Domain=mockError Code=12345 "(null)" (-[ServerConnection getInitialSessionWithToken:success:error:handleResponse:tryCount:]_block_invoke in ServerConnection.m:911)Test Case '-[AuthenticationTests test_mockError]' passed (0.004 seconds).{noformat}This is printed during our test run, where we in debug mode print the function with {code:java}__PRETTY_FUNCTION__{code}As soon as the the function has something named `error:` it generates a false
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title
Steffen Kötte updated an issue
Jenkins / JENKINS-49495
False positive for LLVM/Clang
Change By:
Steffen Kötte
|{{{color:#808080}01{color} {color:#00}Copying the source file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' f{color}{color:#00}rom the workspace to the build folder {color}{color:#ff6100}'25{color}{color:#99}{color}{color:#00}bd.tmp{color}{color:#ff6100}' o{color}{color:#00}n the Jenkins master failed.{color}}} {{{color:#808080}02{color} {color:#00}Seems that the path is relative, however an absolute path is required when copying the sources.{color}}} {{{color:#808080}03{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' c{color}{color:#00}ontained more than once in your workspace?{color}}} {{{color:#808080}04{color} {color:#00}Is the file {color}{color:#ff6100}'20{color}{color:#99}18{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}' a {color}{color:#00}valid filename?{color}}} {{{color:#808080}05{color} {color:#00}If you are building on a slave: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}} {{{color:#808080}06{color} {color:#00}If you are building on the master: please check {color}{color:#7f0055}*if* {color}{color:#00}the file is accessible under {color}{color:#ff6100}'$J{color}{color:#00}ENKINS_HOME/{color}{color:#00}[{color}{color:#00}job-name{color}{color:#00}]{color}{color:#00}/workspace/{color}{color:#99}2018{color}{color:#00}-{color}{color:#99}02{color}{color:#00}-{color}{color:#99}12 01{color}{color:#ff6100}'{color}}}| Follow up for [https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333=1515495766539#app-switcher] The part of the log which is producing the issue is this:{noformat}Test Case '-[AuthenticationTests test_mockError]' started.2018-02-12 01:40:47.179785+0100 App[94246:19282931] ERROR: Error Domain=mockError Code=12345 "(null)" (-[ServerConnection getInitialSessionWithToken:success:error:handleResponse:tryCount:]_block_invoke in ServerConnection.m:911)Test Case '-[AuthenticationTests test_mockError]' passed (0.004 seconds).{noformat}This is printed during our test run, where we in debug mode print the function with {code:java}__PRETTY_FUNCTION__{code}As soon as the the function has something named `error:` it generates a false
[JIRA] (JENKINS-49570) Poll mail box plugin is not able to read the mail box of MS exchange but able to connect
Title: Message Title hemant sharma updated an issue Jenkins / JENKINS-49570 Poll mail box plugin is not able to read the mail box of MS exchange but able to connect Change By: hemant sharma Plugin version :: 1.026Jenkins version :: 2.32.3I have installed Poll-mailbox-trigger-plugin on my jenkins server. we also have a mail server ( MS-Exchange).ISSUE :: some time i have noticed that the plugin not able to read the mail even though there are unread mail present in the mail box but it's able to connect to the server at same time. i found similar issue when i searched https://issues.jenkins-ci.org/browse/JENKINS-32966 and taken care the configuration of poll-mailbox plugin. Note - mostly i noticed this happens in the morning. it never fails once it start working. i tried 3 PM to 11:50 PM and it worked fine but next morning again it started failing to read. Doubt - does the polling-plugin compare the time stamp of jenkins server where the plugin install and the mail-server ? Configuration and the log are attached. Polling time is 2 min. [Poll Mailbox Trigger] - Connected!Found properties:- [attachments:IGNORE]- [folder:INBOX]- [host:mail.xyz.com]- [mail.debug:true]- [mail.debug.auth:true]- [mail.imap.ssl.enable:true]- [mail.imap.starttls.enable:true]- [mail.imaps.host:mail.xyz.com]- [mail.imaps.port:993]- [password:***]- [receivedXMinutesAgo:120]- [storeName:imaps]- [subjectContains:Trigger TESTMAIL]- [username:run...@xyz.com]Connected to mailbox. Searching for messages where:- [flag is unread]- [subject contains 'Trigger TESTMAIL'] Add Comment
[JIRA] (JENKINS-49557) initial admin password cannot contain special characters
Title: Message Title Nicolas De Loof updated an issue Jenkins / JENKINS-49557 initial admin password cannot contain special characters Change By: Nicolas De Loof Component/s: core Component/s: docker Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49557) initial admin password cannot contain special characters
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-49557 initial admin password cannot contain special characters Change By: Nicolas De Loof Assignee: Nicolas De Loof Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49570) Poll mail box plugin is not able to read the mail box of MS exchange but able to connect
Title: Message Title hemant sharma updated an issue Jenkins / JENKINS-49570 Poll mail box plugin is not able to read the mail box of MS exchange but able to connect Change By: hemant sharma Attachment: mailbox.PNG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49570) Poll mail box plugin is not able to read the mail box of MS exchange but able to connect
Title: Message Title hemant sharma created an issue Jenkins / JENKINS-49570 Poll mail box plugin is not able to read the mail box of MS exchange but able to connect Issue Type: Bug Assignee: Nick Grealy Attachments: jenking-polling-issue.txt Components: poll-mailbox-trigger-plugin Created: 2018-02-15 06:01 Priority: Critical Reporter: hemant sharma Plugin version :: 1.026 Jenkins version :: 2.32.3 I have installed Poll-mailbox-trigger-plugin on my jenkins server. we also have a mail server ( MS-Exchange). ISSUE :: some time i have noticed that the plugin not able to read the mail even though there are unread mail present in the mail box but it's able to connect to the server at same time. i found similar issue when i searched https://issues.jenkins-ci.org/browse/JENKINS-32966 and taken care the configuration of poll-mailbox plugin. Note - mostly i noticed this happens in the morning. it never fails once it start working. i tried 3 PM to 11:50 PM and it worked fine but next morning again it started failing to read. Configuration and the log are attached. Polling time is 2 min. [Poll Mailbox Trigger] - Connected! Found properties: [attachments:IGNORE] [folder:INBOX] [host:mail.xyz.com] [mail.debug:true] [mail.debug.auth:true] [mail.imap.ssl.enable:true]
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Madhava Kulkarni commented on JENKINS-49495 Re: False positive for LLVM/Clang Warning Plugin version is: 4.52 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Matt Phillips updated an issue Jenkins / JENKINS-49211 Build gets stuck on Publish Over CIFS Change By: Matt Phillips Since the latest Jenkins updates - # - Build get stuck when it starts a "Publish over CIFS" build step (I need to kill the Jenkins service to make it stop) - *- EDIT 2018-02-15 - This is fixed in v0.9 (JENKINS-49010)* # If I try to modify a job with a "Publish over CIFS" build step, the "CIFS Share" drop down list is empty even though the configuration looks fine under "Manage Jenkins" and I can successfully test those server entries *- EDIT 2018-02-15 - This is still occurring in v0.9* I checked the error logs, but can't see any errors. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Matt Phillips commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS v0.9 was just released, so I've updated and re-tested #1 in my original description is now fixed (in JENKINS-49010) #2 is still a problem - If I try to modify a job with a "Publish over CIFS" build step, the "CIFS Share" drop down list is empty even though the configuration looks fine under "Manage Jenkins" and I can successfully test those server entries Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title
pigloves you created an issue
Jenkins / JENKINS-49569
Pipeline archives artifacts with weird untraceable folder name
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-02-15 03:36
Priority:
Major
Reporter:
pigloves you
Thanks for Blue Ocean plugin, it builds and archives artifacts in "${JENKINS_HOME}/jobs/${PROJ_NAME}/branches/${BRANCH_NAME}". But when a branch name contains "_(underscore)" or ".(dot)", it causes "${hyphened branch name}.${6 chars hash}" which I cannot utilize to deploy. Why does it happen? What's the best practice to use branch archives?
Add Comment
[JIRA] (JENKINS-49543) Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl
Title: Message Title Tim McNally commented on JENKINS-49543 Re: Refusing to marshal org.jenkinsci.main.modules.cli.auth.ssh.UserPropertyImpl I did not see anything from turning on logging for ClassFilterImpl and triggering the exception. After reading through JENKINS-49147 I upgraded our Tomcat server from 8.0.12 to 8.0.50(latest 8.0), this resolves the issue. I also tried upgrading to 8.5.28(latest 8.5) and confirmed that also resolves the issue. Out of curiosity, is running Jenkins in Tomcat a "supported" platform or should I look to moving to the built-in servlet container? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49568) Container template not using correct version of image specified.
Title: Message Title David Rodriguez created an issue Jenkins / JENKINS-49568 Container template not using correct version of image specified. Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-02-15 02:28 Priority: Blocker Reporter: David Rodriguez I have update the version of the image I am using for my container and it's not being used when Jenkins spins up the slave. I have the following ``` containerTemplate(name: 'embedded-builder', image: 'embedded-builder:1.1.4', envVars: [envVar(key: 'BRANCH_NAME', value: "$BRANCH_NAME"),envVar(key: 'J_CREDS_IDS', value: "$J_CREDS_IDS")], ttyEnabled: true, command: 'cat', alwaysPullImage: true, workingDir: '/home/jenkins')``` But when the job runs I describe the slave pod and I see that the container is using an older version. ``` Normal Pulling 1m kubelet, ip-172-20-103-179.ec2.internal pulling image "embedded-builder:1.1.2" Normal Pulled 1m kubelet, ip-172-20-103-179.ec2.internal Successfully pulled image "embedded-builder:1.1.2"``` I have tried restarting jenkins, switching the image version to be latest and nothing seems to be making it budge. Any thoughts on what to try would be greatly appreciated. Add Comment
[JIRA] (JENKINS-49567) Automatically support docker networks in pipelines with multiple containers
Title: Message Title Andrew Berry created an issue Jenkins / JENKINS-49567 Automatically support docker networks in pipelines with multiple containers Issue Type: New Feature Assignee: Unassigned Components: docker-workflow-plugin Created: 2018-02-15 00:37 Priority: Minor Reporter: Andrew Berry As is, it's not possible to create a Jenkinsfile with docker containers that need to communicate with each other (and not just a basic connection from container A to container B). For example, when running Behat tests for Drupal: The webapp container (with PHP etc) çontains Behat, which needs to be able to link to the Selenium container. The Selenium container needs to be able to link back to the webapp container to load pages. This leads to a chicken-and-the-egg problem, since you can't know the ID of a container before it starts. I imagine there's a way to hack it with container names, but that seems collision prone. Under other tools like Circle CI, a docker network is transparently created and all containers ports from their Dockerfiles are automatically exposed to each other. For example, even though there are two containers, from both perspectives all ports are available on localhost. On top of this, the recommended --link parameter has been deprecated by docker, so moving to bridge networks will keep the plugin working with future Docker releases.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title dan tran commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' you can easily use build-helper-maven-plugin to deploy a none jar artifact. In your current test source, pick any .java file Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45437) DomainName attribute
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-45437 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Title: Message Title Ivan Fernandez Calvo updated JENKINS-22088 Jenkins / JENKINS-22088 Disk space leak with multiple copies of winstone-.jar in TEMP folder Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45372) after creating a new pipeline that has Jenkinsfiles / PRs and branches you are told there are no branches with Jenkinsfile
Title: Message Title Ivan Meredith updated JENKINS-45372 I've seen this before, last yearbut I cant reproduce it after a lot of testing. This may be due to environment issues maybe its been fixed. Closing until its seen again. Jenkins / JENKINS-45372 after creating a new pipeline that has Jenkinsfiles / PRs and branches you are told there are no branches with Jenkinsfile Change By: Ivan Meredith Status: In Review Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-48274) Saving to Github/GHE requires email with user or it fails
Title: Message Title Ivan Meredith started work on JENKINS-48274 Change By: Ivan Meredith Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45372) after creating a new pipeline that has Jenkinsfiles / PRs and branches you are told there are no branches with Jenkinsfile
Title: Message Title Ivan Meredith updated JENKINS-45372 Jenkins / JENKINS-45372 after creating a new pipeline that has Jenkinsfiles / PRs and branches you are told there are no branches with Jenkinsfile Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title Cyrille Le Clerc commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' dan tran I am not familiar with rpm and ova. Could you build a sample test case, maybe forking https://github.com/cyrille-leclerc/my-jar.git ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47026) User not completely set in docker containers
Title: Message Title
Taras Bondarchuk commented on JENKINS-47026
Re: User not completely set in docker containers
Since I'm building agent from Dockerfile anyway, I've fixed this by:
agent {
dockerfile {
additionalBuildArgs '--build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g)'
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-47026) User not completely set in docker containers
Title: Message Title
Taras Bondarchuk edited a comment on JENKINS-47026
Re: User not completely set in docker containers
Since I'm building agent from Dockerfile anyway, I've fixed this by: {code:java}agent { dockerfile { additionalBuildArgs '--build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g)' }}{code} and in Dockerfile: {code:java}ARG USER_ID=1000ARG GROUP_ID=1000RUN groupadd -g $GROUP_ID user && \useradd -u $USER_ID -s /bin/sh -g user user{code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-49566) credentials-plugin 2.1.16 breaks ssh-private-key connection to docker slaves
Title: Message Title Daniel Hsueh created an issue Jenkins / JENKINS-49566 credentials-plugin 2.1.16 breaks ssh-private-key connection to docker slaves Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-02-14 22:27 Environment: jenkins 2.98 ssh-credentials 1.13 credentials 2.1.16 docker-plugin 1.1.2 ssh-slaves 1.25.1 Priority: Minor Reporter: Daniel Hsueh I was running a Jenkins setup with above plugins at indicated versions except credentials=2.1.14, with a docker cloud set up, connecting to agent docker container via ssh with a com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey and non-verifying verification strategy, successfully. Builds were working fine. An upgrade of credentials plugin to 2.1.16 immediately resulted in existing working jobs running on docker slaves no longer progressing at all. The job would wait for the node to come online forever. The docker container machine is running, and a "docker ps -a" shows the containers starting up. The jenkins master log shows the container being provisioned and nothing happens after that, for hours and hours (some info redacted like ): Feb 12, 2018 6:42:53 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFO: Asked to provision 1 slave(s) for: Feb 12, 2018 6:42:53 PM com.nirima.jenkins.plugins.docker.DockerCloud provision INFO: Will provision '', for label: '', in cloud: '' Feb 12, 2018 6:42:53 PM com.nirima.jenkins.plugins.docker.DockerCloud addProvisionedSlave INFO: Provisioning '' number '0' on ''; Total containers: '0' Feb 12, 2018 6:42:53 PM
[JIRA] (JENKINS-21052) l:copyButton does not work
Title: Message Title Daniel Beck stopped work on JENKINS-21052 Change By: Daniel Beck Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48407) Permission issue after upgrade to 2.93
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-48407 Permission issue after upgrade to 2.93 This is in 2.105, so should be in the next LTS baseline even if we end up not going with 2.107. Change By: Daniel Beck Labels: 2.89.4-rejected lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49147) JEP-200 location-based whitelisting broken in obsolete versions of Tomcat
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49147 JEP-200 location-based whitelisting broken in obsolete versions of Tomcat This is in 2.104 so realistic LTS baselines will include this (and we're aiming for 2.107). Change By: Daniel Beck Labels: 2.89.4-rejected JEP-200 lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49054) Lack of finally block in TreeUnmarshaller can cause DescribableList to throw ClassCastException or NoSuchMethodException
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-49054 Lack of finally block in TreeUnmarshaller can cause DescribableList to throw ClassCastException or NoSuchMethodException This is in 2.103, so any reasonable upcoming LTS baseline will include this. Change By: Daniel Beck Labels: 2.89.4-rejected diagnostics lts-candidate robustness xstream Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-31511 Recent (since 1.628) bug introduced into pluginManager filter UI Change By: Daniel Beck Labels: lts-candidate newbie-friendly regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-31511) Recent (since 1.628) bug introduced into pluginManager filter UI
Title: Message Title Daniel Beck commented on JENKINS-31511 Re: Recent (since 1.628) bug introduced into pluginManager filter UI The behavior remains; with recent plugin releases more easily observable when typing command-launcher as that has been detached from core fairly recently. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29977) Git Plugin truncates changelog
Title: Message Title
Andrew Macks edited a comment on JENKINS-29977
Re: Git Plugin truncates changelog
{{So, after tracking this issue for a while, and getting excited over the last couple of days with Chris' involvement, I got a little concerned when the issue became Unassigned again and decided to dig into it myself.}}{{It turns out that the issue is actually in git-client-plugin and not git-plugin at all. It appears to be caused by this commit:}} {{}} {code:java}commit de49c9bf21f560ac3851c4f7ea3a3597a114ac8eAuthor: Nicolas De Loof Date: Tue Feb 24 09:44:20 2015 +0100 [FIXED JENKINS-27097] use ISO-8601 in changelog Use an explicit format string (to mimic raw format) to enforce ISO-8601 date format. Side benefit is this format string should not be impacted if a future/exotic git CLI do introduce some subtle changes in format=raw output.{code} {{Basically, an arbitary format was specified for the git whatchanged format:}}{{commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b}}{{The idea was good (to avoid changes in the format of the log pretty raw format), but it also introduced arbitrary wrapping early in the data processing which is probably not the correct place for it (altering the data during input).}}{{Changing this to:}}{{commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%s%n%n%b}}{{fixes the issue.}}{{I don't personally have the environment setup to test this fully, so if somebody can take this information and act upon it, I would be greatly appreciative.}} {{ If there is the desire to maintain the existing (arbitrary) wrapping }} behaviour, then I would suggest adding some sort of flag that allows disabling the arbitrary wrapping. This should (hopefully) make everybody happy :)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace
Title: Message Title javydreamercsw commented on JENKINS-49413 Re: IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace I'll try to explain without giving too much away: We have a testing framework that retrieves artifacts from an internal Maven repositories. The artifact is unzipped and ran as a server. Test framework interacts with the artifact. I understand the security concerns, but the main issue here is that even when I specify the tmp dir to be used in the pipeline it doesn't make it all the way to the actual test. It works fine out of the pipeline. (i.e. moving it within the workspace) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-29977) Git Plugin truncates changelog
Title: Message Title
Andrew Macks commented on JENKINS-29977
Re: Git Plugin truncates changelog
So, after tracking this issue for a while, and getting excited over the last couple of days with Chris' involvement, I got a little concerned when the issue became Unassigned again and decided to dig into it myself. It turns out that the issue is actually in git-client-plugin and not git-plugin at all. It appears to be caused by this commit: {{}}
commit de49c9bf21f560ac3851c4f7ea3a3597a114ac8e
Author: Nicolas De Loof
Date: Tue Feb 24 09:44:20 2015 +0100
[FIXED JENKINS-27097] use ISO-8601 in changelog
Use an explicit format string (to mimic raw format)
to enforce ISO-8601 date format.
Side benefit is this format string should not be
impacted if a future/exotic git CLI do introduce
some subtle changes in format=raw output.
Basically, an arbitary format was specified for the git whatchanged format: commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%w(76,4,4)%s%n%n%b The idea was good (to avoid changes in the format of the log pretty raw format), but it also introduced arbitrary wrapping early in the data processing which is probably not the correct place for it (altering the data during input). Changing this to: commit %H%ntree %T%nparent %P%nauthor %aN <%aE> %ai%ncommitter %cN <%cE> %ci%n%n%s%n%n%b fixes the issue. I don't personally have the environment setup to test this fully, so if somebody can take this information and act upon it, I would be greatly appreciative. {{If there is the desire to maintain the existing (arbitrary) wrapping }}behaviour, then I would suggest adding some sort of flag that allows disabling the arbitrary wrapping. This should (hopefully) make everybody happy
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (TEST-109) [SKY-TV] Real Madrid vs Paris Saint Germain Live Stream Free UCL Online
Title: Message Title Daniel Beck deleted an issue test / TEST-109 [SKY-TV] Real Madrid vs Paris Saint Germain Live Stream Free UCL Online This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-46706) "default to blue ocean" setting
Title: Message Title Ivan Meredith updated JENKINS-46706 Jenkins / JENKINS-46706 "default to blue ocean" setting Change By: Ivan Meredith Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49565) Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-49565 Update Jenkins CLI to Mina SSHD 1.7.0 and make it always similar to the Jenkins Core Issue Type: Improvement Assignee: Unassigned Components: cli, core Created: 2018-02-14 21:51 Priority: Minor Reporter: Oleg Nenashev It is a follow up to https://github.com/jenkinsci/jenkins/pull/3278#issuecomment-365754422 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title dan tran commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' I am using rpm-maven-plugin and build-helper-maven-plugin to deploy .rpm and .ova Note: this used to work with initial work from Bing Shiao ( thanks Bing) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-26052) Fork without join
Title: Message Title Sam Van Oort commented on JENKINS-26052 Re: Fork without join Jesse Glick Can we close this one or is there still a tangible need for it? AFAICT it can be done more or less via invoking external jobs? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48930) Add new way to publish shared libraries
Title: Message Title Fabrice Pipart commented on JENKINS-48930 Re: Add new way to publish shared libraries Why not! Any recommended read to know how to start writing my first Jenkins plugin? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (TEST-109) [SKY-TV] Real Madrid vs Paris Saint Germain Live Stream Free UCL Online
Title: Message Title marie greer created an issue test / TEST-109 [SKY-TV] Real Madrid vs Paris Saint Germain Live Stream Free UCL Online Issue Type: Story Assignee: Oleg Nenashev Components: foo Created: 2018-02-14 21:33 Priority: Minor Reporter: marie greer The most highly-anticipated matchup of the Champions Leauge round of 16 begins on Wednesday when Real Madrid welcomes PSG to the Spanish capital for their first leg. Here's how you can watch the match online WATCH LIVE ONLINE FREE Real Madrid vs PSG: What TV channel, live stream online Real Madrid vs PSG: TV channel, live stream, team news and kick-off time for the Champions League 2018 tie. Real Madrid Paris SaintGermain live score, video stream and H2H ... Real Madrid Paris Saint-Germain live score (and video online live stream*) starts on 14.2.2018. at 19:45 UTC time at Santiago Bernabéu stadium, Madrid, Spain in UEFA Champions League, Knockout stage - Europe. Here on SofaScore livescore you can find all Real Madrid vs Paris Saint-Germain previous results sorted ... Real Madrid vs PSG live stream: Watch online, TV channel, time How to watch Real Madrid vs. PSG in the first leg of the Champions League round of 16 on Wednesday, February 14. Real Madrid vs PSG Live Stream - TOTAL SPORTEK watch Live Streaming links of Every Real Madrid vs Juventus champions league final and pre-season friendly vs FC Barcelona, vs Manchester United & City. Real Madrid vs PSG LIVE STREAM: How to watch Champions League ... REAL MADRID host PSG in the Champions League tonight - here's how to keep up with all the action online and on TV. Real Madrid vs PSG LIVE: Stream details, Champions League team ... REAL MADRID and PSG go head-to-head in the first leg of the Champions League last 16 at the Bernabeu. Follow the action LIVE with Express Sport. Real Madrid vs PSG live stream - How to watch Champions League ...
[JIRA] (JENKINS-49557) initial admin password cannot contain special characters
Title: Message Title Radu Bosneag commented on JENKINS-49557 Re: initial admin password cannot contain special characters Indeed, I followed the setup wizard. Looking for a similar issue happening at installation time I didn't find anything similar that's why I reported it. Thanks for the quick reply! I think we can close this if it's already known... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48463) Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0
Title: Message Title Baptiste Mathus closed an issue as Fixed Fixed in 2.105 Jenkins / JENKINS-48463 Jenkins should create xml 1.1 output in order to support control characters that are illegal in xml 1.0 Change By: Baptiste Mathus Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-49522) [withCredentials] MissingPropertyException from shared library class
Title: Message Title
Ann Beeskau updated an issue
Jenkins / JENKINS-49522
[withCredentials] MissingPropertyException from shared library class
Change By:
Ann Beeskau
I am instantiating an object from within my *vars* (custom step (testCredentials)) shared library. I then execute a method (*getRequiredPackages*) on this instance that contains withCredentials step. A groovy.lang.MissingPropertyException is thrown on the withCredentials variable (see stack trace below)*vars/testCredentials.groovy*{code:java}#!/usr/bin/env groovyimport com.mycorp.deployment.classes.Sourcedef call(body) {def config = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = configbody()def sourceVersion = config.versiontimestamps {node() {try {stage('Test Credentials') {Source buildToolsSource = new Source(steps, sourceVersion)buildToolsSource.getRequiredPackages(steps)}} catch (e) {steps.sh "echo 'Error (${e}) occurred marking the build as failure.'"throw e} finally {steps.cleanWs()}}}}{code}Groovy class */src/com/mycorp/deployment/classes/Source.groovy*{code:java}#!/usr/bin/env groovypackage com.mycorp.deployment.classesimport org.jenkinsci.plugins.workflow.cps.DSLclass Source implements Serializable {String versionSource(DSL steps, version) {this.version = version}def getRequiredPackages(DSL steps) {steps.withCredentials([steps.string(credentialsId: 'git-oauth-token', variable: 'GIT_OAUTH_TOKEN')]) {steps.sh(returnStdout: false,script: "curl -L " + "-H 'Authorization: token ${GIT_OAUTH_TOKEN}' " + "https://api.github.com/repos/mycorp/myrepo/zipball/${this.version} " + "-o _packages/myrepo-${this.version}.zip " + "-vvv")}}}{code} I'm getting the following run-time exception:{quote}groovy.lang.MissingPropertyException: No such property: GIT_OAUTH_TOKEN for class: com.magento.deployment.classes.Source at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.getProperty(DefaultInvoker.java:34) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20){quote}Trying to access the variable via *env* ($\{env.GIT_OAUTH_TOKEN}) produces the following error:{quote}groovy.lang.MissingPropertyException: No such property: env for class: com.magento.deployment.classes.SourceNew at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458) at
[JIRA] (JENKINS-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title Vivek Pandey commented on JENKINS-48027 Re: Blue Ocean dashboard showing no Pipelines Looks like its an issue when '@' is there in branch name. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47978) Lightweight checkout not working for branches that contain forward slash '/'
Title: Message Title Vivek Pandey commented on JENKINS-47978 Re: Lightweight checkout not working for branches that contain forward slash '/' bjorn rohlen Ok, so to confirm Jenkinsfile is getting picked correctly when at its located at repository/branch root. If placed inside a subdirectory its not detected. I checked with github branch source as well, Jenkinsfile discovery doesn't get picked from subdirectory. Looks like this is consistent compared to github branch source. Stephen Connolly can you shade some light as whats expected behavior here? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47958) Closed branches clone again and try build
Title: Message Title Rinat Muhamedgaliev commented on JENKINS-47958 Re: Closed branches clone again and try build Dear Christian Ewald I downloaded source from your GitHub repository and builded it. It work fine! Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47958) Closed branches clone again and try build
Title: Message Title Christian Ewald commented on JENKINS-47958 Re: Closed branches clone again and try build As it looks like, it will take a bit longer to get a patch into the official release. So I decided to build my own patched version. It is based on V2.2.9 and works as expected. You may download it from my drive (No warranty, use at your own risk, no responsibility for data corruption/losses etc.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49564) HTML report is not publishing
Title: Message Title siva krishna jampani created an issue Jenkins / JENKINS-49564 HTML report is not publishing Issue Type: Bug Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2018-02-14 20:13 Priority: Minor Reporter: siva krishna jampani Hi , I am using maven fail safe plugin to test the scenarios. In my test one of the scenario getting failed. So build is failing. Then HTML Publish is not working and not able to see the report in main page. If all test cases are passed then report is publishing in main page. but it is not happening when one test case fails. Add Comment
[JIRA] (JENKINS-49563) Affects performance of master
Title: Message Title Paul Zabelin created an issue Jenkins / JENKINS-49563 Affects performance of master Issue Type: Bug Assignee: Steve Peters Components: flaky-test-handler-plugin Created: 2018-02-14 19:49 Priority: Blocker Reporter: Paul Zabelin We have been using this plugin for the build with 500 tests saving last 500 build results. This caused each build to accumulate ~100Mb xml files generated by this plugin. Viewing the job greatly affects performance of Jenkins master as it tries to read those large XML files over multiple previous builds. We had to disable this plugin unfortunately as it affects other jobs and Jenkins master. Add Comment
[JIRA] (JENKINS-49562) In a sequential pipeline sometimes the job is executed simultaneously in the master and in an agent
Title: Message Title Javier Raez created an issue Jenkins / JENKINS-49562 In a sequential pipeline sometimes the job is executed simultaneously in the master and in an agent Issue Type: Bug Assignee: Unassigned Attachments: JenkinsfileTest Components: workflow-cps-plugin Created: 2018-02-14 19:38 Environment: CloudBees Jenkins Enterprise 2.89.3.4-rolling workflow-aggregator:2.5 'Pipeline' workflow-api:2.24 (update available) 'Pipeline: API' workflow-basic-steps:2.6 'Pipeline: Basic Steps' workflow-cps:2.41 (update available) 'Pipeline: Groovy' workflow-cps-checkpoint:2.4 'CloudBees Pipeline: Groovy Checkpoint Plugin' workflow-cps-global-lib:2.9 'Pipeline: Shared Groovy Libraries' workflow-durable-task-step:2.17 (update available) 'Pipeline: Nodes and Processes' workflow-job:2.16 (update available) 'Pipeline: Job' workflow-multibranch:2.16 (update available) 'Pipeline: Multibranch' workflow-scm-step:2.6 'Pipeline: SCM Step' workflow-step-api:2.14 'Pipeline: Step API' workflow-support:2.16 (update available) 'Pipeline: Supporting APIs' Priority: Minor Reporter: Javier Raez I have created a test script "JenkinsfileTest" that use "agent none" as global configuration and a specific agent. The pipeline only has some checkouts, sleep, and a "sh echo 'hello'". No parallel execution or something similar. When you execute that script sometimes in the Build executor status appears that the job is executed in the master and in the agent at the same time. Unable to render embedded object: File (Screen Shot 2018-02-14 at 19.50.38.png?default=false) not found.
[JIRA] (JENKINS-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Code changed in jenkins User: Oleg Nenashev Path: core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/config_nl.properties http://jenkins-ci.org/commit/jenkins/59bfe03ebe70eafaeb057aa0a0c0184e2097a8c9 Log: Merge pull request #3286 from vStone/feature/JENKINS-49496-dutch-translation-security-fix JENKINS-49498: Fix poorly translated sign-up string (dutch) Compare: https://github.com/jenkinsci/jenkins/compare/09e1f8cd0ca1...59bfe03ebe70 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Code changed in jenkins User: Jan Vansteenkiste Path: core/src/main/resources/hudson/security/HudsonPrivateSecurityRealm/config_nl.properties http://jenkins-ci.org/commit/jenkins/01ed9c9389f92dd34ddde1505d3ca8399c0eeb47 Log: JENKINS-49496: Fix poorly translated sign-up string (dutch) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Oleg Nenashev edited a comment on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard A security process would be an overkill in this case IMHO, but it worth mentioning in the changelog && backporting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Oleg Nenashev commented on JENKINS-49498 Re: Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard A security process would be an overkill in this case IMHO, but it worth mentioning in the changelog Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49498) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49498 Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Change By: Oleg Nenashev Labels: lts-candidate security translation Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Oleg Nenashev commented on JENKINS-49520 Re: Log rotator: empty values decorated with 'Not a positive integer' May need backporting to 2.107 which is the current LTS candidate baseline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49387) "not an integer" error on ports that are not enabled
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49387 "not an integer" error on ports that are not enabled Change By: Oleg Nenashev Labels: lts-candidate regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49520) Log rotator: empty values decorated with 'Not a positive integer'
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49520 Log rotator: empty values decorated with 'Not a positive integer' Change By: Oleg Nenashev Labels: lts-candidate regression Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49387) "not an integer" error on ports that are not enabled
Title: Message Title Oleg Nenashev commented on JENKINS-49387 Re: "not an integer" error on ports that are not enabled May need backporting to 2.107 which is the current LTS candidate baseline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49559) Document: How to raise issues in FSSCM Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-49559 Re: Document: How to raise issues in FSSCM Plugin Yes, it would help. Ernst de Haan could you propose a pull request? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49559) Document: How to raise issues in FSSCM Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-49559 Document: How to raise issues in FSSCM Plugin Change By: Oleg Nenashev Labels: documentation newbie-friendly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49561) FSSCM Does Not Update File Modifiers
Title: Message Title Ernst de Haan created an issue Jenkins / JENKINS-49561 FSSCM Does Not Update File Modifiers Issue Type: Bug Assignee: Oleg Nenashev Components: filesystem_scm-plugin Created: 2018-02-14 18:35 Environment: Jenkins ver. 2.60.3 Filesystem SCM Plugin 2.0 Priority: Major Reporter: Ernst de Haan Steps to reproduce: Have a Jenkins job that uses the FSSCM plugin to copy from the file system into the workspace. Execute the job at least once. Change the modifiers on one of the files in the origin location, e.g. change the x (executable) bit from off to on (e.g. chmod +x filename) Re-execute the job. Expected result: The modifier bit changes also in the checked-out version of the respective file. Actual result: The modifier bit does not change.
[JIRA] (JENKINS-49560) FSSCM does not work with “checkout scm” on agent
Title: Message Title
Ernst de Haan created an issue
Jenkins / JENKINS-49560
FSSCM does not work with “checkout scm” on agent
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
filesystem_scm-plugin
Created:
2018-02-14 18:33
Environment:
Jenkins ver. 2.60.3 Filesystem SCM Plugin 2.0
Labels:
slave-agent
Priority:
Major
Reporter:
Ernst de Haan
Currently, it seems the FileSystem SCM plugin does not work in conjunction with the checkout scm command in a Pipeline script. Here's a simple test case:
Have a Jenkins agent (f.k.a. slave), and tag it agent.
Create a new Pipeline job and name it testjob, using the FSSCM plugin, and have this in the pipeline script (on the file system):
pipeline {
agent {
label: 'agent'
}
stages {
stage('checkout') {
steps {
dir('foobar') {
checkout scm
}
}
}
}
}
Expected result:
[JIRA] (JENKINS-49559) Document: How to raise issues in FSSCM Plugin
Title: Message Title Ernst de Haan created an issue Jenkins / JENKINS-49559 Document: How to raise issues in FSSCM Plugin Issue Type: Improvement Assignee: Oleg Nenashev Components: filesystem_scm-plugin Created: 2018-02-14 18:23 Labels: documentation Priority: Trivial Reporter: Ernst de Haan Request for improvement in documentation: Please document on the GitHub front page for the FSSCM Plugin how to raise issues. Seems like this may require adding a README.md file in the root of the repo, which then references the page: How to report an issue. Add Comment
[JIRA] (JENKINS-40518) Give the unzip step a parameter to suppress verbose output
Title: Message Title Brian Ray commented on JENKINS-40518 Re: Give the unzip step a parameter to suppress verbose output Thank you Matthew Brenner. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49165) Extracting a zip with many files produces a large amount of log output
Title: Message Title Brian Ray closed an issue as Duplicate Jenkins / JENKINS-49165 Extracting a zip with many files produces a large amount of log output Change By: Brian Ray Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-38998) Cannot trigger pipeline job
Title: Message Title Jeff G commented on JENKINS-38998 Re: Cannot trigger pipeline job (Currently running LTS 2.73.1) Pipeline jobs are definitely executable by the Parameterized Trigger Plugin. However, they show as "Unresolved" in the Job page. While that might be concerning to the Job homepage viewer, the only loss of functionality is being able to link to the job being triggered by the parent. This is contrary to the MultiJob plugin which DOES NOT drive Pipeline jobs, period. For the MultiJob plugin, it IS a loss of functionality. Also, if you use Folder / Job / Branch, you can list it as such... for example, the job to trigger could be OrgScanFoo/RepoBar/BranchBaz Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title Andrew Widdersheim commented on JENKINS-49558 Re: Run stages in separate Docker containers when top level agent declared Just to add to this some, it is possible to have each stage run in it's own container instance but requires setting agent on every stage which can become very verbose and not DRY. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Jesse Perez commented on JENKINS-49485
Re: jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
yes, and noticed from jenkins server if I try `curl 'https://api.github.com/?client_id=_secret=' it works so confirming I can communicate using the given client ID and secret. I really would appreciate some help resolving this. I cannot go the route of using SSH keys because I have dozens of repos in my guthub org and managing all the different SSH keys (one per repo) is not practical.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-49558) Run stages in separate Docker containers when top level agent declared
Title: Message Title
Andrew Widdersheim created an issue
Jenkins / JENKINS-49558
Run stages in separate Docker containers when top level agent declared
Issue Type:
New Feature
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-02-14 17:48
Priority:
Minor
Reporter:
Andrew Widdersheim
When specifying either docker or dockerfile as the top level agent this will run the entire pipeline and all of it's stages in the same container instance created at the beginning.
pipeline {
agent {
docker {
image 'python3.6'
}
}
/* These stages all run in the same python3.6 container
* created at the beginning of the pipeline.
*/
stages {
stage('Stage 1') {
steps {
sh 'echo foo'
}
}
stage('Stage 2') {
steps {
sh 'echo bar'
}
}
}
}
It would be nice if there were some setting to run each stage in it's own container instance.
pipeline {
agent {
docker {
image 'python3.6'
runPerStage true
}
}
/* These stages all create their own python3.6 container
* created at the beginning of each stage.
*/
stages {
stage('Stage 1') {
steps {
sh 'echo foo'
}
}
stage('Stage 2') {
steps {
sh 'echo bar'
}
}
}
}
[JIRA] (JENKINS-49557) initial admin password cannot contain special characters
Title: Message Title Nicolas De Loof commented on JENKINS-49557 Re: initial admin password cannot contain special characters Did you created this initial admin using the setup wizard ? If so this is a general Jenkins issue, unrelated to docker image packaging Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-44430) p4 authenticity of 'perforce:1666' can't be established
Title: Message Title Jay Spang commented on JENKINS-44430 Re: p4 authenticity of 'perforce:1666' can't be established We are running Jenkins on Windows Server 2012 R2. Nothing should be touching the .p4trust file, as far as I'm aware (although we have multiple jobs running concurrently, hence my hypothesis of a race condition or concurrency problem). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49047) SyncID and workspace same for all Global libraries
Title: Message Title Paul Allen resolved as Fixed Ready for release. Jenkins / JENKINS-49047 SyncID and workspace same for all Global libraries Change By: Paul Allen Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49047) SyncID and workspace same for all Global libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49047 Re: SyncID and workspace same for all Global libraries Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/scm/GlobalLibraryScmSource.java http://jenkins-ci.org/commit/p4-plugin/e687bf5c387ee70e8314278155390fdca4b0952c Log: Add Library path to client name for a unique SyncID. JENKINS-49047 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49047) SyncID and workspace same for all Global libraries
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49047 SyncID and workspace same for all Global libraries Change By: Paul Allen Labels: P4_B Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49394) Allow to specify visibility on addComment
Title: Message Title Naresh Rayapati commented on JENKINS-49394 Re: Allow to specify visibility on addComment Patrick Ruckstuhl +1, if you would like you open up a pull request that would be awesome. Otherwise I will look into it once I got some time. Thanks for reporting. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45764) Add upload and download attachment steps
Title: Message Title Naresh Rayapati commented on JENKINS-45764 Re: Add upload and download attachment steps PR: https://github.com/jenkinsci/jira-steps-plugin/pull/64 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45764) Add upload and download attachment steps
Title: Message Title Naresh Rayapati updated JENKINS-45764 Jenkins / JENKINS-45764 Add upload and download attachment steps Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48232) PCT fails against core 2.73+
Title: Message Title Francisco Fernández updated JENKINS-48232 Jenkins / JENKINS-48232 PCT fails against core 2.73+ Change By: Francisco Fernández Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49557) initial admin password cannot contain special characters
Title: Message Title Radu Bosneag created an issue Jenkins / JENKINS-49557 initial admin password cannot contain special characters Issue Type: Bug Assignee: Nicolas De Loof Attachments: jenkins error.png, jenkins error.png Components: docker Created: 2018-02-14 17:07 Environment: installed via docker as per docs guide Priority: Minor Reporter: Radu Bosneag After installation, after providing the secret admin password you are asked to create a first `admin` user. If you fill in a password with special characters you get an error page (screenshot attached). In the logs you get this: Caused by: java.lang.IllegalArgumentException: Not valid encoding '%h"' at org.eclipse.jetty.util.UrlEncoded.decodeHexByte(UrlEncoded.java:889) at org.eclipse.jetty.util.UrlEncoded.decodeUtf8To(UrlEncoded.java:522) at org.eclipse.jetty.util.UrlEncoded.decodeTo(UrlEncoded.java:577) at org.eclipse.jetty.server.Request.extractFormParameters(Request.java:522) at org.eclipse.jetty.server.Request.extractContentParameters(Request.java:454) at org.eclipse.jetty.server.Request.getParameters(Request.java:369) ... 95 more We should either: better escape characters
[JIRA] (JENKINS-48232) PCT fails against core 2.73+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48232 Re: PCT fails against core 2.73+ Code changed in jenkins User: Oleg Nenashev Path: Jenkinsfile pom.xml src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPublicKeyAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPublicKeyAuthenticatorTest.java http://jenkins-ci.org/commit/ssh-credentials-plugin/96dc45385428fd768acd605a489311cb5da4d27a Log: Merge pull request #31 from fcojfernandez/JENKINS-48232 JENKINS-48232 PCT fails against core 2.73+ Compare: https://github.com/jenkinsci/ssh-credentials-plugin/compare/55e3d318eedd...96dc45385428 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48232) PCT fails against core 2.73+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48232 Re: PCT fails against core 2.73+ Code changed in jenkins User: Francisco Javier Fernandez Gonzalez Path: pom.xml src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPublicKeyAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPublicKeyAuthenticatorTest.java http://jenkins-ci.org/commit/ssh-credentials-plugin/881987af286c9768b29f22c6cb28623227f16afe Log: JENKINS-48232 Upgrading test dependencies Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48232) PCT fails against core 2.73+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48232 Re: PCT fails against core 2.73+ Code changed in jenkins User: Francisco Javier Fernandez Gonzalez Path: src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/SSHAuthenticator.java http://jenkins-ci.org/commit/ssh-credentials-plugin/4f484196d01ddbf56255e786bf3b728f98478e76 Log: JENKINS-48232 fix findbugs and NullpointerException Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-48232) PCT fails against core 2.73+
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48232 Re: PCT fails against core 2.73+ Code changed in jenkins User: Francisco Javier Fernandez Gonzalez Path: Jenkinsfile pom.xml src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/SSHAuthenticator.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/JSchSSHPublicKeyAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPasswordAuthenticatorTest.java src/test/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/TrileadSSHPublicKeyAuthenticatorTest.java http://jenkins-ci.org/commit/ssh-credentials-plugin/b06d52385d10d9b498e1d306e8a3ce60b8082784 Log: JENKINS-48232 Use of reflection for sshd-core library Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49556) Git polling using workspace blocked until running build completes
Title: Message Title Mark Waite commented on JENKINS-49556 Re: Git polling using workspace blocked until running build completes There is no way to have polling proceed in a Freestyle job while a build is running. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-49556) Git polling using workspace blocked until running build completes
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-49556 Git polling using workspace blocked until running build completes Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-45764) Add upload and download attachment steps
Title: Message Title Naresh Rayapati started work on JENKINS-45764 Change By: Naresh Rayapati Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
