[JIRA] (JENKINS-57103) No signature of method: org.jenkinsci.plugins.workflow.job.WorkflowRun.getBuildVariables()
Title: Message Title Xuyen Tran assigned an issue to Sam Van Oort Jenkins / JENKINS-57103 No signature of method: org.jenkinsci.plugins.workflow.job.WorkflowRun.getBuildVariables() Change By: Xuyen Tran Assignee: Sam Van Oort 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-57114) build name runs over right pane blocking Artifacts
Title: Message Title Henry Buttle created an issue Jenkins / JENKINS-57114 build name runs over right pane blocking Artifacts Issue Type: Bug Assignee: Oliver Gondža Attachments: image-2019-04-18-19-53-59-948.png Components: acceptance-test-harness Created: 2019-04-19 01:58 Environment: chrome Priority: Minor Reporter: Henry Buttle the added name to the delete in the left pane runs over the right pane when the build name is long Add Comment
[JIRA] (JENKINS-47881) Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Title: Message Title
Daniel Mladek edited a comment on JENKINS-47881
Re: Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Just can't figure out where better to ask this question:h4. How can I conditionally set the triggers or options parameters? The same logic as suggested for environment variables section can be applied inside {{options{}}} section, e,g. to some values of {{logRotator()}} function like this: {{numToKeepStr: "${params.IS_IT_NIGHTLY ? '4' : '2'}"}}But how to make it conditional on entire call of the {{logRotator()}} function or in {{triggers}} section when I would like to call {{poolSCM()}} method with different intervals for CI and NIGHTLY builds (or not to call it at all and use just {{cron()}} or whatever ?I'm looking for something like this:{code:java}triggers { if (params.IS_IT_NIGHTLY==true) { pollSCM('''# Once a day, between 12:00AM and 1:59AMH H(0-1) * * * ''') } else { pollSCM('''# every five minutesH/5 * * * * ''') }}{code}If I do that, then {color:#FF}*I'll get this error*{color}:{code:java}WorkflowScript: 25: Expected a trigger @ line 25, column 5. if (params.IS_IT_NIGHTLY==true) { ^1 error{code}h3.The whole point of having parameterized Jenkins pipeline jobsis that most of our the Jenkinsfiles for NIGHTLY and CI builds looks almost identical, except the:* scheduler triggers* SVN checkout (which differs in checkout strategy, depth of checkout, and other minor details)* and of course then a true parametrized split weather to perform a limited or fuld build process with relevant tests and deployment locations.I can't see as it is now implemented how can I achieve this.Thanks,-d
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...@g
[JIRA] (JENKINS-56718) Add unit tests for BlameFactory
Title: Message Title Ulli Hafner updated JENKINS-56718 Jenkins / JENKINS-56718 Add unit tests for BlameFactory Change By: Ulli Hafner 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-47881) Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Title: Message Title
Daniel Mladek commented on JENKINS-47881
Re: Declarative Pipeline: add option to set environment variables based on user passed boolean parameter in the environment directive
Just can't figure out where better to ask this question: How can I conditionally set the triggers or options parameters? The same logic as suggested for environment variables section can be applied inside options section, e,g. to some values of logRotator() function like this: numToKeepStr: "${params.IS_IT_NIGHTLY ? '4' : '2'}" But how to make it conditional on entire call of the logRotator() function or in triggers section when I would like to call poolSCM() method with different intervals for CI and NIGHTLY builds? I'm looking for something like this:
triggers {
if (params.IS_IT_NIGHTLY==true) {
pollSCM('''# Once a day, between 12:00AM and 1:59AM
H H(0-1) * * * ''')
} else {
pollSCM('''# every five minutes
H/5 * * * * ''')
}
}
If I do that, then I'll get this error:
WorkflowScript: 25: Expected a trigger @ line 25, column 5.
if (params.IS_IT_NIGHTLY==true) {
^
1 error
The whole point of having parameterized Jenkins pipeline jobs is that most of our the Jenkinsfiles for NIGHTLY and CI builds looks almost identical, except the:
scheduler triggers
SVN checkout (which differs in checkout strategy, depth of checkout, and other minor details)
and of course then a true parametrized split weather to perform a limited or fuld build process with relevant tests and deployment locations.
I can't see as it is now implemented how can I achieve this. Thanks, -d
Add Comment
[JIRA] (JENKINS-56713) Add unit tests for NewVersusFixedSeriesBuilder
Title: Message Title Ulli Hafner updated JENKINS-56713 Jenkins / JENKINS-56713 Add unit tests for NewVersusFixedSeriesBuilder Change By: Ulli Hafner 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-56712) Add unit tests for NewVersusFixedPieChart
Title: Message Title Ulli Hafner updated JENKINS-56712 Jenkins / JENKINS-56712 Add unit tests for NewVersusFixedPieChart Change By: Ulli Hafner 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-56717) Add unit tests for ToolSelectionDescriptor
Title: Message Title Ulli Hafner updated JENKINS-56717 Jenkins / JENKINS-56717 Add unit tests for ToolSelectionDescriptor Change By: Ulli Hafner 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-56709) Add unit tests for NewVersusFixedTrendChart
Title: Message Title Ulli Hafner updated JENKINS-56709 Jenkins / JENKINS-56709 Add unit tests for NewVersusFixedTrendChart Change By: Ulli Hafner 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-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Ulli Hafner stopped work on JENKINS-56714 Change By: Ulli Hafner Status: In Progress Open 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-38685) MSBuild parser doesn't match errors from clang when -fdiagnostics-format=msvc is used
Title: Message Title Ulli Hafner updated JENKINS-38685 Jenkins / JENKINS-38685 MSBuild parser doesn't match errors from clang when -fdiagnostics-format=msvc is used Change By: Ulli Hafner 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-56708) Add unit tests for HealthTrendChart
Title: Message Title Ulli Hafner updated JENKINS-56708 Jenkins / JENKINS-56708 Add unit tests for HealthTrendChart Change By: Ulli Hafner 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-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-56714 Add unit tests for IssuesChartPortlet Change By: Ulli Hafner Assignee: Andreas Reiser 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-56710) Add unit tests for SeverityPieChart
Title: Message Title Ulli Hafner updated JENKINS-56710 Jenkins / JENKINS-56710 Add unit tests for SeverityPieChart Change By: Ulli Hafner 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-56706) Add unit tests for CompositeResult
Title: Message Title Ulli Hafner updated JENKINS-56706 Jenkins / JENKINS-56706 Add unit tests for CompositeResult Change By: Ulli Hafner 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-56709) Add unit tests for NewVersusFixedTrendChart
Title: Message Title Ulli Hafner started work on JENKINS-56709 Change By: Ulli Hafner 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-56702) Use LookaheadParser for YuiCompressorParser
Title: Message Title Ulli Hafner updated JENKINS-56702 Jenkins / JENKINS-56702 Use LookaheadParser for YuiCompressorParser Change By: Ulli Hafner 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-56702) Use LookaheadParser for YuiCompressorParser
Title: Message Title Ulli Hafner started work on JENKINS-56702 Change By: Ulli Hafner 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-56712) Add unit tests for NewVersusFixedPieChart
Title: Message Title Ulli Hafner started work on JENKINS-56712 Change By: Ulli Hafner 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-38685) MSBuild parser doesn't match errors from clang when -fdiagnostics-format=msvc is used
Title: Message Title Ulli Hafner started work on JENKINS-38685 Change By: Ulli Hafner 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-56706) Add unit tests for CompositeResult
Title: Message Title Ulli Hafner started work on JENKINS-56706 Change By: Ulli Hafner 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-56718) Add unit tests for BlameFactory
Title: Message Title Ulli Hafner started work on JENKINS-56718 Change By: Ulli Hafner 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-56716) Add unit tests for LogHandler
Title: Message Title Ulli Hafner started work on JENKINS-56716 Change By: Ulli Hafner 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-56710) Add unit tests for SeverityPieChart
Title: Message Title Ulli Hafner started work on JENKINS-56710 Change By: Ulli Hafner 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-56717) Add unit tests for ToolSelectionDescriptor
Title: Message Title Ulli Hafner started work on JENKINS-56717 Change By: Ulli Hafner 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-56708) Add unit tests for HealthTrendChart
Title: Message Title Ulli Hafner started work on JENKINS-56708 Change By: Ulli Hafner 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-56713) Add unit tests for NewVersusFixedSeriesBuilder
Title: Message Title Ulli Hafner started work on JENKINS-56713 Change By: Ulli Hafner 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-56714) Add unit tests for IssuesChartPortlet
Title: Message Title Ulli Hafner started work on JENKINS-56714 Change By: Ulli Hafner 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-56484) timestamper 1.9 breaks warnings-ng's ability to find source files
Title: Message Title Ulli Hafner started work on JENKINS-56484 Change By: Ulli Hafner 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-56698) Use LookaheadParser for NagFortranParser
Title: Message Title Ulli Hafner started work on JENKINS-56698 Change By: Ulli Hafner 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-56510) Provide generic issue parser for custom tools
Title: Message Title Ulli Hafner started work on JENKINS-56510 Change By: Ulli Hafner 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-56726) Add unit tests for AggregationAction
Title: Message Title Ulli Hafner updated JENKINS-56726 Jenkins / JENKINS-56726 Add unit tests for AggregationAction Change By: Ulli Hafner 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-56705) Add unit test for SeverityTrendChart that uses Severity.ERROR
Title: Message Title Ulli Hafner updated JENKINS-56705 Jenkins / JENKINS-56705 Add unit test for SeverityTrendChart that uses Severity.ERROR Change By: Ulli Hafner 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-56704) Add unit test for ToolsTrendChart that requites the same color twice
Title: Message Title Ulli Hafner updated JENKINS-56704 Jenkins / JENKINS-56704 Add unit test for ToolsTrendChart that requites the same color twice Change By: Ulli Hafner 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-56701) Use LookaheadParser for GnuFortranParser
Title: Message Title Ulli Hafner updated JENKINS-56701 Jenkins / JENKINS-56701 Use LookaheadParser for GnuFortranParser Change By: Ulli Hafner 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-56700) Use LookaheadParser for GhsMultiParser
Title: Message Title Ulli Hafner updated JENKINS-56700 Jenkins / JENKINS-56700 Use LookaheadParser for GhsMultiParser Change By: Ulli Hafner 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-56727) Add unit tests for AnnotatedReport
Title: Message Title Ulli Hafner updated JENKINS-56727 Jenkins / JENKINS-56727 Add unit tests for AnnotatedReport Change By: Ulli Hafner 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-56075) Script based authentication unable to load authentication script file
Title: Message Title e dunne edited a comment on JENKINS-56075 Re: Script based authentication unable to load authentication script file I hit exactly the same issue using Jenkins, the ZAP pluging and ZAP on centos. This is a config issue that I was able to resolve (although I feel like the ZAP config should be smart enough to avoid this problem).I am on centos 7, running Jenkins 2.150.2, and ZAP_2.7.0 and the official ZAP OWASP plugin 1.1.0. We don't use ZAP independently as a stand alone tool on the Centos system (meaning I don't create ZAP scripts on that system). AnywayI'm putting in a comment as this was crazy frustrating (and the various google groups etc. had no relevant responses), so hopefully this helps.1. using the custom tool installation as part of the job in jenkins (if you follow the various instructions) will install the ZAP plugin in a location like this:/var/lib/jenkins/tools/com.cloudbees.jenkins.plugins.customtools.CustomTool/Zap_2.7.0/ZAP_2.7.0 <-- based on the ZAP global tool configuration (manage jenkins)However, you should kinda think as the above as a static directory that you don't mess with. The first time you run a Zap job it will create a .ZAP sub folder in the root jenkins folder. In my case it was/var/lib/jenkins/.ZAP (remember this is hidden by default. So use ls -al to see the directory). After you create a Zap auth script you need to drop the file into /var/lib/jenkins/.ZAP/script/script/authentication/Now set the ZAP home directory in the jenkins job (the one you want to run zap in) to : /var/lib/jenkins/.ZAPIt should find any file in the /var/lib/jenkins/.ZAP/script/script/authentication/ as long as the file extension is set to .zst file extension, and in the jenkins job you should be able to select your authentication script now.HOWEVERyou will STILL SEE the error associated with the bug above because ZAP doesn't seem smart enough to look into its own scripts/scripts/authentication directory.To fix that (and this is where I think ZAP needs to be smarter) you need to do the following.At the bottom of the config.xml found in the .ZAP directory (so for me this was /var/lib/jenkins/.ZAP/config.xml) you need to add something like (which is generated for you authomatically automatically if you use ZAP on windows through the UIbut which doesn't exist if you run it headless on a linux box as part of a CI install).myLoginScript.zst Mozilla Zest authentication true /var/lib/jenkins/.ZAP/scripts/scripts/authentication/myLoginScript.zst
You obviously don't need the last config xml tag I just added that to show I've put the script element just above it.Anyway as soon as we did that, the error went away and the script happily executed.Hope that helps.
[JIRA] (JENKINS-56075) Script based authentication unable to load authentication script file
Title: Message Title e dunne edited a comment on JENKINS-56075 Re: Script based authentication unable to load authentication script file I hit exactly the same issue using Jenkins, the ZAP pluging and ZAP on centos. This is a config issue that I was able to resolve (although I feel like the ZAP config should be smart enough to avoid this problem).I am on centos 7, running Jenkins 2.150.2, and ZAP_2.7.0 and the official ZAP OWASP plugin 1.1.0. We don't use ZAP independently as a stand alone tool on the Centos system (meaning I don't create ZAP scripts on that system). AnywayI'm putting in a comment as this was crazy frustrating (and the various google groups etc. had no relevant responses), so hopefully this helps.1. using the custom tool installation as part of the job in jenkins (if you follow the various instructions) will install the ZAP plugin in a location like this:/var/lib/jenkins/tools/com.cloudbees.jenkins.plugins.customtools.CustomTool/Zap_2.7.0/ZAP_2.7.0 <-- cased based on the ZAP global tool configuration (manage jenkins) However, you should kinda think as the above as a static directory that you don't mess with. The first time you run a Zap job it will create a .ZAP sub folder in the root jenkins folder. In my case it was/var/lib/jenkins/.ZAP (remember this is hidden by default. So use ls -al to see the directory). After you create a Zap auth script you need to drop the file into /var/lib/jenkins/.ZAP/script/script/authentication/Now set the ZAP home directory in the jenkins job (the one you want to run zap in) to : /var/lib/jenkins/.ZAPIt should find any file in the /var/lib/jenkins/.ZAP/script/script/authentication/ as long as the file extension is set to .zst file extension, and in the jenkins job you should be able to select your authentication script now.HOWEVERyou will STILL SEE the error associated with the bug above because ZAP doesn't seem smart enough to look into its own scripts/scripts/authentication directory.To fix that (and this is where I think ZAP needs to be smarter) you need to do the following.At the bottom of the config.xml found in the .ZAP directory (so for me this was /var/lib/jenkins/.ZAP/config.xml) you need to add something like (which is generated for you authomatically if you use ZAP on windows through the UIbut which doesn't exist if you run it headless on a linux box as part of a CI install).myLoginScript.zst Mozilla Zest authentication true /var/lib/jenkins/.ZAP/scripts/scripts/authentication/myLoginScript.zst
You obviously don't need the last config xml tag I just added that to show I've put the script element just above it.Anyway as soon as we did that, the error went away and the script happily executed. Hope that helps.
[JIRA] (JENKINS-56075) Script based authentication unable to load authentication script file
Title: Message Title e dunne commented on JENKINS-56075 Re: Script based authentication unable to load authentication script file I hit exactly the same issue using Jenkins, the ZAP pluging and ZAP on centos. This is a config issue that I was able to resolve (although I feel like the ZAP config should be smart enough to avoid this problem). I am on centos 7, running Jenkins 2.150.2, and ZAP_2.7.0 and the official ZAP OWASP plugin 1.1.0. We don't use ZAP independently as a stand alone tool on the Centos system (meaning I don't create ZAP scripts on that system). Anyway I'm putting in a comment as this was crazy frustrating (and the various google groups etc. had no relevant responses), so hopefully this helps. 1. using the custom tool installation as part of the job in jenkins (if you follow the various instructions) will install the ZAP plugin in a location like this: /var/lib/jenkins/tools/com.cloudbees.jenkins.plugins.customtools.CustomTool/Zap_2.7.0/ZAP_2.7.0 <-- cased on the ZAP global tool configuration (manage jenkins) However, you should kinda think as the above as a static directory that you don't mess with. The first time you run a Zap job it will create a .ZAP sub folder in the root jenkins folder. In my case it was /var/lib/jenkins/.ZAP (remember this is hidden by default. So use ls -al to see the directory). After you create a Zap auth script you need to drop the file into /var/lib/jenkins/.ZAP/script/script/authentication/ Now set the ZAP home directory in the jenkins job (the one you want to run zap in) to : /var/lib/jenkins/.ZAP It should find any file in the /var/lib/jenkins/.ZAP/script/script/authentication/ as long as the file extension is set to .zst file extension, and in the jenkins job you should be able to select your authentication script now. HOWEVERyou will STILL SEE the error associated with the bug above because ZAP doesn't seem smart enough to look into its own scripts/scripts/authentication directory. To fix that (and this is where I think ZAP needs to be smarter) you need to do the following. At the bottom of the config.xml found in the .ZAP directory (so for me this was /var/lib/jenkins/.ZAP/config.xml) you need to add something like (which is generated for you authomatically if you use ZAP on windows through the UIbut which doesn't exist if you run it headless on a linux box as part of a CI install).
myLoginScript.zst
Mozilla Zest
authentication
true
/var/lib/jenkins/.ZAP/scripts/scripts/authentication/myLoginScript.zst You obviously don't need the last config xml tag I just added that to show I've put the script element just above it. Anyway as soon as we did that, the error went away and the script happily executed. Hope that helps.
[JIRA] (JENKINS-48647) Warnings Plugin MSBuild parser wrong parse msbuild15 warnings output
Title: Message Title Ulli Hafner updated JENKINS-48647 Jenkins / JENKINS-48647 Warnings Plugin MSBuild parser wrong parse msbuild15 warnings output Change By: Ulli Hafner 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-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Jenn Briden commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) Hey! Gavin is right – we are fixing top bugs in Blue Ocean but don't always have time to get to everything. I've filed a Request for Enhancement (RFE) for this issue. I'm the lead Product Manager for Jenkins at CloudBees. Thank you for reporting the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Gavin Mogan commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) Honestly there's just too many bugs and not enough people. We totally welcome a pull request, but otherwise you'll have to be patient. 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-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Carlos Sanchez assigned an issue to Vincent Latombe Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Change By: Carlos Sanchez Assignee: Carlos Sanchez Vincent Latombe 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-57092) Error connecting slave using SSH Plugin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-57092 Re: Error connecting slave using SSH Plugin I wonder which files cause it, Do you have the whole `java.io.IOException: Invalid encoded sequence encountered:` stack trace? I've added it to the troubleshooting guide Corrupt agent workdir folder 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-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Liam Newman Component/s: branch-api-plugin Component/s: cloudbees-folder-plugin Component/s: github-branch-source-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-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman commented on JENKINS-54992 Re: Terrifying message makes me think Jenkins will delete my github repo Merged fix as https://github.com/jenkinsci/branch-api-plugin/pull/150 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-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman started work on JENKINS-54992 Change By: Liam Newman 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-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman updated JENKINS-54992 Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Liam Newman 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-57092) Error connecting slave using SSH Plugin
Title: Message Title Shane Kirk updated JENKINS-57092 I finally figured this out. For anyone else that might encounter something similar. I ended up connecting the slave via "command on the master" and writing a shell script that ssh'd to the server and kicked off the remoting.jar file. I was then able to see the following error: Unable to launch the agent for * java.io.IOException: Invalid encoded sequence encountered: 3D 3D 5B 4A 45 4E 4B 49 4E 53 20 52 45 4D 4F 54 49 4E 47 20 43 41 50 41 43 49 54 59 5D 3D 3D 3D 3E 72 4F 30 41 42 58 4E 79 41 42 70 6F 64 57 52 7A 62 32 34 75 63 6D 56 74 62 33 52 70 62 6D 63 75 51 32 46 77 59 57 4A 70 62 47 6C 30 65 51 41 41 41 41 41 41 41 41 41 42 41 67 41 42 53 67 41 45 62 57 46 7A 61 33 68 77 41 41 41 41 41 41 41 41 41 66 34 That led me down another path which involved me wiping out the workspace on the slave. After deleting the workspace, the slave started up via SSH fine. This issue can be closed. thanks! Jenkins / JENKINS-57092 Error connecting slave using SSH Plugin Change By: Shane Kirk Status: Open Fixed but Unreleased Assignee: Ivan Fernandez Calvo Shane Kirk Resolution: Fixed Add Comment
[JIRA] (JENKINS-57092) Error connecting slave using SSH Plugin
Title: Message Title Shane Kirk updated an issue Jenkins / JENKINS-57092 Error connecting slave using SSH Plugin Change By: Shane Kirk Comment: I finally figured this out. For anyone else that might encounter something similar. I ended up connecting the slave via "command on the master" and writing a shell script that ssh'd to the server and kicked off the remoting.jar file. I was then able to see the following error: Unable to launch the agent for *java.io.IOException: Invalid encoded sequence encountered: 3D 3D 5B 4A 45 4E 4B 49 4E 53 20 52 45 4D 4F 54 49 4E 47 20 43 41 50 41 43 49 54 59 5D 3D 3D 3D 3E 72 4F 30 41 42 58 4E 79 41 42 70 6F 64 57 52 7A 62 32 34 75 63 6D 56 74 62 33 52 70 62 6D 63 75 51 32 46 77 59 57 4A 70 62 47 6C 30 65 51 41 41 41 41 41 41 41 41 41 42 41 67 41 42 53 67 41 45 62 57 46 7A 61 33 68 77 41 41 41 41 41 41 41 41 41 66 34 That led me down another path which involved me wiping out the workspace on the slave. After deleting the workspace, the slave started up via SSH fine. This issue can be closed. 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-57092) Error connecting slave using SSH Plugin
Title: Message Title Shane Kirk commented on JENKINS-57092 Re: Error connecting slave using SSH Plugin I finally figured this out. For anyone else that might encounter something similar. I ended up connecting the slave via "command on the master" and writing a shell script that ssh'd to the server and kicked off the remoting.jar file. I was then able to see the following error: Unable to launch the agent for * java.io.IOException: Invalid encoded sequence encountered: 3D 3D 5B 4A 45 4E 4B 49 4E 53 20 52 45 4D 4F 54 49 4E 47 20 43 41 50 41 43 49 54 59 5D 3D 3D 3D 3E 72 4F 30 41 42 58 4E 79 41 42 70 6F 64 57 52 7A 62 32 34 75 63 6D 56 74 62 33 52 70 62 6D 63 75 51 32 46 77 59 57 4A 70 62 47 6C 30 65 51 41 41 41 41 41 41 41 41 41 42 41 67 41 42 53 67 41 45 62 57 46 7A 61 33 68 77 41 41 41 41 41 41 41 41 41 66 34 That led me down another path which involved me wiping out the workspace on the slave. After deleting the workspace, the slave started up via SSH fine. This issue can be closed. 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-57113) Failed to send out e-mail java.net.ConnectException: Connection refused: connect
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Failed to send out e-mail java.net.ConnectException: Connection refused: connect Change By: Rajesh Nallamotu Summary: Sending a Failed to send out e- mail notification through gmail java.net.ConnectException: Connection refused: connect 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-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline:[core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164|https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164]However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: [ jenkinsci/branch-api-plugin PR #142| https://github.com/jenkinsci/branch-api-plugin/pull/142] Here is the code used in on the Master node and the related test:[core/src/main/java/jenkins/model/Jenkins.java#L979-L993|https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993][test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487|https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487]Here is the code in SlaveComputer.setChannel() and the test file showing no test:[core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698|https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698][test/src/test/java/hudson/slaves/SlaveComputerTest.java|https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java]NOTE: the Jenkins.java code is not correct either since it will swallow more than the contract specifies - including NullPointerException for example. Also, it should probably be a WARNING rather than SEVERE. Add Comment
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline:[ https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/ core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164| https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/ core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164]However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: [ https://github.com/jenkinsci/branch-api-plugin/pull/142 ] Here is the code used in on the Master node and the related test: [core/src/main/java/jenkins/model/Jenkins.java#L979-L993| https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993 ] [test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487| https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487 ] Here is the code in hudson.slaves. SlaveComputer.setChannel () and the test file showing no test: [core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698| https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698 ] [test/src/test/java/hudson/slaves/SlaveComputerTest.java| https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java #L45 ] NOTE: the Jenkins.java code is not correct either since it will swallow more than the contract specifies - including NullPointerException for example. Also, it should probably be a WARNING rather than SEVERE. Add Comment
[JIRA] (JENKINS-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Change By: Rajesh Nallamotu Attachment: Untitled.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Change By: Rajesh Nallamotu Attachment: Untitled.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline: [ https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164 |core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164] However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: https://github.com/jenkinsci/branch-api-plugin/pull/142 Here is the code used in on the Master node and the related test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487Here is the code in hudson.slaves.SlaveComputer.setChannel and the test file showing no test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java#L45NOTE: the Jenkins.java code is not correct either since it will swallow more than the contract specifies - including NullPointerException for example. Also, it should probably be a WARNING rather than SEVERE. Add Comment
[JIRA] (JENKINS-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Change By: Rajesh Nallamotu Attachment: Untitled.png 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-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title frederic larde commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) Is someone could help me? I will be glad to provide more information if necessary. 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-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Change By: Rajesh Nallamotu Attachment: Untitled.png 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-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu updated an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Change By: Rajesh Nallamotu Attachment: Untitled.png 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-57113) Sending a mail notification through gmail
Title: Message Title Rajesh Nallamotu created an issue Jenkins / JENKINS-57113 Sending a mail notification through gmail Issue Type: Task Assignee: Adrien Lecharpentier Attachments: Untitled.png Components: mailer-plugin Created: 2019-04-18 19:10 Environment: Windows server 2012 R2 Labels: exception jenkins Priority: Major Reporter: Rajesh Nallamotu I am not able to send mail notification after build has been succeeded. So could you please look into this issue as soon as possible. When i am checking test connection for sending mail jenkins throws an error like connection refused. i have attached screen shot. please look into it.
[JIRA] (JENKINS-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Steve Collins updated an issue Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Change By: Steve Collins Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: https://github.com/jenkinsci/branch-api-plugin/pull/142 Here is the code used in on the Master node and the related test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487Here is the code in hudson.slaves.SlaveComputer.setChannel and the test file showing no test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java#L45NOTE: the Jenkins.java code is not correct either since it will swallow more than the contract specifies - including NullPointerException for example. Also, it should probably be a WARNING rather than SEVERE. Add Comment This message wa
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: https://github.com/jenkinsci/branch-api-plugin/pull/142 Here is the code used in on the Master node and the related test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487 Here is the code in hudson.slaves.SlaveComputer.setChannel and the test file showing no test:https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java#L45 NOTE: the Jenkins.java code is not correct either since it will swallow more than the contract specifies - including NullPointerException for example. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Steve Collins created an issue Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-04-18 18:51 Environment: Jenkins 2.150.3 and 2.164.2 on Linux Priority: Major Reporter: Steve Collins If I save any Raw Yaml in a pod template, the yaml does not save. A reload of the config page show's no raw yaml. I have confirmed on two different versions of jenkins. If I roll back to version 1.15.0, the yaml persists as it should. Add Comment
[JIRA] (JENKINS-57083) Mouse over in diagrams only works for first diagram
Title: Message Title Ulli Hafner commented on JENKINS-57083 Re: Mouse over in diagrams only works for first diagram What do you mean by "the bug has been resolved in HEAD"? https://wiki.jenkins.io/display/JENKINS/Pipeline+Stage+View+Plugin I haven't checked if the Test Result trend bug is the same, but I recently got an notification about that 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-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman commented on JENKINS-57111 Re: Base class setChannel does not handle exceptions from onOnline call Linked issues are likely all due to this one. 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-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-18 18:33 Priority: Major Reporter: Liam Newman Throwing an exception in ComputerListener.onOnline should not take a node offline: https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/ComputerListener.java#L135-L164 However, there a number of issues filed that show exceptions in onOnline not being handled, the latest being one in branch-api: https://github.com/jenkinsci/branch-api-plugin/pull/142 Here is the code used in on the Master node and the related test: https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/jenkins/model/Jenkins.java#L979-L993 https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/jenkins/model/JenkinsTest.java#L473-L487 Here is the code in hudson.slaves.SlaveComputer.setChannel and the test file showing no test: https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/core/src/main/java/hudson/slaves/SlaveComputer.java#L696-L698 https://github.com/jenkinsci/jenkins/blob/2767b00146ce2ff2738b7fd7c6db95a26b8f9f39/test/src/test/java/hudson/slaves/SlaveComputerTest.java#L45
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Ulli Hafner commented on JENKINS-57098 Re: JSON Exchange format for import/export? Providing an additional format as JSON is a good idea. I think it is not hard to implement something that reads the existing Issue properties. It basically should do the same thing that an XML parser in JENKINS-56510 is doing. Then users have the choice to use the format that is better matching. Is Asciidoctor already a Jenkins Plugin? Note that in this case you can also can consider to directly create the issues using the API rather then working with files at all. Then you do not need to think about flushing of the console log... 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-45140) Add support of throttling of the entire build in Declarative Pipeline
Title: Message Title
Nick Jones commented on JENKINS-45140
Re: Add support of throttling of the entire build in Declarative Pipeline
I had to revert back to a scripted pipeline in order to get throttling to work as intended. The issue seems to be that the throttle option in a Declarative pipeline occurs on a particular agent node, and it's either too late – the executor is already consumed – or it's simply a no-op, but in any case, I'm not seeing any actual evidence of throttling, either overall or per node.
pipeline {
agent { label 'foo' }
options {
throttle(categories: ['MyCategory']) // <-- doesn't do anything, even with MyCategory defined in the system configuration
}
stages {
// ...
}
}
What I would have wanted is either to have the throttle option take effect before the agent is selected, or some sort of declarative syntax that would let me have agent none at the top level of the pipeline (where the throttle option is specified), then the ability to specify a particular agent for all the actual stages to be executed (Build, Test, Publish, etc.). I tried this:
pipeline {
agent none // <-- to avoid having an agent allocated before the throttle category is evaluated
options {
throttle(categories: ['MyCategory'])
}
stages {
stage('Overall') {
agent {
label 'foo' // <-- to get the real agent I want for the real stages
}
stages {
stage('Build') {
// ...
}
stage('Test') {
// ...
}
}
}
}
}
But it simply hung with no useful output. If there's some other way to have agent none at the top level, then a single, reused agent for the actual stages within, I'd be interested to hear about it. I know I could have an agent per stage (Build, Test, etc.), but that wouldn't work for me – it has to be the same machine for all of these, and I'd rather not stash and unstash all the artifacts I need between these stages.
Add Comment
[JIRA] (JENKINS-32087) Configure JIRA credentials at the Job configuration level
Title: Message Title Mathieu Delrocq commented on JENKINS-32087 Re: Configure JIRA credentials at the Job configuration level Hello, we need it in our company so I will try to do it if it is ok for you. I started somes developments at https://github.com/mat1e/jira-plugin/tree/feature/JENKINS-32087_credentials_at_job_level if you want to take a look. 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-17420) ComputerListener.onOffline called after channel closed
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-17420
ComputerListener.onOffline called after channel closed
Change By:
Liam Newman
(JENKINS-22543) The master {{Jenkins}} calls {{onOnline}} during initialization, but never calls {{onOffline}} even during a polite shutdown. So this method cannot be used to clean up anything on master; you would need to use a shutdown hook, perhaps. A {{SlaveComputer}} calls {{onOffline}} after the virtual channel has already been disconnected, so this method cannot run a command on the slave, to (say) clean up temporary files or stop processes that {{onOnline}} created or started.
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-17420) ComputerListener.onOffline called after channel closed
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-17420
ComputerListener.onOffline called after channel closed
Change By:
Liam Newman
(JENKINS-22543) The master {{Jenkins}} calls {{onOnline}} during initialization, but never calls {{onOffline}} even during a polite shutdown. So this method cannot be used to clean up anything on master; you would need to use a shutdown hook, perhaps.A {{SlaveComputer}} calls {{onOffline}} after the virtual channel has already been disconnected, so this method cannot run a command on the slave, to (say) clean up temporary files or stop processes that {{onOnline}} created or started.
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-17420) ComputerListener.onOffline called after channel closed
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-17420 ComputerListener.onOffline called after channel closed Change By: Liam Newman Summary: ComputerListener.onOffline not very useful called after channel 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-22543) Computer getChannel() method returns null in ComputerListeners
Title: Message Title Liam Newman stopped work on JENKINS-22543 Change By: Liam Newman Status: In Progress Open 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-43292) The failed parallel build step should be focused and aborted when failFast
Title: Message Title Devin Nusbaum updated JENKINS-43292 Jenkins / JENKINS-43292 The failed parallel build step should be focused and aborted when failFast Change By: Devin Nusbaum Status: In Review 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-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Jesse Glick commented on JENKINS-55726 Re: GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository Sorry, will leave detailed responses to whomever currently maintains the GitHub integration. 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-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Great, thanks. In the mean time, i'm running on Java 8. 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-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Jon-Paul Sullivan commented on JENKINS-55726 Re: GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository My reading was that the changing name returned from a PR branch build broke things because you need a fixed string for a single job. I didn't read that as requiring a fixed string for every status reported by Jenkins ever. So ci/jenkins/repo/PR-1, ci/jenkins/repo/PR-2 == broken status reporting, but ci/jenkins/repo would not change between Pull Requests and therefore satisfies the requirements of the previous bug report, as I read it. If there is no desire to change the current default behaviour, I would still like a convenient way to change that default behaviour to something more useful to my use case, where multiple jobs need to accurately report status to GitHub without overwriting the reported status of a different job, which I think is a bug, even if the code is working as designed. I think this is a bug because it allows for incorrect changing of data in GitHub - different jobs reporting to the same context looks to me like avoiding the whole point of the context string in the first place. So I would interpret the Jenkins intention is to have 1 job per commit, but that is not a model enforced by a number of other Jenkins<->SCM reporting tools, for example Gerrit and Jenkins allows for multiple jobs reporting status and correctly gates across multiple jobs. Requiring me to remember to change the context every time I create a uniquely named job seems like at best a poor user experience, and similarly requiring code in every Jenkinsfiles I write to correctly report back is again poor user experience. The additions need every time a job is created becomes tribal knowledge that needs to be remembered, and is going to be a source of bug in pipelines for our software delivery. Can I get pointers to the existing elements you mention though please? They may show a template for creating a plugin that modifies the default behaviour? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57095) Validate#check should be case insensitive
Title: Message Title Paul Allen updated JENKINS-57095 Jenkins / JENKINS-57095 Validate#check should be case insensitive Change By: Paul Allen 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-57095) Validate#check should be case insensitive
Title: Message Title Paul Allen updated JENKINS-57095 Ready for release. Jenkins / JENKINS-57095 Validate#check should be case insensitive Change By: Paul Allen Status: In Review 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-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title Jesse Glick commented on JENKINS-55726 Re: GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository The context originally included the job name. This broke things badly for people who configured various tools according to specific contexts, so we switched to constant context names. The intention is that each commit is built by one job. If you want to define additional contexts, if I recall correctly there is a plugin which allows you to override the context name for a given job. There is also a plugin offering an explicit Pipeline step for adding an ad-hoc commit status. I think this can be closed or just treated as a request for clearer documentation. 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-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor commented on JENKINS-56595 Re: Regression: higher than usual CPU usage with 2.164.1 I can also confirm this behavior on 2.164.1 Symptoms are: gerrit queue is blocked CPU utilization is all user and pegged to 100% IO drops to nothing The UI was completely locked up ~925 and was restarted at 937. System CPU spike at 933 was inspecting jenkins logs before reboot. This happens every few days so I should be able to capture more information on the next cycle. I assume a thread dump is the best resource to ascertain what's happening here?? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Ryan Taylor Attachment: image-2019-04-18-10-06-18-006.png 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-56595) Regression: higher than usual CPU usage with 2.164.1
Title: Message Title Ryan Taylor updated an issue Jenkins / JENKINS-56595 Regression: higher than usual CPU usage with 2.164.1 Change By: Ryan Taylor Attachment: image-2019-04-18-10-06-42-865.png 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-55726) GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Title: Message Title
Jon-Paul Sullivan commented on JENKINS-55726
Re: GitHub can incorrectly flag PRs as passing checks if multiple jobs run against the same repository
Related to JENKINS-37100 and JENKINS-36574 - I think the latter may be the genesis for the current situation, which may have been a fix by Jesse Glick? I read through those bugs and can definitely see why the code is as it currently is, but I think an improvement can be made to satisfy both the current use case and also improve the situation where multiple Jenkins jobs are reporting to the single repository. I saw this mentioned but no discussion as to why it was ultimately not followed, so if there are issues then please do explain. The prime requirements for blocking merges is that there is a single string that any PR presents to GitHub so the repository settings can indicate the status of that context must be success prior to merge. This is currently set to "continuous-integration/jenkins/pr-merge".
public String getDefaultContext(TaskListener listener) {
if (head instanceof PullRequestSCMHead) {
if (((PullRequestSCMHead) head).isMerge()) {
return "continuous-integration/jenkins/pr-merge";
} else {
return "continuous-integration/jenkins/pr-head";
}
} else {
return "continuous-integration/jenkins/branch";
}
}
The issue is that every Jenkins job returns that same context. In the case of a Multibranch configuration using GitHub, we will have a job whose name is [/]*/ where is either a branch or a special branch representing a Pull Request. The branch string changes each time a new branch or pull request is created, and this makes it unsuitable to be used as a merge gate for GitHub. I would state that the enclosing job name is perfectly viable to use as a status context though, as that is unchanging across multiple Pull Requests. So the above code would become something like:
public String getDefaultContext(TaskListener listener) {
if (head instanceof PullRequestSCMHead) {
if (((PullRequestSCMHead) head).isMerge()) {
return "continuous-integration/jenkins/" + job.getParent() + "/pr-merge";
} else {
return "continuous-integration/jenkins/" + job.getParent() + "/pr-head";
}
} else {
return "continuous-integration/jenkins/" + job.getParent() + "/branch";
}
}
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title david bensoussan commented on JENKINS-44609 Re: Docker inspect failing on named multi-stage builds There is a PR solving this here: https://github.com/jenkinsci/docker-workflow-plugin/pull/162 Could a maintainer take a look at 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-31507) docker.build throw IOExceptions with some sources
Title: Message Title david bensoussan commented on JENKINS-31507 Re: docker.build throw IOExceptions with some sources There is a PR solving this here: https://github.com/jenkinsci/docker-workflow-plugin/pull/162 Could a maintainer take a look at 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-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title david bensoussan commented on JENKINS-44789 Re: docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom There is a PR solving this here: https://github.com/jenkinsci/docker-workflow-plugin/pull/162 Could a maintainer take a look at 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-40958) Allow pullrequest approved in webhooks for bitbucket multibranch projects
Title: Message Title Kyle Carter commented on JENKINS-40958 Re: Allow pullrequest approved in webhooks for bitbucket multibranch projects https://github.com/jenkinsci/bitbucket-branch-source-plugin/releases/tag/cloudbees-bitbucket-branch-source-2.4.1 This is solved in this version. 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-15925) Change delimiter of SecurityGroups from comma to pipe
Title: Message Title Coltrey Mather commented on JENKINS-15925 Re: Change delimiter of SecurityGroups from comma to pipe Supriya Nandi how has this issue been resolved? The above PR has not been merged... 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-57110) Different "Maximum Total Concurrent Builds" on differetn jobs
Title: Message Title Martin Choma created an issue Jenkins / JENKINS-57110 Different "Maximum Total Concurrent Builds" on differetn jobs Issue Type: Bug Assignee: Unassigned Components: throttle-concurrent-builds-plugin Created: 2019-04-18 15:04 Priority: Minor Reporter: Martin Choma I need to have different values of "Maximum Total Concurrent Builds" on differetn jobs on one category. Global "Maximum Total Concurrent Builds" is always used. Jobs "Maximum Total Concurrent Builds" is not used. Description of field in jenkings GUI: The maximum number of concurrent builds of this project (or category) to be allowed to run at any one time, across all nodes. https://github.com/jenkinsci/throttle-concurrent-builds-plugin: Throttle this project as part of one or more categories For this option you should specify enabled categories using checkboxes Maximum Total Concurrent Builds and Maximum Concurrent Builds Per Node fields will be ignored So is this expected to work or not? Add Comment
[JIRA] (JENKINS-57109) Allow for tag list within docker build arguments
Title: Message Title
Phil Madden updated an issue
Jenkins / JENKINS-57109
Allow for tag list within docker build arguments
Change By:
Phil Madden
As per the docker docs ( [(here --tag)|https://docs.docker.com/engine/reference/commandline/build/#tag-an-image%E2%80%93t], the docker build command's tag option can be specified multiple times to tag an image multiple times.{code:java}docker build --tag org/image:t1 --tag org/image:t2 . {code}
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-57109) Allow for tag list within docker build arguments
Title: Message Title
Phil Madden updated an issue
Jenkins / JENKINS-57109
Allow for tag list within docker build arguments
Change By:
Phil Madden
As per the docker docs ( [ (here --tag ) |https://docs.docker.com/engine/reference/commandline/build/#tag-an-image –t %E2%80%93t ], the docker build command's tag option can be specified multiple times to tag an image multiple times.{code:java}docker build --tag org/image:t1 --tag org/image:t2 . {code}
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-57109) Allow for tag list within docker build arguments
Title: Message Title Phil Madden created an issue Jenkins / JENKINS-57109 Allow for tag list within docker build arguments Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2019-04-18 14:55 Priority: Minor Reporter: Phil Madden As per the docker docs --tag, the docker build command's tag option can be specified multiple times to tag an image multiple times. docker build --tag org/image:t1 --tag org/image:t2 . Add Comment
[JIRA] (JENKINS-15925) Change delimiter of SecurityGroups from comma to pipe
Title: Message Title Supriya Nandi updated JENKINS-15925 Jenkins / JENKINS-15925 Change delimiter of SecurityGroups from comma to pipe Change By: Supriya Nandi Status: In Review 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-15925) Change delimiter of SecurityGroups from comma to pipe
Title: Message Title Supriya Nandi updated JENKINS-15925 Jenkins / JENKINS-15925 Change delimiter of SecurityGroups from comma to pipe Change By: Supriya Nandi 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-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Jie Shen do you have any update on this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
