[JIRA] (JENKINS-58794) Kubernetes plugin handling two JNLP agents
Title: Message Title Alex Earl commented on JENKINS-58794 Re: Kubernetes plugin handling two JNLP agents Are you setting AGENT_WORKDIR via some environment for the container. Also, HOME looks like a Linux path, not a Windows path, not sure if that would cause any issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201104.156478101.7182.1564787700154%40Atlassian.JIRA.
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Sunil Alpati commented on JENKINS-50523 Re: setami doesn't update global config file Is it working for you? Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.7178.1564787340189%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada closed an issue as Fixed Jenkins / JENKINS-58791 Not able to start Jenkins executors in EKS Change By: suryatej yaramada Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7175.1564785180289%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada commented on JENKINS-58791 Re: Not able to start Jenkins executors in EKS Not sure root cause but re installed the plugin and it works now as expected Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7173.1564785180267%40Atlassian.JIRA.
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Sunil Alpati commented on JENKINS-50523 Re: setami doesn't update global config file Raihaan Shouhell is that right call? Is this `Jenkins.getInstance().save()` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.7170.1564784100231%40Atlassian.JIRA.
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Sunil Alpati commented on JENKINS-50523 Re: setami doesn't update global config file Any update in this issue Achal Shah Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.7162.1564784040282%40Atlassian.JIRA.
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Sunil Alpati edited a comment on JENKINS-50523 Re: setami doesn't update global config file Any update in on this issue [~achalshah20] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.7166.1564784040375%40Atlassian.JIRA.
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title Nitin Surana updated JENKINS-58792 Jenkins / JENKINS-58792 @grab no longer works in jenkins v2.176.2 Change By: Nitin Surana Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201102.1564774954000.7138.1564782121297%40Atlassian.JIRA.
[JIRA] (JENKINS-44789) docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom
Title: Message Title Devin Nusbaum resolved as Duplicate A fix for this issue was just released in Docker Pipeline plugin version 1.19. From the release notes: Deprecate the dockerFingerprintFrom and dockerFingerprintRun steps and stop calling them during docker.build and image.run. Fixes various issues with Dockerfile parsing and parsing arguments to docker build. Jenkins / JENKINS-44789 docker 17.05 multistage Dockerfile breaks dockerFingerprintFrom Change By: Devin Nusbaum Status: Reopened Resolved Resolution: Duplicate Released As: docker-workflow 1.19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title Nitin Surana updated JENKINS-58792 Jenkins / JENKINS-58792 @grab no longer works in jenkins v2.176.2 Change By: Nitin Surana Status: Open Fixed but Unreleased Assignee: Nitin Surana Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201102.1564774954000.7137.1564782065115%40Atlassian.JIRA.
[JIRA] (JENKINS-44609) Docker inspect failing on named multi-stage builds
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in Docker Pipeline plugin version 1.19. From the release notes: Deprecate the dockerFingerprintFrom and dockerFingerprintRun steps and stop calling them during docker.build and image.run. Fixes various issues with Dockerfile parsing and parsing arguments to docker build. Jenkins / JENKINS-44609 Docker inspect failing on named multi-stage builds Change By: Devin Nusbaum Status: Reopened Resolved Resolution: Fixed Released As: docker-workflow 1.19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title Nitin Surana edited a comment on JENKINS-58792 Re: @grab no longer works in jenkins v2.176.2 Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-41122 In the new jenkins, instead of creating pipelines libraries globally, I created pipeline library for a specific multi-branch project. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201102.1564774954000.7082.1564782064241%40Atlassian.JIRA.
[JIRA] (JENKINS-57369) Docker build-args incorrectly rejected and successful build marked failed
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in Docker Pipeline plugin version 1.19. From the release notes: Deprecate the dockerFingerprintFrom and dockerFingerprintRun steps and stop calling them during docker.build and image.run. Fixes various issues with Dockerfile parsing and parsing arguments to docker build. Jenkins / JENKINS-57369 Docker build-args incorrectly rejected and successful build marked failed Change By: Devin Nusbaum Status: Open Resolved Resolution: Fixed Released As: docker-workflow 1.19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title Nitin Surana commented on JENKINS-58792 Re: @grab no longer works in jenkins v2.176.2 Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-41122 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201102.1564774954000.7076.156478241%40Atlassian.JIRA.
[JIRA] (JENKINS-58794) Kubernetes plugin handling two JNLP agents
Title: Message Title
Miguel Suarez updated an issue
Jenkins / JENKINS-58794
Kubernetes plugin handling two JNLP agents
Change By:
Miguel Suarez
Environment:
Jenkins 2.176.2 , Kubernetes AKS 1.14 - preview, Jenkins installed from Helm, Kubernetes plugin 1.16.0
Hello, I have tested windows agents using the AKS 1.14 preview. I have created Windows and Linux agents successfully in different pipelines using the plugin by configuring a separate pod template with a jnlp container (for Windows) in the UI. I am trying to have two different containers (one for windows and one for linux) using pod specs from Git. Is this possible? I have been able to run the Jenkinsfile from here: [https://github.com/mluyo3414org/pod-templates] where one pod (linux based) is obtained from Git and one pod (windows based ) is obtained from the UI. The jenkinsfile currently works fine as the label 'windows-test' is configured in the UI but when trying to use [https://github.com/mluyo3414org/pod-templates/blob/master/win/win-pod.yaml] it fails with:25m Warning Failed pod/windows-q658k-sv952 Error: failed to start container "jnlp": Error response from daemon: container jnlp encountered an error during CreateProcess: failure in a Windows system call: The system cannot find the file specified. (0x2) extra info: {"CommandLine":"cat","User":"jenkins","WorkingDirectory":"C:\\Users\\jenkins\\Jenkins","Environment":{"AGENT_WORKDIR":"C:/Users/jenkins/Jenkins/Agent","HOME":"/home/jenkins","JAVA_BASE_URL":"https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u212-b04/OpenJDK8U-","JAVA_HOME":"C:\\openjdk-8","JAVA_URL_VERSION":"8u212b04","JAVA_VERSION":"8u212-b04","JENKINS_AGENT_NAME":"windows-q658k-sv952","JENKINS_AGENT_PORT":"tcp://10.0.103.127:5","JENKINS_AGENT_PORT_5_TCP":"tcp://10.0.103.127:5","JENKINS_AGENT_PORT_5_TCP_ADDR":"10.0.103.127","JENKINS_AGENT_PORT
Add Comment
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Devin Nusbaum resolved as Fixed A fix for this issue was just released in Docker Pipeline Plugin version 1.19. Jenkins / JENKINS-46636 `dir` does not change working directory for contained steps Change By: Devin Nusbaum Status: Reopened Resolved Resolution: Fixed Released As: docker-workflow 1.19 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58794) Kubernetes plugin handling two JNLP agents
Title: Message Title Miguel Suarez created an issue Jenkins / JENKINS-58794 Kubernetes plugin handling two JNLP agents Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-02 21:23 Environment: Jenkins 2.176.2 Priority: Minor Reporter: Miguel Suarez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58793) Add "fields" parameter to api/2/search endpoint for jiraJqlSearch
Title: Message Title Meg Kido created an issue Jenkins / JENKINS-58793 Add "fields" parameter to api/2/search endpoint for jiraJqlSearch Issue Type: New Feature Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2019-08-02 21:08 Priority: Minor Reporter: Meg Kido It appears that jiraJqlSearch uses "jql", "startAt" and "maxResults" parameters for calling Jira REST API with api/2/search endpoint. Jira admin at Teradata where I work wants api/2/search call to be made with "fields" parameter to avoid negatively impacting Jira performance when we update Jira to version 7.13.5. I noticed that your code does not use fields parameter. https://github.com/jenkinsci/jira-steps-plugin/blob/6cd86d5b155599ce8f4d1eaf28604a4bb872bef6/src/main/java/org/thoughtslive/jenkins/plugins/jira/service/JiraService.java#L252 Is it feasible to add fields parameter so I can continue to use jiraJqlSearch in my code for work? Add Comment
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada commented on JENKINS-58791 Re: Not able to start Jenkins executors in EKS I am using following ample test , I tired to downgrade the durable-task plugin but failed as it is dependancy for kubernetes latest version plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7044.1564779180244%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada edited a comment on JENKINS-58791 Re: Not able to start Jenkins executors in EKS I am using following ample test , I tired to downgrade the durable-task plugin but failed as it is dependancy for kubernetes latest version plugin . using corretto8 java in master jenkins please let me know if needed more information Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7046.1564779180275%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title
suryatej yaramada edited a comment on JENKINS-58791
Re: Not able to start Jenkins executors in EKS
``` node('eks-cluster'){ container('eks-cluster') { { sh label: '', script: 'pwd' } } ```
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7042.1564779060238%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title
suryatej yaramada commented on JENKINS-58791
Re: Not able to start Jenkins executors in EKS
```node('eks-cluster'){ container('eks-cluster') { sh label: '', script: 'pwd' } }```
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.7040.1564779060168%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Alexander Komarov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications FYI, the jabber PR no longer has conflicts, but I suspect that it should be updated to depend on a stable version of the instant messaging plugin once it is released with the changes. It's not clear to me whether the SNAPSHOT version is even published in the wild. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.7007.1564776180855%40Atlassian.JIRA.
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title
Nitin Surana updated an issue
Jenkins / JENKINS-58792
@grab no longer works in jenkins v2.176.2
Change By:
Nitin Surana
I had a jenkinsfile pipeline that run successfully in v2.89.4But the same pipeline throws the following error in v2.176.2 java.lang.RuntimeException: No suitable ClassLoader found for grab My jenkinsfile looks like {code:java}@Grab('org.codehaus.groovy.modules.http-builder:http-builder:0.5.0-RC2')import groovy.json.JsonOutputimport groovyx.net.http.RESTClientimport static groovyx.net.http.ContentType.JSONimport groovy.json.JsonSlurperimport groovy.io.FileTypedef call(body) {pipelineConfig = [:]body.resolveStrategy = Closure.DELEGATE_FIRSTbody.delegate = pipelineConfigpipeline {...}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201102.1564774954000.7004.1564775100065%40Atlassian.JIRA.
[JIRA] (JENKINS-58792) @grab no longer works in jenkins v2.176.2
Title: Message Title Nitin Surana created an issue Jenkins / JENKINS-58792 @grab no longer works in jenkins v2.176.2 Issue Type: Bug Assignee: Unassigned Components: pipeline, workflow-job-plugin Created: 2019-08-02 19:42 Priority: Major Reporter: Nitin Surana I had a jenkinsfile pipeline that run successfully in v2.89.4 But the same pipeline throws the following error in v2.176.2 java.lang.RuntimeException: No suitable ClassLoader found for grab Add Comment This message was sent by
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada commented on JENKINS-58791 Re: Not able to start Jenkins executors in EKS I am not seeing this issue with the old version of plugin which is running on PROD , we are planning to update the Jenkins master along with kubernetes-plugin but seeing this error which is hard stopper for us to upgrade Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201101.1564768674000.6981.1564770720090%40Atlassian.JIRA.
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title
suryatej yaramada updated an issue
Jenkins / JENKINS-58791
Not able to start Jenkins executors in EKS
Change By:
suryatej yaramada
Seeing following error while using kubernetes plugin latest version Still waiting to schedule task ‘eks-cluster-0fv20’ is offlineAgent [eks-cluster-0fv20|http://dev-jenkins.mcd.sniadmin/computer/eks-cluster-0fv20] is provisioned from template Kubernetes Pod TemplateRunning on [eks-cluster-0fv20|http://dev-jenkins.mcd.sniadmin/computer/eks-cluster-0fv20/] in /home/jenkins/workspace/Sandbox/surya/eks-test1[Pipeline] {[Pipeline] container[Pipeline] {[Pipeline] shprocess apparently never started in /home/jenkins/workspace/Sandbox/surya/eks-test1@tmp/durable-d09cb7c0( running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] End of 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.
To view this discussion on the web visit
[JIRA] (JENKINS-58791) Not able to start Jenkins executors in EKS
Title: Message Title suryatej yaramada created an issue Jenkins / JENKINS-58791 Not able to start Jenkins executors in EKS Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-02 17:57 Environment: Jenkins master running LTS version in EKS ( used custom image runs on amzonlinux) Priority: Minor Reporter: suryatej yaramada Seeing following error while using kubernetes plugin latest version running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true Add Comment
[JIRA] (JENKINS-58790) Add System hook
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58790 Add System hook Issue Type: Story Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-02 16:52 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda On removal of group, subgroup or project Add Comment
[JIRA] (JENKINS-58593) SCMHeadEvent is not fired in webhook
Title: Message Title Parichay Barpanda updated JENKINS-58593 Jenkins / JENKINS-58593 SCMHeadEvent is not fired in webhook Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200750.1563780141000.6974.1564764660239%40Atlassian.JIRA.
[JIRA] (JENKINS-58739) NPE for group projects MRs
Title: Message Title Parichay Barpanda updated JENKINS-58739 Jenkins / JENKINS-58739 NPE for group projects MRs Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201040.1564575005000.6973.1564764660192%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title
Sergio Merino commented on JENKINS-58789
Re: Timestamps disappear without any reason inside podTemplate
As workaround, adding "timestamps{}" inside podTemplate works. But I was expecting, that configuring it at the higher level would be enough
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201099.1564764393000.6972.1564764480105%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title
Sergio Merino created an issue
Jenkins / JENKINS-58789
Timestamps disappear without any reason inside podTemplate
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2019-08-02 16:46
Priority:
Minor
Reporter:
Sergio Merino
I found this problem after updating from kubernetes:1.17.2 to kubernetes:1.18.1. The timestamp stop appearing for code running inside podTemplate. Not sure if this problem could be related with other plugins, but it is only happening inside podTemplate. Code to replicate the behavior:
timestamps{
Integer echoNumbers = 3
node("master") {
for (i = 0; i "echo \"Pre POD hello ${i}\" && sleep 1"
}
}
podTemplate(showRawYaml: false, label: "alpine1", cloud: "Build farm", containers: [
containerTemplate(name: 'alpine', image: 'alpine', ttyEnabled: true, command: "cat")]) {
node ("alpine1") {
for (i = 0; i "echo \"POD hello ${i}\" && sleep 1"
}
}
}
node("master") {
for (i = 0; i "echo \"POST POD hello ${i}\" && sleep 1"
}
}
}
Console log:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] timestamps
[Pipeline] {
[Pipeline] node
17:44:27 Running on Jenkins in /var/jenkins_home/jobs/***/workspace
[Pipeline] {
[Pipeline] sh
17:44:27 + echo Pre POD hello 0
17:44:27 Pre POD hello 0
17:44:27 + sleep 1
[Pipeline] sh
17:44:28 + echo Pre POD hello 1
17:44:28 Pre POD hello 1
17:44:28
[JIRA] (JENKINS-47874) Support multiple repositories in multi-branch pipeline
Title: Message Title André Ilhicas Santos edited a comment on JENKINS-47874 Re: Support multiple repositories in multi-branch pipeline There is actually a TODO for exactly the same use case described in this issue in the responsible getName function for branch name in Branch class at branch-api-plugin [https://github.com/jenkinsci/branch-api-plugin/blob/1039350970768b27c88bebb0dad6ff9c96e50e0e/src/main/java/jenkins/branch/Branch.java#L143]What would be the impacts of adding another constructor to allow the remote name to be passed as a prefix for instance? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186391.1510100602000.6960.1564763221021%40Atlassian.JIRA.
[JIRA] (JENKINS-47874) Support multiple repositories in multi-branch pipeline
Title: Message Title André Ilhicas Santos commented on JENKINS-47874 Re: Support multiple repositories in multi-branch pipeline There is actually a TODO for exactly the same use case in the responsible getName function for branch name https://github.com/jenkinsci/branch-api-plugin/blob/1039350970768b27c88bebb0dad6ff9c96e50e0e/src/main/java/jenkins/branch/Branch.java#L143 What would be the impacts of adding another constructor to allow the remote name to be passed as a prefix for instance? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186391.1510100602000.6949.1564763220787%40Atlassian.JIRA.
[JIRA] (JENKINS-58491) Cannot configure Nomad plugin with JCasC
Title: Message Title Jonathan Ballet commented on JENKINS-58491 Re: Cannot configure Nomad plugin with JCasC FYI, this has been reported upstream in https://github.com/jenkinsci/nomad-plugin/issues/54 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200629.1563185265000.6946.1564761840144%40Atlassian.JIRA.
[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline
Title: Message Title Victor Martinez commented on JENKINS-54322 Re: Add ability SKIP stage in script pipeline PR: https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/346 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194973.1540842384000.6938.1564761000415%40Atlassian.JIRA.
[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline
Title: Message Title Victor Martinez assigned an issue to Victor Martinez Jenkins / JENKINS-54322 Add ability SKIP stage in script pipeline Change By: Victor Martinez Assignee: Victor Martinez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194973.1540842384000.6922.1564760941432%40Atlassian.JIRA.
[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline
Title: Message Title Victor Martinez started work on JENKINS-54322 Change By: Victor Martinez Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194973.1540842384000.6929.1564760941589%40Atlassian.JIRA.
[JIRA] (JENKINS-54322) Add ability SKIP stage in script pipeline
Title: Message Title Victor Martinez updated JENKINS-54322 Jenkins / JENKINS-54322 Add ability SKIP stage in script pipeline Change By: Victor Martinez Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194973.1540842384000.6931.1564760941633%40Atlassian.JIRA.
[JIRA] (JENKINS-58788) EC2 Plugin throwing NullPointer exception when connecting to Windows agent.
Title: Message Title Tim Brown created an issue Jenkins / JENKINS-58788 EC2 Plugin throwing NullPointer exception when connecting to Windows agent. Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-08-02 15:36 Environment: Docker, windows Priority: Major Reporter: Tim Brown I was using the latest jenkins/jenkins:lts container(2.176.1), and moved to the jenkins/jenkins container (2.187), but same issue. I am also using the latest ec2-plugin version (1.44.1) am using The code and the exception are below. Exception: Connecting to (34.245.65.86) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. Connecting to (34.245.65.86) with WinRM as Administrator Waiting for WinRM to come up. Sleeping 10s. ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.win.EC2WindowsLauncher.connectToWinRM(EC2WindowsLauncher.java:123) at hudson.plugins.ec2.win.EC2WindowsLauncher.launchScript(EC2WindowsLauncher.java:37) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:48) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title
Ryan Felder edited a comment on JENKINS-57695
Re: Jira issue not created when jenkins build failed
I just got this today after verifying my Jira settings test reports success. {code:java} ERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.jira.JiraCreateIssueNotifier.getStatus(JiraCreateIssueNotifier.java:220) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultSuccess(JiraCreateIssueNotifier.java:388) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:161) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'JIRA: Create issue' marked build as failure {code} Now using Jenkins 2.176.2 and Jira Plugin 3.0.8
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.6908.1564758840274%40Atlassian.JIRA.
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Ryan Felder commented on JENKINS-57695 Re: Jira issue not created when jenkins build failed I just got this today after verifying my Jira settings test reports success. ERROR: Build step failed with exception java.lang.NullPointerException at hudson.plugins.jira.JiraCreateIssueNotifier.getStatus(JiraCreateIssueNotifier.java:220) at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultSuccess(JiraCreateIssueNotifier.java:388) at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:161) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1843) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'JIRA: Create issue' marked build as failure Now using Jenkins 2.176.2 and Jira Plugin 3.0.8 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199631.1558935625000.6901.1564758780198%40Atlassian.JIRA.
[JIRA] (JENKINS-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title Jose Bezerra commented on JENKINS-54525 Re: java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) This one has been resolved for one month but unfortunately it hasn't been merged in the repository. Does anyone has access to merge it to the last release please? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195296.1541626449000.6891.1564758060225%40Atlassian.JIRA.
[JIRA] (JENKINS-54525) java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87)
Title: Message Title Jose Bezerra commented on JENKINS-54525 Re: java.lang.NullPointerException at hudson.scm.CvsRepository.(CvsRepository.java:87) +1 vote as this is a current issue on our platform too. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195296.1541626449000.6881.1564757521584%40Atlassian.JIRA.
[JIRA] (JENKINS-58787) Be able to create a job posting config.xml - Or improve docs
Title: Message Title Manuel Cardenas created an issue Jenkins / JENKINS-58787 Be able to create a job posting config.xml - Or improve docs Issue Type: Improvement Assignee: Janario Oliveira Components: http-request-plugin Created: 2019-08-02 14:41 Priority: Minor Reporter: Manuel Cardenas I want to be able to create jobs just by posting config.xml to the jenkins instance using the httprequest step def response = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-type', value: 'application/xml']], ignoreSslErrors: true, outputFile: 'config.xml', responseHandle: "STRING", url: 'http://localhost:8080/job/FOLDER/job/template/config.xml', validResponseCodes: '100:399' def myxml= "'"+response.content+"'" def response1 = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-Type', value: 'TEXT_PLAIN'], [maskValue: false, name: 'requestBody', value: myxml], [maskValue: false, name: 'consoleLogResponseBody', value: 'true'], [maskValue: false, name: 'authentication', value: 'BASIC'] ], httpMode: 'POST', ignoreSslErrors: true, url: "http://localhost:8080/createItem?name=new_job" Or def response = httpRequest authentication: 'JENKINS', customHeaders: [[maskValue: false, name: 'Content-type', value: 'application/xml']], ignoreSslErrors: true, outputFile: 'config.xml', responseHandle: "STRING", url: 'http://localhost:8080/job/FOLDER/job/template/config.xml', validResponseCodes: '100:399' def myxml=
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Valentin Delaye commented on JENKINS-58766 Re: kubernetes-plugin access denied after update to 1.18.0 Thanks for the fix. We had same issue. Upgrading from 1.17.* to 1.18 broke our Jenkins Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.6852.1564756620336%40Atlassian.JIRA.
[JIRA] (JENKINS-58786) Write integration tests for implemented functions
Title: Message Title Andrey Falko created an issue Jenkins / JENKINS-58786 Write integration tests for implemented functions Issue Type: Improvement Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-08-02 14:25 Labels: gsoc-2019 Priority: Major Reporter: Andrey Falko Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58152) Fix Docker Compose demo for new plugin version
Title: Message Title Long Nguyen stopped work on JENKINS-58152 Change By: Long Nguyen Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200197.1561188183000.6833.1564755900943%40Atlassian.JIRA.
[JIRA] (JENKINS-58152) Fix Docker Compose demo for new plugin version
Title: Message Title Long Nguyen started work on JENKINS-58152 Change By: Long Nguyen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200197.1561188183000.6831.1564755840345%40Atlassian.JIRA.
[JIRA] (JENKINS-58690) Add retention strategy for Cloud
Title: Message Title Andrey Falko started work on JENKINS-58690 Change By: Andrey Falko Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200979.1564304727000.6829.1564755840318%40Atlassian.JIRA.
[JIRA] (JENKINS-58777) sh step stuck on when adding inheritFrom in the kubernetes agent section
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-58777 sh step stuck on when adding inheritFrom in the kubernetes agent section Change By: Vincent Latombe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201085.1564724309000.6826.1564755660436%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Vincent Latombe updated JENKINS-58766 Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.6823.1564755600268%40Atlassian.JIRA.
[JIRA] (JENKINS-58785) Environment variables for jnlp container are available to other containers
Title: Message Title Vincent Latombe started work on JENKINS-58785 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201095.156475539.6818.1564755540460%40Atlassian.JIRA.
[JIRA] (JENKINS-58785) Environment variables for jnlp container are available to other containers
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58785 Environment variables for jnlp container are available to other containers Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201095.156475539.6816.1564755540438%40Atlassian.JIRA.
[JIRA] (JENKINS-58785) Environment variables for jnlp container are available to other containers
Title: Message Title Vincent Latombe updated JENKINS-58785 Jenkins / JENKINS-58785 Environment variables for jnlp container are available to other containers Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201095.156475539.6820.1564755540507%40Atlassian.JIRA.
[JIRA] (JENKINS-58785) Environment variables for jnlp container are available to other containers
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-58785 Environment variables for jnlp container are available to other containers Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-08-02 14:16 Priority: Minor Reporter: Vincent Latombe Environment variables such as JENKINS_SECRET, JENKINS_URL, etc. are available in all containers when actually they are only needed in the jnlp container Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-55098) Build Flow: PowerMock and Mockito need massive updates for Java 11
Title: Message Title Oleg Nenashev updated JENKINS-55098 Jenkins / JENKINS-55098 Build Flow: PowerMock and Mockito need massive updates for Java 11 Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196159.1544436745000.6807.1564755120152%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Rob Graham commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I can confirm downgrade to BlueOcean 1.17 has fixed the threading issue - we do have a small memory leak now which I assume is caused also by the sse-gateway (given the change in 1.18 that has introduced this threading issue was a fix for a mem leak), but it's far more manageable than the threading issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6797.1564754220269%40Atlassian.JIRA.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite updated JENKINS-57587 Jenkins / JENKINS-57587 Lightweight checkout gives NPE Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199505.1558465141000.6763.1564753320350%40Atlassian.JIRA.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite updated JENKINS-57587 Thanks for checking again. If you find a way to duplicate it, please reopen it with the details. Jenkins / JENKINS-57587 Lightweight checkout gives NPE Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199505.1558465141000.6761.1564753320311%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Devin Nusbaum Assignee: vjuranek Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6747.1564752960700%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Devin Nusbaum Component/s: sse-gateway-plugin Component/s: groovy-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.6740.1564752960436%40Atlassian.JIRA.
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title
Tim Brown edited a comment on JENKINS-33350
Re: Does not support Amazon's automatic Windows admin password system
Do you know when this fix will be in a release? *Update 1* As a workaround we are trying to set this in the Advanced > Userdata field:{code:xml} # Set administrator password net user Administrator yourpassword wmic useraccount where "name='Administrator'" set PasswordExpires=FALSE # Configure and restart the WinRM Service; Enable the required firewall exception Stop-Service -Name WinRM Set-Service -Name WinRM -StartupType Automatic netsh advfirewall firewall set rule name="Windows Remote Management (HTTP-In)" new action="" localip=any remoteip=any Start-Service -Name WinRM {code} *Update 2*Even adding the Userdata doesn't connect properly. Even though I can connect using the below python script connects with the same credentials.{code:python}import sysimport winrmsession = winrm.Session(sys.argv[1], auth=('Administrator', sys.argv[2]))response = session.run_cmd('ipconfig', ['/all'])print(response.std_out){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.6729.1564752840704%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite edited a comment on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Thanks for the suggestion on the documentation. I've added it to my "[Jenkins Git Use Cases|https://docs.google.com/document/d/1FNofpRVFe8WTtMpKb7exftsBOLS_qJydULlUMePswbY/edit#]" document to remind me of things that need to be documented and where they need to be documented.If you'd like to submit a pull request, the documentation is open for contributions as pull requests . The GitHub interface makes it easy to contribute even without cloning or building locally. Refer to the [when directive in the pipeline syntax|https://github.com/jenkins-infra/jenkins.io/blob/master/content/doc/book/pipeline/syntax.adoc#when]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6726.1564752780231%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title Mark Waite commented on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Thanks for the suggestion on the documentation. I've added it to my "Jenkins Git Use Cases" document to remind me of things that need to be documented and where they need to be documented. If you'd like to submit a pull request, the documentation is open for contributions as pull requests. The GitHub interface makes it easy to contribute even without cloning or building locally. Refer to the when directive in the pipeline syntax. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6724.1564752780201%40Atlassian.JIRA.
[JIRA] (JENKINS-58783) Update pipeline stage-view-plugin to use the new WarningAction API
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-58783 Update pipeline stage-view-plugin to use the new WarningAction API Change By: Devin Nusbaum Labels: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201093.156474881.6718.1564752540719%40Atlassian.JIRA.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Jeff Blaine commented on JENKINS-57587 Re: Lightweight checkout gives NPE Well isn't that fun... I came back finally to provide you with more info and ... can no longer reproduce this. I guess this can be closed. Thanks for assisting and trying to solve this with me, Mark. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199505.1558465141000.6712.1564752480292%40Atlassian.JIRA.
[JIRA] (JENKINS-58784) pipeline-maven-plugin incompatible with JENKINS-22949 QueueItemAuthenticator fallback behavior cleanup
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-58784 pipeline-maven-plugin incompatible with JENKINS-22949 QueueItemAuthenticator fallback behavior cleanup Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-08-02 13:20 Priority: Minor Reporter: Cyrille Le Clerc Pipeline Maven Plugin is incompatible with JENKINS-22949 "QueueItemAuthenticator fallback behavior cleanup". Ref https://groups.google.com/forum/#!topic/jenkinsci-users/qQxwsrvKjO4 Add Comment
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title
Tim Brown edited a comment on JENKINS-33350
Re: Does not support Amazon's automatic Windows admin password system
Do you know when this fix will be in a release?As a workaround we are trying to set this in the Advanced > Userdata field: {code:xml} ``` # Set administrator passwordnet user Administrator yourpasswordwmic useraccount where "name='Administrator'" set PasswordExpires=FALSE# Configure and restart the WinRM Service; Enable the required firewall exceptionStop-Service -Name WinRMSet-Service -Name WinRM -StartupType Automaticnetsh advfirewall firewall set rule name="Windows Remote Management (HTTP-In)" new action="" localip=any remoteip=anyStart-Service -Name WinRM ``` {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.6694.1564751820775%40Atlassian.JIRA.
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Tim Brown edited a comment on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system Do you know when this fix will be in a release? As a workaround we are trying to set this in the Advanced > Userdata field:```# Set administrator passwordnet user Administrator yourpasswordwmic useraccount where "name='Administrator'" set PasswordExpires=FALSE# Configure and restart the WinRM Service; Enable the required firewall exceptionStop-Service -Name WinRMSet-Service -Name WinRM -StartupType Automaticnetsh advfirewall firewall set rule name="Windows Remote Management (HTTP-In)" new action="" localip=any remoteip=anyStart-Service -Name WinRM``` Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.6683.1564751701154%40Atlassian.JIRA.
[JIRA] (JENKINS-51568) Pipeline jobs hanging in Build Executor even if it is finished
Title: Message Title Raphael Greger commented on JENKINS-51568 Re: Pipeline jobs hanging in Build Executor even if it is finished Thank you David. I didn't find this configuration but I did some restriction with the log of job config history. Now the problem seems to be vanished. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190959.1527520483000.6680.1564751701113%40Atlassian.JIRA.
[JIRA] (JENKINS-33350) Does not support Amazon's automatic Windows admin password system
Title: Message Title Tim Brown commented on JENKINS-33350 Re: Does not support Amazon's automatic Windows admin password system Do you know when this fix will be in a release? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168755.1457344701000.6656.1564751520763%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Alexander Komarov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications Will fix, just returning from vacation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.6608.1564750680836%40Atlassian.JIRA.
[JIRA] (JENKINS-58777) sh step stuck on when adding inheritFrom in the kubernetes agent section
Title: Message Title Vincent Latombe commented on JENKINS-58777 Re: sh step stuck on when adding inheritFrom in the kubernetes agent section Probably same as JENKINS-58766, due to JENKINS-58705. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201085.1564724309000.6594.1564750140878%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Vincent Latombe started work on JENKINS-58766 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.6602.1564750141243%40Atlassian.JIRA.
[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.6599.1564750141198%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe commented on JENKINS-58751 Re: TAG_NAME is not populated in declarative multibranch pipeline Yes, thank you, you're assumptions are mostly correct. It turned out the problem is that 'TAG_NAME' is only populated when the build is triggered because of a tag. In order to get builds triggered by tags one needs the Basic Branch Build Strategies plugin (https://wiki.jenkins.io/display/JENKINS/Basic+Branch+Build+Strategies+Plugin). I think the docs on the when condition (https://jenkins.io/doc/book/pipeline/syntax/#when) could be improved upon by mentioning this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6591.1564749960092%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: John Doe Component/s: declarative-pipeline-when-conditions-plugin Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6585.1564749721097%40Atlassian.JIRA.
[JIRA] (JENKINS-58751) TAG_NAME is not populated in declarative multibranch pipeline
Title: Message Title John Doe updated an issue Jenkins / JENKINS-58751 TAG_NAME is not populated in declarative multibranch pipeline Change By: John Doe Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201054.1564649736000.6584.1564749721082%40Atlassian.JIRA.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title
Krisztián Gyula Tóth edited a comment on JENKINS-53946
Re: Bitbucket plugin unable to parse a Pull Request JSON Object
I have a similar issue when using a Post Webhook "Test Connection" on push with Bitbucket Server 6.1.3 (self-hosted). I am using Bitbucket Plugin 1.1.10. (on Jenkins 2.187). PR: [https://github.com/jenkinsci/bitbucket-plugin/pull/65] {code:java}at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:143) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:38) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194548.1539012261000.6576.1564749060181%40Atlassian.JIRA.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Jonathan Araña Cruz commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Just created the issue for Pipeline: Stage View Plugin -> https://issues.jenkins-ci.org/browse/JENKINS-58783 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.6574.1564748889371%40Atlassian.JIRA.
[JIRA] (JENKINS-58783) Update pipeline stage-view-plugin to use the new WarningAction API
Title: Message Title Jonathan Araña Cruz created an issue Jenkins / JENKINS-58783 Update pipeline stage-view-plugin to use the new WarningAction API Issue Type: Improvement Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2019-08-02 12:26 Priority: Minor Reporter: Jonathan Araña Cruz Rel: https://issues.jenkins-ci.org/browse/JENKINS-39203 Update to new WarningAction API and mark blocks properly on per-stage result. https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/#developers Add Comment
[JIRA] (JENKINS-58446) Fix log in GitLabSCMNavigator
Title: Message Title Parichay Barpanda resolved as Fixed This is not an issue. This is how SCMNavigator is designed this way and it just needs to know about one branch. Jenkins / JENKINS-58446 Fix log in GitLabSCMNavigator Change By: Parichay Barpanda Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200578.1562856443000.6315.1564747500087%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Jim Klimov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications > That PR has conflicts that you need to resolve first. Unfortunately I am not the author nor committer there. I think in github the repo maintainer may by default edit the source branch of a PR, in the other developer's repository. Given that the conflict is just something in "versions.gradle", can you please see if it is something you may and can fix easily? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.6247.1564746661013%40Atlassian.JIRA.
[JIRA] (JENKINS-58782) "Zoom Build Notifier" option is not available in Matrix Project
Title: Message Title Freeman Chiang created an issue Jenkins / JENKINS-58782 "Zoom Build Notifier" option is not available in Matrix Project Issue Type: Bug Assignee: zoom us Components: zoom-plugin Created: 2019-08-02 10:59 Environment: jenkins 2.164.2 zoom plugin 1.1 matrix-project 1.14 Priority: Major Reporter: Freeman Chiang In free-style project, it works well, but in Matrix projects (Multi-configuration project), we cannot find the option "Zoom Build Notifier" in Post-build Actions. Add Comment
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title
Krisztián Gyula Tóth edited a comment on JENKINS-53946
Re: Bitbucket plugin unable to parse a Pull Request JSON Object
I have a similar issue when using a Post Webhook "Test Connection" on push with Bitbucket Server 6.1.3 (self-hosted). I am using Bitbucket Plugin 1.1.10. (on Jenkins 2.187).{code:java}at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:143) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:38) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194548.1539012261000.6231.1564743000229%40Atlassian.JIRA.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title
Krisztián Gyula Tóth edited a comment on JENKINS-53946
Re: Bitbucket plugin unable to parse a Pull Request JSON Object
I have the same a similar issue when using a Post Webhook on push with Bitbucket Server 6.1.3 (self-hosted). I am using Bitbucket Plugin 1.1.10. (on Jenkins 2.187). {code:java}at net.sf.json.JSONObject.getString(JSONObject.java:2040) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPostServicePayload(BitbucketPayloadProcessor.java:143) at com.cloudbees.jenkins.plugins.BitbucketPayloadProcessor.processPayload(BitbucketPayloadProcessor.java:38) at com.cloudbees.jenkins.plugins.BitbucketHookReceiver.doIndex(BitbucketHookReceiver.java:54) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194548.1539012261000.6226.1564742820158%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Parichay Barpanda commented on JENKINS-58773 Re: Builds stuck after Querying the current revision of branch Hi Peter, glad it worked for you. Btw your GitLab Server version is fine, I expect it to have full compatibility with our plugin. I have limited knowledge in the area of configuring jobs. I am discussing with jcasc maintainers about this and will try to add them to the docs. Will let you know when done. Please feel free to let me know if anytime there is a bug/feature request (not already known ). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201079.156468431.6224.1564742280126%40Atlassian.JIRA.
[JIRA] (JENKINS-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Krisztián Gyula Tóth commented on JENKINS-53946 Re: Bitbucket plugin unable to parse a Pull Request JSON Object I have the same issue when using a Post Webhook on push with Bitbucket Server 6.1.3 (self-hosted). I am using Bitbucket Plugin 1.1.10. (on Jenkins 2.187). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194548.1539012261000.6219.1564742040289%40Atlassian.JIRA.
[JIRA] (JENKINS-58781) HTTP Input failure Excpetion while creating job using Jenkins-CLI "HTTP" Mode.
Title: Message Title Pratik Moholkar created an issue Jenkins / JENKINS-58781 HTTP Input failure Excpetion while creating job using Jenkins-CLI "HTTP" Mode. Issue Type: Bug Assignee: Unassigned Attachments: config.xml, Failure-with-persist-xml-error.txt, Failure-with-timeout-error.txt Components: cli Created: 2019-08-02 10:32 Labels: jenkins Priority: Major Reporter: Pratik Moholkar We were using Jenkins CLI "Remoting" mode to do several operations. But we have upgraded our Jenkins server to "config.xmlv2.176.1". Now we are unable to execute "Remoting" mode on it. As per [doc|https://jenkins.io/projects/remoting/], Remoting mode is deprecated. So we are try to use HTTP mode. Now while trying to create job we are facing an HTTPInput failure error. Success scenario: When we try it using command "java -jar jenkins-cli.jar -s http://localhost:8080/ -auth user:auth-token -noKeyAuth create-job jenkins-cli-test < config.xml", from command line, the job is getting successfully created. Failure Scenario: When we try it using command "java -jar jenkins-cli.jar -s http://localhost:8080/ -auth user:auth-token -noKeyAuth create-job jenkins-cli-test", from command line, it will wait for user input. If I paste the XML file and press Ctrl+Z as a exit character, it will give me an error "java.io.IOException: Pipe broken" and "Caused: java.io.IOException: Failed to persist config.xml". Attching full stacktrace. (ErrorFileName: Failure-with-persist-xml-error.txt) Also if I use failure scanario and after pasting XML, and wait for more 5 sec it will throw an error at Jenkins log
[JIRA] (JENKINS-58698) Perforce sync fails for symlinks
Title: Message Title Mats Liljegren commented on JENKINS-58698 Re: Perforce sync fails for symlinks I upgraded plugin to 1.10.3, and it seems to work better. Haven't had any issues so far... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200987.156437800.6215.1564741560132%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Peter Leibiger commented on JENKINS-58773 Re: Builds stuck after Querying the current revision of branch This was probably cause by some permission problem on the mac: https://stackoverflow.com/questions/41592836/error-error-fetching-remote-repo-origin-returned-status-code-143 - Solved it by installing Jenkins via brew. Thanks Parichay Barpanda, I updated the plugin and it seems to work. Gitlab is 11.10.8 Unrelated to this, do you have an example on how to configure a group job for Gitlab with JCasC? I didn't manage to adapt a github/Bitbucket example. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201079.156468431.6211.1564741020243%40Atlassian.JIRA.
[JIRA] (JENKINS-58773) Builds stuck after Querying the current revision of branch
Title: Message Title Peter Leibiger updated JENKINS-58773 Jenkins / JENKINS-58773 Builds stuck after Querying the current revision of branch Change By: Peter Leibiger Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201079.156468431.6213.1564741020278%40Atlassian.JIRA.
[JIRA] (JENKINS-55363) Support different SSH providers
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-55363 Re: Support different SSH providers I'm working on this branch https://github.com/jenkinsci/ssh-slaves-plugin/tree/ssh-slaves-2.0 it is not ready to use 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196466.154610799.6206.1564740120367%40Atlassian.JIRA.
[JIRA] (JENKINS-58780) Jenkins cancels the wrong build, when using QueueTaskFuture.cancel()
Title: Message Title Martin Schröder created an issue Jenkins / JENKINS-58780 Jenkins cancels the wrong build, when using QueueTaskFuture.cancel() Issue Type: Bug Assignee: Martin Schröder Components: core Created: 2019-08-02 09:49 Environment: Any (Core issue) Labels: jenkins queue cancel build Priority: Minor Reporter: Martin Schröder When cancelling a build for a specific Future object, Jenkins currently does not care about actually cancelling the queue item that corresponds to the given future. Instead, it simply cancel the first build for the same task that it can find. This can be easily replicated by starting two jobs with different parameters via a Groovy script without having any build hosts online (so that they get queued). The script should hold onto the returned QueueTaskFuture objects and then issue a cancellation on only one of them. Current Jenkins behaviour is to always cancel the first of the tasks, no matter which of the two future objects were called. This does not just affect programmatic calling of builds, but can also happen in downstream-triggered tasks and other build starting methods that rely on a cancellation via the QueueTaskFuture instance being reliable. A new Unittest is going to be provided in the pull request for this scenario.
[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title Daniel Beck commented on JENKINS-58096 Re: Authorize Project plugin not working for pipeline The same way you could complain (even without the plugin) that the user name in the shell is svcbuildadmin and not Michael Marcucilli. Note that Jenkins's SYSTEM user has nothing to do with Windows's SYSTEM (or LocalSystem now?) user. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200138.1560954019000.6192.1564739160202%40Atlassian.JIRA.
[JIRA] (JENKINS-58096) Authorize Project plugin not working for pipeline
Title: Message Title Daniel Beck closed an issue as Not A Defect This isn't how this works. Authorize Project changes the virtual user identity of the build running inside Jenkins, which controls the actions the build can take inside Jenkins (such as triggering other builds). It does not magically cause processes to su to a different user that may not even exist in the OS. Jenkins / JENKINS-58096 Authorize Project plugin not working for pipeline Change By: Daniel Beck Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-58594) Remove webhook when job is removed from Jenkins
Title: Message Title Parichay Barpanda closed an issue as Fixed There might be other jobs that depend on the webhook. So it is best to leave on user to remove the webhook manually. Jenkins / JENKINS-58594 Remove webhook when job is removed from Jenkins Change By: Parichay Barpanda Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200751.1563782949000.6182.1564738560252%40Atlassian.JIRA.
[JIRA] (JENKINS-58779) LogRotator stops cleaning, if a build directory has been deleted externally
Title: Message Title Martin Schröder created an issue Jenkins / JENKINS-58779 LogRotator stops cleaning, if a build directory has been deleted externally Issue Type: Bug Assignee: Martin Schröder Components: core Created: 2019-08-02 09:22 Environment: Any (is a core Jenkins behaviour) Labels: jenkins rotate Priority: Minor Reporter: Martin Schröder The deletion of a build/run in Jenkins is handled by the delete() method. It throws an exception, when the build directory on disk has already beenremoved and stops deleting the build. Unfortunately, the hudson.tasks.LogRotator.perform(Job) method does not check for this exception and will STOP cleaning up, once even just one build throws that exception. This behaviour can be fixed in the following ways (a pull-request will be uploaded shortly): The Run.delete() method must still unlink the job, even if the build directory has been removed externally. The log output of Run.delete() must be made less verbose (it prints the ENTIRE folder content by default, into the job that is doing the cleanup) The LogRotator.perform() method must handle the exceptions being thrown by delete() gracefully.
