[JIRA] (JENKINS-57851) Jenkins redirect from bitbucket results in broken link
Title: Message Title chetan muthappa commented on JENKINS-57851 Re: Jenkins redirect from bitbucket results in broken link issue was solved by installing following plugins: blueocean-commons blueocean-core-js blueocean-jwt blueocean-rest blueocean-web please close ticket Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199809.1559686662000.3425.1562390820224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58368) Fix build status reporting
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58368 Fix build status reporting Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-06 03:55 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58270) Removing extra log `looking up repo` in pipeline job indexing
Title: Message Title Parichay Barpanda resolved as Fixed Fixed. Jenkins / JENKINS-58270 Removing extra log `looking up repo` in pipeline job indexing Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200334.1561860878000.3421.1562384700263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58270) Removing extra log `looking up repo` in pipeline job indexing
Title: Message Title Parichay Barpanda started work on JENKINS-58270 Change By: Parichay Barpanda 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.200334.1561860878000.3420.1562384700139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58365) No public field projectUrl in GitLab Browser
Title: Message Title
Parichay Barpanda resolved as Fixed
Fixed it by adding a getter method for projectUrl:
public String getProjectUrl() {
return super.getRepoUrl();
}
Jenkins / JENKINS-58365
No public field projectUrl in GitLab Browser
Change By:
Parichay Barpanda
Status:
In Progress Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web
[JIRA] (JENKINS-58365) No public field projectUrl in GitLab Browser
Title: Message Title Parichay Barpanda started work on JENKINS-58365 Change By: Parichay Barpanda 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.200480.1562344338000.3418.1562384580072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION no longer set in git plugin 4.0.0-rc
Title: Message Title Mark Waite updated JENKINS-56176 Jenkins / JENKINS-56176 GIT_REVISION no longer set in git plugin 4.0.0-rc Change By: Mark Waite Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197715.155047453.3408.1562370540646%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56010) Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin
Title: Message Title Mark Waite edited a comment on JENKINS-56010 Re: Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin Fixed in [Git plugin 4.0.0-beta10|https://github.com/jenkinsci/git-plugin/releases/tag/git-4.0.0-beta10] released July 5, 2019. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.197428.154949840.3413.1562370540750%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-57603 Git Plugin: No JCasC configurator for Submodule configurations Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199528.1558527868000.3402.1562370480800%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57603) Git Plugin: No JCasC configurator for Submodule configurations
Title: Message Title Mark Waite updated JENKINS-57603 Fixed in Git plugin 4.0.0-beta10 released July 5, 2019 and in Git plugin 3.10.1 released July 5, 2019. Jenkins / JENKINS-57603 Git Plugin: No JCasC configurator for Submodule configurations Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199528.1558527868000.3399.1562370480738%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION no longer set in git plugin 4.0.0-rc
Title: Message Title Mark Waite closed an issue as Fixed Fixed in Git plugin 4.0.0-beta10 released July 5, 2019. Jenkins / JENKINS-56176 GIT_REVISION no longer set in git plugin 4.0.0-rc Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197715.155047453.3404.1562370480860%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Mark Waite edited a comment on JENKINS-51638 Re: No Enum Constant Found - Default PreBuildMerge Failure Fixed in [Git plugin 4.0.0-beta10|https://github.com/jenkinsci/git-plugin/releases/tag/git-4.0.0-beta10] released July 5, 2019 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.191051.152777579.3394.1562370363731%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite updated JENKINS-57683 Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.3396.1562370363759%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Mark Waite updated JENKINS-51638 Fixed in Git plugin 4.0.0-beta10 Jenkins / JENKINS-51638 No Enum Constant Found - Default PreBuildMerge Failure Change By: Mark Waite Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191051.152777579.3358.1562370363270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite updated JENKINS-57683 Fixed in Git plugin 4.0.0-beta10 released July 5, 2019 Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199618.155881147.3395.1562370363741%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Mark Waite updated JENKINS-51638 Jenkins / JENKINS-51638 No Enum Constant Found - Default PreBuildMerge Failure Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191051.152777579.3371.1562370363450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56010) Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin
Title: Message Title Mark Waite closed an issue as Fixed Fixed in Git plugin 4.0.0-beta10 Jenkins / JENKINS-56010 Git Plugin v4.0.0-rc breaks Git-Tag-Message-Plugin Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197428.154949840.3351.1562370240407%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54997) Deprecated calls to Run.getLogFile
Title: Message Title Kayvan Sylvan commented on JENKINS-54997 Re: Deprecated calls to Run.getLogFile Similar failure here: 2019-07-04 21:37:11.446+ [id=17764] WARNING o.j.p.workflow.job.WorkflowRun#getLogFile: Avoid calling getLogFile on Gibraltar/Feature_Onboard_Infra #163 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1085) at hudson.plugins.timestamper.io.LogFileReader.nextLine(LogFileReader.java:157) at hudson.plugins.timestamper.action.TimestampsActionOutput$1.readNextLine(TimestampsActionOutput.java:173) at hudson.plugins.timestamper.action.TimestampsActionOutput$1.read(TimestampsActionOutput.java:132) at java.io.BufferedReader.fill(BufferedReader.java:161) at java.io.BufferedReader.readLine(BufferedReader.java:324) at java.io.BufferedReader.readLine(BufferedReader.java:389) at hudson.plugins.timestamper.action.TimestampsAction.doIndex(TimestampsAction.java:102) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.IndexDispatcher.dispatch(IndexDispatcher.java:27) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:456) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title Bryan Leung edited a comment on JENKINS-36877 Re: Can't select credentials I have this problem too where I created the account but I can't see it in the drop down menu. I went to global credentials and can verify that it was created. Testing shows it's connected. I just can't find it in the dropdown.å!Screen Shot 2019-07-05 at 2.15.49 PM.png|width=407,height=148!Also please update the docs, I find them very helpful when I follow along.I also see that my key that I connected to Jenkins but can't see in the AWS IAM dashboard was recently used. So it's connected, just can't see it in the dropdown. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.172927.1469193114000.3330.1562362320187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title Bryan Leung edited a comment on JENKINS-36877 Re: Can't select credentials I have this problem. I enter also see that my access and secret keys. key that I test connected to Jenkins but can't see in the connection and AWS IAM dashboard was recently used. So it's fine. But then connected, just can't find that credential see it in the drop down menu but if I go into global credentials, I do find that it was added dropdown . !Screen Shot 2019-07-05 at 2.15.49 PM.png|width=458,height=167!Also update the wiki guide please! It's very helpful for me to follow good documentation! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172927.1469193114000.3325.1562362140480%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1878) Ability to move job to top of queue
Title: Message Title Kayvan Sylvan commented on JENKINS-1878 Re: Ability to move job to top of queue Very important for us as well. I don't believe the Accelerated Build Now plugin works. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.131951.1213683192000.3263.1562361961348%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title Bryan Leung updated an issue Jenkins / JENKINS-36877 Can't select credentials Change By: Bryan Leung Attachment: Screen Shot 2019-07-05 at 2.15.49 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172927.1469193114000.3256.1562361900355%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36877) Can't select credentials
Title: Message Title Bryan Leung commented on JENKINS-36877 Re: Can't select credentials I have this problem. I enter my access and secret keys. I test the connection and it's fine. But then can't find that credential in the drop down menu but if I go into global credentials, I do find that it was added. Also update the wiki guide please! It's very helpful for me to follow good documentation! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172927.1469193114000.3259.1562361900439%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58367) cwd set by exws set is replaced by withEnv and withCredentials steps
Title: Message Title
Claudiu Avatamanitei updated an issue
Jenkins / JENKINS-58367
cwd set by exws set is replaced by withEnv and withCredentials steps
Change By:
Claudiu Avatamanitei
Hi, I am experiencing an unexpected change of the current working directory when withEnv or with withCredentials steps are used.dir step is a viable workaround, but I am wondering if there is a more straightforward explanation and solution.Thank you! --- — def extWorkspace = exwsAllocate diskPoolId: 'workspace-pool', strategy: fastestWriteSpeed()stage('init') { node('brenode') { println pwd() //prints local workspace (_${JENKINS_HOME}/workspace/${JOB_NAME}_) exws (extWorkspace) { println pwd() //prints external workspace _${physical_path}/${JOB_NAME}/${BUILD_NUMBER}_ withEnv(["1=1"]) { { println pwd() //prints again local workspace! } } }}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.200483.1562361096000.3251.1562361180131%40Atlassian.JIRA.
For more options, visit
[JIRA] (JENKINS-58367) cwd set by exws set is replaced by withEnv and withCredentials steps
Title: Message Title
Claudiu Avatamanitei created an issue
Jenkins / JENKINS-58367
cwd set by exws set is replaced by withEnv and withCredentials steps
Issue Type:
Bug
Assignee:
Alexandru Somai
Components:
external-workspace-manager-plugin, workflow-basic-steps-plugin
Created:
2019-07-05 21:11
Environment:
JENKINS_VERSION 2.176.1 external-workspace-manager 1.1.2 workflow-basic-steps 2.18
Priority:
Major
Reporter:
Claudiu Avatamanitei
Hi, I am experiencing an unexpected change of the current working directory when withEnv or with steps are used. dir step is a viable workaround, but I am wondering if there is a more straightforward explanation and solution. Thank you! — def extWorkspace = exwsAllocate diskPoolId: 'workspace-pool', strategy: fastestWriteSpeed() stage('init') { node('brenode') { println pwd() //prints local workspace (${JENKINS_HOME}/workspace/${JOB_NAME}) exws (extWorkspace) { println pwd() //prints external workspace ${physical_path}/${JOB_NAME}/${BUILD_NUMBER} withEnv(["1=1"]) { println pwd() //prints again local workspace! } } } }
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Devin Nusbaum updated JENKINS-31314 A fix for this issue was released in Pipeline: Groovy Plugin version 2.71. Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: workflow-cps 2.71 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.166049.1446212529000.3224.1562360821529%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56682 Unable to use initializers in sandboxed Groovy scripts Change By: Devin Nusbaum Component/s: workflow-cps-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.198319.1553261135000.3218.1562360760221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title Devin Nusbaum commented on JENKINS-56682 Re: Unable to use initializers in sandboxed Groovy scripts A fix for this issue in Pipeline scripts was released in Pipeline: Groovy Plugin version 2.71. A fix for this issue in other kinds of sandboxed Groovy scripts was released in Script Security Plugin 1.61. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.198319.1553261135000.3210.1562360700568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56682 Unable to use initializers in sandboxed Groovy scripts Change By: Devin Nusbaum Released As: script-security 1.61 , workflow-cps 2.71 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.198319.1553261135000.3200.1562360640262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Ulli Hafner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration This is not possible. Can't you add parsers using JCasC? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.192001.1530178828000.3191.1562360100197%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58351) buildType is used incorrectly for visual studio builds
Title: Message Title Martin Weber commented on JENKINS-58351 Re: buildType is used incorrectly for visual studio builds Would it be possible to add this as an improvement to the plugin? Ie, when a visual studio generator is set to the generator property use config instead of CMAKE_BUILD_TYPE or would this be too custom? I do not think an implementation will be easy, and if so, be of much use. Remember, users may enter an arbritrary value for the build type (this is because users may define custom build-types in their CMakeLists.txt). Therefore, it is not possible to define a mapping of (in effect with the Makefiles generator on linux) to --config (in effect with the VS generator on windows) in the plugin. Of course, the plugin could offer a way to define that mapping in its UI to solve the problem. But such an UI would be confusing to users and the pipeline UI is text based; making the cmakeBuild invocation code nearly unreadable if someone uses the snippet generator. Apart the mapping problem, my other concerns on implementing the improvement are It would require to build up a knowledge base that tracks which generator needs the CMAKE_BUILD_TYPE variable at script generation time, which generator needs an extra option to specify the build-type at build time and what the name of the option is. Maintenance effort of that knowledge base (Permanent maintenance is required in case cmake comes with new generators). Another obstacle: Users may specify an empty value for the generator, leaving the generator choice to cmake, depending on the OS your code is build on. Could be solved by an extra knowledge base that tracks cmake's default generator choice. Until a problem with a future revision of cmake that switches to a different default generator, which again could be solved by a permanently maintained knowledge base. Citations: Chuck Berry: Too much monkey business. Kevlin Henney: Except for the problem of too many layers of indirection Add Comment
[JIRA] (JENKINS-58094) mTLS client certificates broken in 2.176.1+ by changes in jetty
Title: Message Title Michael DeGuzis commented on JENKINS-58094 Re: mTLS client certificates broken in 2.176.1+ by changes in jetty I wonder if this is also affecting our failure to bind to active directory using the JDK Trustore option of Jenkins > Configure Global Security > Security Ream > Active Directory > TLS Configuration. simple bind failed: LDAP_HOST:636 sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at sun.security.provider.certpath.SunCertPathBuilder.build(SunCertPathBuilder.java:141) at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:126) at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:280) at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:392) Caused: sun.security.validator.ValidatorException: PKIX path building failed at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:397) at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:302) at sun.security.validator.Validator.validate(Validator.java:262) at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:324) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:229) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1621) Caused: javax.net.ssl.SSLHandshakeException at sun.security.ssl.Alerts.getSSLException(Alerts.java:192) at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1946) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:316) at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:310) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1639) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:223) at sun.security.ssl.Handshaker.processLoop(Handshaker.java:1037) at sun.security.ssl.Handshaker.process_record(Handshaker.java:965) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1064) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367) at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:750) at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:443) at com.sun.jndi.ldap.Connection.writeRequest(Connection.java:416) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:359) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:214 As soon as I downgrade to 2.164.3, things work fine again. I setup a QA/Test master with only the Active Directory plugin. Thoughts?
[JIRA] (JENKINS-52884) durable-task-plugin 1.23 powershell step does not return exit code other than 0 or 1
Title: Message Title Devin Nusbaum updated JENKINS-52884 A fix for this issue was just released in version 1.30 of Durable Task Plugin. Jenkins / JENKINS-52884 durable-task-plugin 1.23 powershell step does not return exit code other than 0 or 1 Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: durable-task 1.30 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.192823.1533344703000.3182.1562354640661%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Jesse Glick started work on JENKINS-33217 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.168598.1456760629000.3174.1562353140496%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Jesse Glick updated JENKINS-33217 Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Jesse Glick 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.168598.1456760629000.3177.1562353140586%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56682) Unable to use initializers in sandboxed Groovy scripts
Title: Message Title Devin Nusbaum updated JENKINS-56682 Jenkins / JENKINS-56682 Unable to use initializers in sandboxed Groovy scripts Change By: Devin Nusbaum Status: In Review Fixed but Unreleased Resolution: Fixed Released As: script-security 1.61 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.198319.1553261135000.3167.1562353020436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47430) SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock
Title: Message Title Devin Nusbaum updated JENKINS-47430 A fix for this issue was release in version 1.61 of Script Security Plugin. Jenkins / JENKINS-47430 SandboxResolvingClassLoader use of Guava cache can cause classloading bottleneck/deadlock Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: script-security 1.61 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.185876.1507914808000.3164.1562352960280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58228) CLI usage doesn't work if typo in args
Title: Message Title Natasha Stopa updated JENKINS-58228 Fix merged into master. Jenkins / JENKINS-58228 CLI usage doesn't work if typo in args Change By: Natasha Stopa 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.200288.156159164.3162.1562352360091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58076) Make Default Settings More Generalizable
Title: Message Title Natasha Stopa updated an issue Jenkins / JENKINS-58076 Make Default Settings More Generalizable Change By: Natasha Stopa In [https://github.com/jenkinsci/plugin-installation-manager-tool/pull/3], Oleg mentioned that the current defaults might not be sustainable for environments outside of Docker images. How to change these settings to make them more generalizable needs to be investigated. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200101.1560874848000.3161.1562351880058%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58121) Use -- for long flags
Title: Message Title Natasha Stopa updated JENKINS-58121 Fixed and merged in with https://github.com/jenkinsci/plugin-installation-manager-tool/pull/24 Jenkins / JENKINS-58121 Use -- for long flags Change By: Natasha Stopa 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.200166.1561046126000.3159.1562351820370%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58366) Please add repository URL to currentBuild environment variables for declarative pipeline builds
Title: Message Title Kai Hofmann created an issue Jenkins / JENKINS-58366 Please add repository URL to currentBuild environment variables for declarative pipeline builds Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-07-05 18:22 Environment: Windows, Linux, MacOS, subversion, git, Labels: pipeline-environment repository url git subversion Priority: Trivial Reporter: Kai Hofmann I would like to have a release stage in my Jenkinsfile that only runs when it's checked out from the original repository. This is to avoid error messages on cloned repositories, because of missing keys etc. there. Please see my stackoverflow posting for more: https://stackoverflow.com/questions/56899602/is-it-possible-to-check-if-checked-out-from-a-specific-repository-in-a-jenkins-d As it looks from the responses this would be a feature request to have a solution that is independend of the version control system, because Jenkins itself knowns the version control system and the url. So it should be easily possible to mage the repository url availabe as currentBuild environment variable. Which will allow to have a release stage that only would be executed from the original repository.
[JIRA] (JENKINS-58104) Make Update Center Values Configurable
Title: Message Title Natasha Stopa updated JENKINS-58104 PR merged into master branch. Jenkins / JENKINS-58104 Make Update Center Values Configurable Change By: Natasha Stopa 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.200147.1560972534000.3153.1562350920097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Jesse Glick resolved as Fixed Pierre Larsson this is fixed. What you show is a warning, not an error, about a bug in some plugin. From the log excerpt quoted it is impossible to tell which. Could probably use XmlFile.writing to help diagnose this if it is not obvious from context, but that would be a follow-up diagnostics Enhancement. Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: Jesse Glick Status: Reopened 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
[JIRA] (JENKINS-57502) Cmake arguments sometimes are added to path in parallel build
Title: Message Title Martin Weber closed an issue as Cannot Reproduce Jenkins / JENKINS-57502 Cmake arguments sometimes are added to path in parallel build Change By: Martin Weber Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199365.1557999255000.3144.1562349720171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58350) Move the plugins used for test to /test/resources
Title: Message Title Natasha Stopa updated JENKINS-58350 Fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/26#pullrequestreview-258272167 Jenkins / JENKINS-58350 Move the plugins used for test to /test/resources Change By: Natasha Stopa 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.200465.1562254212000.3142.1562348580230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33217) DescribableHelper does not detect stray parameters
Title: Message Title Carroll Chiou assigned an issue to Carroll Chiou Jenkins / JENKINS-33217 DescribableHelper does not detect stray parameters Change By: Carroll Chiou Assignee: Jesse Glick Carroll Chiou Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.168598.1456760629000.3139.1562347920254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31838) Virtual thread dump uses phony filenames
Title: Message Title Devin Nusbaum commented on JENKINS-31838 Re: Virtual thread dump uses phony filenames Noting that there are some cases where when someone extends CpsScript you can end up with a stack trace like the following: at MyScript.(WorkflowScript:3) See this comment thread for context. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.166776.1449009717000.3134.1562346480200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58365) No public field projectUrl in GitLab Browser
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58365 No public field projectUrl in GitLab Browser Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-05 16:32 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda While branches are being built I am getting the following error by workflow-cps: Jul 05, 2019 8:01:37 PM org.jenkinsci.plugins.structs.describable.DescribableParameter uncoerce WARNING: failed to uncoerce io.jenkins.plugins.gitlabbranchsource.helpers.GitLabBrowser@736b3e2d java.lang.UnsupportedOperationException: no public field ‘projectUrl’ (or getter method) found in class io.jenkins.plugins.gitlabbranchsource.helpers.GitLabBrowser at org.jenkinsci.plugins.structs.describable.DescribableParameter.getValue(DescribableParameter.java:161) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:609) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2_(DescribableModel.java:706) at org.jenkinsci.plugins.structs.describable.DescribableParameter.uncoerce(DescribableParameter.java:196) at org.jenkinsci.plugins.structs.describable.DescribableParameter.inspect(DescribableParameter.java:142) at org.jenkinsci.plugins.structs.describable.DescribableModel.uninstantiate2(DescribableModel.java:609) at
[JIRA] (JENKINS-58261) GitLab branch source server field not working
Title: Message Title Parichay Barpanda resolved as Fixed Resolved in c503cd5 of feature/branch-source branch. Jenkins / JENKINS-58261 GitLab branch source server field not working Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200325.1561793952000.3130.1562344200206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58268) Add necessary dependencies to run pipeline jobs with mvn hpi:run
Title: Message Title Parichay Barpanda resolved as Fixed Fixed by adding test scope of workflow step api. Jenkins / JENKINS-58268 Add necessary dependencies to run pipeline jobs with mvn hpi:run Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200332.1561858768000.3128.1562344080104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum resolved as Fixed Given the core changes have been released, I am closing this issue. As noted in my blog post, if you are still having problems with a Pipeline step from specific please file a new issue with the component set to that plugin (after checking for duplicates), clearly describing which step has the problem and under what circumstances it occurs, and link to the developers section of the post as a reference for how the maintainer might be able to address the problem. Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Devin Nusbaum Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Devin Nusbaum Released As: Blue Ocean 1.17.0, Pipeline: API 2.34, Pipeline: Basic Steps 2. 16 18 , Pipeline: Graph Analysis 1.10, Pipeline: Groovy 2.70, Pipeline: Declarative 1.3.9, JUnit: 1.28 , Warnings Next Generation 5.2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2654.1562343426150%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should I just published a blog post with an overview of this issue and how to take advantage of the recent changes in your Pipeline to improve the way it is visualized in Blue Ocean: https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/. Chris Burroughs Yes, feel free to open a new issue for Stage View integration and link it to this one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2417.1562343305531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42450) Efficiently add a single repo to a github org without requiring a full scan
Title: Message Title Leandro Lucarella commented on JENKINS-42450 Re: Efficiently add a single repo to a github org without requiring a full scan How was this fixed exactly? I still can't find any way to trigger a discovery on a new project without going through a whole organization scan, which for us is horribly slow and it exhausts all the GitHub API rate limit. Each time a new project is created, we basically have to wait for a day to see it in Jenkins... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179362.1488506928000.2413.1562342940211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58364) Default jenkins.war path only supports *NIX style paths
Title: Message Title Alex Earl created an issue Jenkins / JENKINS-58364 Default jenkins.war path only supports *NIX style paths Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-05 16:00 Priority: Minor Reporter: Alex Earl I am looking at incorporating this tool for the Jenkins Windows Docker image. Currently, the default war path is hard coded to a UNIX style path (https://github.com/jenkinsci/plugin-installation-manager-tool/blob/072aae7105cad8b74f769fd93c2ec3f797629863/plugin-management-library/src/main/java/io/jenkins/tools/pluginmanager/config/Settings.java#L9). It would be nice if it would do a check to determine if running on Windows (using java.io.File.separator or something similar) and use the path "C:/ProgramData/Jenkins" as the path root (this is a similar path to /usr/share on UNIX systems). Add Comment
[JIRA] (JENKINS-58072) no notification with successful test connection
Title: Message Title Martin Reinhardt commented on JENKINS-58072 Re: no notification with successful test connection see here: https://github.com/jenkinsci/rocketchatnotifier-plugin/commit/499bf77a2eaa5da48d661381231d72dbf4bc9bf8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200096.156086886.2401.1562341080286%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58363) Add backend API for fetching date presets.
Title: Message Title Jack Shen created an issue Jenkins / JENKINS-58363 Add backend API for fetching date presets. Issue Type: Improvement Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-05 14:59 Labels: gsoc-2019 Priority: Minor Reporter: Jack Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50284) PlasticSCM - cannot use Plastic repository as Shared Library source
Title: Message Title Mikael Kalms commented on JENKINS-50284 Re: PlasticSCM - cannot use Plastic repository as Shared Library source Confirmed, v 2.22 solves our problems with Shared Libraries. We have moved our Shared Libraries from GitHub to Plastic now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189322.1521549463000.2398.1562337360140%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50284) PlasticSCM - cannot use Plastic repository as Shared Library source
Title: Message Title Mikael Kalms assigned an issue to Mikael Kalms Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source Change By: Mikael Kalms Assignee: Miguel González Mikael Kalms Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.189322.1521549463000.2396.1562337300181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58362 CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage Change By: Jesse Glick Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200477.1562336462000.2394.1562336700198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Jesse Glick commented on JENKINS-58362 Re: CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage While there are three associated pull requests, only jenkins #4099 is important to backport to the stable-2.176 branch. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200477.1562336462000.2393.1562336640044%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Jesse Glick updated JENKINS-58362 Jenkins / JENKINS-58362 CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage Change By: Jesse Glick 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.200477.1562336462000.2392.1562336520469%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Jesse Glick started work on JENKINS-58362 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.200477.1562336462000.2391.1562336520456%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58362) CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58362 CommandLauncher2Test.requireApproval failure due to two copies of SystemCommandLanguage Issue Type: Bug Assignee: Jesse Glick Components: command-launcher-plugin, core, jenkins-test-harness Created: 2019-07-05 14:21 Labels: plugin-compat-tester regression lts-candidate Priority: Minor Reporter: Jesse Glick JENKINS-57528 included a bump to the detached script-security which should have been paired with a bump to the detached command-launcher. To reproduce, run mvn -f command-launcher-plugin test -Djenkins.version=2.176.1 -Dtest=CommandLauncher2Test\#requireApproval which passes; now bump its parent to 3.47 and include -Djenkins.version=2.176.2-rc28314.ce9ac38e8574 -Pconsume-incrementals which pulls in this backport by Oliver Gondža and you will get a failure: java.lang.AssertionError: expected: but was: at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at
[JIRA] (JENKINS-51734) sessionTimeout isn't be honoured
Title: Message Title Tarvi Pillessaar commented on JENKINS-51734 Re: sessionTimeout isn't be honoured sessionEviction is actually working (tested with version 2.176.1), just sessionEviction is in seconds and sessionTimeout is in minutes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.191180.1528291999000.2375.1562336340970%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58261) GitLab branch source server field not working
Title: Message Title Parichay Barpanda started work on JENKINS-58261 Change By: Parichay Barpanda 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.200325.1561793952000.2372.1562335800207%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50377) Error when using axis as token
Title: Message Title Patrick Viafore commented on JENKINS-50377 Re: Error when using axis as token I'm seeing this issue too in Token Macro v2.3 and Matrix v1.12. For me, it looks like everything works as expected in the jobs that are defined by each configuration of the matrix (they kick off the appropriate jobs), however the parent job that kicks off the configurations shows the same error as above. I've only seen it when trying to conditionally kick off a job and the condition used the macro as part of its evaluation criteria. For example, mine was using a File Exists check that looked for a name based on the matrix axis. As a workaround, I converted my build conditional step to check a shell command rather than checking through the built-in File Exists. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.189430.1521831319000.2370.1562334960153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58361) Test Webhook
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58361 Test Webhook Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-05 13:34 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Unable to test webhooks as fixing other bugs at the moment. Since gitlab cannot setup webhook on localhost, need to use some service like ngrok. Add Comment
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Bastian Brodbeck commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError I also have this problem with our declarative pipeline, but we do not use parallel steps. We run Jenkins Jenkins 2.176.1 but I had it with 2.150.1 as well. I think it happened from one day to another a few days back. Cannot remember having done any change to Jenkins or the pipeline that caused this to happen. I though updating Jenkins and all installed Plugins might fix the issue, but it did not. The things I noticed: it happens 9 out of 10 builds when it happens then consistent at the same step when chaining the pipeline to mediate the issue it happens at another step (and stays there) – i initially thought it might be related to credentials (withCredentials, withAWS) When i reduce the size of the pipeline it does not happen. But then of course we can not use the result. so far it only happened on my Windows machine, never during a mac build System Log: Unexpected exception in CPS VM thread: CpsFlowExecution java.lang.IllegalStateException: JENKINS-50407: no loaded shell in CpsFlowExecution Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-47839) crowd2 Jenkins plugin crashes if user not found
Title: Message Title Pascal Hofmann commented on JENKINS-47839 Re: crowd2 Jenkins plugin crashes if user not found I just ran into the same problem. Zhenlei Huang: I guess this is the RFC that you are referring to? "A proxy MUST forward unrecognized header fields[…]" - https://tools.ietf.org/html/rfc7230#section-3.2.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.186344.1509974531000.2335.1562332020181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner edited a comment on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration We need to parse the whole job log, so using tee is not an option for us. - This is really blocking us from moving forward to warnings-ng plugin. - This I can do now by fetching the log from the _currentBuild_ and writing it to a file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192001.1530178828000.2330.1562331720182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration For the old warnings plugin I could add a parser with Jenkins.instance.getExtensionList(hudson.plugins.warnings.WarningsDescriptor.class).get(0).addGroovyParser(new hudson.plugins.warnings.GroovyParser(...)) How can this be done for the new warnings-ng 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.192001.1530178828000.2325.1562331602844%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58360) Enabling Permissive Script Security Plugin causes pipelines to appear empty
Title: Message Title Artalus S. created an issue Jenkins / JENKINS-58360 Enabling Permissive Script Security Plugin causes pipelines to appear empty Issue Type: Bug Assignee: Oliver Gondža Attachments: ss-05-07-2019-132223.png Components: permissive-script-security-plugin Created: 2019-07-05 12:58 Environment: Jenkins 2.152 Permissive Script Security Plugin 0.5 Priority: Minor Reporter: Artalus S. When I open any of our pipelines everything is set up except the pipeline script itself. It appears to be empty, even though in `config.xml` it is downloaded from SCM or provided from the job itself. The job can be run and will successfully perform all the steps, but if I reconfigure and save it, the script will be lost as if I really made it empty myself. Disabling the plugin fixes the issue. Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart > One more question what do you mean with orphaned, stop state or no longer in the jenkins interface ? It's not available as an agent in jenkins. It's still in running state when I check the status in AWS console> Did you apply the all the IAM role requested specify in the ec2 plugin page ? I believe I did, since this is a random error it doesn't happen every time . E.g. the instances get terminated after idle timeout Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199745.1559315049000.2317.1562330340401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart > One more question what do you mean with orphaned, stop state or no longer in the jenkins interface ? It's not available as an agent in jenkins. It's still in running state when I check the status in AWS console > Did you apply the all the IAM role requested specify in the ec2 plugin page ? I believe I did, since this is a random error it doesn't happen every time Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.2314.1562330220119%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title Ramon Leon updated JENKINS-57990 Jenkins / JENKINS-57990 Avoid filtering contents without sensible data and do per-content anonymization Change By: Ramon Leon Status: In Review Resolved Resolution: Done Released As: 2.57 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199975.1560350087000.2310.1562329740349%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55493) [support-core] Upgrade parent pom and fix HTMLForm API usage
Title: Message Title Ramon Leon updated JENKINS-55493 Jenkins / JENKINS-55493 [support-core] Upgrade parent pom and fix HTMLForm API usage Change By: Ramon Leon 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.196624.1547065683000.2312.1562329740429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Pierre Larsson edited a comment on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel Reverted to 2.164.3 and the message exception goes away Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199007.1556619184000.2302.1562327640716%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Pierre Larsson commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel Reverted to 2.164.3 and the message goes away Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199007.1556619184000.2293.1562327640512%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Pierre Larsson reopened an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: Pierre Larsson Resolution: Fixed Status: Resolved 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.199007.1556619184000.2284.1562327040742%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title Pierre Larsson commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel Should this be fixed in 2.176.1? The plugins list and versions are: amazon-ecs:1.19 ansicolor:0.6.2 build-monitor-plugin:1.12+build.201809061734 build-timeout:1.19 build-user-vars-plugin:1.5 checkstyle:4.0.0 claim:2.15 cloudbees-folder:6.9 copyartifact:1.42.1 credentials:2.2.0 cucumber-reports:4.7.0 cucumber-testresult-plugin:0.10.1 description-setter:1.10 envinject:2.1.6 extended-read-permission:2.0 flexible-publish:0.15.2 gatling:1.2.6 ghprb:1.42.0 git:3.10.0 github-api:1.95 github:1.29.4 gradle:1.32 htmlpublisher:1.18 job-dsl:1.74 jobConfigHistory:2.22 ldap:1.20 lockable-resources:2.5 matrix-auth:2.4.2 Parameterized-Remote-Trigger:3.0.8 pipeline-model-definition:1.3.9 pipeline-model-extensions:1.3.9 pipeline-stage-tags-metadata:1.3.9 pipeline-model-api:1.3.9 parameterized-trigger:2.35.2 plain-credentials:1.5 postbuild-task:1.8 preSCMbuildstep:0.3 pyenv:0.0.7 rbenv:0.0.17 rebuild:1.31 scoverage:1.4.0 seleniumhtmlreport:1.0 workflow-durable-task-step:2.31 workflow-aggregator:2.6 workflow-api:2.35 ws-cleanup:0.37 xvfb:1.1.3 I've updated all the plugins which I can but get this error: 2019-07-05 11:27:28 FINEST org.jenkinsci.bytecode.TransformationSpec mayNeedTransformation returning false 2019-07-05 11:27:28 FINEST org.jenkinsci.bytecode.Transformer no transformation required for org.jenkinsci.plugins.scoverage.ScoverageBuildAction 2019-07-05 11:27:28 FINE org.eclipse.jetty.webapp.WebAppClassLoader found webapp loaded interface jenkins.tasks.SimpleBuildStep$LastBuildAction 2019-07-05 11:27:28 FINE org.eclipse.jetty.webapp.WebAppClassLoader found webapp loaded interface org.kohsuke.stapler.export.ExportedBean 2019-07-05 11:27:28 FINE org.eclipse.jetty.webapp.WebAppClassLoader found webapp loaded interface hudson.model.ModelObject 2019-07-05 11:27:28 FINE jenkins.security.ClassFilterImpl permitting org.jenkinsci.plugins.scoverage.ScoverageBuildAction due to its location in file:/var/jenkins_home/plugins/scoverage/WEB-INF/lib/scoverage.jar 2019-07-05 11:27:28 FINE jenkins.security.ClassFilterImpl permitting hudson.FilePath due to its location in file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.1.jar 2019-07-05 11:27:28 FINE org.eclipse.jetty.webapp.WebAppClassLoader found webapp loaded class hudson.FilePath 2019-07-05 11:27:28 WARNING hudson.FilePath A FilePath object is being serialized when it should not be, indicating a bug in a plugin. See https://jenkins.io/redirect/filepath-serialization for details. java.io.NotSerializableException: The calling thread Thread[Handling GET / from 10.35.1.195 : qtp1972439101-13 View/index.jelly WeatherColumn/column.jelly,5,main] has no associated channel. The current object null is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel at org.jenkinsci.remoting.SerializableOnlyOverRemoting.getChannelForSerialization(SerializableOnlyOverRemoting.java:67) at hudson.FilePath._getChannelForSerialization(FilePath.java:3001) at
[JIRA] (JENKINS-58359) Blue Ocean visualisation inaccurate while building
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-58359 Blue Ocean visualisation inaccurate while building Issue Type: Bug Assignee: Unassigned Attachments: image-2019-07-05-07-36-26-336.png, image-2019-07-05-07-41-35-587.png Components: blueocean-plugin Created: 2019-07-05 11:42 Priority: Major Reporter: Brian J Murrell While running a pipeline, the Blue Ocean visualisation can be inaccurate. For example, at one point my pipeline looks like this: However, as you can see, when it has completed that stage that was running (Unit Test) and moves on to the next stage it looks like this: So why weren't the parallel Build stage steps showing in the first image above. They were most certainly complete at that point. Add Comment
[JIRA] (JENKINS-58341) Add a markdown library to write these files appropriately in support-core-plugin
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-58341 Add a markdown library to write these files appropriately in support-core-plugin Change By: Ramon Leon Issue Type: Bug 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.200454.1562232715000.2269.1562326020283%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58358) Ger error: The test management module is not available in running ECU-TEST instance
Title: Message Title Arkadi Bahnmann created an issue Jenkins / JENKINS-58358 Ger error: The test management module is not available in running ECU-TEST instance Issue Type: Bug Assignee: TraceTronic GmbH Components: ecutest-plugin Created: 2019-07-05 11:08 Priority: Major Reporter: Arkadi Bahnmann I try to upload the testresults of ecu test to Polarion using the publishTMS command. On a local jenkins installation everything works fine but on our jenkins running on a server and using a build slave I get following error: "[TT] ERROR: Failed publishing report to test management system. [TT] ERROR: The test management module is not available in running ECU-TEST instance! Enable it by setting the feature flag 'TEST-MANAGEMENT-SERVICE'. [TT] ERROR: Caught ComException: Invoke of: GetTestManagementModule Source: Description: Testmanagement is not available." where can I set the mentioned feature flag TEST-MANAGEMENT-SERVICE? Add Comment
[JIRA] (JENKINS-58357) Unable to find the path of the MSBuild
Title: Message Title
Vijay Reddy created an issue
Jenkins / JENKINS-58357
Unable to find the path of the MSBuild
Issue Type:
Task
Assignee:
Lionel Cabasson
Components:
msbuild-plugin
Created:
2019-07-05 10:50
Environment:
Client Environment
Labels:
pipeline configuration
Priority:
Critical
Reporter:
Vijay Reddy
Hi All, We are using multibranch pipeline in local inside the client VDI. We have written descriptive pipeline which would have few stages and installed in MSBuild in Local. This Groovy code is there in the Bit bucket along with my code(Selenium C# code). Configured the MSBuild path of local in the Global Tool Configuration in side the Jenkins. I am getting below errors "WorkflowScript: 47: Invalid tool type "msbuild". Valid tool types: [hudson.tasks.Ant$AntInstallation," hudson.plugins.mercurial.MercurialInstallation] @ line 47, column 7. msbuild 'MSBuild' Sample Groovy Code what we use: pipeline { agent any options { } toos { msbuild 'MSBuild' *47 line this lin* } stages { stage("SCM: Checkout"){ steps{ script { echo "VijayCheckOut1" } } }
[JIRA] (JENKINS-58263) GitLabSCMFile cannot use api, needs heavy checkout
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58263 GitLabSCMFile cannot use api, needs heavy checkout Change By: Parichay Barpanda Need to fix repository api in GitLabSCMFile to check for ` JenkinsFile Jenkinsfile ` in the root dir of the repository. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200327.1561794262000.2250.1562321940155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58356) Test connection even if no credentials specified
Title: Message Title Parichay Barpanda resolved as Fixed Fixed in 68298bf of feature/branch-source branch. Jenkins / JENKINS-58356 Test connection even if no credentials specified Change By: Parichay Barpanda Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200471.1562321721000.2248.1562321880115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58356) Test connection even if no credentials specified
Title: Message Title Parichay Barpanda started work on JENKINS-58356 Change By: Parichay Barpanda 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.200471.1562321721000.2247.1562321760327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58356) Test connection even if no credentials specified
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58356 Test connection even if no credentials specified Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-05 10:15 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda This feature improves user experience by displaying `If the GitLab Server is valid` even if user hasn't specified credentials and does a `Test Connection`. Add Comment
[JIRA] (JENKINS-58355) Cache GitLab Avatar
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58355 Cache GitLab Avatar Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-05 10:05 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda Currently gitlab projects (folder organisation) requires to fetch avatar everytime page reloads. The avatar can be cached inside GitLab instance so that it need not be loaded again and again. Also add a method to refresh if avatar changes. Add Comment
[JIRA] (JENKINS-58354) Refractor api builder and credentials finder methods
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58354 Refractor api builder and credentials finder methods Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-05 09:57 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda This can be fixed by adding a helper class GitLabHelper that contains these generic methods at one place. Add Comment
[JIRA] (JENKINS-49732) java.util.LinkedHashMap$Entry not serializable in Pipeline
Title: Message Title Ulad Muraveika commented on JENKINS-49732 Re: java.util.LinkedHashMap$Entry not serializable in Pipeline Hi Andrew Bayer, It will be very helpful, if you explain why your workaround with groovy closure will work, because I've tried to debug similar code and can see java.util.LinkedHashMap$Entry variables as well. Does serialization works in different way for variables in closures? Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188674.1519637279000.2240.1562318820202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39219) Pipeline from SCM options disappear
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-39219 Re: Pipeline from SCM options disappear was this actually solved? I run into the same issue in version 2.176.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.175646.1477332308000.2236.1562317680160%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart I believe I found the problem, I trying to put in the 1.44.2 that should be release in a couple of days. One more question what do you mean with orphaned, stop state or no longer in the jenkins interface ? Did you apply the all the IAM role requested specify in the ec2 plugin page ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199745.1559315049000.2233.1562317560275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova edited a comment on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue.This is blocking the build of the job, since it throws a NP Null Pointer when it tries to find the scm even though I specified it as 'None' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.179104.148768634.2229.1562317500193%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20073) Add an action to allow moving credentials between credential domains
Title: Message Title Sokratis Galiatsis commented on JENKINS-20073 Re: Add an action to allow moving credentials between credential domains Is there any chance for this to move forward? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.151593.1381922552000.2226.1562317441323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova edited a comment on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue. This is blocking the build of the job, since it throws a NP when it tries to find the scm Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.179104.148768634.2220.1562317440265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42216) Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config
Title: Message Title Karolina Arancibia Valuskova commented on JENKINS-42216 Re: Pipeline job offers inapplicable SCM on initial 'Pipeline from SCM' config Ran into the same issue, is there a work-around until this is solved? my problem is exactly like the duplicate on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179104.148768634.2217.1562317320785%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58351) buildType is used incorrectly for visual studio builds
Title: Message Title
Dennis Cappendijk updated an issue
Jenkins / JENKINS-58351
buildType is used incorrectly for visual studio builds
Change By:
Dennis Cappendijk
I have created a Jenkins pipeline that covers both windows and linux.However it appears that cmakeBuild does not use buildType correctly for visual studioFor Linux is correctly adds -DCMAKE_BUILD_TYPE=Debug or Release in the configure stepHowever for windows the CMAKE_BUILD_TYPE variable is ignored:{code:java}17:47:24Manually-specified variables were not used by the project:17:47:24 17:47:24 CMAKE_BUILD_TYPE{code}And subsequently in the --build step, the --config is unused. Resulting in a Debug-by-default build on windows with the visual studio generator .--config Debug or- -config Release (depending on buildType should be added to the --build phase for windows (and CMAKE_BUILD_TYPE should not be used for visual studio generator) The current workaround to this is adding --config Debug/Release explicitly in the steps:{code:java}steps: [[args: '--config Debug', withCmake: true]]{code}Which of course is less than ideal if the buildType property is available.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-58351) buildType is used incorrectly for visual studio builds
Title: Message Title Dennis Cappendijk commented on JENKINS-58351 Re: buildType is used incorrectly for visual studio builds Adapted ticket title and description to better reflect the issue, thanks Martin Weber Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200466.1562256626000.2210.1562315280113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
