[JIRA] (JENKINS-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström commented on JENKINS-54038 Re: Jacoco creates multiple Coverage reports and Trends graphs Can someone who has the knowledge address this issue plz? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Tomasz Śniatowski commented on JENKINS-54116 Re: Jenkins Jira Plugin - Unable to add version Setting these to non-zero values seems to have helped in my case, but such manual action shouldn't be necessary. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Tomasz Śniatowski commented on JENKINS-54116 Re: Jenkins Jira Plugin - Unable to add version I started getting the same error on all builds on the changelog annotation step after upgrading to 3.0.3, I also found Read timeout and Thread Executor Size both set to zero in the config. It seems the defaults and/or migration is not done properly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54132) Get JEP-8 (GSoC buget) approved
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54132 Get JEP-8 (GSoC buget) approved Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54132) Get JEP-8 (GSoC buget) approved
Title: Message Title Oleg Nenashev started work on JENKINS-54132 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Jesse Glick commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) As already noted in this issue, you can already use withCredentials or sshagent to accomplish this use case. This enhancement would simply make it more convenient. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Jesse Glick commented on JENKINS-21336 Re: ADMINISTER should not imply RUN_SCRIPTS Migrating permissions from the previous set to the new one might be complicated, though. Indeed. See discussion in JENKINS-17200. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37224) Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37224 Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Jesse Glick Labels: regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Likely similar cause to JENKINS-54081—console notes generated in the agent JVM are not trusted and thus ignored during rendering. The best fix would likely be analogous to what I did for JENKINS-48344: deprecate the build wrapper at least for Pipeline, and replace the contextual ConsoleLogFilter with a global TaskListenerDecorator that is able to render ANSI escape sequences in the HTML view rather than embedding SimpleHtmlNote objects. This would have the same efficiency benefit as for JENKINS-48344 (get rid of a vast volume of junk in log), as well as improving Blue Ocean compatibility with a major sore point with this plugin today: you can choose to either enable the wrapper and thus render colors in classic UI but see plain text in BO; or do nothing and thus render colors in BO but see raw escape sequences in classic 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Jesse Glick Component/s: ansicolor-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54043) Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error
Title: Message Title Keng Seng Hor closed an issue as Fixed Closed. Jenkins / JENKINS-54043 Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error Change By: Keng Seng Hor Status: Resolved Closed Assignee: Bruno P. Kinoshita Keng Seng Hor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54043) Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error
Title: Message Title Keng Seng Hor resolved as Fixed Jenkins / JENKINS-54043 Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error Change By: Keng Seng Hor Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54141) After downgrading a plugin the status page doesn't indicate "Pending restart"
Title: Message Title Ethan Spoelstra created an issue Jenkins / JENKINS-54141 After downgrading a plugin the status page doesn't indicate "Pending restart" Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-18 02:56 Environment: Jenkins 2.146 upgraded to 2.147 Java 1.8.0_b181 Ubuntu 14.04 x86_64 Priority: Minor Reporter: Ethan Spoelstra While testing some scripts to automate collecting updated plugins and their versions for our configuration management I wanted to make sure the scripts were idempotent or at least consistent in upgrading everything with an available update that wasn't pinned. To do so I performed a manual downgrade of several plugins through the UI (they were updated from the initial config managed versions by my script) but noticed that on the /updateCenter page I was brought to after clicking 'Downgrade' that the status after downgrading was "Success", with no mention of the restart that IS required to make the downgrade(s) actually take effect. I tested downgrading a couple other plugins with the same result. Navigating to the /pluginManager page I saw that it did have a note at the bottom that an operation was 'awaiting restart' but going to the "pending operations" aka /updateCenter page it simply showed the "Success" status and still no suggestion that the restart was required though the checkbox to restart when no jobs were running was present and usable.
[JIRA] (JENKINS-54043) Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error
Title: Message Title Keng Seng Hor commented on JENKINS-54043 Re: Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error JellyException issue resolved. Rebuilt testlink.jar file to include sidepanel.jelly file into TestLinkResult folder. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54043) Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error
Title: Message Title Keng Seng Hor edited a comment on JENKINS-54043 Re: Clicking "TestLink results" received org.apache.commons.jelly.JellyTagException error JellyException JellyTagException issue resolved. Rebuilt testlink.jar file to include sidepanel.jelly file into TestLinkResult folder. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54140) Unable to archive report when run UFT test from file system
Title: Message Title tracy he created an issue Jenkins / JENKINS-54140 Unable to archive report when run UFT test from file system Issue Type: Bug Assignee: Steven Hermans Components: microdocs-integration-plugin Created: 2018-10-18 02:30 Environment: Jenkins 2.60.3 Micro Focus Application Automation Tools 5.5.2-beta Priority: Major Reporter: tracy he We are getting error when run UFT tests from file system (plugin version is 5.5.2-beta), it throws exception when publish test report. Here is the Error Details It's working when run UFT tests from ALM. Recording test results Report archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORT Zipping report folder: C:\JenkinsMO6\workspace\AOS-COMMON-105-SCM-UFT\Advantage_Shopping\Report copy from slave to master: /var/jenkins_home/jobs/AOS-COMMON-105-SCM-UFT/builds/3/archive/Advantage_Shopping_Report.zip ERROR: Build step failed with exception java.lang.NullPointerException at com.microfocus.application.automation.tools.results.RunResultRecorder.writeReportMetaData2XML(RunResultRecorder.java:603) at com.microfocus.application.automation.tools.results.RunResultRecorder.archiveTestsReport(RunResultRecorder.java:566) at com.microfocus.application.automation.tools.results.RunResultRecorder.recordRunResults(RunResultRecorder.java:217) at com.microfocus.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1462) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676) at
[JIRA] (JENKINS-44405) Unable to archive reports after test
Title: Message Title tracy he edited a comment on JENKINS-44405 Re: Unable to archive reports after test We are getting error when run UFT tests from file system (plugin version is 5.5.2-beta), it throws exception when publish test report. Here is the Error Details And this only happens when run UFT tests from file system, it's working when run UFT tests from ALM Recording test resultsReport archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORTZipping report folder: C:\JenkinsMO6\workspace\AOS-COMMON-105-SCM-UFT\Advantage_Shopping\Reportcopy from slave to master: /var/jenkins_home/jobs/AOS-COMMON-105-SCM-UFT/builds/3/archive/Advantage_Shopping_Report.zipERROR: Build step failed with exceptionjava.lang.NullPointerException at com.microfocus.application.automation.tools.results.RunResultRecorder.writeReportMetaData2XML(RunResultRecorder.java:603) at com.microfocus.application.automation.tools.results.RunResultRecorder.archiveTestsReport(RunResultRecorder.java:566) at com.microfocus.application.automation.tools.results.RunResultRecorder.recordRunResults(RunResultRecorder.java:217) at com.microfocus.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1462) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621) at hudson.model.Run.execute(Run.java:1760) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405)Build step 'Publish Micro Focus tests result' marked build as failureFinished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-44405) Unable to archive reports after test
Title: Message Title tracy he commented on JENKINS-44405 Re: Unable to archive reports after test We are getting error when run UFT tests from file system (plugin version is 5.5.2-beta), it throws exception when publish test report. Here is the Error Details Recording test results Report archiving mode is set to: ALWAYS_ARCHIVE_TEST_REPORT Zipping report folder: C:\JenkinsMO6\workspace\AOS-COMMON-105-SCM-UFT\Advantage_Shopping\Report copy from slave to master: /var/jenkins_home/jobs/AOS-COMMON-105-SCM-UFT/builds/3/archive/Advantage_Shopping_Report.zip ERROR: Build step failed with exception java.lang.NullPointerException at com.microfocus.application.automation.tools.results.RunResultRecorder.writeReportMetaData2XML(RunResultRecorder.java:603) at com.microfocus.application.automation.tools.results.RunResultRecorder.archiveTestsReport(RunResultRecorder.java:566) at com.microfocus.application.automation.tools.results.RunResultRecorder.recordRunResults(RunResultRecorder.java:217) at com.microfocus.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1462) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621) at hudson.model.Run.execute(Run.java:1760) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Build step 'Publish Micro Focus tests result' marked build as failure Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title
Josh McDonald commented on JENKINS-53900
Re: Stage graph in Blue Ocean not showing all stages for large workflows
Righto, good progress, I've built a minimal pipeline that generates the issue reliably, and figured out the trigger: https://gist.github.com/sophistifunk/39cec79eb7d353b67bd70b75a61f95bc It seems that any time you have all of these conditions:
A parallel stage
The last parallel branch (in file order) is nested in a sequential wrapper, ie:
stage('foo') { stages { /*...*/ } }
The sequential wrapper only has one child stage
Then the generated graph data is broken for nodes coming after the offending top-level stage. The problem is (almost certainly) in Blue Ocean server, or (far less likely) the Pipeline plugin. I'll find out which one and get a fix in, should be a small change once I identify the right spot.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Josh Pollara commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Downgrading to Jenkins 2.145 fixed the issue for me. Poor long-term solution. Hoping this is fixed sooner rather than later. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Keith Collison commented on JENKINS-54139 Re: Jacoco report rendering problem google groups discussion link: https://groups.google.com/d/msg/jenkinsci-users/bJ2DGVTWP_Y/UnbtqQh9AwAJ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Keith Collison updated an issue Jenkins / JENKINS-54139 Jacoco report rendering problem Change By: Keith Collison Attachment: jenkinslog.stacktrace.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Keith Collison updated an issue Jenkins / JENKINS-54139 Jacoco report rendering problem Change By: Keith Collison Attachment: jenkinslog.stacktrace.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Keith Collison updated an issue Jenkins / JENKINS-54139 Jacoco report rendering problem Change By: Keith Collison Upon upgrading to the latest pipeline-maven-plugin (3.5.14) , all of our Jacoco report renderings have gone haywire. Specifically, there are 17 "Coverage Trend" links on a branch's side bar, and many trend graphs. The same is true on each individual build page.We are using a multi-branch pipeline, using "withMaven". Our project is a multi-module maven build.There is a seemingly related stacktrace in the jenkins logs that I will also include on this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Keith Collison created an issue Jenkins / JENKINS-54139 Jacoco report rendering problem Issue Type: Bug Assignee: Alvaro Lobato Attachments: coverage_trend_links.png, jenkinslog.stacktrace.txt Components: pipeline-maven-plugin Created: 2018-10-18 01:44 Environment: linux Priority: Major Reporter: Keith Collison Upon upgrading to the latest pipeline-maven-plugin, all of our Jacoco report renderings have gone haywire. Specifically, there are 17 "Coverage Trend" links on a branch's side bar, and many trend graphs. The same is true on each individual build page. We are using a multi-branch pipeline, using "withMaven". Our project is a multi-module maven build. There is a seemingly related stacktrace in the jenkins logs that I will also include on this issue. Add Comment
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Vivek Pandey commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Jesse Glick ptal to rule out possible regression. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Vivek Pandey assigned an issue to Jesse Glick Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline Change By: Vivek Pandey Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. A couple of questions here: Is this a recent thing - did it work before, or is this the first time? Can you post a screenshot of your debian pbuilder build configuration or the relevant part of your Jenkinsfile? Can you post a screenshot of what your workspace for this build looks like? It seems to be failing because either the 'binaries' directory was not created, or there is no .dsc file to build. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54032) ArgumentsActionImpl should protect against storing bizarre step arguments
Title: Message Title Sam Van Oort updated JENKINS-54032 released Jenkins / JENKINS-54032 ArgumentsActionImpl should protect against storing bizarre step arguments Change By: Sam Van Oort Status: In Review Closed Resolution: Done Released As: workflow-cps 2.59 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title
Brian J Murrell commented on JENKINS-54035
Re: can't exclude everything under a given dir
I have. It doesn't seem to help. Currently I am using:
recordIssues enabledForFailure: true,
aggregatingResults: true,
tools: [
[tool: [$class: 'GnuMakeGcc']],
[tool: [$class: 'CppCheck']],
],
filters: [excludeFile('.*\\/_build\\.external\\/.*'),
excludeFile('_build\\.external\\/.*')]
}
at the end of my parallel step which contains two builds, one each for CentOS and Ubuntu.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36375) Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs
Title: Message Title Hector Santana commented on JENKINS-36375 Re: Change assembly version is adding ? char at the beginning of the AssemblyInfo.cs This was merged as part of https://github.com/jenkinsci/change-assembly-version-plugin/pull/11. Now we just need to wait for the next release. Probably v1.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-54084 Create audit catalog repository Change By: Matt Sicker Comparable to [the sample API module|https://github.com/apache/logging-log4j-audit-sample], this repository should be used to record the audit catalog JSON file (managed by an instance of the catalog editor which is typically done on your own computer) as well as provide a build artifact to include the generated audit event code. In this repository, we should have a skeleton plugin and Maven build available. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker commented on JENKINS-54084 Re: Create audit catalog repository I created an initial repository at https://github.com/jvz/audit-log-plugin Once we have some code, we can get it moved to the jenkinsci org. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker assigned an issue to Hashini Galappaththi Jenkins / JENKINS-54084 Create audit catalog repository Change By: Matt Sicker Assignee: Matt Sicker Hashini Galappaththi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54084) Create audit catalog repository
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-54084 Create audit catalog repository Change By: Matt Sicker Assignee: Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Nick Lloyd commented on JENKINS-53952 Re: Linux slaves are not starting anymore We consistently hit this error using spot instances with the latest LTS Jenkins version. Using spot instances in a VPC with no public IP. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41147) bitbucket-build-status-notifier-plugin fails for multiple Git repo
Title: Message Title Sean MacKay commented on JENKINS-41147 Re: bitbucket-build-status-notifier-plugin fails for multiple Git repo I get this error when merging my PR branches together before running the build. I think the notifier does not know which branch to send notifications for since it's a merged commit that isn't in the bitbucket remote. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title marlene cote commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed Mark, thanks for the advice. your comment actually led me right to the culprit. a hook on one of my Bitbucket repos. thank you! Marlene Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48011) Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java
Title: Message Title
Shannon Kerr edited a comment on JENKINS-48011
Re: Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java
I just got this using Artifactory plugin version 2.16. 1 2 with [Jenkins ver. 2.138.1|https://jenkins.io/].{code:java}def newBuildInfo = Artifactory.newBuildInfo()def buildInfo = newBuildInfobuildInfo = (server.download(apiDownloadSpec))buildInfo.append = newBuildInfobuildInfo.number = versionnode (remoteBuildServer) {buildInfo.env.collect()server.upload(buildUploadSpec, buildInfo)}server.publishBuildInfo(buildInfo){code} Fails on the buildInfo.env.collect() from above:{code:java}java.lang.NullPointerException at org.jfrog.hudson.pipeline.types.buildInfo.Env.collect(Env.java:105) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:47) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:156) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:77) at sun.reflect.GeneratedMethodAccessor624.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$101(SandboxContinuable.java:34) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.lambda$run0$0(SandboxContinuable.java:59) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at
[JIRA] (JENKINS-37224) Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37224 Snippet Generator produces incorrect output for "Merge strategy" of "Merge before build" for GIT Change By: Sam Van Oort Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48011) Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java
Title: Message Title
Shannon Kerr commented on JENKINS-48011
Re: Calling buildInfo.env.collect after buildInfo.append(server.upload(uploadSpec)) causing NPE in Env.java
I just got this using Artifactory plugin version 2.16.1 with Jenkins ver. 2.138.1.
def newBuildInfo = Artifactory.newBuildInfo()
def buildInfo = newBuildInfo
buildInfo = (server.download(apiDownloadSpec))
buildInfo.append = newBuildInfo
buildInfo.number = version
node (remoteBuildServer) {
buildInfo.env.collect()
server.upload(buildUploadSpec, buildInfo)
}
server.publishBuildInfo(buildInfo)
Fails on the buildInfo.env.collect() from above:
java.lang.NullPointerException
at org.jfrog.hudson.pipeline.types.buildInfo.Env.collect(Env.java:105)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:47)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at WorkflowScript.run(WorkflowScript:156)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixName(FunctionCallBlock.java:77)
at sun.reflect.GeneratedMethodAccessor624.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:83)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174)
at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163)
at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122)
at
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title Ulli Hafner commented on JENKINS-54035 Re: can't exclude everything under a given dir I’m on vacation till end of October. Maybe you can try the gccmake parser in the meantime... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Mark Waite commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed marlene cote a question asked on a bug report has much less chance of a response than a question asked in one of the chat systems or on the mailing list. Fewer people read the bug reports than read the chat system and the mailing list. I don't know why it reports "started by an SCM change". That is usually an indicator that a notifyCommit was received or that a webhook was called. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54138) Author a JEP for audit logging proposal
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-54138 Author a JEP for audit logging proposal Issue Type: Task Assignee: Unassigned Components: core Created: 2018-10-17 19:28 Labels: audit-logging Priority: Minor Reporter: Matt Sicker In order to better advertise the API and features enabled by this plugin, a new JEP should be authored to describe the proposed design. Add Comment
[JIRA] (JENKINS-54137) Do not submit empty telemetry data
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54137 Do not submit empty telemetry data Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 2018-10-17 19:03 Labels: telemetry Priority: Minor Reporter: Daniel Beck Currently, telemetry is always submitted. Skip sending 'empty' data, and rework existing trials in core to adapt to the change. Add Comment
[JIRA] (JENKINS-54135) Thread unsafe behavior in UserLanguages telemetry
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-54135 Thread unsafe behavior in UserLanguages telemetry Change By: Daniel Beck Labels: regression telemetry Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53128) Chinese Localization
Title: Message Title Martin Weber commented on JENKINS-53128 Re: Chinese Localization Thank you! Mentioned the localization-zh-cn-plugin in cmakebuilder's readme, to know where to ask if messages of cmakebuilder change or get added. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero closed an issue as Fixed Verified fix using v1.12.8 Jenkins / JENKINS-53260 exception seen on jenkins 2.138 Change By: Gabe Montero Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54136) Use per-trial correlator IDs
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54136 Use per-trial correlator IDs Issue Type: Improvement Assignee: Daniel Beck Components: core Created: 2018-10-17 18:46 Labels: telemetry Priority: Major Reporter: Daniel Beck Trials are independent, so they should have independent correlation IDs. Add Comment
[JIRA] (JENKINS-54135) Thread unsafe behavior in UserLanguages telemetry
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-54135 Thread unsafe behavior in UserLanguages telemetry Issue Type: Bug Assignee: Daniel Beck Components: core Created: 2018-10-17 18:45 Labels: regression Priority: Major Reporter: Daniel Beck https://github.com/jenkinsci/jenkins/pull/3687#issuecomment-430732957 points out the code is not thread safe. Add Comment
[JIRA] (JENKINS-54035) can't exclude everything under a given dir
Title: Message Title Brian J Murrell commented on JENKINS-54035 Re: can't exclude everything under a given dir Can we make any further progress here at getting the exclude functionality to work? Is there any additional information I can provide? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53422) Declarative pipeline: stdin/stdout/stderr of a remote process are not redirected
Title: Message Title Carlos Sanchez updated JENKINS-53422 Jenkins / JENKINS-53422 Declarative pipeline: stdin/stdout/stderr of a remote process are not redirected Change By: Carlos Sanchez Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Jesse Glick commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished I am confused by the relationship between your screenshots and the thread dump. build-pipeline-steps.PNG and finished-build.PNG display build #4533. stuck-executor.PNG displays build #4908 running on a one-executor agent jenkins-agent-linux-008, and thread-dump.txt indicates that this agent is currently processing a (Git) checkout. They are not even builds of the same job: one is of KKA/TRIGGER_JOB_NEW_BUILD_IN_NEXUS_FLAG, the other KKA/TRIGGER_JOB_NEW_BUILD_IN_NEXUS. Nothing about this seems improper—you have some running builds, and some completed builds. Maybe I am missing something, or maybe you chose the wrong attachments. I do see one anomalous thing in the thread dump: most of the pool threads for DurableTaskStep retain a Thread.name set in this block even after the block has completed and the thread is parked; WithThreadName ought to be resetting the name reliably, even before the re-schedule call. The code which adds the waiting for JNLP4-connect connection from … suffix to the thread name is here, which also looks like it should be cleaning up properly. I have no explanation for this bug, though I also see no reason to think it is related to your problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Carlos Sanchez commented on JENKINS-50429 Re: Shell command are really slower than before removing the lines https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/ContainerExecDecorator.java#L342-L364 I get the same times with container and without so that is something to look into Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title marlene cote edited a comment on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a very odd behavior that seems to have just started out of the blue. I have a multijob job that does NO polling at all. It is meant to be kicked off manually and depends on many parameters to be set by the user. It is being kicked off randomly saying it was started by an SCM change. since the parameters are not set properly, it fails. Why is this build getting kicked off by scm changes when I don't using polling? !image-2018-10-17-14-03-19-028.png!when I click on the Started by an SCM change link, it brings me to a polling log that is empty. !image-2018-10-17-14-04-05-260.png! jenkins version: 2.121.3git plugin version: 3.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title marlene cote edited a comment on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a very odd behavior that seems to have just started out of the blue. I have a multijob job that does NO polling at all. It is meant to be kicked off manually and depends on many parameters to be set by the user. It is being kicked off randomly saying it was started by an SCM change. since the parameters are not set properly, it fails. Why is this build getting kicked off by scm changes when I don't using polling? jenkins version: 2.121.3git plugin version: 3.9.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title marlene cote commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I am seeing a very odd behavior that seems to have just started out of the blue. I have a multijob job that does NO polling at all. It is meant to be kicked off manually and depends on many parameters to be set by the user. It is being kicked off randomly saying it was started by an SCM change. since the parameters are not set properly, it fails. Why is this build getting kicked off by scm changes when I don't using polling? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54134) OAuth / OpenID Connect support for Jenkins API
Title: Message Title Badal Kotecha created an issue Jenkins / JENKINS-54134 OAuth / OpenID Connect support for Jenkins API Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-17 17:51 Environment: Ubuntu 16.04 Labels: jenkins api OAuth REST Priority: Critical Reporter: Badal Kotecha I have a custom application which allows end users to select and provision cloud resources on azure / aws. The authentication to this portal is configured against Azure AD. Intent is to invoke a Jenkins Job remotely from the portal to execute a deployment pipeline which create resources on cloud service provider. Jenkins is also configured to authenticate and authorize based on Azure AD (using Azure AD Plugin). I am trying to invoke the APIs remotely to trigger the job and I want to retain the user context. Unfortunately Jenkins API does not support OAuth token and I need to rely on user ID and API token. Problem is not every user will ever login to Jenkins via Azure AD to create Jenkins user profile where we need to generate API token, neither there is any way to get the API token programmatically by passing the OAuth Token. I need to do few activities in Jenkins based on the current user context and this does not seem possible given that neither I can get the API token dynamically nor I can pass OAuth token. What is the solution?
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Michael Neufeld edited a comment on JENKINS-34841 Re: Add Multiple SCM TFS Label Support This would be a useful fix. We use either freestyle jobs or original build pipeline. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Michael Neufeld edited a comment on JENKINS-34841 Re: Add Multiple SCM TFS Label Support This would be a useful fix. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Michael Neufeld commented on JENKINS-34841 Re: Add Multiple SCM TFS Label Support +1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Michael Neufeld edited a comment on JENKINS-34841 Re: Add Multiple SCM TFS Label Support +1 This would be a useful fix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34841) Add Multiple SCM TFS Label Support
Title: Message Title Michael Neufeld updated JENKINS-34841 Jenkins / JENKINS-34841 Add Multiple SCM TFS Label Support Change By: Michael Neufeld Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Aleksey Smyrnov commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Today my colleague has faced same problem in another organization/repo. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Sam Van Oort edited a comment on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished [~jglick] Could you please take a look? Appears that the latest comment may reflect a regression due to controller.watch API. Edit: though it's not entirely clear from context Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title
Ben Specht created an issue
Jenkins / JENKINS-54133
No ANSI coloring on slave agents in pipeline
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
Screen Shot 2018-10-17 at 11.17.21 AM.png, Screen Shot 2018-10-17 at 11.26.10 AM.png
Components:
pipeline
Created:
2018-10-17 16:35
Environment:
Jenkins version: 2.138.2 JDK: java-1.8.0-openjdk-1.8.0.161-2.b14.el7.x86_64 OS: CentOS 7 64 bit Pipeline plugin version: 2.6 Jenkins is running directly using SSH agents for the slaves. The slaves are all running CentOS 7 with some of those agents being containers. Jenkins is access through a smart proxy and I'm running the latest version of Google Chrome.
Priority:
Minor
Reporter:
Ben Specht
Pipeline:
node('master'){
ansiColor('xterm') {
sh 'echo -e "\033[31mRed\033[0m"'
}
wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm']) {
sh 'echo -e "\033[31mRed\033[0m"'
}
}
node('ansible'){
ansiColor('xterm') {
sh 'echo -e "\033[31mRed\033[0m"'
}
wrap([$class: 'AnsiColorBuildWrapper', 'colorMapName': 'XTerm']) {
sh 'echo -e "\033[31mRed\033[0m"'
}
}
Output: I've verified I see ANSI coloring on a freestyle project restricted to the same 'ansible' label Shell build step
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Sam Van Oort commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished Jesse Glick Could you please take a look? Appears that the latest comment may reflect a regression due to controller.watch API. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Alexander Tolstikov commented on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) FYI, I can't reproduce it at the moment... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23977) Promoted-builds does not allow build secrets
Title: Message Title Monil Patel updated an issue Jenkins / JENKINS-23977 Promoted-builds does not allow build secrets Change By: Monil Patel Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title
Alexander Moiseenko commented on JENKINS-51568
Re: Pipeline jobs hanging in Build Executor even if it is finished
Hello. Same problem again, our new env: Jenkins 2.121.1, Pipeline Groovy 2.55 Pipeline: job 2.26 Durable Task Plugin: 1.26 Pipeline Nodes and Processes: 2.22 workaround script doesn't help anymore, after durable task plugin update probably. We've created simple pipeline job with `sleep` step to check if problem have reappered again:
pipeline {
options {
timeout(time: 60, unit: 'SECONDS')
}
stages {
stage('sleep') {
steps {
sleep 5
}
}
}
}
which finishes successfully in normal case and fails when executors gets stuck
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title David Hayes commented on JENKINS-53858 Re: Deadlock on EC2 resources Seeing this issue also on ec2-plugin 1.40, with a single cloud configuration, on Jenkins 2.138.2. "EC2 alive slaves monitor thread" daemon prio=5 BLOCKED"EC2 alive slaves monitor thread" daemon prio=5 BLOCKED hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:638) hudson.plugins.ec2.EC2AbstractSlave.getInstance(EC2AbstractSlave.java:279) hudson.plugins.ec2.EC2AbstractSlave.fetchLiveInstanceData(EC2AbstractSlave.java:438) hudson.plugins.ec2.EC2AbstractSlave.isAlive(EC2AbstractSlave.java:406) hudson.plugins.ec2.EC2SlaveMonitor.execute(EC2SlaveMonitor.java:43) hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) java.lang.Thread.run(Thread.java:748) "jenkins.util.Timer [#1]" daemon prio=5 BLOCKED hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:638) hudson.plugins.ec2.EC2AbstractSlave.stop(EC2AbstractSlave.java:300) hudson.plugins.ec2.EC2AbstractSlave.idleTimeout(EC2AbstractSlave.java:348) hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:123) hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:85) hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:43) hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:72) hudson.model.Queue._withLock(Queue.java:1380) hudson.model.Queue.withLock(Queue.java:1257) hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:63) hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748) Add Comment
[JIRA] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Matt Sicker commented on JENKINS-21336 Re: ADMINISTER should not imply RUN_SCRIPTS I had a thought about this problem: what if we introduced a new top-level permission such as ROOT. Then RUN_SCRIPTS, CONFIGURE_UPDATECENTER, UPLOAD_PLUGINS, and ADMINISTER are implied by ROOT. Migrating permissions from the previous set to the new one might be complicated, though. A quick local experiment changing these around only broke 4 integration tests, so either there's not much test coverage, or this idea has some potential. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Andy H commented on JENKINS-54116 Re: Jenkins Jira Plugin - Unable to add version Thanks for the suggestion Daniel Daehler I'll look to give it a go in the morning, when no jobs are running. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Alexander Moiseenko commented on JENKINS-54038 Re: Jacoco creates multiple Coverage reports and Trends graphs We faced the same problem after update from jacoco plugin 3.0.1 to 3.0.3, jenkins core 2.121.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54116) Jenkins Jira Plugin - Unable to add version
Title: Message Title Daniel Daehler commented on JENKINS-54116 Re: Jenkins Jira Plugin - Unable to add version We had the same issue. The comment on pull request #166 provides a fix for the problem. After setting the settings 'Read Timeout' to 30 and 'Thread Executor Size' to 10 the problem was gone. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54132) Get JEP-8 (GSoC buget) approved
Title: Message Title Martin d'Anjou created an issue Jenkins / JENKINS-54132 Get JEP-8 (GSoC buget) approved Issue Type: Task Assignee: Unassigned Components: other Created: 2018-10-17 15:00 Priority: Minor Reporter: Martin d'Anjou We need to get JEP-8: Google Summer of Code Budgeting and Expenses approved. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54106) Long delay from github webhook to polling when polling threads all busy
Title: Message Title Russell Gallop commented on JENKINS-54106 Re: Long delay from github webhook to polling when polling threads all busy I have worked around this by adding a separate job which just does the polling and then triggers the Matrix+Multi-SCM job. That seems to avoid the extraneous triggering. SCM Polling threads are a resource where the user is left to find the "correct" configuration. As such it would be useful if metrics were made available for things like: How many SCM polling threads are busy How long SCM poll tasks have had to wait How long SCM polls tasks are taking That would help enormously in debugging problems such as 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54106) Long delay from github webhook to polling when polling threads all busy
Title: Message Title Russell Gallop updated an issue Jenkins / JENKINS-54106 Long delay from github webhook to polling when polling threads all busy Change By: Russell Gallop Component/s: p4-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54124) Raw HTML when Stapler Security Hardening enabled
Title: Message Title Yura Kovalenko updated an issue Jenkins / JENKINS-54124 Raw HTML when Stapler Security Hardening enabled Change By: Yura Kovalenko After upgrading to 2.138.2 all links in columns are shown in raw HTML. - Looks like setting system property org.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault to false as noted [here|https://jenkins.io/doc/upgrade-guide/2.138/#security-hardening-to-prevent-xss-vulnerabilities] doesn't help. -Setting org.kohsuke.stapler.jelly.CustomJellyContext.escapeByDefault to false helps. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54124) Raw HTML when Stapler Security Hardening enabled
Title: Message Title Yura Kovalenko commented on JENKINS-54124 Re: Raw HTML when Stapler Security Hardening enabled Daniel Beck thanks, was my bad - needed to full-restart Jenkins with "service jenkins restart" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 This issue is experienced in TFS Plugin v5.133 and TFS Plugin v5.139. Please see my above comment. Thanks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel reopened an issue This issue is experienced in TFS Plugin v5.133 and TFS Plugin v5.139. Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Change By: Monil Patel Resolution: Done Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53922) Poll results in changes always found when using 2 global libraries
Title: Message Title Paul Allen updated JENKINS-53922 Ready for release. https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/281/ Jenkins / JENKINS-53922 Poll results in changes always found when using 2 global libraries Change By: Paul Allen Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title
Monil Patel edited a comment on JENKINS-33487
Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
We are experiencing the similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Below is the Console output{code:java}Started by user XYZStarted by user XYZLightweight checkout support not available, falling back to full checkout.Checking out hudson.plugins.tfs.TeamFoundationServerScm into /Jenkins_Home/jenkins/workspace/Project-2/Dev/Build-Proj2@script to read JenkinsfileQuerying for remote changeset at '$/ABC/DEF/HIJ/KLM' as of 'D2018-10-12T11:56:42Z'...Query result is: Changeset #2162775 by 'XYZ' on '2018-10-12T11:56:33Z'.Checking if there exists a mapping for /Jenkins_Home/jenkins/workspace/Project-2/Dev/build-pr...@script...no.Downloading list of workspaces from https://tfs.ABC.com/tfs/DEF...Creating workspace 'Hudson-Build-Proj2-MASTER' owned by 'XYZ'...Mapping '$/ABC/DEF/HIJ/KLM' to local folder '/Jenkins_Home/jenkins/workspace/Project-2/Dev/Build-Proj2@script' in workspace 'Hudson-Build-Proj2-MASTER'...com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: The workspace Hudson-Build-Proj2-MASTER;FirtName LastName (XYZ) already exists on computer 12345678SVRName. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.createWorkspace(_RepositorySoap12Service.java:555) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:784)Caused: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-Build-Proj2-MASTER;FirtName LastName (XYZ) already exists on computer 12345678SVRName. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:792) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1020) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233)Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:143) at
[JIRA] (JENKINS-53193) Provide currentBuild.isRestartedRun and .isRestartedStage global variables
Title: Message Title Fernando Nasser commented on JENKINS-53193 Re: Provide currentBuild.isRestartedRun and .isRestartedStage global variables isRestartedStage variable is needed as well (to match the when condition isRestartedStage() ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53193) Provide currentBuild.isRestartedRun and .isRestartedStage global variables
Title: Message Title Fernando Nasser updated an issue Jenkins / JENKINS-53193 Provide currentBuild.isRestartedRun and .isRestartedStage global variables Change By: Fernando Nasser Summary: Provide currentBuild.isRestartedRun and .isRestartedStage global variable variables Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-54131 "Failed to parse changelog" in JIRA plugin 3.0.3 Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-10-17 14:22 Environment: JIRA 3.0.3, Blue Ocean 1.9.0 Priority: Blocker Reporter: Nick Jones Testing the updating of Jira issues with the Jira 3.0.3 plugin, I get the following stack trace: java.lang.IllegalArgumentException at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1314) at java.util.concurrent.ThreadPoolExecutor.(ThreadPoolExecutor.java:1237) at java.util.concurrent.Executors.newFixedThreadPool(Executors.java:151) at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:457) at hudson.plugins.jira.JiraSite.getSession(JiraSite.java:426) at io.jenkins.blueocean.service.embedded.jira.JiraSCMListener.onChangeLogParsed(JiraSCMListener.java:45) at hudson.model.listeners.SCMListener.onChangeLogParsed(SCMListener.java:120) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) Caused: java.io.IOException: Failed to parse changelog at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:592) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1819) 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
[JIRA] (JENKINS-53662) isRestartedRun() is not reset after a successful stage
Title: Message Title
Fernando Nasser commented on JENKINS-53662
Re: isRestartedRun() is not reset after a successful stage
Andrew Bayer In the example above, DoWork is the stage that fails and is restarted. So when { not{ isRestartedStage() } will allow it to be skipped. But in that case the RestartWork stage will not run with when { isRestartedStage() } because it was not it that failed (but DoWork). Note that I only had to use those two stages because there is no way to test inside the stage if it is a restart or the initial run. My apologies, I liked the isRestartedStage idea, but for my case above it is only useful as a variable. Basically all the when conditions are only useful to skip re-executing the step that failed (assuming you manually did what it was supposed to do), but they do not help in doing an alternative action in case of a restart. That will only be achieved with JENKINS-53193
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53655) Jenkin could not able to load on browser property giving exception
Title: Message Title Damien Giraudet edited a comment on JENKINS-53655 Re: Jenkin could not able to load on browser property giving exception I have the same issue (same trace).Did you found an alternative solution [~mahesh_shitole] ? UPDATE : I finaly removed the plugin that created this problem (temporary solution) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing tht the similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54130) Fix Kafka agent docker build
Title: Message Title Pham Vu Tuan updated JENKINS-54130 Jenkins / JENKINS-54130 Fix Kafka agent docker build Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel edited a comment on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing a tht similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54130) Fix Kafka agent docker build
Title: Message Title Pham Vu Tuan started work on JENKINS-54130 Change By: Pham Vu Tuan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54130) Fix Kafka agent docker build
Title: Message Title Pham Vu Tuan updated JENKINS-54130 Jenkins / JENKINS-54130 Fix Kafka agent docker build Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54130) Fix Kafka agent docker build
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-54130 Fix Kafka agent docker build Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-10-17 14:14 Priority: Minor Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Monil Patel commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 We are experiencing a similar issue with TFS Plugin v5.133.0 and Cloudbees Jenkins v.2.89.4.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title David Taylor commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Claus Schneider we've looked at the pre-tested plugin and we're not sure if it will fit with what we're trying to do. we really just need a way to push changes back to Bitbucket without using SSH keys from the build machine. The Git Plugin / Git Publisher plugin should allow for this but we're not sure how to implement it yet. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero resolved as Fixed Jenkins / JENKINS-53260 exception seen on jenkins 2.138 Change By: Gabe Montero Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53260) exception seen on jenkins 2.138
Title: Message Title Gabe Montero commented on JENKINS-53260 Re: exception seen on jenkins 2.138 And the resulting commit is in v1.12.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
