[JIRA] (JENKINS-47370) Unable to override global envs after update to 2.1.4
Title: Message Title Francisco Lozano commented on JENKINS-47370 Re: Unable to override global envs after update to 2.1.4 We're heavily affected by this issue and can't upgrade from 2.1.3 because of it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Andrew Gray edited a comment on JENKINS-33056 Re: Please add clean remote option [~slide_o_mix] Can this functionality please be published. It seems a long time since v1.19.1 was released. Is this plugin still being maintained? Thank you, Andrew github.com/agray Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Jie Shen started work on JENKINS-53650 Change By: Jie Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-53650 Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 Change By: Jie Shen Status: In Progress Resolved Resolution: Fixed Released As: 0.3.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Jie Shen commented on JENKINS-53650 Re: Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 New version 0.3.1 has been released. It may need some time to be available in the plugin manager. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Oleg Nenashev commented on JENKINS-50483 Re: AWS Device Farm plugin affected by JEP-200 I suggest creating a new defect. Maybe it was a parallel code mwrge, should be trivial to fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48504) Lightweight checkout fails when Pipeline JenkinsFile is in a subfolder
Title: Message Title Robert D commented on JENKINS-48504 Re: Lightweight checkout fails when Pipeline JenkinsFile is in a subfolder Robin Smith, I no longer see the lightweight checkout error with plugin version 2.2.11 (on Jenkins 2.107). The build's console output shows "Obtained subdir/Jenkinsfile from ", unsure if that is from BBSP or another plugin. Since we're no longer getting the lightweight error with the FileNotFoundException, and our atlassian-bitbucket.log is showing the correct "GET .../subdir/Jenkinsfile" request format, I can confirm this is fixed for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33056) Please add clean remote option
Title: Message Title Andrew Gray commented on JENKINS-33056 Re: Please add clean remote option Alex Earl Can this functionality please be published. It seems a long time since v1.19.1 was released. Is this plugin still being maintained? Thank you, Andrew Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Dustin Kerber commented on JENKINS-50483 Re: AWS Device Farm plugin affected by JEP-200 I should also note that this error is new when moving from the SNAPSHOT build you posted earlier, to 1.20. I believe the issue is the pull request to add pipeline support, which re-introduced the PrintStream into AWSDeviceFarmTestResultAction. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title
Dustin Kerber edited a comment on JENKINS-50483
Re: AWS Device Farm plugin affected by JEP-200
[~oleg_nenashev]I hate to report back in, but I'm trying to interact with the resulting AWSDeviceFarmTestResultAction via a Groovy post-build script, and I'm getting the serialization error. I'm unsure if this is strictly related, but it seems very similar. *EDIT*: I'm using aws-device-farm plugin version 1.20 Post-build script{noformat}def testResult = build.getAction(hudson.tasks.junit.TestResultAction.class);{noformat}Resulting Error:{noformat}ERROR: Step ‘Groovy Postbuild’ aborted due to exception: java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) 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 org.jenkinsci.plugins.awsdevicefarm.AWSDeviceFarmTestResultAction#log for class org.jenkinsci.plugins.awsdevicefarm.AWSDeviceFarmTestResultAction 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.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) 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.model.Actionable#actions for class hudson.model.FreeStyleBuild 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
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Shuji Kinoshita commented on JENKINS-53650 Re: Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 Thanks for your quick response, I got it! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Jie Shen commented on JENKINS-53650 Re: Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 Shuji Kinoshita sorry for you inconvenience, the new version of azure commons upgrades the azure sdk version, while ad plugin has not. So please downgrade azure commons version to 0.2.6 temporarily until I release a new ad plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53650 Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53650) Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7
Title: Message Title Shuji Kinoshita created an issue Jenkins / JENKINS-53650 Azure AD Plugin 0.3.0 does not work with Azure Commons v.0.2.7 Issue Type: Bug Assignee: Azure DevOps Attachments: azure-ad-plugin-error-20180918.png Components: azure-ad-plugin, azure-commons-plugin Created: 2018-09-19 02:11 Environment: Jenkins 2.138.1, azure-ad-plugin 0.3.0, azure-commons-plugin 0.2.7 Labels: plugin Priority: Major Reporter: Shuji Kinoshita azure-ad-plugin does not work with azure-commons-plugin 0.2.7 which is just released yesterday (show attachments). With 0.2.6 it can work. I'm not sure whether this is only our environment or not. The stack trace shows the relation to the following library. https://bitbucket.org/nimbusds/oauth-2.0-sdk-with-openid-connect-extensions/src/master
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title
S Nelson updated an issue
Jenkins / JENKINS-53649
Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Change By:
S Nelson
Summary:
Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in ENVIRONMENT an environment variable
Attachment:
EchoNotShowingSomeStrings.PNG
When a string is displayed in the BlueOcean UI from an "echo" step, the string "Print Message" is displayed IF the string being echoed contains a substring that matches the contents of any environment variable. Repro steps:Create a pipeline with this code:{noformat}pipeline {agent anystages {stage('test') {environment {THING = 'foobarbuzz'}steps {echo "blah"echo "foobarbuzz"echo "foobarZZZbuzz"echo "This is a $THING here"}}}}{noformat}Run the pipeline via BlueOcean Blue Ocean Observe that there are four step labels displayed in the BlueOcean Blue Ocean UI. (see attached screenshot) The first and third steps display the strings from "echo" as expected. But, the second and fourth steps display only "Print Message" and don't show the expected string. The user needs to click the step to expand it to see the string. I would expect that all strings from all echo statements should show up in the main Blue Ocean UI and would not require some to be manually expended.
Add Comment
[JIRA] (JENKINS-50483) AWS Device Farm plugin affected by JEP-200
Title: Message Title Dustin Kerber commented on JENKINS-50483 Re: AWS Device Farm plugin affected by JEP-200 Oleg Nenashev I hate to report back in, but I'm trying to interact with the resulting AWSDeviceFarmTestResultAction via a Groovy post-build script, and I'm getting the serialization error. I'm unsure if this is strictly related, but it seems very similar. Post-build script def testResult = build.getAction(hudson.tasks.junit.TestResultAction.class); Resulting Error: ERROR: Step ‘Groovy Postbuild’ aborted due to exception: java.lang.UnsupportedOperationException: Refusing to marshal java.io.PrintStream for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) 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 org.jenkinsci.plugins.awsdevicefarm.AWSDeviceFarmTestResultAction#log for class org.jenkinsci.plugins.awsdevicefarm.AWSDeviceFarmTestResultAction 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.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) 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.model.Actionable#actions for class hudson.model.FreeStyleBuild
[JIRA] (JENKINS-53587) Sequential parallel stages show green while still running
Title: Message Title Olivier Lamy updated JENKINS-53587 Jenkins / JENKINS-53587 Sequential parallel stages show green while still running Change By: Olivier Lamy Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53587) Sequential parallel stages show green while still running
Title: Message Title Olivier Lamy resolved as Fixed fixed with JENKINS-53311 Jenkins / JENKINS-53587 Sequential parallel stages show green while still running Change By: Olivier Lamy Status: Open Resolved Assignee: Olivier Lamy Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53555) Only one parallel steps displayed like in progress on UI
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-53555 Only one parallel steps displayed like in progress on UI Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53555) Only one parallel steps displayed like in progress on UI
Title: Message Title Olivier Lamy resolved as Fixed fixed with JENKINS-53311 Jenkins / JENKINS-53555 Only one parallel steps displayed like in progress on UI Change By: Olivier Lamy Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53555) Only one parallel steps displayed like in progress on UI
Title: Message Title Olivier Lamy updated JENKINS-53555 Jenkins / JENKINS-53555 Only one parallel steps displayed like in progress on UI Change By: Olivier Lamy Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Olivier Lamy updated JENKINS-53311 Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Olivier Lamy Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Olivier Lamy started work on JENKINS-53311 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure
Title: Message Title Federico Naum commented on JENKINS-49707 Re: Auto retry for elastic agents after channel closure Agree with Jon B regarding that this is a critical issue. We have one of the teams switching to TeamCity . In the time being, I'm trying to attack the problem using the new kafka agent plugin. In my tests, it seems quite stable, and I'm not encountering the frequent channel disconnection when running parallel jobs, so I would be deploying that to production this week. I agree as well that the retry in a new node that satisfies the labels can be a different issue, but I would also say that should be top priority. PS: We are also not using AWS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Ben Fiedler edited a comment on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost Well this is embarrassing. I was sure I had originally tried smtpServer (the name that actually shows up extended descriptor) in jcasc unsuccessfully (getting a generic null error or something similar), but trying again with it just now and it works with no problem.Maybe I accidentally tried it with the mailer plugin , or coincidentally had some other problem with my yaml at the time .I will mark this is closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Ben Fiedler updated JENKINS-53486 User error Jenkins / JENKINS-53486 email-ext fails when CasC attempts to set smtpHost Change By: Ben Fiedler Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Ben Fiedler commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost Well this is embarrassing. I was sure I had originally tried smtpServer (the name that actually shows up extended descriptor) in jcasc unsuccessfully (getting a generic null error or something similar), but trying again with it just now and it works with no problem. Maybe I accidentally tried it with the mailer plugin. I will mark this is closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53487) Periodic Update Occurs Too Frequently
Title: Message Title jonathan bridgstock commented on JENKINS-53487 Re: Periodic Update Occurs Too Frequently Good morning, Michael is on leave, so he asked me to keep an eye on this and provide any further information. I have used the Validate IdP Metadata URL button, which was successful. We I then saved the changes and checked the logs. Still getting the same issue: Sep 18, 2018 11:05:11 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:05:11 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 295 ms Sep 18, 2018 11:05:21 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:05:21 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:05:21 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 318 ms Sep 18, 2018 11:05:31 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:05:31 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:05:32 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 555 ms Sep 18, 2018 11:05:41 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:05:41 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:05:41 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 319 ms Sep 18, 2018 11:05:51 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:05:51 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:05:51 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 329 ms Sep 18, 2018 11:06:01 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:06:01 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:06:01 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 279 ms Sep 18, 2018 11:06:11 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:06:11 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:06:11 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 298 ms Sep 18, 2018 11:06:21 PM INFO hudson.model.AsyncAperiodicWork$1 runStarted Update IdP Metadata from URL PeriodicWork Sep 18, 2018 11:06:21 PM INFO org.opensaml.core.config.InitializationService initializeInitializing OpenSAML using the Java Services API Sep 18, 2018 11:06:21 PM INFO hudson.model.AsyncAperiodicWork$1 runFinished Update IdP Metadata from URL PeriodicWork. 293 ms I can also confirm that the refresh period is set to 60 minutes. cheers, Jon.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Alex Earl commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost Can you try using smtpServer instead? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Ben Fiedler edited a comment on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost You are probably right; these are the fields in the extendedemailpublisher descriptor I have successfully configured using jcasc:charset, defaultBody, defaultContentType, defaultSubject, defaultReplyTo, smtpPort, and watchingEnabled.Oddly the smtpHost is the only value that throws an error. For now, as a workaround I am making a groovyscript and sticking it into jenkins init.groovy.d/ which loads the descriptor and then directly modifies the smtpHost member. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Ben Fiedler commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost You are probably right; these are the fields in the extendedemailpublisher descriptor I have successfully configured using jcasc: charset, defaultBody, defaultContentType, defaultSubject, defaultReplyTo, smtpPort, and watchingEnabled. Oddly the smtpHost is the only value that throws an error. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26640) svn: E175002: handshake alert: unrecognized_name
Title: Message Title Rares Vernica commented on JENKINS-26640 Re: svn: E175002: handshake alert: unrecognized_name Setting -Djsse.enableSNIExtension=false fixes the Subversion checkout error, but introduces a new error when initally starting Jenkins. The new error is: ci_1 | javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No subject alternative DNS name matching updates.jenkins.io found. ci_1 | at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) ci_1 | at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1964) ci_1 | at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:328) ci_1 | at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:322) ci_1 | at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1614) ci_1 | at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216) ci_1 | at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1052) ci_1 | at sun.security.ssl.Handshaker.process_record(Handshaker.java:987) ci_1 | at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1072) ci_1 | at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) ci_1 | at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) ci_1 | at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) ci_1 | at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559) ci_1 | at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) ci_1 | at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) ci_1 | at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) ci_1 | at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) ci_1 | at hudson.model.DownloadService.loadJSON(DownloadService.java:167) ci_1 | at hudson.model.UpdateSite.updateDirectlyNow(UpdateSite.java:185) ci_1 | at hudson.model.UpdateCenter.updateDefaultSite(UpdateCenter.java:2185) ci_1 | at jenkins.install.SetupWizard.init(SetupWizard.java:179) ci_1 | at jenkins.install.InstallState$InitialSecuritySetup.initializeState(InstallState.java:164) ci_1 | at jenkins.model.Jenkins.setInstallState(Jenkins.java:1039) ci_1 | at jenkins.install.InstallUtil.proceedToNextStateFrom(InstallUtil.java:97) ci_1 | at jenkins.install.InstallState$Unknown.initializeState(InstallState.java:82) ci_1 | at jenkins.model.Jenkins$17.run(Jenkins.java:3201) ci_1 | at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) ci_1 | at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) ci_1 | at jenkins.model.Jenkins$5.runTask(Jenkins.java:1068) ci_1 | at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) ci_1 | at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) ci_1 | at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ci_1 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ci_1 | at java.lang.Thread.run(Thread.java:748) ci_1 | Caused by: java.security.cert.CertificateException: No subject alternative DNS name matching updates.jenkins.io found. ci_1 | at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:214) ci_1 | at sun.security.util.HostnameChecker.match(HostnameChecker.java:96) ci_1 | at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455) ci_1
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Peter Žeby edited a comment on JENKINS-49183 Re: Retry in Declarative options passes stage but causes false fail in pipeline Have same problem. Running stage 3 times with retry option, but it always keeps FAILURE status at the end, even if second/third time the build (stage) is successful. I wanted to reset `currentBuild.result` as workaround on start of stage, but it can not be changed from FAILURE to SUCCESS based on my tests, only from SUCCESS to FAILURE. Are Is there any solution? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in ENVIRONMENT
Title: Message Title
S Nelson created an issue
Jenkins / JENKINS-53649
Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in ENVIRONMENT
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-09-18 22:20
Environment:
Jenkins: 2.138.1 BlueOcean plugin: 1.8.2 A clean install on Windows 7 with just a standard set of plugins Reproed with Chrome on Windows and Firefox on a Linux desktop
Labels:
ui blueocean-ui
Priority:
Minor
Reporter:
S Nelson
When a string is displayed in the BlueOcean UI from an "echo" step, the string "Print Message" is displayed IF the string being echoed contains a substring that matches the contents of any environment variable. Repro steps: Create a pipeline with this code:
pipeline {
agent any
stages {
stage('test') {
environment {
THING = 'foobarbuzz'
}
steps {
echo "blah"
echo "foobarbuzz"
echo "foobarZZZbuzz"
echo "This is a $THING here"
}
}
}
}
Run the pipeline via BlueOcean Observe that there are four step labels displayed in the BlueOcean UI. The first and third steps display the strings as expected. But, the second
[JIRA] (JENKINS-49119) Support suppression of SSH server inactivity timeouts
Title: Message Title Dmitriy Korobskiy commented on JENKINS-49119 Re: Support suppression of SSH server inactivity timeouts I guess. SSH clients send server-alive messages and can suppress automatic inactivity termination if configured so. My SSH clients are configured correspondingly and it does work with our servers, but our Jenkins jobs are out of luck. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49119) Support suppression of SSH server inactivity timeouts
Title: Message Title Alex Earl commented on JENKINS-49119 Re: Support suppression of SSH server inactivity timeouts So, would this be something like a keep alive? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53648) Jenkins stops executing timed and automatic jobs
Title: Message Title Richard Veitch updated an issue Jenkins / JENKINS-53648 Jenkins stops executing timed and automatic jobs Change By: Richard Veitch Labels: ScheduleBuild bitbucket Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52997) cifsPublisher plugin not copying right files using wildcards
Title: Message Title Alex Earl closed an issue as Not A Defect The patternSeparator was empty. Jenkins / JENKINS-52997 cifsPublisher plugin not copying right files using wildcards Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53648) Jenkins stops executing timed and automatic jobs
Title: Message Title Richard Veitch created an issue Jenkins / JENKINS-53648 Jenkins stops executing timed and automatic jobs Issue Type: Bug Assignee: Unassigned Attachments: badThreadDump Components: core Created: 2018-09-18 21:59 Environment: Jenkins ver. 2.138.1 Priority: Minor Reporter: Richard Veitch I have a Jenkins server running on an EC2 instance with a number of workers running in containers in our data center. Most of my jobs are either triggered on a timed schedule or are triggered by the Bitbucket pr runner plugin. This system has been running fine for months but recently I've been seeing an issue where the timed jobs and Bitbucket pr jobs have stopped being scheduled. During this time I can still launch jobs manually. This happens 2 or 3 times a day and I don't see any errors in the jekins logs. Restarting Jenkins will fix it for a few hours but it always returns. The jenkins master has 16GB of ram and I've checked that it is never close to using it all. Generally it uses 2-3G. I've attached a threadDump taken when this was happening. I'm not sure where else to look to debug this so I'd appreciate any advice on what to look for. Thanks
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Alex Earl commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost There is a lot of custom JSON reading in the configure method of the descriptor, so I think there are a lot of changes needed in the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53647) Xcode 10 Support for iOS Build Teams
Title: Message Title Dalton Robertson created an issue Jenkins / JENKINS-53647 Xcode 10 Support for iOS Build Teams Issue Type: New Feature Assignee: Unassigned Components: xcode-plugin Created: 2018-09-18 21:51 Priority: Minor Reporter: Dalton Robertson As a user, I would like to see Xcode plugin support through LTS for Xcode development. Currently Xcode 10 is not supported and I would like to help out where I can to improve the plugin and the overall experience for iOS build teams. Add Comment
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
[~henryborchers], complexity of your pipeline is completely irrelevant. Just to draw a parallel, the fact that you're creating complex Enterprise product does not justify you to put all it's code in a single file, or even in a single method, does it?Parts of your pipeline has to be a reusable functions in the shared library, so your actual jenkins file should consist only simple statements, something like{code}doThis()if (itsTrue()) { doThat()}{code}That applies only for scripted pipelines, of course. Accordingly to https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines it sounds like declarative pipelines even more limited that than I thought, so I'm happy I don't use 'em.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Dmytro Kryvenko commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Just a quick searching in google reveal there is actually an open source project doing something good enough to demonstrate what I mean: https://github.com/fabric8io/fabric8-pipeline-library https://github.com/fabric8io/fabric8-jenkinsfile-library Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53636) not first time build project，but tip"ERROR: Invalid project setup: Connection reset ERROR: Processing failed due to a bug in the code"
Title: Message Title Owen Wood assigned an issue to Unassigned Jenkins / JENKINS-53636 not first time build project，but tip"ERROR: Invalid project setup: Connection reset ERROR: Processing failed due to a bug in the code" Change By: Owen Wood Assignee: Owen Wood Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Jeff Thompson commented on JENKINS-53569 Re: Remoting deadlock observed after upgrading to 3.26 No, it doesn't look like that Docker issue has anything to do with it. I got a little time to take a look at this and yes, it's a regular old Java threading deadlock. I'm not yet certain of the sequence that is causing this deadlock, or isn't causing it in other cases. I have an idea for a change, which may solve the problem and doesn't seem to cause any other problems that are covered by the automated tests. Unfortunately as usual they don't cover threading, locking, and deadlocking very well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Sam Van Oort commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Nico Schmoigl Ack, we'll wait untuil you have a chance to grab the thread dump – otherwise it'll depend on if this gets fixed by another bugfix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Henry Borchers, complexity of your pipeline is completely irrelevant. Just to draw a parallel, the fact that you're creating complex Enterprise product does not justify you to put all it's code in a single file, or even in a single method, does it? Parts of your pipeline has to be a reusable functions in the shared library, so your actual jenkins file should consist only simple statements, something like
doThis()
if (itsTrue()) {
doThat()
}
That applies only for scripted pipelines, of course. Accordingly to https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines it sounds like declarative pipelines even more limited that I thought, so I'm happy I don't use 'em.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
I finally had a chance to take a look at this.[~iceiceice]: You are using println inside of an {{@NonCPS}} method. It might seem like this should be ok, but [behind the scenes|https://github.com/jenkinsci/workflow-cps-plugin/blob/0e4c25f8d7b84470aa523491e29933db3b3df588/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsScript.java#L221] {{println}} ends up calling the {{echo}} step, which means that you are executing Pipeline Steps inside of an {{@NonCPS}} method, which should not be done even though it may appear to work correctly in some cases.[~tobybro] If you have a minimal pipeline that can reproduce the issue, or a scenario in which you can reproduce the problem consistently it would be very helpful if you could post the Pipeline script and the build folder of one of the builds that failed with the exception here. Otherwise, it would be great to see your actual pipeline that is hitting the error so we can check for any similarities with Alexey's or Rick's Pipelines that might give us an idea of what is happening. The only way EDIT: My original hypothesis was misleading and incorrect, so I have been able to reproduce anything remotely similar to 've edited it based on new information.Notably, the exceptions seen here has been to create exception being thrown in all these cases comes from {{ @NonCPS AbstractQueuedSynchronizer#acquireSharedInterruptibly }} methods that take more than 5 minutes to complete Line 1302 , which causes [CpsThread#runNextChunk to checks the interrupt status before the thread |https://github tries to acquire the lock . com/jenkinsci/workflow-cps-plugin/blob/54d2f4fe8069fde53789bfe21229ce8e545300bb/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThread.java#L170]. AIUI This means that may very well be the code that is interrupting thread was actually interrupted before the step started executing, and {{ pp.get}} [here|https://github.com/jenkinsci/workflow-cps-plugin/blob/54d2f4fe8069fde53789bfe21229ce8e545300bb/src/main/java/org/jenkinsci/plugins/workflow/cps/ CpsStepContext .java # L248], but even so, I am not sure _why_ the CpsFlowExecution's program promise would be taking so long to load. My only theory is that in {{CpsThread# getThreadGroupSynchronously}} the local variable {{pp}} is set just happens to be the nonnull value first piece of {{flowExecution code to check the interrupted flag and throw an exception . programPromise}}, but then maybe something else changes I got access to the value flow nodes of {{flowExecution.programPromise}} another user's pipeline hitting the same exception , but we are still waiting on and noticed that the stale program promise {{pp}} which does not complete for whatever reason duration between the last successfully executed node and eventually it times out. If the start of the step that is threw the issue exception was just over 5 minutes , we might be able which leads me to fix this issue with a patch like believe that the following to {{ code that is doing the interruption is the [Timeout in CpsThread# getThreadGroupSynchronously}} runNextChunk|https : {noformat}diff --git a / src / main/java/org/jenkinsci/plugins/workflow/cps/CpsStepContext github . java b com / src/main/java/org/ jenkinsci/ plugins/ workflow / - cps /CpsStepContext.javaindex 2b90bec1..6f0a45cb 100644 - -- a plugin / src blob / main 54d2f4fe8069fde53789bfe21229ce8e545300bb / java/org/jenkinsci/plugins/workflow/cps/CpsStepContext.java+++ b/ src/main/java/org/jenkinsci/plugins/workflow/cps/
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Dmytro Kryvenko, My pipeline is long because it contains more than just unit testing. It's a complete DevOps pipeline with optional stages depending on the situation. I have sequential stages, parallel stages and most of these have a post section that cleans up or depends on the success or failure of the stage. It's very declarative and pretty easy to reason with so there really shouldn't be a reason to refactored the code. Jenkins has become very very powerful tool with the Pipeline DSL with a lot of very useful features. It's a shame when I when I can't use a feature because my pipeline contains too many lines already. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49183) Retry in Declarative options passes stage but causes false fail in pipeline
Title: Message Title Christopher Kush (Monotype) commented on JENKINS-49183 Re: Retry in Declarative options passes stage but causes false fail in pipeline Yeah, irritating. Whole point of retry is that one of my stages is not reliable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53645) Move SFTPClient class form SSH Slaves plugin
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53645 Jenkins / JENKINS-53645 Move SFTPClient class form SSH Slaves plugin Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53645) Move SFTPClient class form SSH Slaves plugin
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-53645 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41519) Post stages should have well defined order
Title: Message Title Stefan Thurnherr commented on JENKINS-41519 Re: Post stages should have well defined order Fernando Nasser Have you read the earlier comments in this jira issue? You'll find the jira issue for the 'cleanup' addition in Andrew's comment Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Nico Schmoigl commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Please could you attach a thread dump from Jenkins? ... will try to when the server goes down next time. It might become a little tricky, as this is a productive instance and if it is down, pressure is often high to get it back up running again as soon as possible. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53646) Agent command isn't in sync with remoting agent options
Title: Message Title Jeremy Bouse created an issue Jenkins / JENKINS-53646 Agent command isn't in sync with remoting agent options Issue Type: Improvement Assignee: Jan Roehrich Components: amazon-ecs-plugin Created: 2018-09-18 20:00 Environment: OS: ECS-optimized AMI 2018.03.f Jenkins : v2.138.1 ECS plugin v1.16 Priority: Minor Reporter: Jeremy Bouse Current versions of Jenkins remoting (3.x) do not appear to support the -url and -tunnel options any more and instead favor using the -jnlpUrl option with the tunnel being added to the JNLPLauncher. Suggest updating the command being used in the ECS Task to be more in line with current versions of Jenkins: -jnlpUrl /computer//slave-agent.jnlp -secret -workDir instead of: -url -tunnel Add Comment
[JIRA] (JENKINS-41519) Post stages should have well defined order
Title: Message Title Fernando Nasser commented on JENKINS-41519 Re: Post stages should have well defined order Caught by surprise with always not being the last one (it is sort of equivalent to the java finally which runs last, for the same cleanup reasons brought up in several JIRAs). But cleanup would work around that (/me still prefers always being last). Do we have a JIRA for the 'cleanup' addition yet? Could not find with JIRA search as the word is too common. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12699) Temp upload files from file param not removed after transferred to slave
Title: Message Title Brian Hinz commented on JENKINS-12699 Re: Temp upload files from file param not removed after transferred to slave This is still an issue in 2.121.3, and there is no viable workaround that I can find. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Olivier Lamy Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers commented on JENKINS-53311 Re: [Blue Ocean] Sequential stages appear to be completed but are still executing sorry, i accidentally clicked assign to me. didn't mean to and I'm not sure how to revert to the original setting Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Henry Borchers Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Olivier Lamy Henry Borchers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Henry Borchers assigned an issue to Unassigned Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Henry Borchers Assignee: Henry Borchers Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53644) Is it possible to configure the color of the job (success or not) depending on the error number of one parser
Title: Message Title Ulli Hafner updated JENKINS-53644 This is already possible, yes. Are you using Pipelines? Then you simply need to add a step for each parser. Jenkins / JENKINS-53644 Is it possible to configure the color of the job (success or not) depending on the error number of one parser Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser No, the file column is hard coded. All other columns navigate into the details of the selected element. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53610) How to use Warnings plugin 5.00 Public Beta in declarative script?
Title: Message Title Ulli Hafner commented on JENKINS-53610 Re: How to use Warnings plugin 5.00 Public Beta in declarative script? Do you mean for a freestyle build? All parameters for the pipeline are shown in the documentation section right above the whole example. And you can create a full snippet using the declarative snippet generator. Or what part are you missing? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36776) Support Windows Server Containers
Title: Message Title Henry Borchers commented on JENKINS-36776 Re: Support Windows Server Containers I'm super excited to see a pull request that's has passed all the required check. I'm wondering what's holding it back from being merged. Using Windows containers as Jenkins Agents would be very very useful to me for testing in isolation and caching of dependencies and tools. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53625) Provisioning an advanced linux image with Zulu JDK never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image with Zulu JDK never continues after init.sh
I've also been able to reproduce this without Zulu, simply by having any process that hasn't exited. Steps to reproduce (I did this with a CentOS 7.5 image)*init script:*{code:java}sleep 1200{code}Wait until the init script is running and kill the shell script (process "sh init.sh", not the sleep).Jenkins (executeRemoteCommand) will hang until sleep exits (or is killed manually).Most likely, any backgrounded process would also produce this behavior. However, in my earlier Zulu-related hangs, Jenkins code did not resume even after killing the instance in the Azure portal, so this could be different.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53625) Provisioning an advanced linux image with Zulu JDK never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image with Zulu JDK never continues after init.sh
I've also been able to reproduce this without Zulu, simply by having any process that hasn't exited. Steps to reproduce (I did this with a CentOS 7.5 image)*init script:*{code:java}sleep 1200{code}Wait until the init script is running and kill the shell script (process "sh init.sh", not the sleep).Jenkins (executeRemoteCommand) will hang until sleep exits (or is killed manually). Most likely, any backgrounded process would also produce this behavior.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53625) Provisioning an advanced linux image with Zulu JDK never continues after init.sh
Title: Message Title Alexander Komarov commented on JENKINS-53625 Re: Provisioning an advanced linux image with Zulu JDK never continues after init.sh I've also been able to reproduce this without Zulu, simply by having any process that hasn't exited. Steps to reproduce (I did this with a CentOS 7.5 image) init script: sleep 1200 Wait until the init script is running and kill the shell script (process "sh init.sh", not the sleep). Jenkins (executeRemoteCommand) will hang until sleep exits (or is killed manually). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47603) SCP error response code should be printed in the logs
Title: Message Title Ivan Fernandez Calvo updated JENKINS-47603 Jenkins / JENKINS-47603 SCP error response code should be printed in the logs Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53645) Move SFTPClient class form SSH Slaves plugin
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-53645 Move SFTPClient class form SSH Slaves plugin Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: trilead-api-plugin Created: 2018-09-18 16:36 Priority: Minor Reporter: Ivan Fernandez Calvo Move SFTPClient from SSH Slaves plugin to the trilead ssh2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title KaiHsiang Chang resolved as Fixed PR 47 resolved Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: KaiHsiang Chang Status: Reopened Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/releases/tag/Parameterized-Remote-Trigger-3.0.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53644) Is it possible to configure the color of the job (success or not) depending on the error number of one parser
Title: Message Title iostrym created an issue Jenkins / JENKINS-53644 Is it possible to configure the color of the job (success or not) depending on the error number of one parser Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-09-18 16:10 Environment: jenkins 2.121.2 + warning plug-in version 5.X (beta) Priority: Minor Reporter: iostrym currently it is possible to configure the success or not of a job depending on the total error number parsed by all parsers. Is it possible to do the same but using only one parser. Because it is possible that some other parser generates error/warning that should not impact the status of the job. for instance rulecheck. whereas the main process has a separate parser where error are very important and we want only these error to mark the job as failed. Add Comment
[JIRA] (JENKINS-53625) Provisioning an advanced linux image with Zulu JDK never continues after init.sh
Title: Message Title
Alexander Komarov edited a comment on JENKINS-53625
Re: Provisioning an advanced linux image with Zulu JDK never continues after init.sh
You may find this useful: interesting. (and this is a *WORKAROUND*) This init script causes Jenkins to *hang* (although JDK gets installed and the script completes):{noformat}wget https://cdn.azul.com/zulu/bin/zulu8.31.0.1-jdk8.0.181-linux_amd64.deb -O zulu8.debsudo apt-get install -y ./zulu8.deb{noformat}But this one results in a *correctly* *provisioned* slave:{noformat}sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0xB1998361219BD9C9sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable main'sudo apt-get install -y zulu-8{noformat} Even though I'm installing the same package, _how I'm installing_ it matters somehow.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53625) Provisioning an advanced linux image with Zulu JDK never continues after init.sh
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-53625 Provisioning an advanced linux image with Zulu JDK never continues after init.sh Change By: Alexander Komarov Summary: Provisioning an advanced linux image with Zulu JDK never continues after init.sh Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53625) Provisioning an advanced linux image never continues after init.sh
Title: Message Title Alexander Komarov commented on JENKINS-53625 Re: Provisioning an advanced linux image never continues after init.sh You may find this useful: This init script causes Jenkins to hang (although JDK gets installed and the script completes): wget https://cdn.azul.com/zulu/bin/zulu8.31.0.1-jdk8.0.181-linux_amd64.deb -O zulu8.deb sudo apt-get install -y ./zulu8.deb But this one results in a correctly provisioned slave: sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 0xB1998361219BD9C9 sudo apt-add-repository 'deb http://repos.azulsystems.com/ubuntu stable main' sudo apt-get install -y zulu-8 Even though I'm installing the same package, how I'm installing it matters somehow. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53193) Provide currentBuild.isRestartedRun global variable
Title: Message Title Fernando Nasser commented on JENKINS-53193 Re: Provide currentBuild.isRestartedRun global variable Maybe this deserves a separate JIRA, but it is certainly related: In a longer pipeline it is possible that one needs to check if a step has been restarted more than one time. Lets say steps 3 and 7 must behave different when they are restarted. If we restart the step 3 the isRestartedRun() will be true and trick step 7 in believing it has been restarted (when it was not, 3 was the one restarted). We need a way to reset this, perhaps after the first step after the restart is completed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49947) unclear usage of input step in declarative pipeline
Title: Message Title Fernando Nasser commented on JENKINS-49947 Re: unclear usage of input step in declarative pipeline Perhaps add a 'when' configuration option to the 'input' directive? This way we could skip the input for certain cases (like for Liam's prod stage) or even have a different input for each case by playing with the right 'when' conditions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53643) Job with Global Build Stats output
Title: Message Title Got viserion created an issue Jenkins / JENKINS-53643 Job with Global Build Stats output Issue Type: Bug Assignee: David Krischke Components: global-build-stats-plugin Created: 2018-09-18 15:38 Labels: plugin jenkins globalbuildstats Priority: Minor Reporter: Got viserion Hi, I would like to build a job and run a report using this plugin and have the report (or the link) emailed to a set of recipients. I want this in a weekly interval. Please suggest. Add Comment
[JIRA] (JENKINS-47129) Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore
Title: Message Title chanti vlad edited a comment on JENKINS-47129 Re: Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore Hi [~abayer] , [~roel0] and [~abhishekmukherg],i am facing the exact same problem, where i was hoping to have the following set up: * git repo A stores all generic Jenkins pipelines, which need specific env variables to be parameterized * git repo B has a Jenkinsfile that gets executed pre merge on changes in the repo B. This Jenkinsfile would do some things, and then clone the repo A, set the env variable properly, load a Jenkinsfile from A and run it as "sub pipeline".Do i understand you correctly that the best way to do this is to have the generic part in repo A as scripted and not delcarative declarative ?If yes, why this limitation? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53257) evergreen-client should delete plugins included in the deletes section
Title: Message Title R. Tyler Croy resolved as Fixed This has shipped and works a treat! Jenkins / JENKINS-53257 evergreen-client should delete plugins included in the deletes section Change By: R. Tyler Croy Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47129) Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore
Title: Message Title chanti vlad commented on JENKINS-47129 Re: Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore Hi Andrew Bayer , roel postelmans and Abhishek Mukherjee, i am facing the exact same problem, where i was hoping to have the following set up: git repo A stores all generic Jenkins pipelines, which need specific env variables to be parameterized git repo B has a Jenkinsfile that gets executed pre merge on changes in the repo B. This Jenkinsfile would do some things, and then clone the repo A, set the env variable properly, load a Jenkinsfile from A and run it as "sub pipeline". Do i understand you correctly that the best way to do this is to have the generic part in repo A as scripted and not delcarative ? If yes, why this limitation? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49851) Highlight "essential" (i.e. locked) plugins in the Update Center
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-49851 Highlight "essential" (i.e. locked) plugins in the Update Center Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49851) Highlight "essential" (i.e. locked) plugins in the Update Center
Title: Message Title R. Tyler Croy resolved as Won't Do The route we have instead gone with is to prevent users from adding arbitrary plugins which will destabilize their environment Jenkins / JENKINS-49851 Highlight "essential" (i.e. locked) plugins in the Update Center Change By: R. Tyler Croy Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49885) Embed a /doc site
Title: Message Title R. Tyler Croy resolved as Fixed The basics are there Jenkins / JENKINS-49885 Embed a /doc site Change By: R. Tyler Croy Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49885) Embed a /doc site
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-49885 Embed a /doc site Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Josiah Niedrauer commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Sam Van Oort I have not been able to reproduce this after weeks of heavy use. It may have been adding swap that fixed it, or it may have been that a new version was pushed to the lts tag. I am not sure. In either case, it is unlikely that I will be able to get you a thread dump. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
800 lines of code in one file sounds bad in any language. It definitely needs a refactoring and shared libraries.Just to be clear - in my case above I experienced that issue while already having my libraries, and it was due the way I designed these libraries (they treat Jenkinsfile concept as some sort of JIT, they basically doing some calculations based on the input and spits out resulting long Jenkinsfile that I then eval() ed). I solved my case by splitting what I eval() into chunks exchanging the data through the context singleton object in my library (surprisingly singleton instances were not per Jenkins master JVM but per library instance, i.e. per individual build). So technically my case wasn't even related to Jenkins at all. I was sending too long string into eval() method and it was legitimately (accordingly to JVM) giving me a finger. Just to give an example, my chunks would look like:{code:java}getContext('stages')['Test Stage'] = {echo 'hi'}{code}{code:java}getContext('stages')['Second Test Stage'] = { echo 'hi again'} {code}{code:java} getContext('stages')['Second Test Stage'] = { echo 'hi again'} {code}{code:java} timestamps {ansiColor("xterm") {stage('Test Stage', getContext('stages')['Test Stage'])stage('Second Test Stage', getContext('stages')['Second Test Stage'])}}{code}Given that I think this issue may be closed now.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
800 lines of code in one file sounds bad in any language. It definitely needs a refactoring and shared libraries.Just to be clear - in my case above I experienced that issue while already having my libraries, and it was due the way I designed these libraries (they treat Jenkinsfile concept as some sort of JIT, they basically doing some calculations based on the input and spits out resulting long Jenkinsfile that I then eval() ed). I solved my case by splitting what I eval() into chunks exchanging the data through the context singleton object in my library (surprisingly singleton instances were not per Jenkins master JVM but per library instance, i.e. per individual build). So technically my case wasn't even related to Jenkins at all. I was sending too long string into eval() method and it was legitimately (accordingly to JVM) giving me a finger. Just to give an example, my chunks would look like:{code:java}getContext('stages')['Test Stage'] = {echo 'hi'}{code}{code:java}getContext('stages')['Second Test Stage'] = { echo 'hi again'} {code}{code:java}getContext('stages')['Second Test Stage'] = { echo 'hi again'} {code}{code:java}timestamps {ansiColor("xterm") {stage('Test Stage', getContext('stages')['Test Stage'])stage('Second Test Stage', getContext('stages')['Second Test Stage'])}}{code}Given that I think this issue may be closed now.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Dmytro Kryvenko commented on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
800 lines of code sounds bad in any language. It definitely needs a refactoring and shared libraries. Just to be clear - in my case above I experienced that issue while already having my libraries, and it was due the way I designed these libraries (they treat Jenkinsfile concept as some sort of JIT, they basically doing some calculations based on the input and spits out resulting long Jenkinsfile that I then eval() ed). I solved my case by splitting what I eval() into chunks exchanging the data through the context singleton object in my library (surprisingly singleton instances were not per Jenkins master JVM but per library instance, i.e. per individual build). So technically my case wasn't even related to Jenkins at all. I was sending too long string into eval() method and it was legitimately (accordingly to JVM) giving me a finger. Just to give an example, my chunks would look like:
getContext('stages')['Test Stage'] = {
echo 'hi'
}
getContext('stages')['Second Test Stage'] = {
echo 'hi again'
}
getContext('stages')['Second Test Stage'] = {
echo 'hi again'
}
timestamps {
ansiColor("xterm") {
stage('Test Stage', getContext('stages')['Test Stage'])
stage('Second Test Stage', getContext('stages')['Second Test Stage'])
}
}
Given that I think this issue may be closed now.
Add Comment
[JIRA] (JENKINS-52523) Extended Choice Parameter broken by whitelisting change
Title: Message Title vimil commented on JENKINS-52523 Re: Extended Choice Parameter broken by whitelisting change Send me a pull request and I can merge the change in. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori updated an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Change By: leon gregori Environment: Jenkins 2.121.3 , 2.141 Kubernetes IKS 1.11 (Bluemix)Kubernetes Plugin 1.12.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Henry Borchers commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I'm starting to run into this issue myself when my pipeline reaches about 800 lines. I've been creating helper function outside of the "pipeline" brackets and that's helping but I find myself still running into this issue more than I'd like. I can't help it. Having all the new nice features makes me write longer more useful pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36792) Jenkins fails to start with Java 9 / 10 on Debian / Ubuntu
Title: Message Title kamal laungani commented on JENKINS-36792 Re: Jenkins fails to start with Java 9 / 10 on Debian / Ubuntu I'm currently facing the same issue on Ubuntu 18.04.01 LTS Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44195) Add timestamps to the log
Title: Message Title Frank Kelly commented on JENKINS-44195 Re: Add timestamps to the log The lack of this feature is also causing a step back in our ability to debug long running jobs. This is very needed. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44679) need to support script inside options
Title: Message Title
James Nord commented on JENKINS-44679
Re: need to support script inside options
Andrew Bayer has confirmed that the following works now and is now supported.
pipeline {
options {
buildDiscarder(logRotator(numToKeepStr: "${env.CHANGE_ID == null ? '100' : '5'}"))
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37025) workflowLibs custom Exception with simple getters cause java to hog cpu
Title: Message Title Jakub Josef commented on JENKINS-37025 Re: workflowLibs custom Exception with simple getters cause java to hog cpu Custom exceptions defined in pipeline libraries are working for us without any problems. Jenkins 2.127 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46940) Build pipeline plugin duplicates static linked jobs in view
Title: Message Title Adam Krapfl commented on JENKINS-46940 Re: Build pipeline plugin duplicates static linked jobs in view Javier Canillas and Killian Hesterman the workaround I posted above is still valid for our configuration (had to do it again today, because I forgot that this issue was still outstanding . ): Downgrade parameterized-trigger-plugin to 2.33. This workaround is valid for this version combination: Jenkins ver. 2.138.1 build-pipeline-plugin 1.5.8 parameterized-trigger-plugin 2.33 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53624) Branch indexing schedules builds for other branches and repos
Title: Message Title Joe Auty commented on JENKINS-53624 Re: Branch indexing schedules builds for other branches and repos In addition, this might be a totally separate issue, but in BlueOcean's "Changes" tab I'm seeing commits from other repos. If this is worth filing as a separate ticket please let me know and I'll do so. Happy to provide as much detail as is useful with these issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Sam Van Oort commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" Nico Schmoigl Please could you attach a thread dump from Jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Alok Rajiv yes that is the root cause if using IKS 1.11. In Jenkins Pipeline it should be just fine to mount containerd socket instead of docker socket. I could not yet test this as our cluster is not updated yet to containerd. I will keep you updated here. Currently (Working on old IBM IKS) volumes: [ hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: '/etc/docker/certs.d'), hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: '/var/run/docker.sock')] Possible fix (Working on new containerd IBM IKS) volumes: [ hostPathVolume(hostPath: '/etc/docker/certs.d', mountPath: 'Certificates'), hostPathVolume(hostPath: '/var/run/docker.sock', mountPath: 'SOCKET FOR CONTAINERD')] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
