[JIRA] (JENKINS-57921) Add new Custom Step for Self-Promotion
Title: Message Title Prastik Gyawali stopped work on JENKINS-57921 Change By: Prastik Gyawali Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199893.1560090278000.2119.1560835920084%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58043) latest version not uploading the files
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58043 latest version not uploading the files Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200063.1560765751000.2118.1560829620161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57447) Agents sometimes left as suspended after starting from shutdown state
Title: Message Title Jie Shen commented on JENKINS-57447 Re: Agents sometimes left as suspended after starting from shutdown state My assumption here seems to be wrong. This issue seems not be hung on the setChannel method. Any help or suggestion here will be welcome. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199260.1557821873000.2115.1560828840136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58062) We can't set next build number in version 2.176.1 and newer anymore
Title: Message Title
xzy zyl updated an issue
Jenkins / JENKINS-58062
We can't set next build number in version 2.176.1 and newer anymore
Change By:
xzy zyl
We could set the next build number in version 2.164.1 but after we upgraded jenkins to 2.176.1, we failed to do that and got an error:```bashTraceback (most recent call last):Traceback (most recent call last): File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init__.py", line 583, in jenkins_request self._request(req)) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init__.py", line 533, in _response_handler response.raise_for_status() File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\requests\models.py", line 941, in raise_for_status raise HTTPError(http_error_msg, response=self)requests.exceptions.HTTPError: 500 Server Error: Server Error for url: [http://x.x.x.x:8080/job/dc_demo_web/nextbuildnumber/submit|http://10.5.1.126:8080/job/dc_demo_web/nextbuildnumber/submit] During handling of the above exception, another exception occurred: Traceback (most recent call last): File "F:/Projects/mylabs/test_Jenkins.py", line 27, in res = server.set_next_build_number(job_name, 233) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init__.py", line 1150, in set_next_build_number data="" % number).encode('utf-8'))) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init__.py", line 564, in jenkins_open return self.jenkins_request(req, add_crumb, resolve_auth).text File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init__.py", line 594, in jenkins_request raise JenkinsException(msg)jenkins.JenkinsException: Error in request. Possibly authentication failed [500]: Server Error Jenkins [Jenkins]var isRunAsTest=false; var rootURL=""; var resURL="/static/244807d3";crumb.init("Jenkins-Crumb", "083afa1f887c5c490ac1b7fa94cd6681");Skip to content log in createSearchBox("/search/");Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops!A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejava.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:542) at java.lang.Integer.parseInt(Integer.java:615) at org.jvnet.hudson.plugins.nextbuildnumber.NextBuildNumberAction.doSubmit(NextBuildNumberAction.java:96)Caused: javax.servlet.ServletException: Build
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent All tutorials I've seen for the SonarQube plugin show a text field to paste in the User Token. However, I'm seeing a Credentials dropdown for selecting and/or adding a token, except I'm unable to add a token in any form that works (screenshot attached) as nothing ever appears in the dropdown to select a defined token.I'm unsure if this is due to and an issue with the SonarQube plugin or Credentials plugin. (Sorry if I guessed wrongly). !image-2019-06-17-20-12-20-160.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.200082.1560824562000.2111.1560824880061%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58062) We can't set next build number in version 2.176.1 and newer anymore
Title: Message Title
xzy zyl updated an issue
Jenkins / JENKINS-58062
We can't set next build number in version 2.176.1 and newer anymore
Change By:
xzy zyl
We could set the next build number in version 2.164.1 but after we upgraded jenkins to 2.176.1, we failed to do that and got an error:```bashTraceback (most recent call last):Traceback (most recent call last): File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\ jenkins\__init__ jenkins__init__ .py", line 583, in jenkins_request self._request(req)) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\ jenkins\__init__ jenkins__init__ .py", line 533, in _response_handler response.raise_for_status() File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\requests\models.py", line 941, in raise_for_status raise HTTPError(http_error_msg, response=self)requests.exceptions.HTTPError: 500 Server Error: Server Error for url: [ http:// x.x.x.x:8080/job/dc_demo_web/nextbuildnumber/submit|http:// 10.5.1.126:8080/job/dc_demo_web/nextbuildnumber/submit ] During handling of the above exception, another exception occurred:Traceback (most recent call last): File "F:/Projects/mylabs/test_Jenkins.py", line 27, in res = server.set_next_build_number(job_name, 233) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\ jenkins\__init__ jenkins__init__ .py", line 1150, in set_next_build_number data="" % number).encode('utf-8'))) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\ jenkins\__init__ jenkins__init__ .py", line 564, in jenkins_open return self.jenkins_request(req, add_crumb, resolve_auth).text File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\ jenkins\__init__ jenkins__init__ .py", line 594, in jenkins_request raise JenkinsException(msg)jenkins.JenkinsException: Error in request. Possibly authentication failed [500]: Server Error Jenkins [Jenkins]var isRunAsTest=false; var rootURL=""; var resURL="/static/244807d3";crumb.init("Jenkins-Crumb", "083afa1f887c5c490ac1b7fa94cd6681");Skip to content log in createSearchBox("/search/");Jenkins Jenkins project Bug tracker Mailing Lists Twitter: @jenkinsci Oops!A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejava.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:542) at java.lang.Integer.parseInt(Integer.java:615) at
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent created an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Issue Type: Bug Assignee: Unassigned Attachments: image-2019-06-17-20-12-20-160.png Components: credentials-plugin Created: 2019-06-18 02:22 Environment: Jenkins 2.176.1 Ubuntu 18.04 w/ Tomcat8 Credentials Plugin v2.2.0 "SonarQube Scanner for Jenkins" v2.9 Priority: Minor Reporter: Jeff VIncent All tutorials I've seen for the SonarQube plugin show a text field to paste in the User Token. However, I'm seeing a Credentials dropdown for selecting and/or adding a token, except I'm unable to add a token in any form that works (screenshot attached) as nothing ever appears in the dropdown to select a defined token. I'm unsure if this is due to and issue with the SonarQube plugin or Credentials plugin. (Sorry if I guessed wrongly).
[JIRA] (JENKINS-58062) We can't set next build number in version 2.176.1 and newer anymore
Title: Message Title xzy zyl created an issue Jenkins / JENKINS-58062 We can't set next build number in version 2.176.1 and newer anymore Issue Type: Bug Assignee: Alexander Komarov Components: next-build-number-plugin Created: 2019-06-18 02:22 Environment: Jenkins 2.176.1 Next Build Number Plugin: 1.5 Labels: plugin jenkins Priority: Major Reporter: xzy zyl We could set the next build number in version 2.164.1 but after we upgraded jenkins to 2.176.1, we failed to do that and got an error: ```bash Traceback (most recent call last):Traceback (most recent call last): File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins_init.py", line 583, in jenkins_request self._request(req)) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins__init_.py", line 533, in _response_handler response.raise_for_status() File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\requests\models.py", line 941, in raise_for_status raise HTTPError(http_error_msg, response=self)requests.exceptions.HTTPError: 500 Server Error: Server Error for url: http://10.5.1.126:8080/job/dc_demo_web/nextbuildnumber/submit During handling of the above exception, another exception occurred: Traceback (most recent call last): File "F:/Projects/mylabs/test_Jenkins.py", line 27, in res = server.set_next_build_number(job_name, 233) File "C:\Users\Administrator\AppData\Local\Programs\Python\Python36\lib\site-packages\jenkins_init.py", line 1150, in set_next_build_number data="" %
[JIRA] (JENKINS-58042) Set verb "Build" string in button "Build with parameters" to anything else
Title: Message Title Jim Zarakis updated an issue Jenkins / JENKINS-58042 Set verb "Build" string in button "Build with parameters" to anything else Change By: Jim Zarakis Labels: jenkins newbie-friendly pipeline user-experience Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200062.1560764167000.2105.1560819420055%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57490) Get stack trace on Web interface
Title: Message Title Shuo Wang updated an issue Jenkins / JENKINS-57490 Get stack trace on Web interface Change By: Shuo Wang Attachment: stacktrace2.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199351.1557943366000.2102.1560816480713%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57490) Get stack trace on Web interface
Title: Message Title Shuo Wang closed an issue as Not A Defect Jenkins / JENKINS-57490 Get stack trace on Web interface Change By: Shuo Wang Status: Reopened Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199351.1557943366000.2100.1560816480639%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57490) Get stack trace on Web interface
Title: Message Title Shuo Wang updated an issue Jenkins / JENKINS-57490 Get stack trace on Web interface Change By: Shuo Wang Attachment: stacktrace1.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199351.1557943366000.2103.1560816480733%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57490) Get stack trace on Web interface
Title: Message Title Shuo Wang updated an issue Jenkins / JENKINS-57490 Get stack trace on Web interface Change By: Shuo Wang - Got stack trace on UI twice today, with slightly different stack traces. Please see attachment for the full stack traces. - There is only one job listed after the stack trace, should have a list of jobs showingA problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.*Stack trace*org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.164.1.jar!/lib/hudson/projectViewRow.jelly:35:52: java.lang.StackOverflowError at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at
[JIRA] (JENKINS-58035) lightweight Checkouts return error code when trying to checkout jenkins file returns 404
Title: Message Title Robert Orrock started work on JENKINS-58035 Change By: Robert Orrock 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.200054.1560729162000.2098.1560813600117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58035) lightweight Checkouts return error code when trying to checkout jenkins file returns 404
Title: Message Title Robert Orrock stopped work on JENKINS-58035 Change By: Robert Orrock Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200054.1560729162000.2099.1560813600153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58035) lightweight Checkouts return error code when trying to checkout jenkins file returns 404
Title: Message Title Robert Orrock updated an issue Jenkins / JENKINS-58035 lightweight Checkouts return error code when trying to checkout jenkins file returns 404 Change By: Robert Orrock Summary: lightweight hcekcouts Checkouts return error code when trying to checkout jenkins file returns 404 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200054.1560729162000.2097.1560813540065%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58059) Invalid Zepher credentials Error occurs w/ valid credentials
Title: Message Title Tyler Pranger updated an issue Jenkins / JENKINS-58059 Invalid Zepher credentials Error occurs w/ valid credentials Change By: Tyler Pranger I am unable to use Jenkins to update test results due to an invalid credentials error. I have verified my username, password, and API keys are correct and I am still unable to login to Zepher.Things I have done to resolve the issue # Rgenerating Regenerating my keys and using those as a way to resolve the issue and it still does not work. # Restarted Jenkins # Upgraded Jenkins # Upgraded the Zepher plugin # Downgraded the Zepher plugin # Downgraded Jenkins # Restarted the Jenkins Service # Restarted computer to run a clean version of Jenkins Below is the following errors that occur after a test is run:java.lang.NullPointerException at java.lang.String.replace(Unknown Source) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.fetchExecutionIdsZFJC(TestCaseUtil.java:986) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:682) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Publish test result to Zephyr for JIRA' marked build as failure Add Comment
[JIRA] (JENKINS-58059) Invalid Zepher credentials Error occurs w/ valid credentials
Title: Message Title Tyler Pranger updated an issue Jenkins / JENKINS-58059 Invalid Zepher credentials Error occurs w/ valid credentials Change By: Tyler Pranger Summary: Invalid Zepher credentialsError occurs w/ valid credentials Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200080.1560806887000.2094.1560811500206%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58059) Invalid Zepher credentials
Title: Message Title Tyler Pranger updated an issue Jenkins / JENKINS-58059 Invalid Zepher credentials Change By: Tyler Pranger I am unable to use Jenkins to update test results due to an invalid credentials error. I have verified my username, password, and API keys are correct and I am still unable to login to Zepher. Things I have tried regenerating done to resolve the issue # Rgenerating my keys and using those as a way to resolve the issue and it still does not work. I have also tried # Restarted Jenkins # Upgraded Jenkins # Upgraded the Zepher plugin # Downgraded the Zepher plugin # Downgraded Jenkins # Restarted the Jenkins Service # Restarted computer to restart run a clean version of Jenkins . I get Below is the following errors that occur after a test is run:java.lang.NullPointerException at java.lang.String.replace(Unknown Source) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.fetchExecutionIdsZFJC(TestCaseUtil.java:986) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:682) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Publish test result to Zephyr for JIRA' marked build as failure Add Comment
[JIRA] (JENKINS-58059) Invalid Zepher credentials
Title: Message Title Tyler Pranger updated an issue Jenkins / JENKINS-58059 Invalid Zepher credentials Change By: Tyler Pranger Environment: Windows 10Zephyr for JIRA Test Management: Version 1.4 & 1.5 Jenkins 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.200080.1560806887000.2090.1560811200127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58060) misleading comment about spotbugs install site
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-58060 misleading comment about spotbugs install site Issue Type: Task Assignee: Unassigned Components: core Created: 2019-06-17 22:09 Priority: Minor Reporter: Josh Soref Comment in pom: https://github.com/jenkinsci/jenkins/blob/bc40ab3ae57178d477fe919b12ed761080df7d6b/core/pom.xml#L871 Actual results: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 04:44 min [INFO] Finished at: 2019-06-17T18:07:14-04:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on project jenkins-core: Velocity parsing error while reading the site decoration template from org.apache.maven.skins:maven-fluido-skin:jar:1.3.0 skin: Encountered "source" at META-INF/maven/site.vm[line 1039, column 52] [ERROR] Was expecting one of: [ERROR] "," ... [ERROR] ")" ... [ERROR] ... [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[JIRA] (JENKINS-58060) misleading comment about spotbugs install site
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-58060 misleading comment about spotbugs install site Issue Type: Task Assignee: Unassigned Components: core Created: 2019-06-17 22:09 Priority: Minor Reporter: Josh Soref Comment in pom: https://github.com/jenkinsci/jenkins/blob/bc40ab3ae57178d477fe919b12ed761080df7d6b/core/pom.xml#L871 Actual results: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 04:44 min [INFO] Finished at: 2019-06-17T18:07:14-04:00 [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.7.1:site (default-site) on project jenkins-core: Velocity parsing error while reading the site decoration template from org.apache.maven.skins:maven-fluido-skin:jar:1.3.0 skin: Encountered "source" at META-INF/maven/site.vm[line 1039, column 52] [ERROR] Was expecting one of: [ERROR] "," ... [ERROR] ")" ... [ERROR] ... [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[JIRA] (JENKINS-58059) Invalid Zepher credentials
Title: Message Title Tyler Pranger created an issue Jenkins / JENKINS-58059 Invalid Zepher credentials Issue Type: Bug Assignee: Zephyr Developer Components: zephyr-enterprise-test-management-plugin, zephyr-for-jira-test-management-plugin Created: 2019-06-17 21:28 Environment: Windows 10 Zephyr for JIRA Test Management: Version 1.4 Jenkins Version: 2.176.1 Labels: zephyr-plugin Priority: Major Reporter: Tyler Pranger I am unable to use Jenkins to update test results due to an invalid credentials error. I have verified my username, password, and API keys are correct and I am still unable to login to Zepher. I have tried regenerating my keys and using those as a way to resolve the issue and it still does not work. I have also tried to restart Jenkins. I get the following errors after a test is run: java.lang.NullPointerException at java.lang.String.replace(Unknown Source) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.fetchExecutionIdsZFJC(TestCaseUtil.java:986) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:682) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Robert Rodrigues commented on JENKINS-58056 Re: Add option to fail the step if no files are found for pattern I think it would make sense to, perhaps optionally, fail on any errors. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200077.1560795254000.2084.1560806760102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7122) Disable lshistory
Title: Message Title Stuart Rowe assigned an issue to Stuart Rowe Jenkins / JENKINS-7122 Disable lshistory Change By: Stuart Rowe Assignee: Vincent Latombe Stuart Rowe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.137219.1280759392000.2079.1560806580230%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-7122) Disable lshistory
Title: Message Title Stuart Rowe assigned an issue to Vincent Latombe Sorry, not sure how I managed to assign this to myself. Jenkins / JENKINS-7122 Disable lshistory Change By: Stuart Rowe Assignee: Stuart Rowe Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.137219.1280759392000.2082.1560806580263%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55911) java lint warning about annotation processor is not recognized
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55911 java lint warning about annotation processor is not recognized Change By: Ulli Hafner Component/s: analysis-model Component/s: 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.197314.1549031392000.2076.1560806100156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56456) Newbie Issues - Warnings Next Generation Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56456 Newbie Issues - Warnings Next Generation Plugin Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198054.1551950501000.2074.1560805920295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56630) Warnings Plugin - Page objects for integration tests
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-56630 Warnings Plugin - Page objects for integration tests Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198257.1553071221000.2071.1560805860244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56717) Add unit tests for ToolSelectionDescriptor
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-56717 Add unit tests for ToolSelectionDescriptor Change By: Ulli Hafner Status: Reopened Closed 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.198356.1553340462000.2065.1560805800297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56707) Improve unit tests for LinesChartModel
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-56707 Improve unit tests for LinesChartModel Change By: Ulli Hafner Status: In Progress Closed 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.198346.1553338453000.2069.1560805800391%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56709) Add unit tests for NewVersusFixedTrendChart
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-56709 Add unit tests for NewVersusFixedTrendChart Change By: Ulli Hafner Status: Reopened Closed 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.198348.155333861.2067.1560805800332%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title
René Scheibe edited a comment on JENKINS-43693
Re: multibranchPipelineJob overrides old branch indexing sources
[~daspilker] is there a way in Job DSL to resemble the automatic {{id}} creation as done when the job is created via the UI? Or can the {{id}} automatically be set only on job creation but not changed when updating the job?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.181107.1492615058000.2052.1560805740387%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57283) Trend Carousel (in Details View)
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57283 Trend Carousel (in Details View) Change By: Ulli Hafner Status: In Progress Closed 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.199049.1556744617000.2039.1560805680803%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57278) Console Log View
Title: Message Title Ulli Hafner updated JENKINS-57278 Jenkins / JENKINS-57278 Console Log View Change By: Ulli Hafner Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199044.1556741728000.2047.1560805680929%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57277) Source Code View
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57277 Source Code View Change By: Ulli Hafner Status: Open Closed 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.199043.1556741629000.2049.1560805680956%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57280) Source Control Table (in Details Tab)
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57280 Source Control Table (in Details Tab) Change By: Ulli Hafner Status: In Progress Closed 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.199046.1556742198000.2045.1560805680862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57282) Overview Carousel (in Details View)
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57282 Overview Carousel (in Details View) Change By: Ulli Hafner Status: In Progress Closed 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.199048.1556744575000.2041.1560805680823%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57281) Details Tab (in Details View)
Title: Message Title Ulli Hafner updated JENKINS-57281 Jenkins / JENKINS-57281 Details Tab (in Details View) Change By: Ulli Hafner Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199047.1556742712000.2043.1560805680842%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57284) Charts (in Details View)
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57284 Charts (in Details View) Change By: Ulli Hafner Status: Open Closed 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.199050.1556744678000.2037.1560805620478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57286) Trend Charts (in job summary view)
Title: Message Title Ulli Hafner closed an issue as Won't Fix Jenkins / JENKINS-57286 Trend Charts (in job summary view) Change By: Ulli Hafner Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199052.1556745051000.2033.1560805620401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57285) Issues Portlet (in Dashboard View)
Title: Message Title Ulli Hafner closed an issue as Fixed Jenkins / JENKINS-57285 Issues Portlet (in Dashboard View) Change By: Ulli Hafner Status: Open Closed 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.199051.1556744729000.2035.1560805620449%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43693) multibranchPipelineJob overrides old branch indexing sources
Title: Message Title René Scheibe commented on JENKINS-43693 Re: multibranchPipelineJob overrides old branch indexing sources Daniel Spilker is there a way in Job DSL to resemble the automatic id creation as done when the job is created via the UI? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.181107.1492615058000.2029.1560805560870%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57290) Token Macro Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57290 Token Macro Plugin Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199056.1556746694000.2031.1560805560891%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57292) Folder Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57292 Folder Plugin Change By: Ulli Hafner 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.199058.1556746895000.2015.1560805560661%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57293) Pipeline Groove Plugin (Snippet Generator)
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57293 Pipeline Groove Plugin (Snippet Generator) Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199059.1556747096000.2013.1560805440185%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57295) EnvInject Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57295 EnvInject Plugin Change By: Ulli Hafner 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.199061.1556747654000.2011.1560805380419%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57296) Dashboard View Plugin
Title: Message Title Ulli Hafner started work on JENKINS-57296 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199062.1556747815000.2007.1560805380354%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57295) EnvInject Plugin
Title: Message Title Ulli Hafner started work on JENKINS-57295 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199061.1556747654000.2009.1560805380386%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57297) Timestamper Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57297 Timestamper Plugin Change By: Ulli Hafner 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.199063.1556747896000.2004.1560805320227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57298) List View Column (Core)
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57298 List View Column (Core) Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199064.1556748124000.2002.1560805260188%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57312 Provide tokens for new and fixed warnings Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199081.1556811582000.2000.1560805200378%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57325) Groovy Generator
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57325 Groovy Generator Change By: Ulli Hafner 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.199096.1556896079000.1997.1560805200320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57403) Use natural order to sort Details table
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57403 Use natural order to sort Details table Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199187.1557487169000.1995.1560805140141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57448) excludeMessage does not work with single quotes
Title: Message Title Ulli Hafner closed an issue as Cannot Reproduce Jenkins / JENKINS-57448 excludeMessage does not work with single quotes Change By: Ulli Hafner Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199261.1557822768000.1993.1560804960459%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57673) Add column sort to "Fixed Issues"
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57673 Add column sort to "Fixed Issues" Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199606.155872154.1991.1560804900143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57799) IndexOutOfBoundsException
Title: Message Title Ulli Hafner commented on JENKINS-57799 Re: IndexOutOfBoundsException I created an issue in the dependency: https://github.com/tomasbjerre/violations-lib/issues/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.199750.1559324204000.1989.1560804840253%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57799) IndexOutOfBoundsException
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57799 IndexOutOfBoundsException Change By: Ulli Hafner URL: https://github.com/tomasbjerre/violations-lib/issues/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.199750.1559324204000.1987.1560804780137%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57799) IndexOutOfBoundsException
Title: Message Title Ulli Hafner commented on JENKINS-57799 Re: IndexOutOfBoundsException Ping, please provide an example 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.199750.1559324204000.1985.1560804720123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57854) With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml
Title: Message Title Ulli Hafner commented on JENKINS-57854 Re: With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml Ping? I can change it but I'm not sure if this is really a problem for someone... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199813.1559715209000.1983.1560804300086%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner edited a comment on JENKINS-58056 Re: Add option to fail the step if no files are found for pattern Would it make sense to fail the build if there are any errors in the log of the warnings plugin (they all show up as errors in the info view of the plugin in a build)? Or should it fail only in the specific case of the non matching pattern? The former one would be much easier to implement (and would catch some other similar problems as well). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200077.1560795254000.1981.1560804240096%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner commented on JENKINS-58056 Re: Add option to fail the step if no files are found for pattern Would it make sense to fail the build if there are any errors in the log of the warnings plugin (they all show up as errors in the info view of the plugin in a build)? Or should it fail only in the specific case of the non matching pattern? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200077.1560795254000.1979.1560804180090%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58058) spotbugs
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-58058 spotbugs Issue Type: Task Assignee: Josh Soref Components: extras-executable-war Created: 2019-06-17 20:41 Priority: Minor Reporter: Josh Soref Bad practice Main.readStringNonBlocking(InputStream, int) ignores result of java.io.InputStream.read(byte[]) Method ignores results of InputStream.read() This method ignores the return value of one of the variants of java.io.InputStream.read() which can return multiple bytes. If the return value is not checked, the caller will not be able to correctly handle the case where fewer bytes were read than the caller requested. This is a particularly insidious kind of bug, because in many programs, reads from input streams usually do read the full amount of data requested, causing the program to fail only sporadically. Bug kind and pattern: RR - RR_NOT_CHECKED Dodgy code At MainTest.java:[line 15] In method MainTest.should HaveNoStandardDependenciesFile() Local variable named versions Dead store to local variable This instruction assigns a value to a local variable, but the value is not read or used in any subsequent instruction. Often, this indicates an error, because the value computed is never used. Note that Sun's javac compiler often generates dead stores for final local variables. Because SpotBugs is a bytecode-based tool, there is no
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58056 Add option to fail the step if no files are found for pattern Change By: Ulli Hafner Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200077.1560795254000.1976.1560803940120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56892) Add support for include what you use (IWYU)
Title: Message Title Ulli Hafner closed an issue as Postponed Typically, new parsers are added by contributors. Since nobody stepped in up to now I close the issue until someone reopens and tries to provide a PR. Jenkins / JENKINS-56892 Add support for include what you use (IWYU) Change By: Ulli Hafner Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.198563.1554437232000.1973.1560803760238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57789) Warning-ng plugin doesn't capture 'Hint' output from msBuild
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57789 Warning-ng plugin doesn't capture 'Hint' output from msBuild Change By: Ulli Hafner Labels: help-wanted newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199737.1559308621000.1970.1560803640167%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz commented on JENKINS-52781 Re: tar function is breaking symlinks Jesse Glick you're right. Added this in the plugin: https://github.com/jenkinsci/shelve-project-plugin/pull/19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.192677.1532710807000.1968.1560801180147%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz updated JENKINS-52781 Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Pierre Beitz 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.192677.1532710807000.1961.1560801121118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz updated JENKINS-52781 Jenkins / JENKINS-52781 tar function is breaking symlinks Change By: Pierre Beitz Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192677.1532710807000.1956.1560801121059%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52781) tar function is breaking symlinks
Title: Message Title Pierre Beitz started work on JENKINS-52781 Change By: Pierre Beitz 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.192677.1532710807000.1957.1560801121070%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 an issue
Jenkins / JENKINS-57990
Avoid filtering contents without sensible data and do per-content anonymization
Change By:
Ramon Leon
Change the behavior of the {{Contents}} to avoid filtering when it's not needed. And change the way it's anonymized by delegating it to the component to avoid losing the structure of the information.*Should be filtered* * NodesContent: include labels and filesystem path * AboutUser * AgentsConfigFile (secrets encrypted but maybe other sensitive info) * BuildQueue: name of the job * ConfigFileComponent (secrets encrypted but maybe other sensitive info) * EnvironmentVariables * JenkinsLogs * JVMProcessSystemMetricsContent (environment variables) * LoggerManager * NetworInterfaces (ips) * NodeMonitors (computer name) * OtherConfigFilesComponent * RoocCAs * SlaveLaunchLogs * SlaveLogs * SystemConfiguration Agents and Master (user running) * UpdateCenter (proxy information: urls) * SystemProperties*Shouldn’t be filtered* * AboutContent * AboutBrowser * ActivePlugins * DisabledPlugins * FailedPlugins * Dockerfile * MasterChecksumsContent * NodeChecksumsContent * AdministrativeMonitors * DeadlockRequestComponent * DumpExportTable * FileDescriptorLimit * GCLogs - Out of scope, it needs some refactor of classes. To tackle on another ticket - Done because i needed the infra for other components. * HeapUsageHistogram * ItemsContent * LoadStats * Metrics * RemotingDiagnostics * ReverseProxy * SlaveCommandStatistics * SlowRequestComponent * ThreadDumpsAvoid anonymizing the labels, the structure of the files under the control of the plugin (.md files, and information files). Analyze what values should be anonymized.The contents generated on the fly are going to extend the PrefilteredContent by creating a new *PrefilteredPrintedContent* and they are going to filter the information by themselves.The ones that are being filtered and shouldn't to will override the {{shouldBeFiltered}} method to avoid that.h3. Acceptance criteria * The support-core plugin is changed by creating a new {{PrefilteredPrintedContent}} that extends {{PrefilteredContent}} * The contents that don't need to be filtered don't do that by overriding {{shouldBeFiltered}} (false) * The contents that need to be filtered extends from a {{PrefilteredContent}}, most likely {{PrefilteredPrintedContent}} and do the filtering by themselves implementing the new {{writeTo}} method. Look at: [https://github.com/jenkinsci/support-core-plugin/blob/e2d79249818d4ea96979a710ac3404018f78/src/main/java/com/cloudbees/jenkins/support/api/StringContent.java#L58] avoiding to filter the structure of the markdown or whatever is going to affect the comprehension of the content. * Some tests are implemented for: * * * A content that was filtered and now it's not * * * A content that was filtered affecting the structure (markdown) and now it's not affected * The PR in support-core is merged
[JIRA] (JENKINS-57990) Avoid filtering contents without sensible data and do per-content anonymization
Title: Message Title Ramon Leon commented on JENKINS-57990 Re: Avoid filtering contents without sensible data and do per-content anonymization PR: https://github.com/jenkinsci/support-core-plugin/pull/174/files Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.1951.1560801060112%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 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.199975.1560350087000.1950.1560800580087%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Larry West edited a comment on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable My $0.02 – this is such an annoying bug. And seemingly trivial to fix.We had been telling our users to look in the Blue Ocean output to see what happened to their build, because the graphic view of pipelines has the potential to make it much clearer.But then they see 10 or 20 or 50 "Print message" lines and have to click most of them to see the important messages.It's not clear there is any purpose behind this hiding the text .And we often have to tell them how to find their way to the "pipeline.log" to get the full story.So it's easier to tell people to just go to the old style console log :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.1936.1560799560417%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Larry West commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable My $0.02 – this is such an annoying bug. And seemingly trivial to fix. We had been telling our users to look in the Blue Ocean output to see what happened to their build, because the graphic view of pipelines has the potential to make it much clearer. But then they see 10 or 20 or 50 "Print message" lines and have to click most of them to see the important messages. It's not clear there is any purpose behind this. And we often have to tell them how to find their way to the "pipeline.log" to get the full story. So it's easier to tell people to just go to the old style console log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194144.1537309242000.1921.1560799500440%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58057) Jenkins CLI - notable to execute
Title: Message Title Khurram Shahzad created an issue Jenkins / JENKINS-58057 Jenkins CLI - notable to execute Issue Type: Task Assignee: Unassigned Components: cli Created: 2019-06-17 19:23 Environment: Jenkins latest version Priority: Minor Reporter: Khurram Shahzad D:\Program Files (x86)\Jenkins\tools>java -jar jenkins-cli.jar -s http://myservername:8080/ -auth myusername:mypassword help java.io.IOException: Server returned HTTP response code: 401 for URL: http://myservername:8080/cli?remoting=false at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.cli.FullDuplexHttpStream.(FullDuplexHttpStream.java:72) at hudson.cli.CLI.plainHttpConnection(CLI.java:279) at hudson.cli.CLI._main(CLI.java:271) at hudson.cli.CLI.main(CLI.java:83) Add Comment
[JIRA] (JENKINS-57814) The unicode of Jira changelog maybe incorrect
Title: Message Title Wisen Tanasa commented on JENKINS-57814 Re: The unicode of Jira changelog maybe incorrect Thanks for getting back to this issue. I'm a little tight on my capacity at the moment and it's going to take sometime (few weeks) before I can have start looking into this issue. Feel free to contribute to the project though! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199766.1559546507000.1918.1560799200081%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57245) Support Kotlin compiler warnings (in an obvious manner)
Title: Message Title Ulli Hafner updated JENKINS-57245 Jenkins / JENKINS-57245 Support Kotlin compiler warnings (in an obvious manner) Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199008.1556622259000.1916.1560798960301%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title Mark Waite edited a comment on JENKINS-58049 Re: GIT SparseCheckout for multiple clones This is not a bug as far as I can tell. Refer to [my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-58049/Jenkinsfile] for a working example.I was able to confirm that sparse checkout is not correctly supported by the command line git version that is included with CentOS 6. CentOS 6 includes command line 1.7.1 which is not supported by the Jenkins git plugin. There are authentication modes which that old version of command line git does not support and several other features which are not available. The current version of command line git is 2.22.0. Sparse checkout is also not supported by the JGit implementation that is bundled inside the git client plugin. However, the JGit implementation is not enabled by default. If it is enabled and a Pipeline job is configured to use it, and the Pipeline job attempts to perform a sparse checkout, then the Pipeline checkout will fail with a message that sparse checkout is not supported by JGit. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200070.1560780449000.1913.1560797880117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title Mark Waite updated JENKINS-58049 Jenkins / JENKINS-58049 GIT SparseCheckout for multiple clones 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.200070.1560780449000.1911.1560796800233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title Mark Waite edited a comment on JENKINS-58049 Re: GIT SparseCheckout for multiple clones This is not a bug as far as I can tell. Refer to [my jenkins-bugs repo|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-58049/Jenkinsfile] for a working example. I was able to confirm that sparse checkout is not correctly supported by the command line git version that is included with CentOS 6. CentOS 6 includes command line 1.7.1 which is not supported by the Jenkins git plugin. There are authentication modes which that old version of command line git does not support and several other features which are not available. The current version of command line git is 2.22.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.200070.1560780449000.1909.1560796800198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57851) Jenkins redirect from bitbucket results in broken link
Title: Message Title chetan muthappa edited a comment on JENKINS-57851 Re: Jenkins redirect from bitbucket results in broken link I face this issue as well, I have the plugin | |[Bitbucket Build Status Notifier Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Bitbucket+Cloud+Build+Status+Notifier+Plugin]| version [1.4.1|https://rb-jmaas.de.bosch.com/Athena_Video/pluginManager/plugin/bitbucket-build-status-notifier/thirdPartyLicenses] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.1907.1560796200192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[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 I face this issue as well, I have the plugin version 1.4.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.199809.1559686662000.1904.1560795960356%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58056) Add option to fail the step if no files are found for pattern
Title: Message Title
Robert Rodrigues created an issue
Jenkins / JENKINS-58056
Add option to fail the step if no files are found for pattern
Issue Type:
New Feature
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-06-17 18:14
Priority:
Major
Reporter:
Robert Rodrigues
If the plugin's step is configured with a file pattern which does not match any files, it logs the error but has no options for having this actually fail the step/build. i.e. {{[CodeNarc] [-ERROR-] No files found for pattern 'build/reports/codenarc/*.xml'. Configuration error?}}
Add Comment
[JIRA] (JENKINS-57772) Build strategy for tags is not working, if you specify ignore tags lesser than 7days
Title: Message Title Liam Newman commented on JENKINS-57772 Re: Build strategy for tags is not working, if you specify ignore tags lesser than 7days Here is where the plugin tests dates and it uses the "timestamp" of the tag: https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/src/main/java/jenkins/branch/buildstrategies/basic/TagBuildStrategyImpl.java#L152 It is up to the the implementers of TagSCMHead to provide that: https://github.com/jenkinsci/scm-api-plugin/blob/master/src/main/java/jenkins/scm/api/mixin/TagSCMHead.java The git plugin does what Mark Waite described - use the date of tag creation for annotated tags and the date of the last commit for lightweight tags: https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/jenkins/plugins/git/GitTagSCMHead.java#L37-L38 This comment on SO repeats what Mark Waite said: There is no date information attached to a lightweight tag. ... The dates in the output of git log --tags --simplify-by-decoration --pretty="format:%ai %d" are the dates of the objects to which the tags point, not the dates when the tags themselves were created. I think either of the command above would have this same problem, but you'd need to test them to be sure. Further, it is likely that this behavior will differ depending on the underlying branch source - git, github, bitbucket, etc. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.199719.1559261241000.1897.1560794940676%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-58055) NPE Cannot get property 'closure' after resume on Jenkins restart
Title: Message Title John Malmberg created an issue Jenkins / JENKINS-58055 NPE Cannot get property 'closure' after resume on Jenkins restart Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2019-06-17 17:59 Environment: CentOS Linux release 7.5.1804 (Core) 64 bit. java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode) jenkins.noarch 2.164.3-1.1 @jenkins Jenkins running in a CentOS 7.5 VM as a service via the rpm. Jenkins running via reverse proxy HA-PROXY. Slave node launched by SSH. Web Browser: Firefox 67.0.1 Plugins: blue-ocean 1.16.0 branch-api 2.5.2 credentials-binding 1.20 credentials 2.2.20 github-branch-source 2.5.3 pipeline-build-step 2.9 pipeline-github 2.5 pipeline-github-lib 1.0 pipeline-githubnotify-step 1.0.4 pipeline-graph-analysis 1.10 pipeline-input-step 2.1.0 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.8 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.8 pipeline-model-extensions 1.3.8 pipeline-rest-api 2.11 pipeline-stage-step 2.3 pipeline-stage-tages-metadata 1.3.8 pipeline-stage-view 2.11 pipeline-utility-steps 2.3.0 workflow-aggregator 2.6 workflow-api 2.3.4 workflow-basic-steps 2.16 workflow-cps-global-lib 2.1.3 workflow-cps 2.68 workflow-durable-task-step 2.3.0 workflow-job 2.32 workflow-multibranch 2.21 workflow-scm-step 2.7 workflow-step-api 2.19 workflow-support 3.3 Priority: Minor Reporter: John Malmberg This issue occurred after doing an upgrade of Plugins: branch-api from 2.5.0 to 2.5.2 credentials-binding 1.18 to 2.19 credentials 2.1.19 to 2.2.0 github-branch-source 2.5.2 to 2.5.3 workflow-basic-steps 2.16 to 2.18 workflow-cps 2.68 to
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title
Mez Pahlan created an issue
Jenkins / JENKINS-58054
Support release notes
Issue Type:
New Feature
Assignee:
Mez Pahlan
Components:
appcenter-plugin
Created:
2019-06-17 17:47
Priority:
Major
Reporter:
Mez Pahlan
Support updating the release with release notes specified in Markdown format. PATCH /v0.1/apps/ {owner_name} / {app_name} /releases/ {release_id} Is the API that allows uploading of release notes. Acceptance: 1. Users can enter release notes via the plugin front end. 2. Release notes sent via the API to AppCenter
Add Comment
[JIRA] (JENKINS-57235) Seed job (job-dsl) runs trigger a rebuild of all multibranch pipelines branches
Title: Message Title Jonathan Pigrée commented on JENKINS-57235 Re: Seed job (job-dsl) runs trigger a rebuild of all multibranch pipelines branches Thanks. I found this solution myself a while ago and forgot to update the 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.198995.1556591767000.1889.1560793020220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title
Mez Pahlan updated an issue
Jenkins / JENKINS-58054
Support release notes
Change By:
Mez Pahlan
Support updating the release with release notes specified in Markdown format.PATCH/v0.1/apps/ \ {owner_name \ }/ \ {app_name \ }/releases/ \ {release_id \ }Is the API that allows uploading of release notes.Acceptance:1. Users can enter release notes via the plugin front end.2. Release notes sent via the API to AppCenter
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.200075.1560793667000.1893.1560793740068%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43400) Autofavorite broken on remote agents
Title: Message Title Christopher Sang commented on JENKINS-43400 Re: Autofavorite broken on remote agents This issue started occurring for me on BlueOcean 1.17.0 / autofavorite plugin 1.2.4. In addition to filling our logs with stack traces, it also seems to break the rendering of pipeline input steps. Is anyone else experiencing this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180643.1491509101000.1875.1560791640345%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-58049 GIT SparseCheckout for multiple clones Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200070.1560780449000.1872.1560790740284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title Mark Waite updated JENKINS-58049 This is not a bug as far as I can tell. Refer to my jenkins-bugs repo for a working example. Jenkins / JENKINS-58049 GIT SparseCheckout for multiple clones Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200070.1560780449000.1870.1560790680203%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58049) GIT SparseCheckout for multiple clones
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58049
GIT SparseCheckout for multiple clones
Change By:
Mark Waite
Hi,While trying to use sparseCheckout option under jenkins build step or in pipeline script. i am unable to use it for multiple directories checkout. In both instances the path mentioned at the last checks out ignoring the earlier ones. This is the code i am using {noformat} checkout( [ $class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [ [$class: 'SparseCheckoutPaths', sparseCheckoutPaths: [[path: 'TIA-Profiles/*'], [path: '${TARGET_ENVIRONMENT}/*']]] ], submoduleCfg: [], userRemoteConfigs: [ [ credentialsId: '***', url: 'ssh://g...@bitbucket.internal.fbd.ie:7999/rem/properties.git' ]]]) {noformat} It ignores the first path [path: 'TIA-Profiles/*'] and only checks-out path: '${TARGET_ENVIRONMENT}/*']Out Repo contitutes of multiple directories and properties files and we don't want to checkout all of it in workspace due security and space constraints. Had tried multiple different ways of doing it but does not works. Kindly suggest.Thanks,
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-54557) hudson.AbortException: Ansible playbook execution failed
Title: Message Title
Shaik Nagulameera commented on JENKINS-54557
Re: hudson.AbortException: Ansible playbook execution failed
Hi Team, I have created the job to deploy AKS on Azure using Ansible Here is my environment details: Ansible Version: 2.5.1 Jenkins Version: 2.180 once I start the build getting below error: fatal: [localhost]: FAILED! => {"changed": false, "msg": "Do you have packaging installed? Try `pip install packaging`- No module named packaging.version"}fatal: [localhost]: FAILED! => {"changed": false, "msg": "Do you have packaging installed? Try `pip install packaging`- No module named packaging.version"} to retry, use: --limit @/var/lib/jenkins/workspace/K8s/aks-azure-cni.retry PLAY RECAP *localhost : ok=1 changed=0 unreachable=0 failed=1 FATAL: command execution failedhudson.AbortException: Ansible playbook execution failed at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:262) at org.jenkinsci.plugins.ansible.AnsiblePlaybookBuilder.perform(AnsiblePlaybookBuilder.java:232) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1818) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)ERROR: Ansible playbook execution failedFinished: FAILURE Please let me know the changes I have to do. Thanks & Regards Shaik.Nagulameera
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
[JIRA] (JENKINS-58028) Move from gmaven-plugin to gmavenplus-plugin
Title: Message Title Liam Newman commented on JENKINS-58028 Re: Move from gmaven-plugin to gmavenplus-plugin Jesse Glick It seems like something we could find a way to produce a warning/error for - https://maven.apache.org/enforcer/enforcer-rules/bannedPlugins.html . We could make both available to start and then ban gmaven in a later release. I understand you have a strong opinion about how groovy should and should not be used in the project, but that is a much larger change. This change, on the other hand, is almost a drop in replacement that unblocked one of our core plugins to build and run on Java 11. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.200048.1560550059000.1837.1560789120154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31314) Running asynchronous code inside a @NonCPS method should fail cleanly
Title: Message Title Devin Nusbaum updated JENKINS-31314 Jenkins / JENKINS-31314 Running asynchronous code inside a @NonCPS method should fail cleanly Change By: Devin Nusbaum Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166049.1446212529000.1813.1560787982484%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56925) extra newline character from powershell output
Title: Message Title
Patrik Ehringer edited a comment on JENKINS-56925
Re: extra newline character from powershell output
Maybe this is related...The console output is different for the 2 scripts below - depending on if 'returnStdout: true' is used or not.The second script does it right, the first - where 'returnStdout: true' is used - does it wrong.I'm quite sure that the first script also worked correctly 2 months or so ago. {code:java}pipeline {agent anystages {stage('Test') {steps {script {stdo = powershell(returnStdout: true, script: ''' Write-Host "Will there be a newline after me? " -NoNewLine Write-Host "Yes! -> Unfortunately!"''')}script {powershell(script: ''' Write-Host "Will there be a newline after me? " -NoNewLine Write-Host "No! -> Great!"''')}}}}}{code} {noformat} [Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] script[Pipeline] {[Pipeline] powershellWill there be a newline after me? Yes! -> Unfortunately![Pipeline] }[Pipeline] // script[Pipeline] script[Pipeline] {[Pipeline] powershellWill there be a newline after me? No! -> Great![Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.198603.1554635511000.1810.1560787560141%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56925) extra newline character from powershell output
Title: Message Title
Patrik Ehringer commented on JENKINS-56925
Re: extra newline character from powershell output
Maybe this is related... The console output is different for the 2 scripts below - depending on if 'returnStdout: true' is used or not. The second script does it right, the first - where 'returnStdout: true' is used - does it wrong. I'm quite sure that the first script also worked correctly 2 months or so ago.
pipeline {
agent any
stages {
stage('Test') {
steps {
script {
stdo = powershell(returnStdout: true, script: '''
Write-Host "Will there be a newline after me? " -NoNewLine
Write-Host "Yes! -> Unfortunately!"
''')
}
script {
powershell(script: '''
Write-Host "Will there be a newline after me? " -NoNewLine
Write-Host "No! -> Great!"
''')
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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.198603.1554635511000.1807.1560787500142%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48398) [Ionic + Cordova + Gradle + Android + Jenkins on Windows] Build failed with the pipe is being closed
Title: Message Title
Dario Telese commented on JENKINS-48398
Re: [Ionic + Cordova + Gradle + Android + Jenkins on Windows] Build failed with the pipe is being closed
Hello, this solution is great!! Look: https://stackoverflow.com/questions/51934907/gradlew-change-jcenter-url-for-react-native-build In .gradle Jenkins directory, create init.gradle file and insert this code:
apply plugin: EnterpriseRepositoryPlugin
class EnterpriseRepositoryPlugin implements Plugin {
private static String NEXUS_REPO = "https://mynexus/repository/mymavenrepo/"
private static String GOOGLE_REPOSITORY_URL = "https://dl.google.com/dl/android/maven2/"
private static String JCENTER_REPOSITORY_URL = "https://jcenter.bintray.com/"
private static String MAVEN_REPOSITORY_URL = "https://repo.maven.apache.org/maven2/"
void apply(Gradle gradle) {
// ONLY USE NEXUS REPO FOR DEPENDENCIES
gradle.allprojects { project ->
project.repositories {
// Remove all repositories not pointing to the NEXUS repository url
all { ArtifactRepository repo ->
if ((repo instanceof MavenArtifactRepository)){
if ((repo.url.toString() == GOOGLE_REPOSITORY_URL) || (repo.url.toString() == JCENTER_REPOSITORY_URL) || (repo.url.toString() == MAVEN_REPOSITORY_URL) ) {
project.logger.lifecycle "Repository ${repo.name} removed. Only NEXUS REPOSITORY is allowed"
remove repo
}
}
}
// add the NEXUS repository
maven {
name "NEXUS_REPO"
url NEXUS_REPO
}
}
}
}
}
Customize for your case and enjoy!! Bye
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-58053) Original login page still accessible
Title: Message Title John Jerry created an issue Jenkins / JENKINS-58053 Original login page still accessible Issue Type: Bug Assignee: Mohamed El Habib Components: gitlab-oauth-plugin Created: 2019-06-17 15:25 Environment: Plugin version: 1.4 Jenkins version: 2.180 Running Jenkins directly Priority: Major Reporter: John Jerry After installing the GitLab OAuth Plugin the authentication is performed using GitLab. Unfortunately the original Jenkins login page is still accessible under http:///login Using the plugin this page should not be accessible or it should redirect triggering the intended GitLab authentication. Add Comment
