[JIRA] (JENKINS-55535) Warnings does not fail the build
Title: Message Title John V created an issue Jenkins / JENKINS-55535 Warnings does not fail the build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-11 07:24 Priority: Major Reporter: John V The recordIssues (probably the other functions too) pipeline step does mark builds as failed when there are warnings (they are listed on the site but nothing happens with the build status), even if setting "failedTotalAll: 0". Setting "failedTotalAll: 0" is how I used to make builds fail if there is any warnings in the old warnings plugin. Is this something that has changed? Since I find this to be a critical feature of this plugin. Add Comment
[JIRA] (JENKINS-53008) Localize the report layouts
Title: Message Title Share Cheng updated an issue Jenkins / JENKINS-53008 Localize the report layouts Change By: Share Cheng 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51926) Supporting combining reports within a build(e.g. after parallel() execution in Pipeline)
Title: Message Title Share Cheng updated JENKINS-51926 Jenkins / JENKINS-51926 Supporting combining reports within a build(e.g. after parallel() execution in Pipeline) Change By: Share Cheng 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-51367) Add support of optional report names
Title: Message Title Share Cheng stopped work on JENKINS-51367 Change By: Share Cheng Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51367) Add support of optional report names
Title: Message Title Share Cheng updated an issue Jenkins / JENKINS-51367 Add support of optional report names Change By: Share Cheng 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52631) Release cobertura plugin with code coverage api compatibility
Title: Message Title Share Cheng started work on JENKINS-52631 Change By: Share Cheng 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-52631) Release cobertura plugin with code coverage api compatibility
Title: Message Title Share Cheng updated JENKINS-52631 Jenkins / JENKINS-52631 Release cobertura plugin with code coverage api compatibility Change By: Share Cheng 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-52631) Release cobertura plugin with code coverage api compatibility
Title: Message Title Share Cheng updated JENKINS-52631 Jenkins / JENKINS-52631 Release cobertura plugin with code coverage api compatibility Change By: Share Cheng 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-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-55499 Jenkins can`t display jobs view,my jenkins version 2.157 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-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Oleg Nenashev commented on JENKINS-55499 Re: Jenkins can`t display jobs view,my jenkins version 2.157 I am on the long vacation: https://groups.google.com/forum/m/#!topic/jenkinsci-dev/uc6NsMoCFQI . I would have triaged it in general, but not this month. There is no default assignee for a reason Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55446) Unable to Execute Test in HP Performance Center 12.01
Title: Message Title Pradeepkumar Subramaniam commented on JENKINS-55446 Re: Unable to Execute Test in HP Performance Center 12.01 Hi Daniel Danan, Any updates on this issues. It's kind of blocker for me to proceed further with Jenkins and PC Setup. Can you please help out. Thanks,Pradeep. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55462) "shelve project" button missing for all non-admin users
Title: Message Title Roger Wang commented on JENKINS-55462 Re: "shelve project" button missing for all non-admin users just add what we have tested: granted all permissions except administrator to user, the shelve project button is missing. change the authorisation to matrix based, the problem is still appeared. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55418) Pipeline Syntax generator not present
Title: Message Title Andrew Gray commented on JENKINS-55418 Re: Pipeline Syntax generator not present Under General Step I only see "Record Compiler Warnings..." and "Record fingerprints..." Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Kevin commented on JENKINS-55499 Re: Jenkins can`t display jobs view,my jenkins version 2.157 Could you tell me who anyone can shoot these issues? Thank you very much. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54683) Pods entering error state
Title: Message Title Kevin commented on JENKINS-54683 Re: Pods entering error state test Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55424) Putting a space at the end of Script Path causes java.io.FileNotFoundException
Title: Message Title Jesse Glick commented on JENKINS-55424 Re: Putting a space at the end of Script Path causes java.io.FileNotFoundException This could perhaps trim(). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55424) Putting a space at the end of Script Path causes java.io.FileNotFoundException
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55424 Putting a space at the end of Script Path causes java.io.FileNotFoundException Change By: Jesse Glick Component/s: workflow-cps-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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 Jesse Glick assigned an issue to Stephen Connolly Has been observed recently on ci.jenkins.io as well. Jenkins / JENKINS-54126 Jenkinsfile not found in PR on GitHub Change By: Jesse Glick Component/s: github-branch-source-plugin Component/s: github-api-plugin Component/s: github-organization-folder-plugin Assignee: Kohsuke Kawaguchi Stephen Connolly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Kevin stopped work on JENKINS-55499 Change By: Kevin Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Kevin assigned an issue to Oleg Nenashev Jenkins / JENKINS-55499 Jenkins can`t display jobs view,my jenkins version 2.157 Change By: Kevin Assignee: Daniel Beck 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-55499) Jenkins can`t display jobs view,my jenkins version 2.157
Title: Message Title Kevin assigned an issue to Daniel Beck Jenkins / JENKINS-55499 Jenkins can`t display jobs view,my jenkins version 2.157 Change By: Kevin Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54776) Node stays suspended after node is started
Title: Message Title Jie Shen commented on JENKINS-54776 Re: Node stays suspended after node is started Hi Balaal Ashraf, you are right. This issue is caused by the codes. https://github.com/jenkinsci/azure-vm-agents-plugin/blob/ea8dc0b19184c381172afac0a41cac46435eaaf4/src/main/java/com/microsoft/azure/vmagent/AzureVMCloud.java#L707 may throw some exceptions in some cases and then skip the azureComputer.setAcceptingTasks(true). I made some changes to just catch and ignore the exceptions. But it seems not a proper way to fix it. I need to find out why the exceptions are thrown and how to avoid it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55534) Support Shared Image Gallery in Image Configuration
Title: Message Title Jie Shen commented on JENKINS-55534 Re: Support Shared Image Gallery in Image Configuration Start to investigate this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55534) Support Shared Image Gallery in Image Configuration
Title: Message Title Jie Shen started work on JENKINS-55534 Change By: Jie Shen 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-55534) Support Shared Image Gallery in Image Configuration
Title: Message Title Jie Shen created an issue Jenkins / JENKINS-55534 Support Shared Image Gallery in Image Configuration Issue Type: Task Assignee: Jie Shen Components: azure-vm-agents-plugin Created: 2019-01-11 02:36 Priority: Minor Reporter: Jie Shen Shared Image Gallery can also serves as a provider of image, details https://docs.microsoft.com/en-us/azure/virtual-machines/windows/shared-image-galleries Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-42643) Conditional application of triggers in Declarative
Title: Message Title Daniel Watrous commented on JENKINS-42643 Re: Conditional application of triggers in Declarative Sean Grider, I found https://plugins.jenkins.io/parameterized-scheduler while looking for this same feature. My use case is a little different. I have a build that deploys software, but I want that software to get cleaned up some fixed number of hours after the last build. What I really want is to schedule a one time build, but I realized I might be able to use triggers for this. When the initial build runs, I dynamically generate the cron to run at a time that would be the number of hours later that I want. When the clean up build runs, I would set the cron trigger to an empty string, so it effectively on runs one time... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55533) Support for new PostBuildScript configuration
Title: Message Title
Kelvin Chung created an issue
Jenkins / JENKINS-55533
Support for new PostBuildScript configuration
Issue Type:
Improvement
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, postbuildscript-plugin
Created:
2019-01-11 02:15
Priority:
Minor
Reporter:
Kelvin Chung
Although this has been discussed in JENKINS-48692 and in https://github.com/jenkinsci/job-dsl-plugin/pull/1098, I would like the Job DSL plugin's maintainers to reconsider the decision to not support newer versions of PostBuildScript in light of the fact that the experience with configuring a post-build build step is different from a build step defined in a steps block. For example, one would expect something like this to work:
postBuildScript {
buildSteps {
postBuildStep {
buildSteps {
criticalBlock {
shell 'pwd'
}
}
}
}
}
When in reality, criticalBlock and everything inside of it would need to be configured differently, owing to the fact that it isn't executing with respect to a StepContext, and criticalBlock itself is nontrivial in its implementation. (Similarly, configuring a shell step is different with respect to a StepContext compared to the dynamic DSL context, given that the implementation of shell shortcuts the command part.) Additionally, while it is true that PostBuildScript itself handles configuration of its older configuration generated from the existing postBuildScripts step (including migration to the MatrixPostBuildScript class, new to newer versions, where applicable), and that dynamic DSL does cover most remaining features (notwithstanding the build step inconsistency described above, and that dynamic DSL may not be
[JIRA] (JENKINS-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel updated an issue Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Change By: Ahmed Kamel My devs are complaining of builds failing randomly when a stage starts. The builds fail when attempting to run "sh" in a container in the pods running the job. Here is the error message I see. ``` [Pipeline] shrpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3786794 to cgroups caused \"failed to write 3786794 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod70971cd7-153a-11e9-9fe5-42010a567404/6b66fd31d9718f168c34810477e328045af5caead06e9e7f48ed3b9431eb3d37/cgroup.procs: invalid argument\""[Pipeline] echoError: java.io.IOException: Pipe closed... ... ...ERROR: script returned exit code 1 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 Google 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-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel updated an issue Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Change By: Ahmed Kamel My devs are complaining of builds failing randomly when a stage starts. The builds fail when attempting to run "sh" in a container in the pods running the job. Here is the error message I see. [Pipeline] shrpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3786794 to cgroups caused \"failed to write 3786794 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod70971cd7-153a-11e9-9fe5-42010a567404/6b66fd31d9718f168c34810477e328045af5caead06e9e7f48ed3b9431eb3d37/cgroup.procs: invalid argument\""[Pipeline] echoError: java.io.IOException: Pipe closed... ... ... ERROR: script returned exit code 1 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 Google 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-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel updated an issue Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Change By: Ahmed Kamel My devs are complaining of builds failing randomly when a stage starts. The builds fail when attempting to run "sh" in a container in the pods running the job. Here is the error message I see. ``` [Pipeline] shrpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3786794 to cgroups caused \"failed to write 3786794 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod70971cd7-153a-11e9-9fe5-42010a567404/6b66fd31d9718f168c34810477e328045af5caead06e9e7f48ed3b9431eb3d37/cgroup.procs: invalid argument\""[Pipeline] echoError: java.io.IOException: Pipe closed... ... ...ERROR: script returned exit code 1 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 Google 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-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel updated an issue Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Change By: Ahmed Kamel My devs are complaining of builds failing randomly when a stage starts. The builds fail when attempting to run "sh" in a container in the cluster pods running the job .Here is the error message I see. [Pipeline] shrpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3786794 to cgroups caused \"failed to write 3786794 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod70971cd7-153a-11e9-9fe5-42010a567404/6b66fd31d9718f168c34810477e328045af5caead06e9e7f48ed3b9431eb3d37/cgroup.procs: invalid argument\""[Pipeline] echoError: java.io.IOException: Pipe closed.ERROR: script returned exit code 1Finished: 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 Google 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-55527) Builds fail randomly when running sh in container
Title: Message Title Ahmed Kamel created an issue Jenkins / JENKINS-55527 Builds fail randomly when running sh in container Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-01-11 01:05 Environment: Running jenkins in a Kubernetes cluster on GCP Labels: bug Priority: Major Reporter: Ahmed Kamel My devs are complaining of builds failing randomly when a stage starts. The builds fail when attempting to run "sh" in the cluster. Here is the error message I see. [Pipeline] shrpc error: code = 2 desc = oci runtime error: exec failed: container_linux.go:247: starting container process caused "process_linux.go:87: adding pid 3786794 to cgroups caused \"failed to write 3786794 to cgroup.procs: write /sys/fs/cgroup/cpu,cpuacct/kubepods/besteffort/pod70971cd7-153a-11e9-9fe5-42010a567404/6b66fd31d9718f168c34810477e328045af5caead06e9e7f48ed3b9431eb3d37/cgroup.procs: invalid argument\""[Pipeline] echoError: java.io.IOException: Pipe closed... ... ...ERROR: script returned exit code 1 Finished: FAILURE
[JIRA] (JENKINS-38508) git scm poll doesn't ignore changes with pipeline
Title: Message Title Aaron Ling commented on JENKINS-38508 Re: git scm poll doesn't ignore changes with pipeline I hit this issue as well. Setting changelog to false and restarting Jenkins seems to bypass the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55500) Warnings per project portlet
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55500 Warnings per project portlet Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55500) Warnings per project portlet
Title: Message Title Ulli Hafner started work on JENKINS-55500 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55462) "shelve project" button missing for all non-admin users
Title: Message Title Roger Wang updated an issue Jenkins / JENKINS-55462 "shelve project" button missing for all non-admin users Change By: Roger Wang Priority: Blocker Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55526) Incorrect extension `reference` produces ERROR in log, should probably be lower sev
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-55526 Incorrect extension `reference` produces ERROR in log, should probably be lower sev Change By: Karl Shultz Summary: Missing optional Incorrect extension `reference` produces ERROR in log, should probably be lower sev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55526) Missing optional extension `reference` produces ERROR in log, should probably be lower sev
Title: Message Title
Karl Shultz created an issue
Jenkins / JENKINS-55526
Missing optional extension `reference` produces ERROR in log, should probably be lower sev
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-01-10 22:58
Environment:
* Jenkins core 2.156 * All experimental update center level plugins, including git and git-client betas
Priority:
Minor
Reporter:
Karl Shultz
Summary While stress testing the submodule changes as I've described in git-plugin PR 352, I noticed an ERROR in the job's log. This was because the optional `reference` extension shown in this `checkout` step was missing. The presence of `ERROR` seemed jarring, so Mark and I agreed that log message should be shown at a lower severity. Steps to recreate 1. Create a pipeline job and use a Jenkinsfile with a checkout step. This checkout should include a extensions section, with a reference pointing to something that doesn't exist. Like this one:
node() {
deleteDir()
stage('Checkout') {
checkout([
$class: 'GitSCM',
branches: [[name: '*/master']],
extensions: [[$class: 'CloneOption', noTags: false, reference: '/path/to/something/that/is/not/here.git', shallow: false]],
gitTool: 'Default',
userRemoteConfigs: [[
credentialsId: '06df34bc-ea33-4a9b-a5bb-5728a0d6fddc',
url: 'https://github.com/jenkinsci/pipeline-model-definition-plugin.git'
]]
])
}
}
2. Run the pipeline. 3. In the
[JIRA] (JENKINS-42292) Sort, limit results via AQL download spec
Title: Message Title Chris Ladd commented on JENKINS-42292 Re: Sort, limit results via AQL download spec Any updates on using AQL sort and limit with the new declarative pipeline commands in 3.0? I love being able to use AQL with the new rtDownload step, but need to tell it just to download a limited number of results. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55524 Triggers on wrong branch when pushing multiple merges 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55525) Full username with Saml 2.0 plugin
Title: Message Title saurav ghosh created an issue Jenkins / JENKINS-55525 Full username with Saml 2.0 plugin Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2019-01-10 20:49 Priority: Minor Reporter: saurav ghosh Saml 2.0 plugin not displaying the full user name after the login to jenkins. If I put "first_name" in "Username Attribute" it gives the firstname of the user and if I put "last_name" in "Username Attribute" it shows the last name of the user. What is the way to display the user's full name? Add Comment
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title
Aaron Jensen updated an issue
Jenkins / JENKINS-55524
Triggers on wrong branch when pushing multiple merges
Change By:
Aaron Jensen
We use Bitbucket Server for source control. We have three permanent branches: develop, release, master. We have automatic merges turned on so that for any PR/merge into the release branch, Bitbucket will merge release into the develop branch. For any PR/merge into the master branch, Bitbucket will merge master into release *and* develop. Bitbucket is configured to always create a new merge commit.After the merge, Bitbucket sends a commit notification to Jenkins. In the situation of a merge into release, two notifications are sent: one for the merge into release and another for the automatic merge into the develop branch.When the git plugin polls for what branches are included in the merge to release commit , it sees both the develop *and* release branch instead of just the release branch. It looks like the Git plugin is using {{--contains - }} instead of {{- - points-at}} to determine what branch a commit points to.Steps to Reproduce:1. Create a repo. 2. Create a develop branch. Make a commit on that branch.3. Make a release branch.4. Make a new commit on the develop branch. Merge it into the release branch.5. Merge the release branch into the develop branch. `git log -2 --graph` should look something like this: {code :java }* commit e00fb35bcd9b7fc218f0c6b7aec352d7ad1fb62e (HEAD -> develop, tag: 2019.110.100, origin/develop, origin/HEAD) |\ Merge: a251303 366bf67 | | Author: | | Date: Thu Jan 10 10:34:48 2019 -0800 | | | | Automatic merge from release -> develop | | | | * commit '366bf67833c09f8d09280d8ec31b8142dfd5c43f': | | | * commit 366bf67833c09f8d09280d8ec31b8142dfd5c43f (tag: 2019.110.99, origin/release) | |\ Merge: 60db8dd a251303 | |/ Author: |/| Date: Thu Jan 10 10:34:48 2019 -0800 | | | | Merge pull request #11 from develop to release | | | | * commit 'a251303c15524fad76d3634834ffe6b8aec51dbe': | | {code} 6. Create a Jenkins freestyle job that polls your repository but doesn't actually poll the repository. Set the branches to build to {{origin/**}}.7. Make a notifyCommit web request for the merge to release commit: {{ [ https:///git/notifyCommit?url=""> |https://%2A%2A%2A%2A%2A%2A%2A%2A/git/notifyCommit?url=""> }}8. Note that the plugin reports the build happening on the develop branch instead of the release branch. I would expect (and want) the build to run on the release branch.I think the problem is with the command to determine what branches a commit points to. The plugin is currently using:{ {> code} git
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title
Aaron Jensen updated an issue
Jenkins / JENKINS-55524
Triggers on wrong branch when pushing multiple merges
Change By:
Aaron Jensen
We use Bitbucket Server for source control. We have three permanent branches: develop, release, master. We have automatic merges turned on so that for any PR/merge into the release branch, Bitbucket will merge release into the develop branch. For any PR/merge into the master branch, Bitbucket will merge master into release *and* develop. Bitbucket is configured to always create a new merge commit.After the merge, Bitbucket sends a commit notification to Jenkins. In the situation of a merge into release, two notifications are sent: one for the merge into release and another for the automatic merge into the develop branch.When the git plugin polls for what branches are included in the merge to release commit , it sees both the develop *and* release branch instead of just the release branch. It looks like the Git plugin is using {{--contains}} instead of {{--points-at}} to determine what branch a commit points to.Steps to Reproduce:1. Create a repo. 2. Create a develop branch. Make a commit on that branch.3. Make a release branch.4. Make a new commit on the develop branch. Merge it into the release branch.5. Merge the release branch into the develop branch. `git log -2 --graph` should look something like this:{ { code} * commit e00fb35bcd9b7fc218f0c6b7aec352d7ad1fb62e (HEAD -> develop, tag: 2019.110.100, origin/develop, origin/HEAD) |\ Merge: a251303 366bf67 | | Author: | | Date: Thu Jan 10 10:34:48 2019 -0800 | | | | Automatic merge from release -> develop | | | | * commit '366bf67833c09f8d09280d8ec31b8142dfd5c43f': | | | * commit 366bf67833c09f8d09280d8ec31b8142dfd5c43f (tag: 2019.110.99, origin/release) | |\ Merge: 60db8dd a251303 | |/ Author: |/| Date: Thu Jan 10 10:34:48 2019 -0800 | | | | Merge pull request #11 from develop to release | | | | * commit 'a251303c15524fad76d3634834ffe6b8aec51dbe': | | {code } } 6. Create a Jenkins freestyle job that polls your repository but doesn't actually poll the repository. Set the branches to build to {{origin/**}}.7. Make a notifyCommit web request for the merge to release commit: {{https:///git/notifyCommit?url="">8. Note that the plugin reports the build happening on the develop branch instead of the release branch. I would expect (and want) the build to run on the release branch.I think the problem is with the command to determine what branches a commit points to. The plugin is currently using:{{> git branch -a -v --no-abbrev --contains 366bf67833c09f8d09280d8ec31b8142dfd5c43f}}I
[JIRA] (JENKINS-55524) Triggers on wrong branch when pushing multiple merges
Title: Message Title
Aaron Jensen created an issue
Jenkins / JENKINS-55524
Triggers on wrong branch when pushing multiple merges
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-01-10 20:47
Environment:
Jenkins 2.138.3 Git Plugin 2.7.3 Windows 2012 Chrome
Priority:
Minor
Reporter:
Aaron Jensen
We use Bitbucket Server for source control. We have three permanent branches: develop, release, master. We have automatic merges turned on so that for any PR/merge into the release branch, Bitbucket will merge release into the develop branch. For any PR/merge into the master branch, Bitbucket will merge master into release and develop. Bitbucket is configured to always create a new merge commit. After the merge, Bitbucket sends a commit notification to Jenkins. In the situation of a merge into release, two notifications are sent: one for the merge into release and another for the automatic merge into the develop branch. When the git plugin polls for what branches are included in the merge to release commit , it sees both the develop and release branch instead of just the release branch. It looks like the Git plugin is using -contains instead of -points-at to determine what branch a commit points to. Steps to Reproduce: 1. Create a repo. 2. Create a develop branch. Make a commit on that branch. 3. Make a release branch. 4. Make a new commit on the develop branch. Merge it into the release branch. 5. Merge the release branch into the develop branch. `git log -2 --graph` should look something like this: {{* commit e00fb35bcd9b7fc218f0c6b7aec352d7ad1fb62e (HEAD -> develop, tag: 2019.110.100, origin/develop, origin/HEAD)
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Fernando Nasser commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once I'd rather keep the switches to avoid unnecessary overhead in the cases these are not 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-55522) HTML publisher plugin is throwing error
Title: Message Title siva krishna jampani updated JENKINS-55522 Jenkins / JENKINS-55522 HTML publisher plugin is throwing error Change By: siva krishna jampani Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55522) HTML publisher plugin is throwing error
Title: Message Title siva krishna jampani assigned an issue to siva krishna jampani Jenkins / JENKINS-55522 HTML publisher plugin is throwing error Change By: siva krishna jampani Assignee: Richard Bywater siva krishna jampani Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54502) Jenkins crashed when a running build was aborted.
Title: Message Title marlene cote commented on JENKINS-54502 Re: Jenkins crashed when a running build was aborted. happening to me too. please fix 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-53828) GitHub Enterprise Servers plugin - ERROR - This URL requires POST
Title: Message Title Vivek Pandey closed an issue as Duplicate Jenkins / JENKINS-53828 GitHub Enterprise Servers plugin - ERROR - This URL requires POST Change By: Vivek Pandey Status: Open Closed 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-45129) Unable to scan branches in multibranch plugin when user has two-step verification enabled
Title: Message Title Vivek Pandey commented on JENKINS-45129 Re: Unable to scan branches in multibranch plugin when user has two-step verification enabled Thanks Nenad Miksa! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-45129) Unable to scan branches in multibranch plugin when user has two-step verification enabled
Title: Message Title Vivek Pandey closed an issue as Cannot Reproduce Jenkins / JENKINS-45129 Unable to scan branches in multibranch plugin when user has two-step verification enabled Change By: Vivek Pandey 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update I've discovered a regression in Util.isSymlink that relates to the can't delete files in a symbolically linked Jenkins home (or other symlink issues). Including in this 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout()def stderr = returnObj.getStderr(){code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters.Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would could just return the POJO, and you could either use it or not.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout() def stderr = returnObj.getStderr() {code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters.Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would just return the POJO, and you could either use it or not.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout(){code}Using a Map you would need to know the keys therein, but with a POJO you can use the javadoc to know the getters. Perhaps the parameter flags returnStatus, returnStdout, returnStderr would not be necessary. It would just return the POJO, and you could either use it or not.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Sverre Moe edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
It would be better using a specific POJO than a Map.{code}def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches")def status = returnObj.getStatus()def stdout = returnObj.getStdout(){code}Using a Map you would need to know the values keys therein, but with a POJO you can use the javadoc to know the getters.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Sverre Moe commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once It would be better using a specific POJO than a Map. def returnObj = sh(returnStatus: true, returnStdout: true, returnStderr: true, script: "git merge --no-edit $branches") def status = returnObj.getStatus() def stdout = returnObj.getStdout() Using a Map you would need to know the values therein, but with a POJO you can use the javadoc to know the getters. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55522) HTML publisher plugin is throwing error
Title: Message Title siva krishna jampani created an issue Jenkins / JENKINS-55522 HTML publisher plugin is throwing error Issue Type: Bug Assignee: Richard Bywater Attachments: PublishHtmlReport.PNG Components: htmlpublisher-plugin Created: 2019-01-10 19:42 Priority: Major Reporter: siva krishna jampani When generating report its throwing below error. I am passing the right path as well. **/target/site/serenity/index.html Recording test results ERROR: Step ‘Publish JUnit test result report’ aborted due to exception: org.dom4j.DocumentException: Error on line 164 of document : The element type "link" must be terminated by the matching end-tag "". Nested exception: The element type "link" must be terminated by the matching end-tag "". at org.dom4j.io.SAXReader.read(SAXReader.java:482) at org.dom4j.io.SAXReader.read(SAXReader.java:343) at hudson.tasks.junit.SuiteResult.parse(SuiteResult.java:178) at hudson.tasks.junit.TestResult.parse(TestResult.java:348) at hudson.tasks.junit.TestResult.parsePossiblyEmpty(TestResult.java:281) at hudson.tasks.junit.TestResult.parse(TestResult.java:206) at hudson.tasks.junit.TestResult.parse(TestResult.java:178) at hudson.tasks.junit.TestResult.(TestResult.java:143) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:146) at hudson.tasks.junit.JUnitParser$ParseResultCallable.invoke(JUnitParser.java:118) at hudson.FilePath.act(FilePath.java:1077) at hudson.FilePath.act(FilePath.java:1060) at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:114) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:137) at hudson.tasks.junit.JUnitResultArchiver.parseAndAttach(JUnitResultArchiver.java:167) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:154) at
[JIRA] (JENKINS-55521) Allow for random resource return.
Title: Message Title Mike Delaney created an issue Jenkins / JENKINS-55521 Allow for random resource return. Issue Type: Bug Assignee: Unassigned Components: lockable-resources-plugin Created: 2019-01-10 19:33 Environment: Jenkins: 1.150.1 Lockable resource plugin: 2.3 Priority: Minor Reporter: Mike Delaney When getting a resource, I'd like to way to get a random resource. The current behavior seems to return the first on the stack. This ends with one resource getting used more then the others but I'd like to be able to randomize the resource returned. Add Comment
[JIRA] (JENKINS-55520) Running plugin by class call in Declarative pipeline
Title: Message Title Zachary LaCelle created an issue Jenkins / JENKINS-55520 Running plugin by class call in Declarative pipeline Issue Type: Bug Assignee: Marco Steffan Components: cppcheck-plugin, cppncss-plugin Created: 2019-01-10 19:33 Environment: jenkinsci/blue-ocean image (latest) Ubuntu 18.04 cppncss-plugin: 1.2 cppcheck-plugin: 1.24 Priority: Major Reporter: Zachary LaCelle TL;DR: For plugins which don't have Pipeline integration, and for which I'd like to call their publisher class manually using a "step([$class: '']) call, how do I find: The name of the class to use (e.g. CppNCSSPublisher) The names of parameters to use Which ones are required/options Or is there a better way to integrate these publishers? -- I'm using the BlueOcean container with Declarative pipelines. I'm also running some code quality tools that I've used in the past on non-pipeline Jenkins jobs (namely cppcheck and lizard, which dumps cppncss-formatted XML). Lots and lots of reporting plugins don't yet work in Pipelines. Specifically, CppNCSS-plugin. To run this plugin from the pipeline, in my "post" section I'm trying to call the class manually as a "step()" call, but it keeps crashing. I'm having a very hard time finding useful documentation to explain how to do this, or if there's another way. My current command attempt:
[JIRA] (JENKINS-55519) ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob
Title: Message Title Gennady Feldman created an issue Jenkins / JENKINS-55519 ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob Issue Type: Bug Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-01-10 19:18 Priority: Major Reporter: Gennady Feldman We are using Organization plugin and Jenkinsfile to override some of the repo/project level settings. One of them changed the build behavior to not trigger master branch buiilds automatically and instead run then on schedule. After upgrading Branch API and installing Basic Branch Build Strategies plugin I started seeing this error on the Job Console: ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob I don't see any other way right now to change project level settings. Add Comment
[JIRA] (JENKINS-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes Change By: German Pineda Environment: Jenkins: 2.150.1 LTSBitbucket Branch Source Plugin: 2.3.0 Pipeline Multibranch Plugin: 2.20 Installation: Windows 2016 Server (Used windows installer)Proxy: NoneBrowser: Chrome Version 71.0.3578.98 (Official Build) (64-bit) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Change By: German Pineda Summary: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes
Title: Message Title German Pineda created an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of changes Issue Type: Bug Assignee: Unassigned Attachments: PRBuilds.PNG Components: bitbucket-branch-source-plugin Created: 2019-01-10 19:04 Environment: Jenkins: 2.150.1 LTS Bitbucket Branch Source Plugin: 2.3.0 Installation: Windows 2016 Server (Used windows installer) Proxy: None Browser: Chrome Version 71.0.3578.98 (Official Build) (64-bit) Labels: plugin Priority: Major Reporter: German Pineda I currently have a Bibucket Mercurial Multibranch pipeline that scans every 5 minutes for any PRs submitted against master which triggers our build for those branches. After updating our Bitbucket Branch Source plugin version from 2.2.12 to 2.2.15, some scans would periodically result in retriggering all of our PR builds even though none of those PRs were updated. This has a tremendous impact as all of our Jenkins agents would overload with unnecessary builds. I recently updated the Bitbucket Branch Source plugin version to 2.3.0 (most recent release) hoping this had been fixed and it's still a problem. This issue appears to have been introduced in version 2.2.13. I'm reverting back to 2.2.12 until this issue is fixed.
[JIRA] (JENKINS-55516) Time zone is not allowing in Build periodically with parameters
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55516 Time zone is not allowing in Build periodically with parameters Change By: Baptiste Mathus Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker updated JENKINS-55448 Jenkins / JENKINS-55448 File cleaning failure, old build and plugin update Change By: Matt Sicker 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-55516) Time zone is not allowing in Build periodically with parameters
Title: Message Title Baptiste Mathus commented on JENKINS-55516 Re: Time zone is not allowing in Build periodically with parameters siva krishna jampani as far as I understand your request/idea, this is more a feature request than a bug. I changed the issue type to reflect this. Please clarify if I'm missing your point. 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-55512) Safe shutdown/restart should not block completion of complex jobs (that spawn child jobs)
Title: Message Title Jim Klimov updated JENKINS-55512 Jenkins / JENKINS-55512 Safe shutdown/restart should not block completion of complex jobs (that spawn child jobs) Change By: Jim Klimov 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-55512) Safe shutdown/restart should not block completion of complex jobs (that spawn child jobs)
Title: Message Title Jim Klimov started work on JENKINS-55512 Change By: Jim Klimov 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-55512) Safe shutdown/restart should not block completion of complex jobs (that spawn child jobs)
Title: Message Title Jim Klimov assigned an issue to Jim Klimov Jenkins / JENKINS-55512 Safe shutdown/restart should not block completion of complex jobs (that spawn child jobs) Change By: Jim Klimov Assignee: Jim Klimov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Think I've discovered the root cause here. The File API automatically normalized some file names, while Path does not by default. I've pushed those changes to the PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Alright, I've discovered one regression so far where a path like /var/foo/bar/../baz will not delete due to order of delete operations being reversed here since the parent is attempted to be deleted first. I have an idea on how this might be fixed now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Robert Koncier commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Sorry Matt Sicker I forgot mention I linked Jenkins workspace from different 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Robert Koncier updated an issue Jenkins / JENKINS-55448 File cleaning failure, old build and plugin update Change By: Robert Koncier Attachment: image-2019-01-10-11-09-44-118.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title Nic Stevens commented on JENKINS-55460 Re: Cleaning of svn workspace broken in 2.157 Updated to indicate the same things is happening in the latest Subversion plugin. Appears to be more than just a minor 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-55516) Time zone is not allowing in Build periodically with parameters
Title: Message Title siva krishna jampani created an issue Jenkins / JENKINS-55516 Time zone is not allowing in Build periodically with parameters Issue Type: Bug Assignee: Baptiste Mathus Components: parameterized-scheduler-plugin Created: 2019-01-10 18:05 Priority: Major Reporter: siva krishna jampani When using with Build periodically with parameters and trying to run based on the timezone its not allowing keep time zone as below TZ=EST5EDT. its throwing error Add Comment This message was
[JIRA] (JENKINS-55460) Cleaning of svn workspace broken in 2.157
Title: Message Title Nic Stevens updated an issue Jenkins / JENKINS-55460 Cleaning of svn workspace broken in 2.157 Change By: Nic Stevens Component/s: subversion-plugin Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker edited a comment on JENKINS-55448 Re: File cleaning failure, old build and plugin update What I tried: # Create a freestyle project using the git repo [https://github.com/jvz/example-java-docker.git] # Under Build Environment, I checked "Delete workspace before build starts" and Advanced # Under Advanced, I added an include pattern for build/classes/** and also apply to directories. # Under Build, add an "invoke gradle script" step to build the project. # Save, build now. # No 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update What I tried: Create a freestyle project using the git repo https://github.com/jvz/example-java-docker.git Under Build Environment, I checked "Delete workspace before build starts" and Advanced Under Advanced, I added an include pattern for build/classes/** and also apply to directories. Save, build now. No 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Robert Koncier edited a comment on JENKINS-55448 Re: File cleaning failure, old build and plugin update [~jvz] could you please also try option to drop only specific sub-folder of the job. Here are my settings: !image-2019-01-10-10-44-33-149.png!and I'm getting error immediately*10:40:37* [EnvInject] - Loading node environment variables.*10:40:37* Building in workspace /var/lib/jenkins/workspace/xxx/DEV/dev1-xxx*10:40:37* [WS-CLEANUP] Deleting project workspace...*10:40:43* ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete '/var/lib/jenkins/workspace/xxx/DEV/dev1-xxx/bin/custom'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.*10:40:43* ERROR: Cannot delete workspace: Unable to delete '/var/lib/jenkins/workspace/ Hybris/ xxx/ DEV/ dev1-xxx/bin/custom'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.*10:40:43* SSH: Current build result is [FAILURE], not going to run.*10:40:43* Finished: FAILUREWhere bin/custom folder only files generated during java project compilation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Robert Koncier commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Matt Sicker could you please also try option to drop only specific sub-folder of the job. Here are my settings: and I'm getting error immediately 10:40:37 [EnvInject] - Loading node environment variables.10:40:37 Building in workspace /var/lib/jenkins/workspace/xxx/DEV/dev1-xxx*10:40:37* [WS-CLEANUP] Deleting project workspace...10:40:43 ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete '/var/lib/jenkins/workspace/xxx/DEV/dev1-xxx/bin/custom'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.10:40:43 ERROR: Cannot delete workspace: Unable to delete '/var/lib/jenkins/workspace/Hybris/xxx/dev1-xxx/bin/custom'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.10:40:43 SSH: Current build result is [FAILURE], not going to run.10:40:43 Finished: FAILURE Where bin/custom folder only files generated during java project compilation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update Thanks Robert Koncier, I'll give that a try. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Robert Koncier updated an issue Jenkins / JENKINS-55448 File cleaning failure, old build and plugin update Change By: Robert Koncier Attachment: image-2019-01-10-10-44-33-149.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker edited a comment on JENKINS-55448 Re: File cleaning failure, old build and plugin update I've tried reproducing some of the scenarios provided, though I haven't been able to reproduce the issue (using my PR): * Tried with JENKINS_HOME being a symlink. * Tried using a multibranch pipeline (github) where branches get created and deleted later. * Tried renaming my project to ".example" to test the leading dot.However, I'd only expect my PR to have affected any stacktraces with FilePath.delete in them. Some of the stacktraces are executed on master, though, and I haven't been able to figure out how to reproduce that yet. Is this issue affecting specific multibranch pipeline providers? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update I've tried reproducing some of the scenarios provided, though I haven't been able to reproduce the issue (using my PR): Tried with JENKINS_HOME being a symlink. Tried using a multibranch pipeline where branches get created and deleted later. Tried renaming my project to ".example" to test the leading dot. However, I'd only expect my PR to have affected any stacktraces with FilePath.delete in them. Some of the stacktraces are executed on master, though, and I haven't been able to figure out how to reproduce that 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update I've opened a PR here: https://github.com/jenkinsci/jenkins/pull/3841 Please let me know if this fixes the problem you're seeing. This might only be a partial fix so far, 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Devin Nusbaum commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log Are there any error messages in your logs? Do you see any kind of coloration in any jobs? What tools are producing colorized output in your logs (Ansible)? Can you copy-paste one of the lines that is showing up incorrectly here (preferably replacing literal occurrences of the character 0x1B with 0x1B here so we can see how control characters are being processed?) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update It looks like I had forgotten to update FilePath.deleteRecursive() and FilePath.deleteContents() to use the updated Util methods. This causes an inconsistency in behavior between deleting files directly versus deleting them via remoting APIs. I'll make a PR that you can try out to see if this fixes your 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Victor Verbitsky commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log If ansicolor 0.6.x is installed then I see the 1 variant of the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55436) warnings-ng is not backwards compatible
Title: Message Title
Matthias Fuchs commented on JENKINS-55436
Re: warnings-ng is not backwards compatible
Yeah that worked for me too. So I did some further trials. And actually androidLint seems to be the culprit. The following declarative script fails for me
pipeline {
agent any
stages {
stage('Static Analysis') {
steps {
echo 'Hello World!'
}
post {
always {
// When uncommenting pmd and checkstyle but commenting out androidLint it works
//pmd canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "pmd.xml", unHealthy: '', unstableTotalAll: '0'
//checkstyle canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "checkstyle.xml", unHealthy: '', unstableTotalAll: '0'
androidLint canComputeNew: false, canRunOnFailed: true, defaultEncoding: '', healthy: '', pattern: "$reports/lint*.xml", unHealthy: '', unstableTotalAll: '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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Devin Nusbaum commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log Thanks for trying it out Victor Verbitsky! It would be great if anyone seeing the issue could report whether they are seeing variant 1 or 2 of the issue while ansicolor 0.6.x is installed as described in my comment on the GitHub 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-55450) Checkout of library to be used in a Pipeline script with SVN hangs
Title: Message Title Matt Sicker resolved as Fixed Jenkins / JENKINS-55450 Checkout of library to be used in a Pipeline script with SVN hangs Change By: Matt Sicker 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-55411) Whitelist DateTimeFormatter.ofPattern(String)
Title: Message Title Devin Nusbaum started work on JENKINS-55411 Change By: Devin Nusbaum 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-55411) Whitelist DateTimeFormatter.ofPattern(String)
Title: Message Title Devin Nusbaum updated JENKINS-55411 Jenkins / JENKINS-55411 Whitelist DateTimeFormatter.ofPattern(String) Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55411) Whitelist DateTimeFormatter.ofPattern(String)
Title: Message Title Aleksei Zhogov edited a comment on JENKINS-55411 Re: Whitelist DateTimeFormatter.ofPattern(String) PR to fix this: https://github.com/jenkinsci/script-security-plugin/pull/ 235 237 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55448) File cleaning failure, old build and plugin update
Title: Message Title Matt Sicker commented on JENKINS-55448 Re: File cleaning failure, old build and plugin update I tried using a symlink for my JENKINS_HOME and am not getting that error, though it looks like it's ignoring symlinks for deletion? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55478) CompositeIOException when deleting workspace before check-out
Title: Message Title Matt Sicker commented on JENKINS-55478 Re: CompositeIOException when deleting workspace before check-out Ok, based on those logs, I have a hypothesis: Previously, when retrying a delete, if the previous retry had an error, but then the current retry works, this will still throw an exception for the prior issue. If this is the case, then it might be a rather simple fix for all the related regressions here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54683) Pods entering error state
Title: Message Title Utsav Chokshi edited a comment on JENKINS-54683 Re: Pods entering error state Hi Carlos,Even I am getting the same error with version `1.14.2`.Here are logs :```Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: graph-builder-bindings-slave-zlvmdJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Jan 10, 2019 11:04:05 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.19Jan 10, 2019 11:04:05 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among <>Jan 10, 2019 11:04:05 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Jan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: <> Agent port:5 Identity: 8c:53:79:cc:4f:da:d6:54:56:0a:9e:9d:2a:d4:a3:3bJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to [<>|http://jenkins.cn-codegraph-prod-k8s.devfactory.com:5/]Jan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: 8c:53:79:cc:4f:da:d6:54:56:0a:9e:9d:2a:d4:a3:3bJan 10, 2019 11:04:05 AM org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer onRecvINFO: [JNLP4-connect connection to [jenkins.cn-codegraph-prod-k8s.devfactory.com/10.69.160.22:5 <> |http://jenkins.cn-codegraph-prod-k8s.devfactory.com/10.69.160.22:5]] Local headers refused by remote: Unknown client name: graph-builder-bindings-slave-zlvmdJan 10, 2019 11:04:05 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Protocol JNLP4-connect encountered an unexpected exceptionjava.util.concurrent.ExecutionException: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: graph-builder-bindings-slave-zlvmdat org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)at hudson.remoting.Engine.innerRun(Engine.java:609)at hudson.remoting.Engine.run(Engine.java:469)Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Unknown client name: graph-builder-bindings-slave-zlvmdat org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.newAbortCause(ConnectionHeadersFilterLayer.java:378)at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.onRecvClosed(ConnectionHeadersFilterLayer.java:433)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287)at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)at [org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154|http://org.jenkinsci.remoting.protocol.networklayer.onrecvclosed%28networklayer.java:154/])at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48)at
[JIRA] (JENKINS-52744) Using not existing environment variables in environment GString expression causes strange error message
Title: Message Title Andrew Bayer updated JENKINS-52744 Merged, will be in the upcoming 1.3.5 release. Jenkins / JENKINS-52744 Using not existing environment variables in environment GString _expression_ causes strange error message Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55508) PCT - PCT is not able to recognize plugins from pipeline-stage-view as it's a multi-module
Title: Message Title Adrien Lecharpentier commented on JENKINS-55508 Re: PCT - PCT is not able to recognize plugins from pipeline-stage-view as it's a multi-module I still have a problem as the parent pom replacement done by PCT breaks the hierarchy on the plugin. The groupId of the plugin is different than what other plugins are using. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.
