[JIRA] (JENKINS-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Josh McDonald commented on JENKINS-5 Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab I will go back to 1.5 and see if I can trigger it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51111) Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab
Title: Message Title Josh McDonald commented on JENKINS-5 Re: Navigating to downstream job via Blue Ocean Triggered Builds does not show tests in Tests tab I can't replicate this, it works fine for me. Can anybody verify it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45688) Unable to set extensions for Git SCM Source via DSL
Title: Message Title Sam Gleske commented on JENKINS-45688 Re: Unable to set extensions for Git SCM Source via DSL This nonsense requiring the configure block is ridiculous. I've spent the past 5 hours trying to figure it out and I'm definitely not a Job DSL newb. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51490) New name of "Aborted" button for input statement
Title: Message Title Galleputin Vladimir created an issue Jenkins / JENKINS-51490 New name of "Aborted" button for input statement Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2018-05-23 04:51 Labels: pipeline Priority: Minor Reporter: Galleputin Vladimir Good day! How change name of "Aborted" button in input statement? The name of "Proceed" button can be changed using the "ok" option . Add Comment
[JIRA] (JENKINS-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
Title: Message Title Abubakar Mohammed edited a comment on JENKINS-27070 Re: Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration" Any update on this issue? Jenkins is generating non stop huge logs which is causing the performance issues . Please let me know if we have a fix for this.Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-27070) Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration"
Title: Message Title Abubakar Mohammed commented on JENKINS-27070 Re: Plenty of "SEVERE: Host connection pool not found, hostConfig=HostConfiguration" Any update on this issue? Jenkins is generating non stop huge logs which is causing the performance issues . Please let me know if we a fix for this. Thanks Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45688) Unable to set extensions for Git SCM Source via DSL
Title: Message Title Sam Gleske commented on JENKINS-45688 Re: Unable to set extensions for Git SCM Source via DSL Here's a link to the DSL used. https://github.com/gimp-ci/jenkins-dsl/blob/292cafd41e8c26e200dbe967aba7ec71e120df84/jobs/gimp_multibranch_pipelines.groovy Here's a list of plugins installed that broke the the DSL. https://github.com/gimp-ci/jenkins-os-packages/commit/2e9e0e6b5a2e0287268ca70d836f2a7e71fef72b In particular I confirmed the following plugins broke the DSL. org.jenkins-ci.plugins:cloudbees-bitbucket-branch-source:2.2.11 org.jenkins-ci.plugins:github-branch-source:2.3.4 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45614) Activity tab is really slow
Title: Message Title Olivier Lamy commented on JENKINS-45614 Re: Activity tab is really slow Sverre Moe I wonder if you guys have a lot of test results per build? I'd like to ensure my findings are right. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-41102) Job "Changes" do not match "Filter for Poll SCM"
Title: Message Title Timothy Williams commented on JENKINS-41102 Re: Job "Changes" do not match "Filter for Poll SCM" AccuRev plugin 0.7.16 did not fix this issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51456) Code coverage report for essentials client/server setup
Title: Message Title R. Tyler Croy started work on JENKINS-51456 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51456) Code coverage report for essentials client/server setup
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy Jenkins / JENKINS-51456 Code coverage report for essentials client/server setup Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts and fileExists inconsistent inside() docker containers
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51462
archiveArtifacts and fileExists inconsistent inside() docker containers
Change By:
Alexander Komarov
The following Pipeline code produces an error:{code:java}def image = docker.image("any_existing_image_eg_alpine")image.inside {sh 'date > /tmp/test.txt'sh 'cat /tmp/test.txt' //works, shows filedef fileContents = readFile '/tmp/test.txt' //worksecho "Contents: ${fileContents}" //works, shows file echo "Exists: ${fileExists('/tmp/test.txt')}" //FAILS (returns false) archiveArtifacts '/tmp/*.txt' //FAILS the build }{code}archiveArtifacts always reports that it matched no files (except in $WORKSPACE, see below).DSL steps in docker summary (what I've tried): * *readFile()*: works correctly on files in or out of $WORKSPACE * *writeFile()*: works correctly on files in or out of $WORKSPACE * *fileExists()*: works correctly only on files in $WORKSPACE (auto-mounted volume) * *archiveArtifacts()*: archives only files in $WORKSPACE (auto-mounted volume) So I guess there is a pattern ... and yet the behavior is inconsistent. I could not find any documentation that explains what the rules are.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51462) archiveArtifacts and fileExists inconsistent inside() docker containers
Title: Message Title Alexander Komarov edited a comment on JENKINS-51462 Re: archiveArtifacts and fileExists inconsistent inside() docker containers Workaround is to first copy the necessary files to the $WORKSPACE that is automatically mounted in the container ( , or [copy files from image to host|http://larstechnica.com/2017/05/docker-copy-files-from-image-to-local] by running docker commands just do everything in a shell step) the mounted directory in the first place. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts and fileExists inconsistent inside() docker containers
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-51462 archiveArtifacts and fileExists inconsistent inside() docker containers Change By: Alexander Komarov Summary: archiveArtifacts and fileExists not working inconsistent inside() docker containers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts and fileExists not working inside() docker containers
Title: Message Title Alexander Komarov updated an issue Jenkins / JENKINS-51462 archiveArtifacts and fileExists not working inside() docker containers Change By: Alexander Komarov Summary: archiveArtifacts and fileExists not working inside() docker containers Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts not working inside() docker containers
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51462
archiveArtifacts not working inside() docker containers
Change By:
Alexander Komarov
The following Pipeline code produces an error:{code:java}def image = docker.image("any_existing_image_eg_alpine")image.inside {sh 'date > /tmp/test.txt'sh 'cat /tmp/test.txt' //works, shows filedef fileContents = readFile '/tmp/test.txt' //worksecho "Contents: ${fileContents}" //works, shows filearchiveArtifacts '/tmp/*.txt' //FAILS}{code} No matter what pattern I've tried with archiveArtifacts , it always reports that it matched no files . It does not appear to be looking on the docker host either (except in $WORKSPACE , because '/**' or '**' also match nothing see below) .DSL steps in docker summary (what I've tried): * *readFile()*: works correctly on files in or out of $WORKSPACE * *writeFile()*: works correctly on files in or out of $WORKSPACE * *fileExists()*: incorrect works correctly only on files in $WORKSPACE ( reports false when file exists auto-mounted volume ) * *archiveArtifacts()*: ( archives only files under in $WORKSPACE tree while in inside ( ) ( auto-mounted volume ) ) So I guess there is a pattern ... and yet the behavior is inconsistent. I could not find any documentation that explains what the rules are.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51462) archiveArtifacts not working inside() docker containers
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51462
archiveArtifacts not working inside() docker containers
Change By:
Alexander Komarov
The following Pipeline code produces an error:{code:java}def image = docker.image("any_existing_image_eg_alpine")image.inside {sh 'date > /tmp/test.txt'sh 'cat /tmp/test.txt' //works, shows filedef fileContents = readFile '/tmp/test.txt' //worksecho "Contents: ${fileContents}" //works, shows filearchiveArtifacts '/tmp/*.txt' //FAILS}{code}No matter what pattern I've tried with archiveArtifacts, it always reports that it matched no files. It does not appear to be looking on the docker host either, because '/**' or '**' also match nothing.DSL steps in docker summary (what I've tried): * *readFile()*: works correctly * *writeFile()*: works correctly * *fileExists()*: incorrect (reports false when file exists) * *archiveArtifacts()*: (archives nothing only files under $WORKSPACE tree while in inside() (auto-mounted ) )
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51250) Prototype output format for manifest to be ingested by Update service
Title: Message Title R. Tyler Croy updated JENKINS-51250 Jenkins / JENKINS-51250 Prototype output format for manifest to be ingested by Update service Change By: R. Tyler Croy Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts not working inside() docker containers
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51462
archiveArtifacts not working inside() docker containers
Change By:
Alexander Komarov
The following Pipeline code produces an error:{code:java}def container image = docker.image("any_existing_image_eg_alpine") container image .inside {sh 'date > /tmp/test.txt'sh 'cat /tmp/test.txt' //works, shows filedef fileContents = readFile '/tmp/test.txt' //worksecho "Contents: ${fileContents}" //works, shows filearchiveArtifacts '/tmp/*.txt' //FAILS}{code}No matter what pattern I've tried with archiveArtifacts, it always reports that it matched no files. It does not appear to be looking on the docker host either, because '/**' or '**' also match nothing. The interesting thing is that readFile works. DSL steps in docker summary (what I've even tried using writeFile ): * *readFile () to create the file, it made no difference. *: works correctly Update * *writeFile()* : " works correctly * * fileExists " also fails in a container ( returns )*: incorrect (reports false when file exists) , even though readFile works. * *archiveArtifacts()*: (archives nothing while in inside() )
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-51462) archiveArtifacts not working inside() docker containers
Title: Message Title
Alexander Komarov updated an issue
Jenkins / JENKINS-51462
archiveArtifacts not working inside() docker containers
Change By:
Alexander Komarov
The following Pipeline code produces an error:{code:java}def container = docker.image("any_existing_image_eg_alpine")container.inside {sh 'date > /tmp/test.txt'sh 'cat /tmp/test.txt' //works, shows filedef fileContents = readFile '/tmp/test.txt' //worksecho "Contents: ${fileContents}" //works, shows filearchiveArtifacts '/tmp/*.txt' //FAILS}{code}No matter what pattern I've tried with archiveArtifacts, it always reports that it matched no files. It does not appear to be looking on the docker host either, because '/**' or '**' also match nothing.The interesting thing is that readFile works. I've even tried using writeFile() to create the file, it made no difference. Update: "fileExists" also fails in a container (returns false when file exists), even though readFile works.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-33918) listener for pipeline build stage or step changes
Title: Message Title Daniel Garzon commented on JENKINS-33918 Re: listener for pipeline build stage or step changes Jesse Glick using `GraphListener.onNewHead(FlowNode node)` did it for me. Unfortunately, I cannot seem to capture when a `StepAtomNode` starts or ends executing. Is there a way to do this? I am writing a plugin that capture pipeline metrics, and this is a deal-breaker for my use case as I cannot record individual steps! Thank you in advanced! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50081) Integration Test for JobAction
Title: Message Title Nikolai Wohlgemuth commented on JENKINS-50081 Re: Integration Test for JobAction Ich bin leider mit dem Testen bisher noch nicht sehr weit gekommen. Aktuell erhalte ich die JobAction und könnte die verschiedenen Methoden testen, allerdings ist es mir bisher nicht gelungen, auf eine Instanz des StaplerRequests zuzugreifen um ihm der JobAction zu übergeben. Ist es möglich einen Request auszulesen oder muss dieser selbst erstellt werden? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51137) Kubernetes plugin ignores "Max number of instances" when using yaml
Title: Message Title Carlos Sanchez commented on JENKINS-51137 Re: Kubernetes plugin ignores "Max number of instances" when using yaml https://github.com/jenkinsci/kubernetes-plugin/pull/326 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51137) Kubernetes plugin ignores "Max number of instances" when using yaml
Title: Message Title Carlos Sanchez updated JENKINS-51137 Jenkins / JENKINS-51137 Kubernetes plugin ignores "Max number of instances" when using yaml Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50268) instanceCap reached with preexisting pods because labels are empty
Title: Message Title Carlos Sanchez updated JENKINS-50268 Jenkins / JENKINS-50268 instanceCap reached with preexisting pods because labels are empty Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50268) instanceCap reached with preexisting pods because labels are empty
Title: Message Title Carlos Sanchez commented on JENKINS-50268 Re: instanceCap reached with preexisting pods because labels are empty https://github.com/jenkinsci/kubernetes-plugin/pull/325 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51137) Kubernetes plugin ignores "Max number of instances" when using yaml
Title: Message Title Carlos Sanchez started work on JENKINS-51137 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50268) instanceCap reached with preexisting pods because labels are empty
Title: Message Title Carlos Sanchez started work on JENKINS-50268 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50664) Default slave labels are missing in kubernetes-plugin
Title: Message Title Carlos Sanchez resolved as Duplicate Jenkins / JENKINS-50664 Default slave labels are missing in kubernetes-plugin Change By: Carlos Sanchez Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51137) Kubernetes plugin ignores "Max number of instances" when using yaml
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-51137 Kubernetes plugin ignores "Max number of instances" when using yaml Change By: Carlos Sanchez Summary: Kubernetes plugin ignores "Max number of instances" when using yaml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50664) Default slave labels are missing in kubernetes-plugin
Title: Message Title Carlos Sanchez started work on JENKINS-50664 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48885) JenkinsRule always returns null in getPluginManager().getPlugin() on new core versions
Title: Message Title Mike Kobit commented on JENKINS-48885 Re: JenkinsRule always returns null in getPluginManager().getPlugin() on new core versions Job DSL is another plugin that makes use of these APIs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51462) archiveArtifacts not working inside() docker containers
Title: Message Title Alexander Komarov edited a comment on JENKINS-51462 Re: archiveArtifacts not working inside() docker containers Workaround is to first copy the necessary files to the $WORKSPACE that is automatically mounted in the container (or [copy files from image to host|http://larstechnica.com/2017/05/docker-copy-files-from-image-to-local] first by running docker commands in a shell step . Brittle but gets the job done. ) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42851) secretVolume not created read only
Title: Message Title Carlos Sanchez commented on JENKINS-42851 Re: secretVolume not created read only something like the example k8s provides apiVersion: v1 kind: Pod metadata: name: mypod spec: containers: - name: maven image: maven:alpine volumeMounts: - name: foo mountPath: "/etc/foo" volumes: - name: foo secret: secretName: mysecret defaultMode: 256 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45916) Path is not getting set correctly in pipeline when there is a variable present
Title: Message Title
Michael Musenbrock edited a comment on JENKINS-45916
Re: Path is not getting set correctly in pipeline when there is a variable present
Hi, I'm not sure if this is was [~bbborro] was referencing:{code:java}pipeline {agent {docker {image 'alpine:latest'}}environment {PATHX = "${env.WORKSPACE}:${env.PATH}"PATH = "${env.WORKSPACE}:${env.PATH}"}stages {stage('Test') {steps {echo "PATH : ${env.PATH}"echo "PATHX: ${env.PATHX}"sh "printenv | grep PATH"}}}}{code}Which prints:{noformat}[Pipeline] echo PATH : / home jenkins_slave / catroid/jenkins_slave2_emulator/ workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games[Pipeline] echo PATHX: / home jenkins_slave / catroid/jenkins_slave2_emulator/ workspace/test:/ home jenkins_slave / catroid/jenkins_slave2_emulator/ workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games[Pipeline] sh[test] Running shell script+ printenv+ grep PATHPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binCLASSPATH=PATHX=/ home jenkins_slave / catroid/jenkins_slave2_emulator/ workspace/test:/ home jenkins_slave / catroid/jenkins_slave2_emulator/ workspace/test:/usr/local/bin:/usr/bin:/bin:/usr/games{noformat}So both variables are expanded correctly, but PATH is not passed to the environment of sh. Could also be a problem in the sh step.I'm also confused with the order of expansion: whether (in the environment stage) i put PATHX first or second, it seems that PATH gets always set first, because PATHX has the WORKSPACE variable content always prefixed twice
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42851) secretVolume not created read only
Title: Message Title Bill Warner commented on JENKINS-42851 Re: secretVolume not created read only Carlos Sanchez is there an example on how to get the defaultmode injected into the correct array index of the secret volume? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51486) Cannot upgrade to 2.123 version
Title: Message Title Leandro Fachinelli commented on JENKINS-51486 Re: Cannot upgrade to 2.123 version Thanks a lot ! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51486) Cannot upgrade to 2.123 version
Title: Message Title Leandro Fachinelli updated an issue Jenkins / JENKINS-51486 Cannot upgrade to 2.123 version Change By: Leandro Fachinelli Comment: How can I change the URL in auto update inside Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51286) container cap doesn't work correctly in kubernetes plugin
Title: Message Title Carlos Sanchez closed an issue as Duplicate Jenkins / JENKINS-51286 container cap doesn't work correctly in kubernetes plugin Change By: Carlos Sanchez Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50083) Integration Test for Quality Gate
Title: Message Title
Michaela Reitschuster edited a comment on JENKINS-50083
Re: Integration Test for Quality Gate
Ich habe für den Integrationstest für Qualitygate eine generische Lösung, nur habe ich Probleme den Build mit dem MavenModuleSet zu machen. Wenn Sobald ich build.getAction(ResultAction.{color:#cc7832}class{color}){color:#cc7832} {color:#33}aufrufe, ist keine verfügbar. Probeweise habe ich es mit getActions(Action.class) versucht, aber das hat mir leider keine weiteren Erkenntnisse gebracht. {color} {color} {color:#cc7832}{color:#33}Wissen Sie vielleicht wo mein Fehler liegt? {color}{color}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51486) Cannot upgrade to 2.123 version
Title: Message Title Leandro Fachinelli commented on JENKINS-51486 Re: Cannot upgrade to 2.123 version How can I change the URL in auto update inside Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum updated JENKINS-51483 Jenkins / JENKINS-51483 Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum started work on JENKINS-51483 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case commented on JENKINS-51485 Re: Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Getting the tooling to create a pull request wasn't that difficult after all... PR Created: https://github.com/jenkinsci/warnings-plugin/pull/128 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51489) Implement an essentials mode in the ATH
Title: Message Title Oleg Nenashev commented on JENKINS-51489 Re: Implement an essentials mode in the ATH Raul Arabaolaza FYI Custom WAR packager now produces BOM as output. So we can route it into runATH() and runPCT() if needed https://github.com/jenkins-infra/pipeline-library/blob/master/vars/essentialsTest.groovy#L15-L20 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-27488) gss.conf file not found
Title: Message Title Florian Schmaus assigned an issue to Unassigned Jenkins / JENKINS-27488 gss.conf file not found Change By: Florian Schmaus Assignee: Florian Schmaus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-16433) Jabber Plugin does not connect: stream:error conflict
Title: Message Title Florian Schmaus assigned an issue to Unassigned Jenkins / JENKINS-16433 Jabber Plugin does not connect: stream:error conflict Change By: Florian Schmaus Assignee: Florian Schmaus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51489) Implement an essentials mode in the ATH
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-51489 Implement an essentials mode in the ATH Issue Type: Task Assignee: Raul Arabaolaza Components: acceptance-test-harness Created: 2018-05-22 16:36 Labels: essentials Priority: Minor Reporter: Raul Arabaolaza After conversations with Jesse Glick and Oleg Nenashev regarding JENKINS-51306 we have agreed on that a good solution for ATH and PCT runs based on a BOM is to force a sane dependency graph in your BOM file. This graph should be enough to run the specified tests without any further plugin modification. In this situation makes sense to modify the ATH to have an "essentials mode" where WithPlugins just validates that the war file under tests is able to execute the test but it does not install/update or modify existing plugins in any way. If the validation fails, that is there is a requirement on a plugin not already installed or installed in a lower version than the one needed by the test, the test should fail or optionally be skipped with the proper reason
[JIRA] (JENKINS-51462) archiveArtifacts not working inside() docker containers
Title: Message Title Alexander Komarov commented on JENKINS-51462 Re: archiveArtifacts not working inside() docker containers Workaround is to copy files from image to host first by running docker commands in a shell step. Brittle but gets the job done. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50083) Integration Test for Quality Gate
Title: Message Title Michaela Reitschuster commented on JENKINS-50083 Re: Integration Test for Quality Gate Ich habe für den Integrationstest für Qualitygate eine generische Lösung, nur habe ich Probleme den Build mit dem MavenModuleSet zu machen. Wenn ich build.getAction(ResultAction.class) aufrufe, ist keine verfügbar. Probeweise habe ich es mit getActions(Action.class) versucht, aber das hat mir leider keine weiteren Erkenntnisse gebracht. Wissen Sie vielleicht wo mein Fehler liegt? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51488) ZIp step on jenkins slave duplicates full pah and fails
Title: Message Title Nico Navarrete created an issue Jenkins / JENKINS-51488 ZIp step on jenkins slave duplicates full pah and fails Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2018-05-22 16:30 Environment: Jenkins (docker) 2.107.3 docker ssh slave pipeline-utility-steps 2.1.0 Priority: Major Reporter: Nico Navarrete Building a zip works when running in "master" but when running in docker slave. it duplicates full path and fails // fails //def tmp = pwd tmp:true // works on slave def tmp = './@tmp' zip zipFile:"$tmp/file.zip" , archive:true, dir:"$dest/package/dist" java.nio.file.NoSuchFileException: /home/jenkins/workspace/Integration/accesoproveedor/home/jenkins/workspace/Integration/accesoproveedor@tmp/accesoproveedor-2017.0.4-abe2418.zip at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(UnixFileAttributeViews.java:218) at sun.nio.fs.UnixFileAttributeViews$Posix.readAttributes(UnixFileAttributeViews.java:131) at
[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Julien Lafourcade edited a comment on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 Hello, We have exactly the same behavior. I see hold builds which have a build.xml inthe folder. New build folders do not have build.xml. This only happens on build that are generated with jenkins DSL dans and the seed plugin. Anyone knows what may be the cause ? Thx Julien Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51251) Unable to login to Cisco Jabber Server (bad-request - modify)
Title: Message Title Florian Schmaus reopened an issue Re-opening, since technically, the issue still exists (while a confirmed workaround also exists). Jenkins / JENKINS-51251 Unable to login to Cisco Jabber Server (bad-request - modify) Change By: Florian Schmaus Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you 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-30314) Unable to connect using Jabber plugin (bad-request)
Title: Message Title Florian Schmaus closed an issue as Fixed Jenkins / JENKINS-30314 Unable to connect using Jabber plugin (bad-request) Change By: Florian Schmaus Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51484) Rename Job is failing when the job is in a folder
Title: Message Title Francisco Fernández updated JENKINS-51484 Jenkins / JENKINS-51484 Rename Job is failing when the job is in a folder Change By: Francisco Fernández Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50595) build history disappeared after upgrade to 2.107.1
Title: Message Title Julien Lafourcade commented on JENKINS-50595 Re: build history disappeared after upgrade to 2.107.1 Hello, We have exactly the same behavior. I see hold builds which have a build.xml inthe folder. New build folders do not have build.xml. This only happens on build that are generated with jenkins DSL dans the seed plugin. Anyone knows what may be the cause ? Thx Julien Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus created an issue Jenkins / JENKINS-51487 Update Smack to 4.3 Issue Type: Improvement Assignee: Florian Schmaus Components: jabber-plugin Created: 2018-05-22 16:15 Priority: Minor Reporter: Florian Schmaus Update Smack to 4.3.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43171) Correct Pom for build-monitor-plugin
Title: Message Title Stefan Verhoeff commented on JENKINS-43171 Re: Correct Pom for build-monitor-plugin We have the same issue, using the build-monitor-plugin as dependency with Gradle. It's reported to the project's GitHub project: https://github.com/jan-molak/jenkins-build-monitor-plugin/issues/373 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51486) Cannot upgrade to 2.123 version
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51486 Cannot upgrade to 2.123 version Change By: Oleg Nenashev Component/s: core Component/s: git-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51486) Cannot upgrade to 2.123 version
Title: Message Title Oleg Nenashev resolved as Duplicate Please see https://jenkins.io/changelog/#v2.123 . 2.123 release has been burned, please use 2.124. Jenkins / JENKINS-51486 Cannot upgrade to 2.123 version Change By: Oleg Nenashev Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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,
[JIRA] (JENKINS-2742) Allow 'nice' priority levels
Title: Message Title Clemens vm commented on JENKINS-2742 Re: Allow 'nice' priority levels Would be happy if exists Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51484) Rename Job is failing when the job is in a folder
Title: Message Title Francisco Fernández updated an issue Jenkins / JENKINS-51484 Rename Job is failing when the job is in a folder Change By: Francisco Fernández See [TopLevelItem.renameTo| https://github.com/jenkinsci/acceptance-test-harness/blob/2717edb1797bf13ed12c68639958794ef53a5267/src/main/java/org/jenkinsci/test/acceptance/po/TopLevelItem.java#L47 ] method. This method has been updated because of [JENKINS-22936|https://issues.jenkins-ci.org/browse/JENKINS-22936]. The href used [to locate the _Rename_ link|https://github.com/jenkinsci/acceptance-test-harness/blob/2717edb1797bf13ed12c68639958794ef53a5267/src/main/java/org/jenkinsci/test/acceptance/po/TopLevelItem.java#L57] is valid in general, but fails when the job is located in a folder. In those cases the href would be in the way of: /folder/job/name/confirm_rename Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-51486) Cannot upgrade to 2.123 version
Title: Message Title Leandro Fachinelli created an issue Jenkins / JENKINS-51486 Cannot upgrade to 2.123 version Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-05-22 15:53 Environment: Windows 2012 R2 Labels: upgrade jenkins.war Priority: Blocker Reporter: Leandro Fachinelli Hello, I'm trying to upgrade jenkins from 2.120 to 2.123 and I'm getting error below: java.io.FileNotFoundException: http://mirrors.jenkins-ci.org/war/2.123/jenkins.war I realised that jenkins.war is missing inside the folder 2.123 in mirror URL. Please fix asap. At, Leandro Add Comment
[JIRA] (JENKINS-51251) Unable to login to Cisco Jabber Server (bad-request - modify)
Title: Message Title Andrew Null closed an issue as Fixed Jenkins / JENKINS-51251 Unable to login to Cisco Jabber Server (bad-request - modify) Change By: Andrew Null Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza resolved as Not A Defect The problem is not on the ATH itself, and the root cause needs discussion about the way to be solved Jenkins / JENKINS-51306 ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Change By: Raul Arabaolaza Status: In Progress Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Oleg Nenashev Closing this as it seems not related to the ATH itself Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Raul Arabaolaza commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version Confirmed, with the following BOM all failures related to plugins not being installed are solved metadata: # labels and annotations are key: value string attributes labels: name: bom-it # Needed to make PCT happy groupId: org.jenkins-ci.main artifactId: jenkins-war version: 2.118-artifact-manager-s3-SNAPSHOT spec: core: version: 2.118 plugins: - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-api" version: 2.28-rc333.0675e9e9cb4c - groupId: "org.jenkins-ci.plugins" artifactId: "copyartifact" version: 1.40-rc298.60da56cfabea # Maven HPI Plugin improperly resolves dependency trees, needs upper bounds check - groupId: "org.jenkins-ci.plugins" artifactId: "structs" version: 1.14 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-step-api" version: 2.14 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-job" version: 2.21 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-basic-steps" version: 2.7 - groupId: "org.jenkins-ci.plugins.workflow" artifactId: "workflow-support" version: 2.18 - groupId: "org.jenkins-ci.plugins" artifactId: "junit" version: 1.24 - groupId: "org.jenkins-ci.plugins" artifactId: "mailer" version: 1.21 - groupId: "org.jenkins-ci.plugins" artifactId: "scm-api" version: 2.2.7 - groupId: "org.jenkins-ci.plugins" artifactId: "script-security" version: 1.44 - groupId: "org.jenkins-ci.plugins" artifactId: "aws-java-sdk" version: 1.11.264 - groupId: "org.jenkins-ci.plugins" artifactId: "apache-httpcomponents-client-4-api" version: 4.5.5-2.0 - groupId: "org.jenkins-ci.plugins" artifactId: "matrix-project" version: 1.7.1 - groupId: "org.jenkins-ci.plugins" artifactId: "jackson2-api" version: 2.8.11.2 - groupId: "org.jenkins-ci.plugins" artifactId: "display-url-api" version: 2.2.0 environments: - name: aws plugins: #TODO: BOM does not support FileSystem REFs, so somebody needs to add BOM auto-update logic here - groupId: "io.jenkins.plugins" artifactId: "artifact-manager-s3" version: 1.0-alpha-1-rc20.60688a35a736 Jesse Glick Made a very interesting (and right IMO) statement in a conversation if the plugin is bundled by the CWP, then by definition you do _not_ want to update it That means if any transitive one is on the wrong version, you should add explicitly on the right one. As a corollary from that (which I can agree also) in the end we are (IMO) going to need a tool to update/generate the BOM file automatically or maintaining it is going to be so impractical that nobody is going to do that, again Jesse Glick has pointed to
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-51485
Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Change By:
John Case
The following output (from [sass - lint| [ https://github.com/sasstools/sass-lint]) ] is not properly handled by the MSBuild parser: {code:java}dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0`{code} After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values"Currently, the regex only expects letters and numbers in that string, it does not match on hyphens.I think the regex should be expanded to handle hyphens (and underscores would be good too.)The change should be simple enough. Just modify the regex: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}with the following: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9\\-_]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}I'd be happy to make a pull request in the [github repo|https://github.com/jenkinsci/warnings-plugin] but it would take me a bit to get the tooling on my workstation to write a test.
Add Comment
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title
John Case updated an issue
Jenkins / JENKINS-51485
Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Change By:
John Case
The following output (from [sass lint|https://github.com/sasstools/sass-lint]) is not properly handled by the MSBuild parser: {code:java}dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0`{code} After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values"Currently, the regex only expects letters and numbers in that string, it does not match on hyphens.I think the regex should be expanded to handle hyphens (and underscores would be good too.)The change should be simple enough. Just modify the regex: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}with the following: {code:java}private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|"+ ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9\\-_]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?"+ "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";{code}I'd be happy to make a pull request in the [github repo|https://github.com/jenkinsci/warnings-plugin] but it would take me a bit to get the tooling on my workstation to write a test.
Add Comment
[JIRA] (JENKINS-51485) Warnings Plugin MSBuildParser does not handle hyphen or underscore in category
Title: Message Title John Case created an issue Jenkins / JENKINS-51485 Warnings Plugin MSBuildParser does not handle hyphen or underscore in category Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-05-22 15:34 Priority: Minor Reporter: John Case The following output (from [sass-lint|https://github.com/sasstools/sass-lint)] is not properly handled by the MSBuild parser: dist/search-list.component.scss(41,17): warning shorthand-values : Property `margin` should be written more concisely as `5px 0 0` instead of `5px 0 0 0` After fiddling around with it, I was able to figure out that it is failing on the category value "shorthand-values" Currently, the regex only expects letters and numbers in that string, it does not match on hyphens. I think the regex should be expanded to handle hyphens (and underscores would be good too.) The change should be simple enough. Just modify the regex: private static final String MS_BUILD_WARNING_PATTERN = "(?:^(?:.*)Command line warning ([A-Za-z0-9]+):\\s*(.*)\\s*\\[(.*)\\])|" + ANT_TASK + "(?:(?:\\s*\\d+>)?(?:(?:(?:(.*)\\((\\d*)(?:,(\\d+))?.*\\)|.*LINK)\\s*:|(.*):)\\s*([A-z-_]*\\s?(?:[Nn]ote|[Ii]nfo|[Ww]arning|(?:fatal\\s*)?[Ee]rror))\\s*:?\\s*([A-Za-z0-9]+)\\s*:\\s(?:\\s*([A-Za-z0-9.]+)\\s*:)?\\s*(.*?)(?: \\[([^\\]]*)[/][^\\]]+\\])?" + "|(.*)\\s*:.*error\\s*(LNK[0-9]+):\\s*(.*)))$";
[JIRA] (JENKINS-51377) High Thread contention around WorkflowRun
Title: Message Title Sam Van Oort commented on JENKINS-51377 Re: High Thread contention around WorkflowRun Taking this one on because I have a lot of in-progress for it, it turns out Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51377) High Thread contention around WorkflowRun
Title: Message Title Sam Van Oort assigned an issue to Sam Van Oort Jenkins / JENKINS-51377 High Thread contention around WorkflowRun Change By: Sam Van Oort Assignee: rsandell Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-40689) Java 10 compatibility
Title: Message Title Oleg Nenashev commented on JENKINS-40689 Re: Java 10 compatibility > Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole. That's correct. We will definitely change the version when really start working on that seriously. Stay tuned Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-32402) Credentials binding fails to find creds when using a Parameterized Expression, but only for timed jobs
Title: Message Title Maksym Kit commented on JENKINS-32402 Re: Credentials binding fails to find creds when using a Parameterized _expression_, but only for timed jobs I observe the same behavior. I have a Job A, which triggers Job B and passes an credentials ID using Jenkins Parameterized Trigger Plugin Predefined parameters. Job B project is parameterized and has Credentials Parameter specified. Job B also has "Use secret text(s) or file(s)" enabled (provided with Credentials Binding Plugin) and a corresponding binding specified. When I start Job A manually Job B will start correctly and have credentials resolved correctly, however when Job A is being triggered by GitHub push Job B will fail to resolve credentials. Sounds like a user error. Credentials parameters could not be used across jobs like this. Why? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title Kalle Niemitalo commented on JENKINS-45228 Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command In my case, git merge was run because of pull request discovery in a multibranch project using Bitbucket Branch Source. Perhaps that is why the environment variable in Jenkinsfile did not affect it. I have now disabled pull request discovery so that I won't have to kill processes on agents. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-40689) Java 10 compatibility
Title: Message Title Bruno Laturner commented on JENKINS-40689 Re: Java 10 compatibility > Java 9 is EoL, so I have renamed ticket to Java 10. It does not change the scope much. Java 11, ehm, may be fun Java 10 will also be EoL soon, in September 2018. On the other hand (Oracle's) Java 11 will be a 5-year Long Term Support version. 11 might be a better target version, instead of pursuing the current rabbit down the hole. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-51483
Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Change By:
Devin Nusbaum
Problem: If apache-httpcomponents-client-4-api is tested with a core dependency of 2.112 or higher it will fail with ClassNotFoundException for hudson.tools.JDKInstaller.In JENKINS-22367 I detached {{JDKInstaller}} from core into the jdk-tool plugin. At one point the work-in-progress jdk-tool build depended on apache-httpcomponents-client-4-api so that JDKInstaller could be updated to use httpcomponents-client version 4 instead of version 3, so I added an [entry to split-plugins.txt|https://github.com/jenkinsci/jenkins/blob/9966c5d479a7ef35b6e4171cf5f351121d66b097/core/src/main/resources/jenkins/split-plugin-cycles.txt#L14] to break the cycle between these plugins. Later, I decided to wait to refactor the httpcomponents-client code until the plugin was detached, and removed the dependency on apache-httpcomponents-client-4-api, but did not remove the entry in split-plugin-cycles.txt.In practice, this means that apache-httpcomponents-client-4-api does not have an implied dependency on jdk-tool even though it should. This is not an issue in standard usage of the plugin, but apache-httpcomponents-client-4-api has a (broken) test that uses JDKInstaller: [Client4JDKInstallerTest|https://github.com/jenkinsci/apache-httpcomponents-client-4-api-plugin/blob/master/src/test/java/org/jenkinsci/plugins/apachehttpclient4api/Client4JDKInstallerTest.java].This issue was discovered by testing the plugin using the PCT with a new core version. We can fix it by removing the split-plugin-cycles.txt entry.
Add Comment
[JIRA] (JENKINS-51484) Rename Job is failing when the job is in a folder
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-51484 Rename Job is failing when the job is in a folder Issue Type: Bug Assignee: Francisco Fernández Components: acceptance-test-harness Created: 2018-05-22 14:58 Priority: Minor Reporter: Francisco Fernández See [TopLevelItem.renameTo| https://github.com/jenkinsci/acceptance-test-harness/blob/2717edb1797bf13ed12c68639958794ef53a5267/src/main/java/org/jenkinsci/test/acceptance/po/TopLevelItem.java#L47 ] method. This method has been updated because of JENKINS-22936. The href used to locate the Rename link is valid in general, but fails when the job is located in a folder. In those cases the href would be in the way of: /folder/job/name/confirm_rename Add Comment
[JIRA] (JENKINS-51484) Rename Job is failing when the job is in a folder
Title: Message Title Francisco Fernández started work on JENKINS-51484 Change By: Francisco Fernández Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title
Kalle Niemitalo commented on JENKINS-45228
Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
I verified that the git-lfs process has GIT_ASKPASS=echo in its environment, even though my Jenkinsfile starts like this:
pipeline {
environment {
// Possible workaround for git-merge hanging in Jenkins
// due to repeated Git LFS credential prompts
GIT_ASKPASS = 'false'
}
So, I cannot use that as a workaround. These repeated credential retries are consuming about 80% CPU time of one hardware thread, too.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51467) Successful download from Artifactory but file not found
Title: Message Title Sion Williams commented on JENKINS-51467 Re: Successful download from Artifactory but file not found So, the issue was the missing slash in the download target path. Stupid on my part, but potentially should have been caught by the plugin? At a minimum this should be documented. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48776) Not able to trigger builds
Title: Message Title Mike Foley commented on JENKINS-48776 Re: Not able to trigger builds kgiloo - This appears to have been fixed in 2.0.18. I just checked and that is the version we are currently on and see that it is set to scan every 30 minutes. I think the other issue with Bitbucket Webhooks was also addressed, so everything seems to be working for us. Can you check on your end? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45228) Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
Title: Message Title
Kalle Niemitalo commented on JENKINS-45228
Re: Git merge requires authentication in LFS merges, plugin does not authenticate the git merge command
After "git merge" hangs like this and I abort the build via Jenkins, the git-lfs process keeps running on the Windows agent. IIRC, it keeps asking for credentials and running "git credential reject". I didn't check the environment variables of the processes but it seems freshEnv.put("GIT_ASKPASS", "echo"); in launchCommandIn, which is intended to prevent the build from hanging, isn't fulfilling its purpose. I wonder if it should do freshEnv.put("GIT_ASKPASS", "false"); instead; that might make the build at least fail cleanly. I should try changing my Jenkinsfiles to set that.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-51483) Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-51483 Erroneous entry in split-plugin-cycles.txt for jdk-tool and apache-httpcomponents-client-4-api Issue Type: Bug Assignee: Devin Nusbaum Components: core Created: 2018-05-22 14:19 Priority: Minor Reporter: Devin Nusbaum Problem: If apache-httpcomponents-client-4-api is tested with a core dependency of 2.112 or higher it will fail with ClassNotFoundException for hudson.tools.JDKInstaller. In JENKINS-22367 I detached JDKInstaller from core into the jdk-tool plugin. At one point jdk-tool depended on apache-httpcomponents-client-4-api so that JDKInstaller could be updated to use httpcomponents-client version 4 instead of version 3, so I added an entry to split-plugins.txt to break the cycle between these plugins. Later, I decided to wait to refactor the httpcomponents-client code until the plugin was detached, and removed the dependency on apache-httpcomponents-client-4-api, but did not remove the entry in split-plugin-cycles.txt. In practice, this means that apache-httpcomponents-client-4-api does not have an implied dependency on jdk-tool even though it should. This is not an issue in standard usage of the plugin, but apache-httpcomponents-client-4-api has a (broken) test that uses JDKInstaller: Client4JDKInstallerTest. This issue was discovered by testing the plugin using the PCT with a new core version. We can fix it by removing the split-plugin-cycles.txt entry.
[JIRA] (JENKINS-44342) Karaoke does not resume after "scroll to bottom"
Title: Message Title Josh McDonald commented on JENKINS-44342 Re: Karaoke does not resume after "scroll to bottom" Christian Ciach work on addressing these issues is currently in progress. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38662) Issue with Jenkins pipeline and java.nio.file.* methods
Title: Message Title Christoph Henrici edited a comment on JENKINS-38662 Re: Issue with Jenkins pipeline and java.nio.file.* methods [~jglick] Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software, resp Processes. And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline and are as such bound to a specific build, how does a humble Jenkins user share application spaning data? BTW: the "shared" the is also not bound to be read-only Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-39878) unclassified method java.io.File eachFileRecurse groovy.io.FileType
Title: Message Title Christoph Henrici edited a comment on JENKINS-39878 Re: unclassified method java.io.File eachFileRecurse groovy.io.FileType [~jglick] Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software , resp Processes . And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline and are as such bound to a specific build , now how does a humble Jenkins user share application spaning data? BTW: the "shared" the is also not bound to be read-only Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38662) Issue with Jenkins pipeline and java.nio.file.* methods
Title: Message Title Christoph Henrici edited a comment on JENKINS-38662 Re: Issue with Jenkins pipeline and java.nio.file.* methods [~jglick] Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software , resp Processes . And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline and are as such bound to a specific build , now how does a humble Jenkins user share application spaning data? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-38662) Issue with Jenkins pipeline and java.nio.file.* methods
Title: Message Title Christoph Henrici commented on JENKINS-38662 Re: Issue with Jenkins pipeline and java.nio.file.* methods Jesse Glick Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software. And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline, now does a humble Jenkins user share application spaning data? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-46067) Pipeline task scheduled on uninitialized node
Title: Message Title
Steve Ames commented on JENKINS-46067
Re: Pipeline task scheduled on uninitialized node
As a workaround, does anyone know how to setup the retry so that it will try to use a different node? I can setup some retries around functions executing on the node (e.g.) jenkinsObject.retry(3) { jenkinsObject.doTheThing() // Do a clever thing on this node } However I'm not sure how to setup a retry around a failed node. Infrastructure fails sometimes. Fact of life. I know there's gotta be a way to compensate for that so that my Jenkins jobs are a little more robust, but I'm not seeing it...
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-39878) unclassified method java.io.File eachFileRecurse groovy.io.FileType
Title: Message Title Christoph Henrici edited a comment on JENKINS-39878 Re: unclassified method java.io.File eachFileRecurse groovy.io.FileType [~jglick] Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software. And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline, now does a humble user share application spaning data? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-39878) unclassified method java.io.File eachFileRecurse groovy.io.FileType
Title: Message Title Christoph Henrici commented on JENKINS-39878 Re: unclassified method java.io.File eachFileRecurse groovy.io.FileType Why exactly? (Apart from the master / node problematic)? Jenkins is not alone in the world: Pipelines are bound to share data (files), which other Software. And since readFile and writeFile "only" is supported for files with in the workspace of a Pipeline, now does a humble user share application spaning data? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-42355) P4 checkout to survive restarts
Title: Message Title Sam Van Oort closed an issue as Incomplete Closing as incomplete since there's no "impossible" status Jenkins / JENKINS-42355 P4 checkout to survive restarts Change By: Sam Van Oort Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-49365) Resuming of pipelines vs. docker.image(...).inside(...)?
Title: Message Title Reinhold Füreder commented on JENKINS-49365 Re: Resuming of pipelines vs. docker.image(...).inside(...)? Absolutely! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49365) Resuming of pipelines vs. docker.image(...).inside(...)?
Title: Message Title Sam Van Oort commented on JENKINS-49365 Re: Resuming of pipelines vs. docker.image(...).inside(...)? Reinhold Füreder Any issue that can no longer be reproduced after apply updates is one I'll count as a win! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50962) set influxdb server from groovy
Title: Message Title Frederic Rousseau commented on JENKINS-50962 Re: set influxdb server from groovy I submitted PR https://github.com/jenkinsci/influxdb-plugin/pull/31 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50962) set influxdb server from groovy
Title: Message Title Frederic Rousseau assigned an issue to Frederic Rousseau Jenkins / JENKINS-50962 set influxdb server from groovy Change By: Frederic Rousseau Assignee: Aleksi Simell Frederic Rousseau Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-51306) ATH does not restart instance when withPlugin() requires newer dependency than the bundled version
Title: Message Title Jesse Glick commented on JENKINS-51306 Re: ATH does not restart instance when withPlugin() requires newer dependency than the bundled version This does not look like a bug to me—just an incorrect BOM. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-16703) Too many periodic requests to Crowd server
Title: Message Title Thomas Reith commented on JENKINS-16703 Re: Too many periodic requests to Crowd server Hello Arnaud, thx for your fix. It works like a charm. My crowd and jenkins were on very heavy load. Now it looks better Thomas Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-44358) the first time scm polling of a job after server restart always return "changes found"
Title: Message Title Lucas Nunes commented on JENKINS-44358 Re: the first time scm polling of a job after server restart always return "changes found" I was having the same problem, and using Makson Lee's workaround worked for me. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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.
