[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated JENKINS-57917 Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Change By: ikedam 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23964.1559971320250%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam updated an issue Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild https://github.com/jenkinsci/groovy-postbuild-plugin/pull/42 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23966.1559971320278%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam started work on JENKINS-57917 Change By: ikedam 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199886.1559968232000.23962.1559971260233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57917) addHtmlBadge for groovy-postbuild
Title: Message Title ikedam created an issue Jenkins / JENKINS-57917 addHtmlBadge for groovy-postbuild Issue Type: New Feature Assignee: ikedam Components: groovy-postbuild-plugin Created: 2019-06-08 04:30 Priority: Minor Reporter: ikedam HTML texts are escaped for addShortText or other badge-related features since groovy-postbuild-2.4. I decided NOT to revert that change as it causes security issues. addHtmlBadge is introduced since badge-plugin-1.3 and it would be useful also for groovy-postbuild and can help users used HTML texts in addShortText. Add Comment
[JIRA] (JENKINS-51370) Error on using Groovy Postbuild plugin
Title: Message Title ikedam updated JENKINS-51370 No response from the reporter. Please reopen when more detailed information is available. Jenkins / JENKINS-51370 Error on using Groovy Postbuild plugin Change By: ikedam Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190717.1526489375000.23956.1559966820459%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: ikedam Assignee: Stefan Wolf ikedam 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.23943.1559965020636%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title ikedam started work on JENKINS-54262 Change By: ikedam 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194906.154053702.23950.1559965020835%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57877) PromotionBadge compatibility with pipelines
Title: Message Title Prastik Gyawali updated JENKINS-57877 Jenkins / JENKINS-57877 PromotionBadge compatibility with pipelines Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199840.1559812947000.23939.1559957760171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Prastik Gyawali updated JENKINS-57903 Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.23938.1559957760142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56016) Input Submitter parameter ignored
Title: Message Title Omit Rathore edited a comment on JENKINS-56016 Re: Input Submitter parameter ignored This is very dangerous issue , team relying on permissions control with submitter is broken. We had to revert to 2.8 . Ideal flow would be only user/team mentioned as submitter should be allowed to proceed. it It is classical example of privilege escalation. It is kind of security threat. It's fine to have these feature if submitter is not mentioned. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197434.1549522612000.23934.1559945940161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57916) Container not created using YAML
Title: Message Title Jay Mehta updated an issue Jenkins / JENKINS-57916 Container not created using YAML Change By: Jay Mehta In same declarative pipeline script container does not create if specified as yaml. It . gets created if specified using containerTemplate. See attached log and pipeline script. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199885.1559944294000.23932.1559944380149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57916) Container not created using YAML
Title: Message Title Jay Mehta created an issue Jenkins / JENKINS-57916 Container not created using YAML Issue Type: Bug Assignee: Unassigned Attachments: Jenkins.log, Jenkinsfile Components: kubernetes-pipeline-plugin Created: 2019-06-07 21:51 Priority: Major Reporter: Jay Mehta In same declarative pipeline script container does not create if specified as yaml. It . gets created if specified using containerTemplate. See attached log and pipeline script. Add Comment
[JIRA] (JENKINS-57915) TestResult annotate function handling of URL's behaves differently than Jenkins core UrlConsoleAnnotator
Title: Message Title Aaron Ray updated an issue Jenkins / JENKINS-57915 TestResult annotate function handling of URL's behaves differently than Jenkins core UrlConsoleAnnotator Change By: Aaron Ray This is arguably a feature request, but I opted to make it a bug due to divergence in behavior with Jenkins core.The Jenkins UrlConsoleAnnotator ignores the closing bracket when translating URL's to hyperlinks from the raw text output of stdout:[https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/console/UrlAnnotator.java#L28]The JUnit plugin does not ignore this closing bracket:[https://github.com/jenkinsci/junit-plugin/blob/25f5a5cbfff16c0e6e2b30a8c5e8728a3b2b99d6/src/main/java/hudson/tasks/test/TestResult.java#L276]This only seems to cause problems when the link ending in a closing bracket is a filename. My use case is that we run Selenium test automation via Jenkins, and our framework outputs screenshots that are stored in the Jenkins workspace to stdout as URL's. We are wrapping the URL's in brackets (e.g. \ [http://google.com \ ]). This makes it easy to reference the screenshots from the console when troubleshooting. It is easier to look at the output via the testReport view provided by this plugin, but the link is then broken. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) --
[JIRA] (JENKINS-57915) TestResult annotate function handling of URL's behaves differently than Jenkins core UrlConsoleAnnotator
Title: Message Title Aaron Ray created an issue Jenkins / JENKINS-57915 TestResult annotate function handling of URL's behaves differently than Jenkins core UrlConsoleAnnotator Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2019-06-07 21:34 Environment: O/S: Windows 10 64-bit JRE: 1.8.0_191 Jenkins: 2.164.3 JUnit Plugin: 1.28 Browser: Chrome 75.0.3770.80 64-bit Running Jenkins directly as Windows service Slaves are also running as Windows services No proxies Priority: Minor Reporter: Aaron Ray This is arguably a feature request, but I opted to make it a bug due to divergence in behavior with Jenkins core. The Jenkins UrlConsoleAnnotator ignores the closing bracket when translating URL's to hyperlinks from the raw text output of stdout: https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/console/UrlAnnotator.java#L28 The JUnit plugin does not ignore this closing bracket: https://github.com/jenkinsci/junit-plugin/blob/25f5a5cbfff16c0e6e2b30a8c5e8728a3b2b99d6/src/main/java/hudson/tasks/test/TestResult.java#L276 This only seems to cause problems when the link ending in a closing bracket is a filename. My use case is that we run Selenium test automation via Jenkins, and our framework outputs screenshots that are stored in the Jenkins workspace to stdout as URL's. We are wrapping the URL's in brackets (e.g. http://google.com). This makes it easy to reference the screenshots from the console when troubleshooting. It is easier to look at the output via the testReport view provided by this plugin, but the link is then broken.
[JIRA] (JENKINS-56016) Input Submitter parameter ignored
Title: Message Title Omit Rathore commented on JENKINS-56016 Re: Input Submitter parameter ignored This is very dangerous issue , team relying on permissions control with submitter is broken. We had to revert to 2.8 . Ideal flow would be only user/team should be allowed to proceed. it is classical example of privilege escalation. It is kind of security threat. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197434.1549522612000.23927.1559943180116%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56994) Provide User-Managed Service Identity support
Title: Message Title daniele vottero edited a comment on JENKINS-56994 Re: Provide User-Managed Service Identity support raised this PR [https://github.com/jenkinsci/azure-vm-agents-plugin/pull/ 157/ 158 ] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198691.1555090331000.23924.1559941740122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57738) Job DSL API viewer fails to load
Title: Message Title Daniel Spilker updated JENKINS-57738 The class hudson.tools.JDKInstaller is missing. This has been removed from Jenkins core in 2.112 and is now provided by the JDK Tool plugin. Check the plugin manager for missing plugins and install the JDK Tool plugin. Jenkins / JENKINS-57738 Job DSL API viewer fails to load Change By: Daniel Spilker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199682.155913859.23922.1559940600348%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title CJ Harmath commented on JENKINS-50548 Re: Shared Library should be allowed to declare reusable stages Okay, so I just re-read the docs and as I understand what I should be doing is to just put the entire pipeline into my shared library. https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines This kind of makes me wonder if we allow defining entire pipeline, why not allow stages as well ? But I guess I am already happy with this as I only need to maintain one pipeline per app type. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189617.1522766954000.23879.1559936220691%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
CJ Harmath edited a comment on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
I would like this as well.Use case:share build stages across similar projects, to keep things DRY and have a central shared library defining the various build stages per project types.i.e.: I might have many many microservices all using the same 1) package restore 2) lint 3) build 4) run unit tests stages with only parameter differences and it would be awesome if app devs can just include a single line with the necessary parameters to call these 4 steps. so instead of {code:java} stages { stage('restore') { steps { echo 'package restore' restore() } } stage('build') { steps { echo 'building' build() } } stage('test') { steps { echo 'testing' test() } }} {code} you could do this: {code:java} stages { sharedMicroserviceStages()} {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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189617.1522766954000.23838.1559935800953%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
CJ Harmath commented on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
I would like this as well. Use case: share build stages across similar projects, to keep things DRY and have a central shared library defining the various build stages per project types. i.e.: I might have many many microservices all using the same 1) package restore 2) lint 3) build 4) run unit tests stages with only parameter differences and it would be awesome if app devs can just include a single line with the necessary parameters to call these 4 steps. so instead of stages { stage('restore') { steps { echo 'package restore' restore() } } stage('build') { steps { echo 'building' build() } } stage('test') { steps { echo 'testing' test() } } } you could do this: stages { sharedMicroserviceStages() }
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189617.1522766954000.23797.1559935680827%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-57805 Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Change By: Devin Nusbaum Released As: workflow-api 2.35 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.23795.1559931480117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55737) "No polling baseline - Changes found" causing runaway polling
Title: Message Title Jay Spang commented on JENKINS-55737 Re: "No polling baseline - Changes found" causing runaway polling This seems to be fixed now. It has not reprod since 1.9.7 was installed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197010.1548200108000.23791.1559931120133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56825) Don't redact URL in support-core anonymization
Title: Message Title Arnaud Héritier commented on JENKINS-56825 Re: Don't redact URL in support-core anonymization John C Bland II which emails are you talking about ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198481.1554062136000.23787.1559930344742%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Pavel Janoušek commented on JENKINS-57642 Re: Wrong parameter type and squashing its content when trigger a job Thank you very much Scott! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.23783.1559927940205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57826) catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE
Title: Message Title Andrew Bayer updated JENKINS-57826 Woo, merged - it'll be in 1.3.9, which I should release soon. Jenkins / JENKINS-57826 catchError(buildResult: hudson.model.Result.SUCCESS, stageResult: hudson.model.Result.FAILURE) doesn't set stage to FAILURE Change By: Andrew Bayer 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199781.1559585434000.23758.1559926740536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories
Title: Message Title
Eugene G edited a comment on JENKINS-24440
Re: Jenkins cannot delete root-owned files/folders in jenkins-owned directories
This helps in my case:{code:java}stages { stage('Build') {steps {script { // ... image = docker . build inside ( '-u root ) { some code creates files and folders } } }} post {cleanup {script {image.inside('-u root') {sh "chmod -R 777 'find . " -user root -name \'*\' | xargs chmod ugo+rw' }}deleteDir()}} {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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157021.1409056797000.23742.1559925960407%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43756) Delete content of the S3 "folder" before the save
Title: Message Title F C commented on JENKINS-43756 Re: Delete content of the S3 "folder" before the save same 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181172.1492769191000.23739.1559925780153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42860) RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
Title: Message Title
Daryl Banttari commented on JENKINS-42860
Re: RejectedAccessException: Scripts not permitted to use method hudson.plugins.git.GitSCM getBranches
I was able to work around a similar issue using (in my Jenkins config scripts): def scriptApproval = org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.get() scriptApproval.approveSignature('method hudson.plugins.git.BranchSpec getName') scriptApproval.approveSignature('method hudson.plugins.git.GitSCM getBranches') and now I can use "${scm.branches[0].name}" in my Jenkinsfile c.f. https://stackoverflow.com/questions/47925058/how-to-approve-script-snippets-from-a-jenkinsfile-via-the-groovy-script-console Would save a lot of grief for people if these methods were @Whitelisted
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179864.1489697851000.23719.1559924520404%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57210) Issue with docker.withRegistry
Title: Message Title Jeff Wartes commented on JENKINS-57210 Re: Issue with docker.withRegistry Encountered the same issue. Resolved by editing the Dockerfile involved from "from ubuntu:xenial" to "FROM ubuntu:xenial". Docker says the instruction is not case sensitive, but apparently something in Jenkins/docker doesn't agree. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198968.1556502359000.23717.1559924220101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57914) SCM Polling uses last polled branch always
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-57914 SCM Polling uses last polled branch always Change By: Vincent Latombe Component/s: pipeline Component/s: pollscm-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199882.1559918325000.23710.1559922480163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57817) Job DSL + Warnings-NG + Spotbugs not working
Title: Message Title Daniel Spilker commented on JENKINS-57817 Re: Job DSL + Warnings-NG + Spotbugs not working PR https://github.com/jenkinsci/job-dsl-plugin/pull/1179 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199771.1559562134000.23683.1559922300675%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57817) Job DSL + Warnings-NG + Spotbugs not working
Title: Message Title Daniel Spilker started work on JENKINS-57817 Change By: Daniel Spilker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199771.1559562134000.23686.1559922300718%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title
Jesse Glick commented on JENKINS-46076
Re: Test flake in CpsThreadTest.stop
Reproducible with
diff --git a/pom.xml b/pom.xml
index 3e1b3830..41948296 100644
--- a/pom.xml
+++ b/pom.xml
@@ -84,7 +84,7 @@
org.jenkins-ci.plugins.workflow
workflow-api
-2.30
+2.32
org.jenkins-ci.plugins.workflow
@@ -152,7 +152,7 @@
org.jenkins-ci.plugins.workflow
workflow-job
-2.26
+2.33-SNAPSHOT
test
picking up
diff --git a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
index 2eaac3a..f630809 100644
--- a/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
+++ b/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowRun.java
@@ -577,6 +577,11 @@ public final class WorkflowRun extends Run implements F
completed = Boolean.TRUE;
duration = Math.max(0, System.currentTimeMillis() - getStartTimeInMillis());
}
+try {
+Thread.sleep(3_000);
+} catch (InterruptedException x) {
+x.printStackTrace();
+}
try {
LOGGER.log(Level.INFO, "{0} completed: {1}", new Object[]{toString(), getResult()});
if (nullListener) {
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Marky Jackson updated JENKINS-57886 Jenkins / JENKINS-57886 Add JCasC config test Change By: Marky Jackson Status: In Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199850.1559832725000.23655.1559920020568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57803) Add README to GitHub repository
Title: Message Title Marky Jackson started work on JENKINS-57803 Change By: Marky Jackson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199754.1559329605000.23652.1559919900598%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Marky Jackson started work on JENKINS-57760 Change By: Marky Jackson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199706.1559207961000.23650.1559919900575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Daniel Beck Component/s: winstone-jetty 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.23647.1559919480450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-57888 Custom log format broken by 2.177 Change By: Daniel Beck Labels: regression 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.23645.1559919480427%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-46076 Test flake in CpsThreadTest.stop Change By: Jesse Glick Assignee: Jesse Glick 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.23634.1559918400641%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Jesse Glick started work on JENKINS-46076 Change By: Jesse Glick 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.23639.1559918400700%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Jesse Glick updated JENKINS-46076 Jenkins / JENKINS-46076 Test flake in CpsThreadTest.stop Change By: Jesse Glick Status: Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184309.1502230337000.23635.1559918400654%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57914) SCM Polling uses last polled branch always
Title: Message Title Chris McIntosh created an issue Jenkins / JENKINS-57914 SCM Polling uses last polled branch always Issue Type: Bug Assignee: Vincent Latombe Components: pollscm-plugin Created: 2019-06-07 14:38 Priority: Minor Reporter: Chris McIntosh Similar to https://issues.jenkins-ci.org/browse/JENKINS-50168 and https://issues.jenkins-ci.org/browse/JENKINS-27327 BUT both of those tickets got distracted with the parameterized branch name, while the polling branch issue I think is distinct. Problem: When using pollscm in a pipeline job, the plugin will always poll with the branch that was configured on the last job run. Reproduction steps: Create an empty git repo Create a pipeline job file in the git repo on the master branch Create a branch off of master in the git repo Create a pipeline job in jenkins Configure your pipeline job to poll (every minute is usually good to test with) Configure your pipeline job to use the pipeline file you have checked in to master Run your job On your jenkins master vm navigate to the job folder E.G. /var/lib/jenkins/jobs/ (if you are using the default ubuntu package for instance) Validate that scm-polling.log is looking at your master branch Update your pipeline job in Jenkins to point to your second branch
[JIRA] (JENKINS-57579) New "unstable" step is not visualizing stage as unstable
Title: Message Title Devin Nusbaum updated JENKINS-57579 My PR was merged, but has not yet been released. Jenkins / JENKINS-57579 New "unstable" step is not visualizing stage as unstable 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199495.1558434359000.23595.1559917142322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum commented on JENKINS-57805 Re: Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Ok, considering that the PRs to core and workflow-api should fix the immediate problems described by this ticket, and that halting Pipeline execution is a bit more experimental and would require more time to investigate then I have at the moment, I filed JENKINS-57913 to track that as a separate improvement. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.23593.1559916840265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57913) Make errors thrown by CpsFlowExecution.getNode halt Pipeline execution
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-57913 Make errors thrown by CpsFlowExecution.getNode halt Pipeline execution Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-plugin Created: 2019-06-07 14:11 Labels: pipeline robustness Priority: Minor Reporter: Devin Nusbaum Spun out of JENKINS-57805 as a separate improvement. Because Pipeline lazily loads flow nodes as they are needed after a Jenkins restart, almost any caller of methods that end up traversing the flow graph and calling CpsFlowExecution.getNode may end up receiving an IOException due to an invalid FlowNode. Even if that caller is able to handle the error, the flow graph may be left in a corrupted state for other callers (i.e. if FlowNode.loadParents fails, we may have a node in the middle of the flow with no parents). Once the flow graph is corrupted, other callers may run into further issues when they manipulate/traverse the graph, especially because they might not see the original exception and will instead see corrupt/invalid data without necessarily realizing it. To avoid further issues, it seems safer to try to halt Pipeline execution when CpsFlowExecution.getNode throws an Exception to avoid compounding issues. Whether this can be done safely and in a way that actually improves the situation is not immediately obvious to me, and it would take some experimentation. A test case that can be adapted to reproduce this kind of problem can be found in https://github.com/jenkinsci/workflow-api-plugin/pull/94.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Daniel Beck commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher Mathieu Rousseau Well, did you click "Submit" right below test URL after entering credentials? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23580.1559916360296%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23564.1559916003780%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23553.1559916003445%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau commented on JENKINS-54903 Re: Updates through proxy server with authentication not working after update to core 2.152 or higher I have the same issue in 2.164.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23542.1559916003299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23531.1559916003178%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23520.1559916002946%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54903) Updates through proxy server with authentication not working after update to core 2.152 or higher
Title: Message Title Mathieu Rousseau updated an issue Jenkins / JENKINS-54903 Updates through proxy server with authentication not working after update to core 2.152 or higher Change By: Mathieu Rousseau Attachment: 003528.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195909.1543385478000.23500.1559915940516%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57805) Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance
Title: Message Title Devin Nusbaum updated JENKINS-57805 Jenkins / JENKINS-57805 Exception thrown from ExecutorStepExecution.PlaceHolderTask.getAffinityKey breaks Queue maintenance Change By: Devin Nusbaum 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199756.1559335134000.23449.1559915400571%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57912) Jenkins build fail with emulator issue
Title: Message Title
Ishan Kansara created an issue
Jenkins / JENKINS-57912
Jenkins build fail with emulator issue
Issue Type:
Bug
Assignee:
Christopher Orr
Components:
android-emulator-plugin
Created:
2019-06-07 13:40
Environment:
Jenkins version: 2.164.1 OS : Windows 10 Android emulator plugin : 3.0 JDK: 1.8.0 Browser: Chrome
Labels:
jenkins plugin windows
Priority:
Major
Reporter:
Ishan Kansara
// > git rev-parse "refs/remotes/origin/jenkins^{commit}" # timeout=10
> git rev-parse "refs/remotes/origin/refs/heads/jenkins^{commit}" # timeout=10
Checking out Revision 180d412c0dbee298a137ae1635b7269874cc5fdb (refs/remotes/origin/jenkins)
> git config core.sparsecheckout # timeout=10
> git checkout -f 180d412c0dbee298a137ae1635b7269874cc5fdb
Commit message: "Update gradle.properties"
> git rev-list --no-walk af1a52e8b891ee5d47b407a6bef5e75bb790d336 # timeout=10
No emails were triggered.
$ C:\Users\ishan\AppData\Local\Android\/tools/bin/avdmanager.bat list target
[android] Using Android SDK: C:\Users\ishan\AppData\Local\Android\
[android] Waiting 5 seconds before starting emulator...
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe start-server
* daemon not running; starting now at tcp:5863
* daemon started successfully
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe start-server
[android] Snapshots are enabled, but cannot be used as they are
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working
Title: Message Title Julie Shamji commented on JENKINS-57857 Re: Dashboard - 'Select subset of tools' not working Hi Ulli, I have done some further testing. If I remove all the charts, then add a chart with no subset, I see the chart with the correct numbers. If I think add another chart with a different name with a subset, the first chart displayed with the subset counts instead of all counts and the other is blank when that one should display what the first is displaying. So the issue is when multiple charts are configured on the same dashboard with different settings, the last one is used for the first chart and all other charts are blank. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199818.1559728494000.23438.1559913900097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Title: Message Title Emanuel Felipe Oliveira commented on JENKINS-28055 Re: Pipeline arrows are not displaying or displayed incorrectly Hello to all. What is the "correct" workaround to this issue. We also not remove or downgrade the plugin because of others dependencies... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162255.142976980.23427.1559913120350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Francesco Gualazzi edited a comment on JENKINS-53305
Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
A workaround we found with the Mailer plugin v 1.22 but same LTS version (2.121.3) .A workaround we found is to add the MIME types explicitly, like so{code}import javax.activation.MailcapCommandMap;import javax.activation.CommandMap;@NonCPSdef setupMail(){MailcapCommandMap mc = (MailcapCommandMap) CommandMap.getDefaultCommandMap();mc.addMailcap("text/html;; x-java-content-handler=com.sun.mail.handlers.text_html");mc.addMailcap("text/xml;; x-java-content-handler=com.sun.mail.handlers.text_xml");mc.addMailcap("text/plain;; x-java-content-handler=com.sun.mail.handlers.text_plain");mc.addMailcap("multipart/*;; x-java-content-handler=com.sun.mail.handlers.multipart_mixed");mc.addMailcap("message/rfc822;; x-java-content- handler=com.sun.mail.handlers.message_rfc822");}node {setupMail()mail( from: 'jenk...@co.com', replyTo: 'm...@co.com', to: some...@co.com,subject: "Hi there MIME", body: "It Works!")}{code}Hope this helps :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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193384.1535529489000.23413.1559912460351%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Francesco Gualazzi commented on JENKINS-53305
Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
A workaround we found with the same LTS version (2.121.3) is to add the MIME types explicitly, like so
import javax.activation.MailcapCommandMap;
import javax.activation.CommandMap;
@NonCPS
def setupMail(){
MailcapCommandMap mc = (MailcapCommandMap) CommandMap.getDefaultCommandMap();
mc.addMailcap("text/html;; x-java-content-handler=com.sun.mail.handlers.text_html");
mc.addMailcap("text/xml;; x-java-content-handler=com.sun.mail.handlers.text_xml");
mc.addMailcap("text/plain;; x-java-content-handler=com.sun.mail.handlers.text_plain");
mc.addMailcap("multipart/*;; x-java-content-handler=com.sun.mail.handlers.multipart_mixed");
mc.addMailcap("message/rfc822;; x-java-content- handler=com.sun.mail.handlers.message_rfc822");
}
node {
setupMail()
mail( from: 'jenk...@co.com',
replyTo: 'm...@co.com',
to: some...@co.com,
subject: "Hi there MIME",
body: "It Works!")
}
Hope this helps
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193384.1535529489000.23399.1559912280545%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57317) Exception when checking 'Validate S3 Bucket configuration'
Title: Message Title Baptiste Mathus commented on JENKINS-57317 Re: Exception when checking 'Validate S3 Bucket configuration' Facepalm. This is https://github.com/jenkins-infra/evergreen/pull/396 which I'm going to finally actually revert... Sorry about that 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199086.1556866104000.23351.1559907183537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.
Title: Message Title Nicola Kahale commented on JENKINS-12096 Re: ThinBackup Worker Thread thread is still running. Execution aborted. I'm running into this same issue and it's really causing a headache since it's causing Jenkin's to indefinitely be in a Quiet Down until manually cancelled. Jenkins Version: 2.164.3 ThinBackup Version: 1.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.142417.1323810533000.23375.1559907183975%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title jpschewe commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly More information. Found something else that is odd. On scan shows Checking branch current-release ‘Jenkinsfile’ found Met criteria No changes detected: current-release (still at d79cc62c7dc3e036229e8bd1adc5a8aab7f9aa57) The next scan shows Checking branch current-release ‘Jenkinsfile’ not found Does not meet criteria and this is the one that also says at the bottom that current-release is being removed. I haven't made any changes to the current release branch and it does in fact have a Jenkinsfile as can be seen by the next scan that says Checking branch current-release ‘Jenkinsfile’ found Met criteria Scheduled build for branch: current-release The repository for this Jenkins job is at https://github.com/jpschewe/fll-sw/ The last commit was February 4, 2019. This particular reset of the history was on June 3, 2019. I think I've had a reset between those two dates, but not since I started monitoring the scan log in May. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority
Title: Message Title ethorsa edited a comment on JENKINS-42679 Re: Allow lock retrieval based on requested priority There's a pending PR already: [ * PR#78 * |https://github.com/jenkinsci/lockable-resources-plugin/pull/78] Unfortunately it's stuck since months. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179631.1489173063000.23335.1559905560156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority
Title: Message Title ethorsa edited a comment on JENKINS-42679 Re: Allow lock retrieval based on requested priority There's a pending PR already: [ PR#78| https://github.com/jenkinsci/lockable-resources-plugin/pull/78] Unfortunately it's stuck since months. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179631.1489173063000.23331.1559905380181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title jpschewe commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly I'm using the github plugin for the source. For the others seeing this issue are you also using the github plugin for the source? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.23322.1559905320268%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42679) Allow lock retrieval based on requested priority
Title: Message Title ethorsa commented on JENKINS-42679 Re: Allow lock retrieval based on requested priority There's a pending PR already: https://github.com/jenkinsci/lockable-resources-plugin/pull/78 Unfortunately it's stuck since months. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179631.1489173063000.23318.1559905260157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57911) Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation
Title: Message Title LambdaTest Automation created an issue Jenkins / JENKINS-57911 Unable to Deploy Artefact on https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation Issue Type: Bug Assignee: LambdaTest Automation Attachments: permission-issue.png Components: lambdatest-automation-plugin Created: 2019-06-07 10:46 Priority: Blocker Reporter: LambdaTest Automation Getting lack of permission issue while deploying new artefact on repo.jenkins-ci.org [https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/lambdatest-automation ] Please advice Add Comment
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title jpschewe commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly I found a clue. I've been capturing the git index log and found a message in the log just before the the branch was rebuilt. [Mon Jun 03 10:39:07 EDT 2019] Finished branch indexing. Indexing took 7.5 sec Evaluating orphaned items in FLL-SW Will remove current-release as it is too old Finished: SUCCESS What is this message about the branch being too old? I want the branch jobs to stay around forever, unless the branch is deleted. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.23306.1559902740332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57664) On Release of a Version recieve a Null Pointer exception
Title: Message Title Vilppu Vuorinen commented on JENKINS-57664 Re: On Release of a Version recieve a Null Pointer exception After a single successful release the issue has resurfaced. I've now rolled back to 3.0.6 hoping I could get the releases rolling again. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199597.1558709739000.23303.1559902020128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57910) Connection with Testlink-Problem
Title: Message Title Deepika siddunuri created an issue Jenkins / JENKINS-57910 Connection with Testlink-Problem Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink-plugin Created: 2019-06-07 10:04 Environment: jenkins 2.164.2 TestLink Plugin 3.16 TestLink 1.9.19 Priority: Major Reporter: Deepika siddunuri After jenkins-testlink plugin when I click TestLink Results,I'm getting the following error org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-57909) JMX: VM and System metrics shouldn't be exported
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-57909 JMX: VM and System metrics shouldn't be exported Issue Type: Improvement Assignee: Unassigned Components: metrics-plugin Created: 2019-06-07 10:01 Priority: Minor Reporter: Vincent Latombe Currently, all metrics are exported through JMX. For VM and System metrics, it doesn't make sense, because they are already exported through standard JMX MBeans such as java.lang:Memory and java.lang:OperatingSystem Add Comment
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title Cyrille Le Clerc commented on JENKINS-42179 Re: withMaven doesn't discover the released artifacts when executing "mvn release" Robin Jansohn thanks for the update. We currently don't see a solution to operate without using JAVA_TOOLS_OPTIONS to pass parameters to forked maven processes (e.g. when performing "mvn release:prepare release:perform") 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179061.148752434.23291.1559900340303%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57908) Export JMX using a proper domain
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-57908 Export JMX using a proper domain Issue Type: Improvement Assignee: Unassigned Attachments: mbeans.png Components: metrics-plugin Created: 2019-06-07 09:38 Priority: Minor Reporter: Vincent Latombe The current JMX export for metrics is using the default DropWizard metrics API domain (which is 'metrics'). When connecting to a Jenkins instance using JMX, it is not obvious at all that the domain 'metrics' is in fact hosting Jenkins metrics. JMX best practices The domain part of an Object Name should start with a Java package name. This prevents collisions between MBeans coming from different subsystems. There might be additional text after the package name. Examples: Therefore, I propose to use io.jenkins as domain to expose metrics via JMX. Add Comment
[JIRA] (JENKINS-57907) Provide URL resource with GPG key of agent.jar
Title: Message Title
Anton Bronnikov updated an issue
Jenkins / JENKINS-57907
Provide URL resource with GPG key of agent.jar
Change By:
Anton Bronnikov
I want to create an automated script to deploy/configure Jenkins agent on a new machine. As per the [documentation ]( | https://wiki.jenkins.io/display/JENKINS/Distributed+builds#Distributedbuilds-Launchagentheadlesslyfromagentbacktomasteroncommandline ) ] : > {quote} A copy of agent.jar can be downloaded from http://yourserver:port/jnlpJars/agent.jar {quote} However, I would like to add a bit of extra security and verify the GPG key of the downloaded file. Therefore, I need Jenkins to provide this key at some other URL.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199872.1559899167000.23288.1559899320069%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57907) Provide URL resource with GPG key of agent.jar
Title: Message Title Anton Bronnikov created an issue Jenkins / JENKINS-57907 Provide URL resource with GPG key of agent.jar Issue Type: New Feature Assignee: Unassigned Components: core Created: 2019-06-07 09:19 Labels: slave Priority: Minor Reporter: Anton Bronnikov I want to create an automated script to deploy/configure Jenkins agent on a new machine. As per the [documentation](https://wiki.jenkins.io/display/JENKINS/Distributed+builds#Distributedbuilds-Launchagentheadlesslyfromagentbacktomasteroncommandline): > A copy of agent.jar can be downloaded from http://yourserver:port/jnlpJars/agent.jar However, I would like to add a bit of extra security and verify the GPG key of the downloaded file. Therefore, I need Jenkins to provide this key at some other URL. Add Comment
[JIRA] (JENKINS-57870) populate: previewOnly(quiet: true) fail
Title: Message Title
Karl Wirth updated an issue
Jenkins / JENKINS-57870
populate: previewOnly(quiet: true) fail
Change By:
Karl Wirth
Hi, When I use jenkins with swarm automated test,I use the pipeline code like{code:java}checkout perforce( populate: previewOnly(quiet: true) workspace: templateSpec( ... )){code}and template workspace have all depot like{code:java}//depotA/... //$P4_CLIENT/depotA/...//depotB/... //$P4_CLIENT/depotB/...//depotC/... //$P4_CLIENT/depotC/..{code}and I create new workspace and delete after finished job always. as you know, because I want to do likeunshelve files in the review item and run some test.I don't need sync, sync -n or sync -k and flush, delete, whatever.. here's error message. {code:java} [Pipeline] container[Pipeline] {[Pipeline] checkout* 02:02:57* (p4):cmd:... p4 client -o TEMPLATE__SE_SWARM_AT_SA TEMPLATE_SE_SWARM_AT_SA * 02:02:57* p4 client -o TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA * 02:02:57* * 02:02:57 * (p4):stop:3* 02:02:57* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:57* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:57* * 02:02:58 * (p4):stop:4* 02:02:58* (p4):cmd:... p4 client -i* 02:02:58* p4 client -i* 02:02:58* * 02:02:58 * Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved. * 02:02:58 * * 02:02:58 * (p4):stop:5* 02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* * 02:02:58 * (p4):stop:6* 02:02:58* (p4):cmd:... p4 client -i* 02:02:58* p4 client -i* 02:02:58* * 02:02:58 * Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z saved. * 02:02:58 * * 02:02:58 * (p4):stop:7* 02:02:58* (p4):cmd:... p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at- s___* s_ 02:02:58 * p4 client -f -s -t TEMPLATE__SE_SWARM_AT_SA TEMPLATESE_SWARM_AT_SA jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* * 02:02:58 * Client jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z switched. * 02:02:58 * * 02:02:58 * (p4):stop:8* 02:02:58* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:58* * 02:02:59 * (p4):stop:9* 02:02:59* (p4):cmd:... p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:59* p4 client -o jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z* 02:02:59* * 02:02:59 * (p4):stop:10* 02:02:59* (p4):cmd:... p4 counter change* 02:02:59* p4 counter change* 02:02:59* * 02:02:59 * (p4):stop:11* 02:02:59* (p4):cmd:... p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/. ___* _ 02:02:59 * p4 changes -m1 -ssubmitted //jenkins-SE-SWARM_AT_SA-21-se-swarm-at-sa-sv1sw-klt6z/... * 02:02:59 * *
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title Robin Jansohn commented on JENKINS-42179 Re: withMaven doesn't discover the released artifacts when executing "mvn release" Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear... EDIT: I fixed it by explicitly setting JAVA_TOOL_OPTIONS to empty value for that separate process. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179061.148752434.23280.155989752%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42179) withMaven doesn't discover the released artifacts when executing "mvn release"
Title: Message Title Robin Jansohn updated an issue Jenkins / JENKINS-42179 withMaven doesn't discover the released artifacts when executing "mvn release" Change By: Robin Jansohn Comment: Is there any way to suppress this output? One of our tests starts a separate java process and expects no output to appear... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179061.148752434.23282.1559897521333%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57906) Expand variables in 'Obtained Jenkinsfile from' line in console output
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57906 Expand variables in 'Obtained Jenkinsfile from' line in console output Change By: Karl Wirth Labels: P4_B 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199871.1559896179000.23277.1559896620187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56775) Parameters are not replaced in the "Stream Codeline" field
Title: Message Title Karl Wirth commented on JENKINS-56775 Re: Parameters are not replaced in the "Stream Codeline" field Hi Daniel Hoerner - Thanks for the confirmation. I've raised a new job for this and added Paul's and my comments - JENKINS-57906. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198419.1553681537000.23276.1559896620173%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57906) Expand variables in 'Obtained Jenkinsfile from' line in console output
Title: Message Title Karl Wirth commented on JENKINS-57906 Re: Expand variables in 'Obtained Jenkinsfile from' line in console output Have discussed this with Paul and it's part of the variable scope problem. There are a lot of variables that we have to jump through hoops to get at different times during the jobs. May not be possible to expand these variables for this message until something changes on the Jenkins side or we redesign how we connect to Jenkins. My 5c - Yes it would be good if we can expand these variables but the message is useful for debugging so I would prefer to keep the 'Obtained Jenkinsfile from' at this position in the code even if we are not able to expand variables at this point. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199871.1559896179000.23273.1559896500185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57905) Build Flow Job unable to save build
Title: Message Title Gopal Ahir updated an issue Jenkins / JENKINS-57905 Build Flow Job unable to save build Change By: Gopal Ahir Hi Team,Recently we have upgraded our jenkins from 2.19.3 to 2.164.1.After that whenever we run any build flow job, the job is completing successfully but jenkins is not able to save it on UI. During next jenkins restart or next day the job is getting removed from build history. Build flow plugin version is 0.20. Below are the error logs from jenkins server. Jun 07, 2019 3:37:57 PM hudson.model.Run executeINFO: Gopal-test-BuildFlow #2 main build action completed: SUCCESSJun 07, 2019 3:37:57 PM hudson.model.Run executeSEVERE: Failed to save build recordjava.io.IOException: java.lang.RuntimeException: Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2012) at hudson.model.Run.execute(Run.java:1873) at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.lang.RuntimeException: Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun 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.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:193) ... 5 moreCaused by: java.lang.RuntimeException: Failed to serialize com.cloudbees.plugins.flow.JobInvocation#lock for class com.cloudbees.plugins.flow.JobInvocation$Start at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at
[JIRA] (JENKINS-57906) Expand variables in 'Obtained Jenkinsfile from' line in console output
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-57906
Expand variables in 'Obtained Jenkinsfile from' line in console output
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-06-07 08:29
Environment:
p4-plugin 1.10.0
Priority:
Minor
Reporter:
Karl Wirth
Here it is, this is the very beginning of the console log:
Started by user **
Obtained Jenkinsfile from p4-Perforce-${P4_DEPOT}/${P4_STREAM}
Expected:
Started by user **
Obtained Jenkinsfile from p4-Perforce-MyReplacedDepotName/MyReplacedStream
[JIRA] (JENKINS-57905) Build Flow Job unable to save build
Title: Message Title jay yap commented on JENKINS-57905 Re: Build Flow Job unable to save build I also facing the same issue for the Build Flow Job unable to save build error. then the job history some of it went missing appear in Jenkins website. I only encounter on this plugin issue only. Is there got any solution on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199870.1559894727000.23268.1559895420129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51791) git polling fails to detect changes when build uses multiple repos
Title: Message Title Jan Pesta commented on JENKINS-51791 Re: git polling fails to detect changes when build uses multiple repos Hi all, I just later find out that pooling is behaving little different according to variable resolutions when used this notation for checkout: [[name: '*/branchVariable']] to [[name: '*/'+branchVariable]] In first case, checkout works, becase variable resolution is done properly in checkout, but in case of pooling it is trying to find branch with name branchVariable which is not existing. Second case works for checkout and pooling. Hope this help. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191239.1528398073000.23262.1559895003661%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57904) unzip cannot overwrite read-only files
Title: Message Title
Werner Wessely updated an issue
Jenkins / JENKINS-57904
unzip cannot overwrite read-only files
Change By:
Werner Wessely
When trying to unzip a file which already exists and is read-only, the unzip step fails.Happens on Linux and Windows slaves.Tested with:{code:java}node(" atgraz278 my_node "){ sh("touch file.txt")sh("rm -f file.zip")zip(zipFile: "file.zip")sh("chmod -w file.txt")unzip(zipFile: "file.zip")}{code}I get the following output in blue ocean:{code:java}Extracting from /data/jenkins/workspace/ZipTest/file.zipExtracting: file.txt -> /data/jenkins/workspace/ZipTest/file.txt/data/jenkins/workspace/ZipTest/file.txt{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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199869.1559894553000.23254.1559894820396%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44414) Lost ssh connection is not recognized
Title: Message Title Markus Winter resolved as Fixed fixed Jenkins / JENKINS-44414 Lost ssh connection is not recognized Change By: Markus Winter 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182240.1495451398000.23249.1559894760731%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57905) Build Flow Job unable to save build
Title: Message Title Gopal Ahir created an issue Jenkins / JENKINS-57905 Build Flow Job unable to save build Issue Type: Bug Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2019-06-07 08:05 Environment: Production Labels: build-flow Priority: Critical Reporter: Gopal Ahir Hi Team, Recently we have upgraded our jenkins from 2.19.3 to 2.164.1. After that whenever we run any build flow job, the job is completing successfully but jenkins is not able to save it on UI. During next jenkins restart or next day the job is getting removed from build history. Below are the error logs from jenkins server. Jun 07, 2019 3:37:57 PM hudson.model.Run execute INFO: Gopal-test-BuildFlow #2 main build action completed: SUCCESS Jun 07, 2019 3:37:57 PM hudson.model.Run execute SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun at hudson.XmlFile.write(XmlFile.java:200) at hudson.model.Run.save(Run.java:2012) at hudson.model.Run.execute(Run.java:1873) at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:155) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.RuntimeException: Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at
[JIRA] (JENKINS-57904) unzip cannot overwrite read-only files
Title: Message Title
Werner Wessely updated an issue
Jenkins / JENKINS-57904
unzip cannot overwrite read-only files
Change By:
Werner Wessely
When trying to unzip a file which already exists and is read-only, the unzip step fails.Happens on Linux and Windows slaves.Tested with:{code:java}node("atgraz278"){ sh("touch file.txt")sh("rm -f file.zip")zip(zipFile: "file.zip")sh("chmod -w file.txt")unzip(zipFile: "file.zip")}{code} I get the following output in blue ocean:{code:java}Extracting from /data/jenkins/workspace/ZipTest/file.zipExtracting: file.txt -> /data/jenkins/workspace/ZipTest/file.txt/data/jenkins/workspace/ZipTest/file.txt{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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199869.1559894553000.23244.1559894760658%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45095) retrigger doesn't work when deleting build from Queue
Title: Message Title Markus Winter resolved as Fixed was fixed in 2.25.0 Jenkins / JENKINS-45095 retrigger doesn't work when deleting build from Queue Change By: Markus Winter 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183189.1498203664000.23240.1559894700529%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57904) unzip cannot overwrite read-only files
Title: Message Title
Werner Wessely created an issue
Jenkins / JENKINS-57904
unzip cannot overwrite read-only files
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2019-06-07 08:02
Environment:
Jenkins ver. 2.177 Pipeline: Basic Steps ver. 2.16
Priority:
Minor
Reporter:
Werner Wessely
When trying to unzip a file which already exists and is read-only, the unzip step fails. Happens on Linux and Windows slaves. Tested with:
node("atgraz278")
{
sh("touch file.txt")
sh("rm -f file.zip")
zip(zipFile: "file.zip")
sh("chmod -w file.txt")
unzip(zipFile: "file.zip")
}
Add Comment
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Ananda lahari Bhavaraju commented on JENKINS-54557 Re: hudson.AbortException: Ansible playbook execution failed I got the same issue. But I found a work around in my case. I wrote a rescue block in the end of my playbook to ensure that the pipeline continues execution Then I enabled ansible log in ansible configuration file. I wrote a python snippet to parse my ansible configuration and create retry file.( based on fail >0) This way we can ensure that the pipeline execution doesn't stop. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195333.1541773391000.23236.1559894221200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57901) Concurrent Pipeline builds report all changes since last completed build
Title: Message Title Karl Wirth commented on JENKINS-57901 Re: Concurrent Pipeline builds report all changes since last completed build Hi William Brode - Thanks for highlighting this. To help me test this, do the concurrent jobs have unique workspace names?For example are you including 'EXECUTOR_NUMBER' in the workspace name and can you see in the job output that a different workspace is used in each? Also are both jobs running on the same slave node or in a unique node (such as a docker container)? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199866.1559866894000.23200.1559892720159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57901) Concurrent Pipeline builds report all changes since last completed build
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57901 Concurrent Pipeline builds report all changes since last completed build Change By: Karl Wirth Assignee: Karl Wirth 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199866.1559866894000.23202.1559892720197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Prastik Gyawali started work on JENKINS-57903 Change By: Prastik Gyawali 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199868.1559891975000.23198.1559892060206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57903) New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin.
Title: Message Title Prastik Gyawali created an issue Jenkins / JENKINS-57903 New PromotionProcess,PromotionCondition and PromotionConditionDescriptor classes for the plugin. Issue Type: Task Assignee: Prastik Gyawali Components: promoted-builds-plugin Created: 2019-06-07 07:19 Labels: gsoc-2019 gsoc2019-artifact-promotion-in-pipeline Priority: Minor Reporter: Prastik Gyawali Before implementing the promotion-conditions(Self and Manual Conditions), it seems necessary to build new abstract/classes for the following existing classes. PromotionProcess PromotionCondition PromotionConditionDescriptor For readability ease all these classes are being added by the word "Pipeline" as their prefix. Three new analogous classes are being made retaining some of the original functions and will timely be updated as other classes start depending on them.
[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title
Elie Kassis edited a comment on JENKINS-55616
Re: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
[~abayer], we are facing an issue after upgrading jenkins and several plugins.All executePostBuild are failing with below error. +Potential guilty plugin+ pipeline-model-definition -> Guilty issue: JENKINS-56402*Pipeline: Model API* ==> current version 1.3.8 ==> old version 1.3.4.1 Can you please assist ? {code:java}hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@4e4c0304), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Prepare Debug Job, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@193f4d75), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Push Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@889e600, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@142cbef4), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Retry Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@1fbed651, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@15f20b8e), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Profile, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@8b9d24e, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6689d642), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Parsing, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@40674bbf, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@11bed30b), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Archiving, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@57800d78, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@5ca25f43), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([failure:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@577ff6e2),
[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title Elie Kassis commented on JENKINS-55616 Re: hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage() we are facing an issue after upgrading jenkins and several plugins. All executePostBuild are failing with below error. Can you please assist ? hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() is applicable for argument types: (org.jenkinsci.plugins.pipeline.modeldefinition.model.Root) values: [org.jenkinsci.plugins.pipeline.modeldefinition.model.Root(org.jenkinsci.plugins.pipeline.modeldefinition.model.Agent(org.jenkinsci.plugins.workflow.cps.CpsClosure2@4e4c0304), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stages([org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Prepare Debug Job, null, null, null, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@193f4d75), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Push Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@889e600, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@142cbef4), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Retry Debug, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@1fbed651, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@15f20b8e), null, [], null, false, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageOptions(), null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Profile, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@8b9d24e, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@6689d642), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Parsing, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@40674bbf, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@11bed30b), null, [], null, false, null, null), org.jenkinsci.plugins.pipeline.modeldefinition.model.Stage(Archiving, null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StageConditionals(org.jenkinsci.plugins.workflow.cps.CpsClosure2@57800d78, false, false), null, null, org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@5ca25f43), null, [], null, false, null, null)]), org.jenkinsci.plugins.pipeline.modeldefinition.model.MappedClosure([failure:org.jenkinsci.plugins.pipeline.modeldefinition.model.StepsBlock(org.jenkinsci.plugins.workflow.cps.CpsClosure2@577ff6e2),
[JIRA] (JENKINS-55616) hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage()
Title: Message Title Elie Kassis updated an issue Jenkins / JENKINS-55616 hudson.remoting.ProxyException: groovy.lang.MissingMethodException: No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.evaluateStage() Change By: Elie Kassis Priority: Minor Blocker 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196787.1547637213000.23190.1559890920471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project (Community Bonding)
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-57437 Update jenkins.io page for the Role Strategy GSoC 2019 project (Community Bonding) Change By: Abhyudaya Sharma Summary: Update jenkins.io page for the Role Strategy GSoC 2019 project (Community Bonding) Sprint: GSoC 2019. Community Bonding , GSoC 2019. Coding Phase 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.23180.1559889480130%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57425) Implement JMH benchmark in pull request build
Title: Message Title Abhyudaya Sharma updated JENKINS-57425 Jenkins / JENKINS-57425 Implement JMH benchmark in pull request build Change By: Abhyudaya Sharma Resolution: Postponed Status: Fixed but Unreleased Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199237.1557740286000.23175.1559889000453%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
