[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title An Tran commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax Jesse Glick From what I see in last comment int this ticket here https://issues.jenkins-ci.org/browse/JENKINS-53048?focusedCommentId=351304&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-351304 , Adam Carroll really wants to have an improvement instead of a bug report because the UI really on supports only declarative syntax of parallel command. If there is a bug, I would open a new one and keep this as 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56862) Provide support to claim failing test(s).
Title: Message Title Alokkumar Mahajan created an issue Jenkins / JENKINS-56862 Provide support to claim failing test(s). Issue Type: New Feature Assignee: jpiironen Components: robot-plugin Created: 2019-04-03 06:48 Priority: Minor Reporter: Alokkumar Mahajan I have request to claim failed tests from Robot Framework tests reports in addition to claiming the failed job. I can claim the failing job using claim plugin but right now there's no way if i want to claim failing test(s) from the Robot Framework Tests Report. i see this feature is available for Junit tests report as part of JUnit Plugin. Can we have this feature added as part of Robot Framework plugin as well? Add Comment
[JIRA] (JENKINS-56846) filesystem scm load stuck in jenkinfile-runner
Title: Message Title Evaristo Gutierrez commented on JENKINS-56846 Re: filesystem scm load stuck in jenkinfile-runner Can you please make a couple things and let me know the results? sh 'ls /workspace' inside the pipeline so that we can see the content of such folder the pipeline is able to view (before the shared library loading of course). FSSCM.checkout /workspace/my_shared_library to /tmp/jenkinsfileRunner.tmp/jfr2108196765485727374.run/workspace/job@libs/my I can still see only "my" at the end. Could you change the folder to something without the '_' character to validate that is not the issue? Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Summary: Unable to connect node to slave using ssh slave . Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh. Slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Labels: jenkins plugins regression slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Labels: jenkins regression slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Labels: 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian Labels: jenkins regression Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56861) Send PMD, FB, Checkstyle metrics to influxDB
Title: Message Title Somasekhar Korapati created an issue Jenkins / JENKINS-56861 Send PMD, FB, Checkstyle metrics to influxDB Issue Type: Improvement Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-04-03 04:49 Priority: Minor Reporter: Somasekhar Korapati It would be great to push static code analysis (PMD, Findbugs) metrics to influxDB. Currently I see that build, code coverage metrics pushed to influx but not other metrics part of my CI. If there is already available, pls let me know. Add Comment
[JIRA] (JENKINS-53694) Add event "Pull request review comments" to the webhook trigger
Title: Message Title Nitin Surana commented on JENKINS-53694 Re: Add event "Pull request review comments" to the webhook trigger Priyatham Tadikonda Jenkins Github Plugin is not responsible for merging your PR. If your PR is successful, you can either manually merge the PR or create a script that does so. Github can notify your script to merge through a Webhook attached to pull_request event. Your script can be hosted somewhere where it can receive the request from github webhook. https://developer.github.com/v3/activity/events/types/#pullrequestevent - Here is what the event payload can contain. https://developer.github.com/v3/pulls/#get-if-a-pull-request-has-been-merged - Here is how to check if a PR is merged. https://developer.github.com/webhooks/ - The `pull_request` event is triggered when a pull request is assigned, unassigned, labeled, unlabeled, opened, edited, closed, reopened, synchronize, ready_for_review , a pull request review is requested, or a review request is removed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56860) Rebuild plugin records incorrect "Started by user"
Title: Message Title Jason Stangroome updated an issue Jenkins / JENKINS-56860 Rebuild plugin records incorrect "Started by user" Change By: Jason Stangroome When rebuilding, the new build has the "Started by user" populated with the value from the source build, not the details of the user who requested the rebuild.I.e.: # User Alice triggers Build 1 # Build 1 completes and states "Started by user Alice". # User Bob opens Build 1 and clicks "Rebuild", triggering Build 2. # Build 2 completes and states "Started by user Alice" but should have stated "Started by user Bob".This creates confusion for accountability and auditing. Reverting to Rebuilder plugin 1.29 fixes the issue. Two other users have also reported the issue here on the PR for the release which introduced the bug:[https://github.com/jenkinsci/rebuild-plugin/pull/56#issuecomment-478868354] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56860) Rebuild plugin records incorrect "Started by user"
Title: Message Title Jason Stangroome created an issue Jenkins / JENKINS-56860 Rebuild plugin records incorrect "Started by user" Issue Type: Bug Assignee: ragesh_nair Components: rebuild-plugin Created: 2019-04-03 03:01 Environment: Jenkins v2.164.1 LTS on Ubuntu 14.04 Trusty w/ Rebuilder plugin v1.30 Labels: regression security Priority: Major Reporter: Jason Stangroome When rebuilding, the new build has the "Started by user" populated with the value from the source build, not the details of the user who requested the rebuild. I.e.: User Alice triggers Build 1 Build 1 completes and states "Started by user Alice". User Bob opens Build 1 and clicks "Rebuild", triggering Build 2. Build 2 completes and states "Started by user Alice" but should have stated "Started by user Bob". This creates confusion for accountability and auditing. Two other users have also reported the issue here on the PR for the release which introduced the bug: https://github.com/jenkinsci/rebuild-plugin/pull/56#issuecomment-478868354
[JIRA] (JENKINS-56859) I get 400 error While pushing Cucumber Report to slack from Jenkins
Title: Message Title
Ansar SN created an issue
Jenkins / JENKINS-56859
I get 400 error While pushing Cucumber Report to slack from Jenkins
Issue Type:
Task
Assignee:
Gareth Evans
Components:
cucumber-slack-notifier-plugin
Created:
2019-04-03 01:41
Priority:
Major
Reporter:
Ansar SN
Hello All, i was trying to send cucumber report generated in a Jenkins job to Slack. I have integrated cucumber slack notifier plugin https://wiki.jenkins.io/display/JENKINS/Cucumber+Slack+Notifier+Plugin. and followed the instructions. I am not using a pipeline. But a Jenkins job and configured the webhook in the global configurations as well. In the job configuration, as post-build action i have added Cucumber Slack notification and kept the channel name and the Cucumber.Json path as well. But i get 400 error. When i try sending the message to slack from my windows machine using this command, `curl -X POST -H "Content-type: application/json" --data "{\"text\":\"Hello world\"}" MY-WEBHOOK-URL`, the same message gets posted to slack. I am wondering why the Json payload is not being sent to slack channel. My jenkins also installed on Windows Could you give your valuable suggestions on this? I get below error ERROR: Build step failed with exception java.lang.RuntimeException: Received HTTP Status code [400] while posting to slack at org.jenkinsci.plugins.slacknotifier.SlackClient.postToSlack(SlackClient.java:62) at org.jenkinsci.plugins.slacknotifier.SlackClient.postToSlack(SlackClient.java:54) at org.jenkinsci.plugins.slacknotifier.SlackClient.postToSlack(SlackClient.java:41) at org.jenkinsci.plugins.slacknotifier.CucumberSlackService.sendCucumberReportToSlack(CucumberSlackService.java:33) at org.jenkinsci.plugins.slacknotifier.CucumberSlackPostBuildNotifier.perform(CucumberSlackPostBuildNotifier.java:67) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$Abstra
[JIRA] (JENKINS-56804) RSA Keys larger than 4096 bits do not work with ansible playbooks
Title: Message Title Troy Lea updated JENKINS-56804 Not an issue, user error (see comments) Jenkins / JENKINS-56804 RSA Keys larger than 4096 bits do not work with ansible playbooks Change By: Troy Lea 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56804) RSA Keys larger than 4096 bits do not work with ansible playbooks
Title: Message Title Troy Lea updated JENKINS-56804 There isn't a bug, I added a comment about this explaining my error. Jenkins / JENKINS-56804 RSA Keys larger than 4096 bits do not work with ansible playbooks Change By: Troy Lea 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56804) RSA Keys larger than 4096 bits do not work with ansible playbooks
Title: Message Title Troy Lea commented on JENKINS-56804 Re: RSA Keys larger than 4096 bits do not work with ansible playbooks I am embarrassed to say that this bug report I created is incorrect. The whole issue turned out to be how I copied the private key from my linux host and pasted it into the Jenkins credentials repository. I had "cat id_rsa", copied the output and pasted it into the credentials repository and this was the cause of all my problems. When I opened id_rsa in my text editor (geany) and copied it that way it correctly pasted it into the credentials repository and worked fine. It's really strange, because I did a test where I copied the entry from the credentials repository into the ssh581441855617245626.key example file above and it worked, so I assumed that the key was OK. But clearly the copy from the weird entry in credentials repository was fixed when I pasted it into a file. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48756) SMTP settings get lost after first email notification
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-48756 SMTP settings get lost after first email notification Change By: Alex Earl 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46485) Pre-send script not working in extemail step
Title: Message Title Alex Earl closed an issue as Not A Defect For pipeline, you should use run instead of build in presendScripts. Jenkins / JENKINS-46485 Pre-send script not working in extemail step Change By: Alex Earl 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title
Satoshi Goto updated an issue
Jenkins / JENKINS-56854
ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Change By:
Satoshi Goto
h3. Problem Abstractenv GIT_COMMIT is not always same the real git revision in particular situation.Before pipeline stage begin, two merge commits generated by plugins.It is the reason why the revision doesn't match GIT_COMMIT. GIT_COMMIT, SHA of the current, is defined by [Git Plugin|https://wiki.jenkins.io/display/JENKINS/Git+Plugin].h3. Problem DetailI use [GitHub Branch Source Plugin|https://plugins.jenkins.io/github-branch-source] to run Pull Request job with Jenkinsfile.My job use Jenkinsfile in my github repository.I found GIT_COMMIT is sometime different from real git revision in the stage of Pipeline. When the problem happen, Jenkisn build logs says it causes git merge twice.First merge is to read Jenkinsfile from git, second merge is to setup working directory.So I print the revision in my Pipeline script.env.GIT_COMMIT = 75ddc1933fd10b87c529536e3107ea7313debaea HEAD revision = a98b709283bd47d251dfcc9360b91ffc024af16bGIT_COMMIT is the revision at first merge, and HEAD is the revision at second merge.h3. How to reproduce this problemI test with minimum condition which can reproduce the problem by using it↓[https://github.com/mtgto/jenkins-pipeline-test/blob/prtest/Jenkinsfile][https://github.com/mtgto/jenkins-pipeline-test/pull/1] The problem is only happened below all conditions matched: # The job is Multibranch job. # The job uses pipeline with Jenkinsfile in git repository. # The pull request can't merge fast-forward. # Twice Two merge commits is away at least one second.1, 2: The condition to generate twice merge commits.3: Fast-forward merge doesn't change the revision by time.4: Git object contains time, it is changed by the second. Same time merge commits always have same revisions.h4. EnvironmentsI use Jenkins 2.164.1 in Docker container to reproduce this problem. {noformat}$ docker run -d --name jenkins -p 8080:8080 --name jenkins -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts-alpine{noformat} I install two plugins while first setup: * [GitHub Branch Source|https://plugins.jenkins.io/github-branch-source] * [Pipeline|https://plugins.jenkins.io/workflow-aggregator] h5. Installed Plugins * Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 * Authentication Tokens API Plugin - 1.3 * bouncycastle API Plugin - 2.17 * Branch API Plugin - 2.2.0 * Command Agent Launcher Plugin - 1.3 * Credentials Binding Plugin - 1.18 * Credentials Plugin - 2.1.18 * Display URL API - 2.3.1 * Docker Commons Plugin - 1.13 * Docker Pipeline - 1.17 * Durable Task Plugin - 1.29 * Folders Plugin - 6.7 * Git client plugin - 2.7.6 * Git plugin - 3.9.3 * GIT server Plugin - 1.7 * GitHub API Plugin - 1.95 * GitHub Branch Source Plugin - 2.4.5 * GitHub plugin - 1.29.4 * Jackson 2 API Plugin - 2.9.8 * _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 * _javascript_ GUI Lib: Handlebars bundle plugin
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title
Satoshi Goto updated an issue
Jenkins / JENKINS-56854
ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Change By:
Satoshi Goto
h3. Problem Abstractenv GIT_COMMIT is not always same the real git revision in particular situation. Before pipeline stage begin, two merge commits generated by plugins.It is the reason why the revision doesn't match GIT_COMMIT . GIT_COMMIT , SHA of the current, is defined by [Git Plugin|https://wiki.jenkins.io/display/JENKINS/Git+Plugin].h3. Problem DetailI use [GitHub Branch Source Plugin|https://plugins.jenkins.io/github-branch-source] to run Pull Request job with Jenkinsfile.My job use Jenkinsfile in my github repository.I found GIT_COMMIT is sometime different from real git revision in the stage of Pipeline. When the problem happen, Jenkisn build logs says it causes git merge twice.First merge is to read Jenkinsfile from git, second merge is to setup working directory.So I print the revision in my Pipeline script.env.GIT_COMMIT = 75ddc1933fd10b87c529536e3107ea7313debaea HEAD revision = a98b709283bd47d251dfcc9360b91ffc024af16bGIT_COMMIT is the revision at first merge, and HEAD is the revision at second merge.h3. How to reproduce this problemI test with minimum condition which can reproduce the problem by using it↓[https://github.com/mtgto/jenkins-pipeline-test/blob/prtest/Jenkinsfile][https://github.com/mtgto/jenkins-pipeline-test/pull/1] The problem is only happened below all conditions matched: # The job is Multibranch job. # The job uses pipeline by with Jenkinsfile in git repository. # The pull request can't merge fast-forward. # Twice merge commits is away at least one second.1, 2: The condition to generate twice merge commits.3: Fast-forward merge doesn't change the revision by current time.4: Git object contains time, it is by the second. Same time merge commits always have same revisions.h4. EnvironmentsI use Jenkins 2.164.1 in Docker container to reproduce this problem . {noformat}$ docker run -d --name jenkins -p 8080:8080 --name jenkins -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts-alpine{noformat} h5. Installed Plugins * Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 * Authentication Tokens API Plugin - 1.3 * bouncycastle API Plugin - 2.17 * Branch API Plugin - 2.2.0 * Command Agent Launcher Plugin - 1.3 * Credentials Binding Plugin - 1.18 * Credentials Plugin - 2.1.18 * Display URL API - 2.3.1 * Docker Commons Plugin - 1.13 * Docker Pipeline - 1.17 * Durable Task Plugin - 1.29 * Folders Plugin - 6.7 * Git client plugin - 2.7.6 * Git plugin - 3.9.3 * GIT server Plugin - 1.7 * GitHub API Plugin - 1.95 * GitHub Branch Source Plugin - 2.4.5 * GitHub plugin - 1.29.4 * Jackson 2 API Plugin - 2.9.8 * _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 * _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 * _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 * _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 * JDK Tool Plugin - 1.2 * JSch
[JIRA] (JENKINS-49056) Pipeline Support for Ansible Adhoc Commands
Title: Message Title Michael Cresswell assigned an issue to Unassigned Jenkins / JENKINS-49056 Pipeline Support for Ansible Adhoc Commands Change By: Michael Cresswell Assignee: Michael Cresswell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-49056) Pipeline Support for Ansible Adhoc Commands
Title: Message Title Michael Cresswell commented on JENKINS-49056 Re: Pipeline Support for Ansible Adhoc Commands Sorry sai sendil but I haven't used this plugin or Ansible in a year. You're welcome to take a look at what I was working on previously. It's in Github at https://github.com/michaelcresswell/ansible-plugin/commits/JENKINS-49056. Maybe it will be helpful in getting this feature implemented. Emilio Escobar may be able to to help get a completed feature deployed if you make it that 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title
Yufen Kuo updated an issue
Jenkins / JENKINS-56858
unable to load plugins
Change By:
Yufen Kuo
followed the steps from [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md] # git clone [https://github.com/jenkinsci/jenkinsfile-runner.git] # run the mvn package command # cd /local/test/jenkins # {{wget [http://mirrors.jenkins.io/war-stable/latest/jenkins.war]}} # {{unzip jenkins.war -d /local/test/jenkins/jenkins_home}} # {{export JENKINS_HOME=/local/test/jenkins/jenkins_home}} # {{ {{ run java -jar jenkins.war to install suggested plugins}} }}# create Jenkinsfile # /local/test/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -w /local/test/jenkins -p /local/test/jenkins/jenkins_home/plugins -f /local/test/jenkins/foo -a "param1=Test¶m2=MyTest" {{}} {{}} Then you will get messages like below, although my jenkins version is 2.164.1 and not 2.89. see the attached out file for the complete output {{1.436 [id=55] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api)}}{{java.io.IOException: Pipeline: Step API v2.19 failed to load.}} \ {{ - You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.}} \ {{ at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)}} \ {{ at hudson.PluginManager$2$1$1.run(PluginManager.java:513)}} \ {{ at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)}} \ {{ at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)}} \ {{ at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065)}} \ {{ at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)}} \ {{ at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)}} \ {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} \ {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} \ {{ at java.lang.Thread.run(Thread.java:748)}}{{ 1.439 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api)}}{{java.io.IOException: Pipeline: API v2.33 failed to load.{ { }}} }
Add Comment
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title
Yufen Kuo updated an issue
Jenkins / JENKINS-56858
unable to load plugins
Change By:
Yufen Kuo
followed the steps from [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md] # git clone [https://github.com/jenkinsci/jenkinsfile-runner.git] # run the mvn package command # cd /local/test/jenkins # {{wget [http://mirrors.jenkins.io/war-stable/latest/jenkins.war]}} # {{unzip jenkins.war -d /local/test/jenkins/jenkins_home}} # {{export JENKINS_HOME=/local/test/jenkins/jenkins_home}} # {{ {{ run java -jar jenkins.war to install suggested plugins}} }}# create Jenkinsfile # /local/test/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -w /local/test/jenkins -p /local/test/jenkins/jenkins_home/plugins -f /local/test/jenkins/foo -a "param1=Test¶m2=MyTest" {{}} {{}} Then you will get messages like below, although my jenkins version is 2.164.1 and not 2.89. see the attached out file for the complete output {{1.436 [id=55] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api)}}{{java.io.IOException: Pipeline: Step API v2.19 failed to load.}} \ {{ - You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.}} \ {{ at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)}} \ {{ at hudson.PluginManager$2$1$1.run(PluginManager.java:513)}} \ {{ at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)}} \ {{ at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)}} \ {{ at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065)}} \ {{ at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)}} \ {{ at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)}} \ {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} \ {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} \ {{ at java.lang.Thread.run(Thread.java:748)}}{{ 1.439 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api)}}{{java.io.IOException: Pipeline: API v2.33 failed to load.{ { }}} }
Add Comment
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo updated an issue Jenkins / JENKINS-56858 unable to load plugins Change By: Yufen Kuo Attachment: out Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56724) Add unit tests for DeltaReport
Title: Message Title Andreas Pabst started work on JENKINS-56724 Change By: Andreas Pabst Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo created an issue Jenkins / JENKINS-56858 unable to load plugins Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-04-02 22:46 Environment: jenkins version 2.164.1 Priority: Major Reporter: Yufen Kuo followed the steps from https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md git clone https://github.com/jenkinsci/jenkinsfile-runner.git run the mvn package command cd /local/test/jenkins wget http://mirrors.jenkins.io/war-stable/latest/jenkins.war unzip jenkins.war -d /local/test/jenkins/jenkins_home export JENKINS_HOME=/local/test/jenkins/jenkins_home
[JIRA] (JENKINS-56792) Create additional constructor in Issue (TreeString)
Title: Message Title Nils Engelbrecht commented on JENKINS-56792 Re: Create additional constructor in Issue (TreeString) Ok thank you - I’ll do that. My bad! You’re right: the fileName was already of type TreeString before. I guess the test fails because I changed the type of the parameter of the setter for fileName and removed the logic of normalization. Might that be the reason? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42348) Jelly file was not found in email-ext v. 2.57
Title: Message Title Alex Earl closed an issue as Not A Defect Jenkins / JENKINS-42348 Jelly file was not found in email-ext v. 2.57 Change By: Alex Earl 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56792) Create additional constructor in Issue (TreeString)
Title: Message Title Ulli Hafner commented on JENKINS-56792 Re: Create additional constructor in Issue (TreeString) Am I allowed to delete test cases such as IssueTest#testFileNameBackslashConversion (therefore of course I would create a new one in the IssueBuilderTest class) ? Yes, just move the tests to the IssueBuilder class. Another question I got is how to cope with failure of the test case IssueTest#shouldReadIssueFromOldSerialization ? I assume this is due to the type-change of fileName from String to TreeString. Hmm, does the serialization change? The type changed only in the constructor, but the field still is TreeString. Or do I miss something? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56857) Unable to add Jira site in jenkins
Title: Message Title Bunty Reddy created an issue Jenkins / JENKINS-56857 Unable to add Jira site in jenkins Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-04-02 21:36 Environment: Jenkins ver. 2.150.2, Jira Version - 7.12.3, JIRA Plugin version in Jenkins -3.0.6, Jenkins Add-on version in Jira - 3.8.0-DC Labels: jira Priority: Blocker Reporter: Bunty Reddy After adding the Jira URL, validate settings shows below error: java.lang.NullPointerException at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:1179) 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) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispat
[JIRA] (JENKINS-56792) Create additional constructor in Issue (TreeString)
Title: Message Title Nils Engelbrecht commented on JENKINS-56792 Re: Create additional constructor in Issue (TreeString) I understand. Sounds good to me! After reworking this for the fileName parameter about 8 test cases are failing. Am I allowed to delete test cases such as IssueTest#testFileNameBackslashConversion (therefore of course I would create a new one in the IssueBuilderTest class) ? Another question I got is how to cope with failure of the test case IssueTest#shouldReadIssueFromOldSerialization ? I assume this is due to the type-change of fileName from String to TreeString. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56720) Add unit tests for GitChecker
Title: Message Title Ulli Hafner updated JENKINS-56720 Jenkins / JENKINS-56720 Add unit tests for GitChecker Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56846) filesystem scm load stuck in jenkinfile-runner
Title: Message Title
Shurik Gefter commented on JENKINS-56846
Re: filesystem scm load stuck in jenkinfile-runner
Hi Evaristo, You are right, I change the message only in this ticket. I align the example
pipeline {
agent any
options { skipDefaultCheckout() }
stages {
stage('Load Library') {
steps {
library identifier: 'my@master',
retriever: legacySCM(
filesystem(clearWorkspace: true, copyHidden: false, path: "/workspace/my_shared_library"))
}
}
stage('Test') {
steps {
my_method param1: "aaa"
}
}
}
}
I run it via docker command
docker run --rm -v /users/shurik/jira_workspace:/workspace shurikg/jenkinsfile-runner
The output
16.932 [id=25]WARNING i.j.p.c.i.s.VaultSecretSource#getCommaSeparatedVariables: [Deprecation Warning] CASC_VAULT_PATH will be deprecated. Please use CASC_VAULT_PATHS instead.
Started
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /tmp/jenkinsfileRunner.tmp/jfr2108196765485727374.run/workspace/job
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Load Library)
[Pipeline] library
Loading library my@master
FSSCM.checkout /workspace/my_shared_library to /tmp/jenkinsfileRunner.tmp/jfr2108196765485727374.run/workspace/job@libs/my
FSSCM.clearWorkspace...
My jira_workspace folder contains
jira_workspace/my_shared_library/vars
jira_workspace/my_shared_library/vars/my_method.groovy
jira_workspace/Jenkinsfile
Please note, when I run with the same pipe and workspace via cli runner (not docker), it's working ok.
[JIRA] (JENKINS-56625) Too many open file descriptors from embedded build status usage
Title: Message Title Adam BH commented on JENKINS-56625 Re: Too many open file descriptors from embedded build status usage This has become higher priority for us so I made the fix required and tested a SNAPSHOT hpi https://github.com/jenkinsci/embeddable-build-status-plugin/pull/42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Gavin Mogan commented on JENKINS-56773 Re: High master CPU usage introduced by Blue Ocean 1.14.0 So had a bit of a chat with keith (original executor plugin author) and it was never really designed for more than a proof of concept on how to write a BlueOcean plugin. We are pretty sure its caused by https://github.com/jenkinsci/blueocean-plugin/blob/e2dd04dcb3015063a2e31c8d37c90ee5c1ef4d98/blueocean-executor-info/src/main/js/ExecutorInfoService.js#L14 (which will grab executor info every time any pipeline does work) So Plans: I think the plan is going to be to drop making the executor plugin as a requirement, it'll have to be manually installed again (Sorry Craig) Put a throttle on the lookup so it doesn't call nearly as often. Since there is a work around in place until the next release, and I personally have a few pressing issues to deal with first, i'm going to leave it unassigned, but we'll get it fixed before we do the next 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49056) Pipeline Support for Ansible Adhoc Commands
Title: Message Title sai sendil commented on JENKINS-49056 Re: Pipeline Support for Ansible Adhoc Commands I'm trying to invoke the ansible adhoc command from a declarative pipeline, is this issue a WIP item? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55405) org.apache.commons.jelly.JellyTagException:
Title: Message Title Moazzam Naim edited a comment on JENKINS-55405 Re: org.apache.commons.jelly.JellyTagException: I am also getting below Exception when tried to access Failed Tests from the Test Results Analyzer report. I can successfully access the Passed Tests from this report. Exception error occurs only when tried to access Failed Tests. Please see the attached file for the full dump of Exception message. My Jenkins version is 2.121.1 and have Test Results Analyzer plugin installed along with TestNg and Extent Reports plugins. org.apache.commons.jelly.JellyTagException: jar: [ file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/layout.jelly:267:25: |file:///C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/layout.jelly:267:25:] org.apache.commons.jelly.JellyTagException: jar: [ file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/main-panel.jelly:36:21: |file:///C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/main-panel.jelly:36:21:] org.apache.commons.jelly.JellyTagException: Cannot get property 'escapeExceptionMsg' on null object Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55405) org.apache.commons.jelly.JellyTagException:
Title: Message Title Moazzam Naim updated an issue Jenkins / JENKINS-55405 org.apache.commons.jelly.JellyTagException: Change By: Moazzam Naim Environment: Jenkins ver. 2.150.1WIN 10Testlink plugin 3.15 c Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55405) org.apache.commons.jelly.JellyTagException:
Title: Message Title Moazzam Naim commented on JENKINS-55405 Re: org.apache.commons.jelly.JellyTagException: I am also getting below Exception when tried to access Failed Tests from the Test Results Analyzer report. I can successfully access the Passed Tests from this report. Exception error occurs only when tried to access Failed Tests. Please see the attached file for the full dump of Exception message. org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/layout.jelly:267:25: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/war/WEB-INF/lib/jenkins-core-2.121.1.jar!/lib/layout/main-panel.jelly:36:21: org.apache.commons.jelly.JellyTagException: Cannot get property 'escapeExceptionMsg' on null object Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-55405) org.apache.commons.jelly.JellyTagException:
Title: Message Title Moazzam Naim updated an issue Jenkins / JENKINS-55405 org.apache.commons.jelly.JellyTagException: Change By: Moazzam Naim Attachment: Jenkins-JellyTagException.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title
frederic larde commented on JENKINS-56772
Re: Git branch with slashes are double encoded (Jenkins core and blue ocean)
Doesn't work in both case. In core: in the GIT repo ("job/ice" url - "ice" is the name of my repo), all links of branches are double encoded => 404 In blueocean : Links work, but AJAX calls failed (so we have an empty screen)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-56214) PHP CodeSniffer errors treated as warnings
Title: Message Title Ulli Hafner commented on JENKINS-56214 Re: PHP CodeSniffer errors treated as warnings See https://github.com/jenkinsci/analysis-model/pull/142 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56214) PHP CodeSniffer errors treated as warnings
Title: Message Title Ulli Hafner updated JENKINS-56214 Jenkins / JENKINS-56214 PHP CodeSniffer errors treated as warnings Change By: Ulli Hafner Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56674) In case of execute withDockerContainer inside withDockerCotainer env variables is not masked
Title: Message Title Devin Nusbaum updated JENKINS-56674 A fix for this issue was release in version 1.18 of the Docker Pipeline plugin. See the release notes on the plugin's wiki page for details. Jenkins / JENKINS-56674 In case of execute withDockerContainer inside withDockerCotainer env variables is not masked Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: docker-workflow 1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-46105) Docker 17.05 ARG in FROM breaks docker inspect
Title: Message Title Devin Nusbaum updated JENKINS-46105 The lingering issue with ARGs that specified a default value was fixed in version 1.18 of the Docker Pipeline plugin. See the release notes on the plugin's wiki page for details. Jenkins / JENKINS-46105 Docker 17.05 ARG in FROM breaks docker inspect Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: docker-workflow 1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.c
[JIRA] (JENKINS-48437) Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId
Title: Message Title Devin Nusbaum updated JENKINS-48437 A fix for this issue was just released in version 1.18 of the Docker Pipeline plugin. See the release notes on the plugin's wiki page for details. Jenkins / JENKINS-48437 Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: docker-workflow 1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.goo
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title Gavin Mogan commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) so works in classic, fails in blueocean? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56856) Setup wizards handles password field wrong
Title: Message Title Gavin Mogan started work on JENKINS-56856 Change By: Gavin Mogan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45489) checkout(scm) step can return wrong variables when used following another Git checkout
Title: Message Title Mark Wright commented on JENKINS-45489 Re: checkout(scm) step can return wrong variables when used following another Git checkout Richard Bowater, on (Windows) build-server, we use the following in our scripts as Mark Waite suggests: def sha = bat(returnStdout: true, script: '@git rev-parse HEAD').trim() Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56856) Setup wizards handles password field wrong
Title: Message Title Gavin Mogan commented on JENKINS-56856 Re: Setup wizards handles password field wrong https://github.com/jenkinsci/jenkins/pull/3960 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56681) Malware process kintegrityds run by Jenkins user
Title: Message Title Daniel Beck closed an issue as Not A Defect This does not demonstrate a bug in Jenkins. There could be any number of causes for this, most notably: Running outdated plugins with known security vulnerabilities Having a permission setup that allows strangers to perform administrative actions, possibly after logging in to GitHub/Google, or signing up with a new account. If you are interested in determining the root cause, please ask for assistance in #jenkins on Freenode IRC, in Gitter, or on the jenkinsci-users mailing list. Jenkins / JENKINS-56681 Malware process kintegrityds run by Jenkins user 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)
[JIRA] (JENKINS-56761) Debug Output Hidden
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-56761 Debug Output Hidden Change By: Daniel Beck Component/s: powershell-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56856) Setup wizards handles password field wrong
Title: Message Title Gavin Mogan commented on JENKINS-56856 Re: Setup wizards handles password field wrong Did some quick investigation and found out that while all the other fields were escaped, the large json blob was not, so jetty didn't know how to handled the non escaped data. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56852) Regression: Can't invoke function with optional arguments twice
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-56852 Regression: Can't invoke function with optional arguments twice Change By: Daniel Beck Component/s: pipeline Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56856) Setup wizards handles password field wrong
Title: Message Title Gavin Mogan assigned an issue to Gavin Mogan Jenkins / JENKINS-56856 Setup wizards handles password field wrong Change By: Gavin Mogan Assignee: Gavin Mogan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56856) Setup wizards handles password field wrong
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-56856 Setup wizards handles password field wrong Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-04-02 18:01 Labels: setup-wizard Priority: Minor Reporter: Daniel Beck From https://twitter.com/scy/status/1112663270341644289 it looks like Jenkins setup wizard does not properly escape some form fields and processes them as code ( ? ). Add Comment
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title
jernej goricki commented on JENKINS-36568
Re: workflow script node step cannot trigger build on specific node
Ok to answer my own question... In my case I only needed a regular string parameter and then pass it into the node block like:
...
string(defaultValue: '', description: 'select node', name: 'node')
...
node(params.node) {}
I'm sure I tried this before and it didn't work, so I thought I need to use the node/label plugin :/
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54997) Deprecated calls to Run.getLogFile
Title: Message Title Alex Earl updated JENKINS-54997 Fixed in https://github.com/jenkinsci/email-ext-plugin/commit/21fbd402665848a18205b26751424149e51e86e4 Jenkins / JENKINS-54997 Deprecated calls to Run.getLogFile Change By: Alex Earl Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21942) Unreliable defaulting of Jenkins.workspaceDir
Title: Message Title David Moles commented on JENKINS-21942 Re: Unreliable defaulting of Jenkins.workspaceDir I'm seeing the same, in a Docker image configured with JCasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56704) Add unit test for ToolsTrendChart that requites the same color twice
Title: Message Title Tanja Roithmeier started work on JENKINS-56704 Change By: Tanja Roithmeier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56259) Allow input timeout parameter
Title: Message Title Jesse Glick commented on JENKINS-56259 Re: Allow input timeout parameter Mark Vinkx this is about input as part of a stage rather than one of its steps, which has different behavior (if I understand correctly) with respect to when an executor is locked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56701) Use RegexpLineParser for GnuFortranParser
Title: Message Title Sebastian Heunke assigned an issue to Sebastian Heunke Jenkins / JENKINS-56701 Use RegexpLineParser for GnuFortranParser Change By: Sebastian Heunke Assignee: Sebastian Heunke Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56700) Use RegexpLineParser for GhsMultiParser
Title: Message Title Sebastian Heunke assigned an issue to Sebastian Heunke Jenkins / JENKINS-56700 Use RegexpLineParser for GhsMultiParser Change By: Sebastian Heunke Assignee: Sebastian Heunke Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56700) Use RegexpLineParser for GhsMultiParser
Title: Message Title Sebastian Heunke assigned an issue to Sebastian Heunke Jenkins / JENKINS-56700 Use RegexpLineParser for GhsMultiParser Change By: Sebastian Heunke Assignee: Sebastian Heunke Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56844) timeout error not propagated when sh step with returnStatus not finished
Title: Message Title
Pablo Carballo updated an issue
Jenkins / JENKINS-56844
timeout error not propagated when sh step with returnStatus not finished
Change By:
Pablo Carballo
When a long running sh step with returnStatus is running, timeout error is not propagated.Steps to reproduce:1. Having this pipeline, I expect *echo 'Continue ...'* to never be executed because the internal sh step takes more than the timeout.{noformat}node {stage('stage 1') { test() echo 'Continue working after timeout'}}def test() {timeout(time: 10, unit: 'SECONDS') {echo 'working ...'sh script: 'sleep 15'//, returnStatus: true}}{noformat}And that works. 2. If the same pipeline is executed removing the commented code comment , with enabling *returnStatus: true*, the interrupt signal is sent but the Pipeline continues and *echo ' Continue working after timeout'* is executed finishing with status SUCCESS.Here is the log:{noformat}Timeout set to expire in 10 sec[Pipeline] {[Pipeline] echoworking ...[Pipeline] sh[test-pipeline] Running shell script+ sleep 15Sending interrupt signal to processCancelling nested steps due to timeoutTerminated[Pipeline] }[Pipeline] // timeout[Pipeline] echoContinue working after timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56844) timeout error not propagated when sh step with returnStatus not finished
Title: Message Title
Pablo Carballo updated an issue
Jenkins / JENKINS-56844
timeout error not propagated when sh step with returnStatus not finished
Change By:
Pablo Carballo
When a long running sh step with returnStatus is running, timeout error is not propagated.Steps to reproduce:1. Having this pipeline, I expect *echo 'Continue ...'* to never be executed because the internal sh step takes more than the timeout.{noformat}node {stage('stage 1') { test() echo 'Continue working after timeout'}}def test() {timeout(time: 10, unit: 'SECONDS') { while (true) { echo 'working ...'sh script: 'sleep 15'//, returnStatus: true break }} } {noformat}And that works. 2. If the same pipeline is executed removing the commented code, with *returnStatus: true*, the interrupt signal is sent but the Pipeline continues and *echo 'working after timeout'* is executed finishing with status SUCCESS.Here is the log:{noformat}Timeout set to expire in 10 sec[Pipeline] {[Pipeline] echoworking ...[Pipeline] sh[test-pipeline] Running shell script+ sleep 15Sending interrupt signal to processCancelling nested steps due to timeoutTerminated[Pipeline] }[Pipeline] // timeout[Pipeline] echoContinue working after timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56844) timeout error not propagated when sh step with returnStatus not finished
Title: Message Title
Pablo Carballo updated an issue
Jenkins / JENKINS-56844
timeout error not propagated when sh step with returnStatus not finished
Change By:
Pablo Carballo
When a long running sh step with ruturnStatus returnStatus is running, timeout error is not propagated.Steps to reproduce:1. Having this pipeline, I expect *echo 'Continue ...'* to never be executed because the internal sh step takes more than the timeout.{noformat}node {stage('stage 1') { test() echo 'Continue working after timeout'}}def test() {timeout(time: 10, unit: 'SECONDS') {while (true) {echo 'working ...'sh script: 'sleep 15'//, returnStatus: true break}}}{noformat}And that works. 2. If the same pipeline is executed removing the commented code, with *returnStatus: true*, the interrupt signal is sent but the Pipeline continues and *echo 'working after timeout'* is executed finishing with status SUCCESS.Here is the log:{noformat}Timeout set to expire in 10 sec[Pipeline] {[Pipeline] echoworking ...[Pipeline] sh[test-pipeline] Running shell script+ sleep 15Sending interrupt signal to processCancelling nested steps due to timeoutTerminated[Pipeline] }[Pipeline] // timeout[Pipeline] echoContinue working after timeout[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: SUCCESS{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-36568) workflow script node step cannot trigger build on specific node
Title: Message Title jernej goricki commented on JENKINS-36568 Re: workflow script node step cannot trigger build on specific node Hi guys, Install Node and Label parameter plugin In test_job's configuration, select 'This build is parameterized' and add a Label parameter and set the parameter name to 'node' In pipeline script, use Cuong Tran's code: What if I would like to do step 2 in a parameterized scripted pipeline itself ? But I do not know how to define the label parameter. I tried the following: properties([[$class : 'RebuildSettings', autoRebuild: false, rebuildDisabled: false], parameters([org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterDefinition(name: 'node')])]) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56259) Allow input timeout parameter
Title: Message Title
Mark Vinkx commented on JENKINS-56259
Re: Allow input timeout parameter
You simply can wrap the input in a timeout
stages {
stage('Deploy') {
steps {
timeout(time: 5, unit: "MINUTES") {
input message: 'Do you want to approve the deploy?', ok: 'Yes'
}
sh './flakey-deploy.sh'
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-56214) PHP CodeSniffer errors treated as warnings
Title: Message Title Tanja Roithmeier updated JENKINS-56214 Jenkins / JENKINS-56214 PHP CodeSniffer errors treated as warnings Change By: Tanja Roithmeier Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title
Satoshi Goto updated an issue
Jenkins / JENKINS-56854
ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Change By:
Satoshi Goto
h3. Problem Abstractenv GIT_COMMIT is not always same the real git revision in particular situation.GIT_COMMIT, SHA of the current, is defined by [Git Plugin|https://wiki.jenkins.io/display/JENKINS/Git+Plugin].h3. Problem DetailI use [GitHub Branch Source Plugin|https://plugins.jenkins.io/github-branch-source] to run Pull Request job with Jenkinsfile.My job use Jenkinsfile in my github repository.I found GIT_COMMIT is sometime different from real git revision in the stage of Pipeline. When the problem happen, Jenkisn build logs says it causes git merge twice.First merge is to read Jenkinsfile from git, second merge is to setup working directory.So I print the revision in my Pipeline script.env.GIT_COMMIT = 75ddc1933fd10b87c529536e3107ea7313debaea HEAD revision = a98b709283bd47d251dfcc9360b91ffc024af16bGIT_COMMIT is the revision at first merge, and HEAD is the revision at second merge.h3. How to reproduce this problemI test with minimum condition which can reproduce the problem by using it↓[https://github.com/mtgto/jenkins-pipeline-test/blob/prtest/Jenkinsfile][https://github.com/mtgto/jenkins-pipeline-test/pull/1] The problem is only happened below all conditions matched: # The job is Multibranch job. # The job uses pipeline by Jenkinsfile in git repository. # The pull request can't merge fast-forward. # Twice merge commits is away at least one second.1, 2: The condition to generate twice merge commits.3: Fast-forward merge doesn't change by current time.4: Git object contains time, it is by the second. Same time merge commits always have same revisions. h3 h4 . EnvironmentsI use Jenkins 2.164.1 in Docker container. {noformat}$ docker run -d --name jenkins -p 8080:8080 --name jenkins -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts-alpine{noformat} h5. Installed Plugins * Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0 * Authentication Tokens API Plugin - 1.3 * bouncycastle API Plugin - 2.17 * Branch API Plugin - 2.2.0 * Command Agent Launcher Plugin - 1.3 * Credentials Binding Plugin - 1.18 * Credentials Plugin - 2.1.18 * Display URL API - 2.3.1 * Docker Commons Plugin - 1.13 * Docker Pipeline - 1.17 * Durable Task Plugin - 1.29 * Folders Plugin - 6.7 * Git client plugin - 2.7.6 * Git plugin - 3.9.3 * GIT server Plugin - 1.7 * GitHub API Plugin - 1.95 * GitHub Branch Source Plugin - 2.4.5 * GitHub plugin - 1.29.4 * Jackson 2 API Plugin - 2.9.8 * _javascript_ GUI Lib: ACE Editor bundle plugin - 1.1 * _javascript_ GUI Lib: Handlebars bundle plugin - 1.1.1 * _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin - 1.2.1 * _javascript_ GUI Lib: Moment.js bundle plugin - 1.1.1 * JDK Tool Plugin - 1.2 * JSch dependency plugin - 0.1.55 * JUnit Plugin - 1.27 * Lockable Resources plugin - 2.5 * Mailer Plugin - 1.23 * Matrix Project Plugin - 1.14 * Pipeline - 2.6 * Pipeline Graph Analys
[JIRA] (JENKINS-55658) Can't install nvm wrapper version 0.1.6
Title: Message Title Mehdy Chaillou commented on JENKINS-55658 Re: Can't install nvm wrapper version 0.1.6 Likewise. Happy to provide any additional info that could help. Tried uninstalling/reinstalling, installing the plugin manually.. it will constantly stay at 0.1.5 and constantly display an available update at 0.1.6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title
Garrett Nickerson updated an issue
Jenkins / JENKINS-56855
MessagingException message: IOException while sending message
Change By:
Garrett Nickerson
I am seeing an intermittent issue where emails are not being sent, and there is no output in the regular log to indicate why. 3 out of our last 12 builds failed to email. When I turned on email-ext debug logging I got the following output: {noformat}[Pipeline] emailextmessageContentType = text/html; charset=UTF-8Adding recipients from project recipient listAnalyzing: **@***.comLooking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0Analyzing: **@***.comLooking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0Analyzing: **@***.comLooking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0Adding recipients from trigger recipient listAnalyzing: ***-Jenkins,<**@***.com>Looking for: ***-Jenkins starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ***-Jenkins,<**@***.com> => found type: 0Looking for: **@***.com starting at: 12 firstFoundIdx: 13 firstFoundIdx-substring: **@***.com> => found type: 0Analyzing: ***-Jenkins,<**@***.com>Looking for: ***-Jenkins starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ***-Jenkins,<**@***.com> => found type: 0Looking for: **@***.com starting at: 12 firstFoundIdx: 13 firstFoundIdx-substring: **@***.com> => found type: 0Successfully created MimeMessageSending email to: **@***.comMessagingException message: IOException while sending message{noformat} The only difference between a successful email sent and an email failure is that last line: {code:java}MessagingException message: IOException while sending message{code} I noticed a similar recent issue in a different email plugin: https://issues.jenkins-ci.org/browse/JENKINS-53305Since we cannot rely on an email notification, we had to implement a policy to closely watch builds to see if they fail.
Add Comment
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Garrett Nickerson created an issue Jenkins / JENKINS-56855 MessagingException message: IOException while sending message Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2019-04-02 15:34 Environment: Jenkins Version: 2.121.3 email-ext-plugin version: 2.63 java.version: 1.8.0_144 Priority: Major Reporter: Garrett Nickerson I am seeing an intermittent issue where emails are not being sent, and there is no output in the regular log to indicate why. 3 out of our last 12 builds failed to email. When I turned on email-ext debug logging I got the following output: [Pipeline] emailext messageContentType = text/html; charset=UTF-8 Adding recipients from project recipient list Analyzing: **@***.com Looking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0 Analyzing: **@***.com Looking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0 Analyzing: **@***.com Looking for: **@***.com starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: **@***.com => found type: 0 Adding recipients from trigger recipient list Analyzing: ***-Jenkins,<**@***.com> Looking for: ***-Jenkins starting at: 0 firstFoundIdx: 0 firstFoundIdx-substring: ***-Jenkins,<**@***.com> => found type: 0 Looking for: **@***.com starting at: 12 firstFoundIdx: 13 firstFoundIdx-substring: **@***.com> => found type: 0 Analyzing: ***-Jenkins,<**@***.com> L
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Satoshi Goto updated an issue Jenkins / JENKINS-56854 ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub Change By: Satoshi Goto Attachment: consoleText.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56854) ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub
Title: Message Title Satoshi Goto created an issue Jenkins / JENKINS-56854 ENV GIT_COMMIT is not match the right revision occasionally when using Jenkinsfile in GitHub Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-04-02 15:25 Priority: Minor Reporter: Satoshi Goto Problem Abstract env GIT_COMMIT is not always same the real git revision in particular situation. GIT_COMMIT, SHA of the current, is defined by Git Plugin. Problem Detail I use GitHub Branch Source Plugin to run Pull Request job with Jenkinsfile. My job use Jenkinsfile in my github repository. I found GIT_COMMIT is sometime different from real git revision in the stage of Pipeline. When the problem happen, Jenkisn build logs says it causes git merge twice. First merge is to read Jenkinsfile from git, second merge is to setup working directory. So I print the revision in my Pipeline script. env.GIT_COMMIT = 75ddc1933fd10b87c529536e3107ea7313debaea HEAD revision = a98b709283bd47d251dfcc9360b91ffc024af16b GIT_COMMIT is the revision at first merge, and HEAD is the revision at second merge. How to reproduce this problem I test with minimum condition which can reproduce the problem by using it↓ https://github.com/mtgto/jenkins-pipeline-test/blob/prtest/Jenkinsfile https://github.com/mtgto/jenkins-pipeline-test/pull/1 The problem is only happened below all conditions matched: The job is Multibranch job. The job uses pipeline by Jenkinsfile in git repository. The pull request can't merge fast-forward. Twice merge commits is away at least one second. 1, 2: The condition to generate twice merge commits. 3: Fast-forward
[JIRA] (JENKINS-53694) Add event "Pull request review comments" to the webhook trigger
Title: Message Title Nitin Surana updated an issue Jenkins / JENKINS-53694 Add event "Pull request review comments" to the webhook trigger Change By: Nitin Surana The webhooks created right now are triggered only for "Pull Request" & "Push" events.Please also add the event "Pull request review comments" to the webhook created. Usecase :The build can fail due to network connectivity issues; overlord overload of resources or parallel builds eating up too many resources or just times out.Solution :Ability to re-trigger the build through "pull request reviwe review comments". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56719) Add unit tests for NullBlamer
Title: Message Title Florian Hageneder started work on JENKINS-56719 Change By: Florian Hageneder Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56846) filesystem scm load stuck in jenkinfile-runner
Title: Message Title Evaristo Gutierrez updated an issue Jenkins / JENKINS-56846 filesystem scm load stuck in jenkinfile-runner Change By: Evaristo Gutierrez Labels: triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56846) filesystem scm load stuck in jenkinfile-runner
Title: Message Title
Evaristo Gutierrez commented on JENKINS-56846
Re: filesystem scm load stuck in jenkinfile-runner
Hi Shurik Gefter, thanks for using Jenkinsfile Runner. I've noticed how the path is different in the pipeline ("workspace/my") and in the log message ("workspace/my_shared_library"). Maybe it was only that you change it in order to put it here, but could you please make sure the path is correct? Also the path is your host while the Jenkinsfile is run into the Docker image? Then you need to make sure you are sharing the volume. Probably you could also configure the shared library though the Configuration As Code plugin. See this 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55438 Allow sequential stages inside parallel in Scripted syntax Change By: Jesse Glick Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title
Jesse Glick commented on JENKINS-55438
Re: Allow sequential stages inside parallel in Scripted syntax
I do not know how Blue Ocean works in any detail. My comment was very much about the terminology. None of the examples given so far in this issue are using actual Scripted syntax—they all start with pipeline, which is Declarative syntax, and so all bets are off. At any rate, the closest Scripted analogue I can come up with for the original Declarative script would be
parallel 'Build and Test Linux': {
stage("Build (Linux)") {
echo "Inside for loop 1"
}
stage("Test (Linux)") {
echo "Inside for loop 2"
}
}, 'Build and Test Windows': {
stage("Build (Windows)") {
echo "Inside for loop 3"
}
stage("Test (Windows)") {
echo "Inside for loop 4"
}
}
which indeed also fails to display the stages—only the branches are shown. (Similarly when the whole script is enclosed in stage('Build and Test') {…}.)So I would consider that a bug in Blue Ocean: it should display a Pipeline build with a structure that its visualization layer supports, regardless of the syntax used to run that build. Perhaps there is some workaround that a B.O. developer could explain.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-56853) Pull Request validation by multiple jenkins
Title: Message Title Carlos Rodríguez López created an issue Jenkins / JENKINS-56853 Pull Request validation by multiple jenkins Issue Type: New Feature Assignee: Unassigned Attachments: pr-validation.png, webhooks.png Components: scm-api-plugin Created: 2019-04-02 14:19 Priority: Minor Reporter: Carlos Rodríguez López I would like to have one PR validation per repo Webhook linked to a different Jenkins instance The current behavior is as follows: 1.- Once Multibranch Pipeline is saved, scm api creates automatically the webhook for you... So under this repo Webhooks is set multiple webhooks per each of your masters (with their respective endpoints).2.- Once a developer makes a new PR the build is launched in each of the masters... but just one validation (continuous-integration/jenkins/pr-merge) is happening for the repo. The last webhook which was joined to the repo. Add Comment
[JIRA] (JENKINS-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier
Title: Message Title Sydney Rasquinha commented on JENKINS-50792 Re: Overall Admin access is required to create/copy a job, which wasn't required earlier The issue has not been resolved. It is still seen in Jenkins 2.121.2 when using "Matrix-based security" or "Project-based Matrix Authorization Strategy". Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian I have updated Jenkins to the latest version (Jenkins ver. 2.164.1) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error:[04/02/19 10:17:45] [SSH] Starting sftp client.[04/02/19 10:17:45] [SSH] Copying latest slave.jar...[04/02/19 10:17:45] [SSH] Copied 789,283 bytes.Expanded the channel window size to 4MB[04/02/19 10:17:45] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running?at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984)at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)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 java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jarat hudson.FilePath.copyTo(FilePath.java:2191)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)at hudson.remoting.UserRequest.perform(UserRequest.java:212)at hudson.remoting.UserRequest.perform(UserRequest.java:54)at hudson.remoting.Request$2.run(Request.java:369)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) ... 4 more Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to automation-jenkins-nodeWith SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 13:52:10] [SSH] Starting sftp client.[04/02/19 13:52:10] [SSH] Copying latest remoting.jar...[04/02/1
[JIRA] (JENKINS-52669) IndexOutOfBoundsException after upgrade to 1.2.3
Title: Message Title Vlastimil Dolejš commented on JENKINS-52669 Re: IndexOutOfBoundsException after upgrade to 1.2.3 I can confirm that the problem is related to the version range. In my case, I don't have direct dependency with version range but there is some transitive dependency in my dependency tree that has version declared as a range. I have cloned the plugin source and written unit test for my artifact so I know the details. The problematic dependency in my case is org.webjars.npm:js-tokens:jar:[1.0.1,2) This dependency can be resolved and there are these versions in repository: [1.0.0, 1.0.1, 2.0.0, 3.0.0, 3.0.1, 3.0.2, 4.0.0]. The problematic part of code is in ReleasedVersionRangeResolver#resolveVersionRange on lines 134 and 135. The 3.0.2 and 4.0.0 is picked as the versionsAndUpToDates.latestCandidates and versionsAndUpToDates.releaseCandidates which is then passed to getLatest() but none of these versions satisfy version range constraint which is [1.0.1,2). So I think there are 2 problems. 1/ The getLatest() method should return null instead of throwing exception if it won't match any version with the version range. 2/ I think we should pass versionsAndUpToDates.versions instead of versionsAndUpToDates.latestCandidates and releaseCandidates to the getLatest() method on lines 134 and 135. I have created pull request for the first problem: https://github.com/jenkinsci/repository-connector-plugin/pull/37 This will completely resolve the problem because resolving transitive dependencies is not necessary. Add Comment
[JIRA] (JENKINS-56852) Regression: Can't invoke function with optional arguments twice
Title: Message Title
Franz Hoffmann created an issue
Jenkins / JENKINS-56852
Regression: Can't invoke function with optional arguments twice
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-04-02 14:06
Environment:
Ubuntu 16.04.6 LTS OpenJDK Runtime Environment java.runtime.version: 1.8.0_181-8u181-b13-2~deb9u1-b13 Jenkins ver. 2.164.1 Groovy plug-in version 2.2 Running Jenkins master inside Docker container
Priority:
Minor
Reporter:
Franz Hoffmann
I have a shared library my-lib that contains only one file vars/hello.groovy:
// vars/hello.groovy
def call(params) {
println "DEBUG A-1"
}
I also have the following Jenkins job:
library "my-lib@master"
node("master") {
writeFile file: "myTest.groovy",
text: """
def execute() {
println "DEBUG 1"
hello()
println "DEBUG 2"
hello()
println "DEBUG 3"
}
// Boilerplate-coding necessary! Do not delete!
return this
"""
def localtest = load "myTest.groovy"
localtest.execute()
}
The job worked fine in Jenkins 2.60.3 (Groovy plug-in version 2.0)
[JIRA] (JENKINS-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian I have updated Jenkins to the latest version (Jenkins ver. 2.164.1) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error:[04/02/19 10:17:45] [SSH] Starting sftp client.[04/02/19 10:17:45] [SSH] Copying latest slave.jar...[04/02/19 10:17:45] [SSH] Copied 789,283 bytes.Expanded the channel window size to 4MB[04/02/19 10:17:45] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running?at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984)at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)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 java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jarat hudson.FilePath.copyTo(FilePath.java:2191)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)at hudson.remoting.UserRequest.perform(UserRequest.java:212)at hudson.remoting.UserRequest.perform(UserRequest.java:54)at hudson.remoting.Request$2.run(Request.java:369)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) ... 4 more Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to automation-jenkins-node With SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 13:52:10] [SSH] Starting sftp client.[04/02/19 13:52:10] [SSH] Copying latest remoting.jar...[0
[JIRA] (JENKINS-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Jesse Glick commented on JENKINS-54643 Re: A connection interruption causes the pipeline to fail when USE_WATCHING=true Filed JENKINS-56851 for loss of output. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54643) A connection interruption causes the pipeline to fail when USE_WATCHING=true
Title: Message Title Jesse Glick resolved as Duplicate Considering a duplicate of JENKINS-41854 since that was the primary reported problem. Jenkins / JENKINS-54643 A connection interruption causes the pipeline to fail when USE_WATCHING=true Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title An Tran commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax I did experiment a lot already before asking here Ok let's keep the terminology aside. Can you help me to understand why only one stage is shown in each parallel branch even though I habe 2 stages for each branch in my script? Is it a bug? Should I create a bug report for that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56849) Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1
Title: Message Title iulian iulian updated an issue Jenkins / JENKINS-56849 Unable to connect node to slave using ssh slave plugin (1.11 and 1.29) and Jenkins ver. 2.164.1 Change By: iulian iulian I have updated Jenkins to the latest version (Jenkins ver. 2.164.1) and Selenium Grid version is: 3.12.0. Java varsion on master (where run the hub) is: openjdk version "1.8.0_191", on the slave is: java version "1.8.0_191" and SSH Slave plugin version 1.11. When the nod is trying to connect to slave is throw this error:[04/02/19 10:17:45] [SSH] Starting sftp client.[04/02/19 10:17:45] [SSH] Copying latest slave.jar...[04/02/19 10:17:45] [SSH] Copied 789,283 bytes.Expanded the channel window size to 4MB[04/02/19 10:17:45] [SSH] Starting slave process: cd "/var/jenkins" && /usr/lib/jvm/jdk1.8.0_191/bin/java -Xmx128m -Xms128m -jar slave.jarchannel startedRemoting version: 3.29This is a Unix agentEvacuated stdoutStarting Selenium nodes on automation-jenkins-nodeApr 02, 2019 10:17:47 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.plugins.selenium.configuration.DirectJsonInputConfiguration$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running?at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:984)at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:137)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:725)at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:706)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 java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: Failed to copy /var/lib/jenkins/plugins/selenium/WEB-INF/lib/selenium-server-standalone-3.12.0.jar to /var/jenkins/selenium-server-standalone-3.12.0.jarat hudson.FilePath.copyTo(FilePath.java:2191)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:76)at hudson.plugins.selenium.callables.SeleniumCallable.invoke(SeleniumCallable.java:23)at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3041)at hudson.remoting.UserRequest.perform(UserRequest.java:212)at hudson.remoting.UserRequest.perform(UserRequest.java:54)at hudson.remoting.Request$2.run(Request.java:369)at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)With SSH Slave plugin version 1.29 is throwing a different error:[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Starting sftp client.[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Copying latest slave remoting .jar...[04/02/19 09 13 : 29 52 : 28 10 ] [SSH] Copied 789,283 bytes.
[JIRA] (JENKINS-56851) Flush durable task output before agent shutdown or before writing lastLocation
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-56851 Flush durable task output before agent shutdown or before writing lastLocation Issue Type: Improvement Assignee: Unassigned Components: workflow-durable-task-step-plugin Created: 2019-04-02 13:56 Priority: Major Reporter: Jesse Glick See discussion in this PR. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title Jesse Glick commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax I do not know, you would need to experiment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56777) Chrome opens, but nothing happens (Selenium)
Title: Message Title Lee Leibke commented on JENKINS-56777 Re: Chrome opens, but nothing happens (Selenium) Thanks for sharing that info Andrei. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-56850) When block outside of stage
Title: Message Title
Michael Werner created an issue
Jenkins / JENKINS-56850
When block outside of stage
Issue Type:
New Feature
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2019-04-02 13:44
Priority:
Major
Reporter:
Michael Werner
If you have a couple of microservices inside a single git repository and for each microservice there is a Jenkins Job sharing the same Jenkinsfile. e. g. https://github.com/Xaseron/phippyandfriends The goal is that the pipeline for each microservice is only run if a change is made in the subdirectory or the build is triggered manually. The current possible solution is kind of ugly: (the job is multibranch pipeline named after the microservice e.g. captainkube)
pipeline {
options {
timestamps()
}
agent {
node {
label 'master'
}
}
environment {
/* get the foo out of e.g. foo/master */
MICROSERVICE = "${env.JOB_NAME.tokenize('/')[0]}"
}
stages {
/* useless stage to get the when block at the top level */
stage('Meta') {
/* only start a build when something changed inside the microservice or it is triggered manually */
when {
anyOf {
triggeredBy cause: 'UserIdCause'
changeset "$MICROSERVICE/**"
}
}
stages {
stage('Build') {
steps {
echo "I've got a change in $MICROSERVICE"
echo "docker build -t $MICROSERVICE:$BUILD_NUMBER $MICROSERVICE"
}
}
stage('Test') {
steps {
echo 'test'
}
}
stage('Deploy')
[JIRA] (JENKINS-55438) Allow sequential stages inside parallel in Scripted syntax
Title: Message Title An Tran commented on JENKINS-55438 Re: Allow sequential stages inside parallel in Scripted syntax Jesse Glick Ok, so what is the correct way to do it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51638) No Enum Constant Found - Default PreBuildMerge Failure
Title: Message Title Jesse Glick commented on JENKINS-51638 Re: No Enum Constant Found - Default PreBuildMerge Failure A proper fix would require something like JENKINS-44892, which has been discussed for some time but never prototyped. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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.
