[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title
Markus May updated an issue
Jenkins / JENKINS-39664
Docker builds do not work with Kubernetes Pipeline plugin
Change By:
Markus May
I have setup a Kubernetes Pipeline (see below) which is working fine, as long as I do use shell-scripts to generate the Docker-Image. As soon as I try to use the docker-Workflow plugin, the script comes back, with an exception in a (not defined by myself) dockerFingerprintFrom-step. This step does not seem to be able to find the generated docker-image anymore. Therefor I do assume, that this step is then not run in the container, where I build the image.Any help is appreciated.{code:groovy}podTemplate(label: 'docker-mysql', containers: [containerTemplate(name: 'docker', image: 'docker:1.12.3-dind', ttyEnabled: true, command: 'cat', privileged: true, instanceCap: 1),containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:2.62-alpine', args: '${computer.jnlpmac} ${computer.name}'), ], volumes: [hostPathVolume(mountPath: "/var/run/docker.sock", hostPath: "/var/run/docker.sock") ]) { node() {stage('Preparation') { // for display purposes git url: 'https://github.com/ devopskube repo /docker-mysql.git' container('docker') {stage('Build the docker image') {sh 'docker build -t devopskube/mysql:latest .'sh 'docker inspect -f {{.Id}} devopskube repo /mysql:latest'id = sh ( script: 'docker inspect -f {{.Id}} devopskube repo /mysql:latest', returnStdout: true ).trim()} }} }{code}
Add Comment
[JIRA] (JENKINS-39664) Docker builds do not work with Kubernetes Pipeline plugin
Title: Message Title
Markus May created an issue
Jenkins / JENKINS-39664
Docker builds do not work with Kubernetes Pipeline plugin
Issue Type:
Bug
Assignee:
Ioannis Canellos
Components:
docker-workflow-plugin, kubernetes-pipeline-plugin
Created:
2016/Nov/11 7:51 AM
Environment:
Jenkins 2.19.1 Kubernetes-Pipeline-Plugin 0.9 Docker-Workflow-Plugin 1.9
Priority:
Major
Reporter:
Markus May
I have setup a Kubernetes Pipeline (see below) which is working fine, as long as I do use shell-scripts to generate the Docker-Image. As soon as I try to use the docker-Workflow plugin, the script comes back, with an exception in a (not defined by myself) dockerFingerprintFrom-step. This step does not seem to be able to find the generated docker-image anymore. Therefor I do assume, that this step is then not run in the container, where I build the image. Any help is appreciated.
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
podTemplate(label: 'docker-mysql', containers: [
containerTemplate(name: 'docker', image: 'docker:1.12.3-dind', ttyEnabled: true, command: 'cat', privileged: true, instanceCap: 1),
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:2.62-alpine', args: '${computer.jnlpmac} ${computer.name}'),
],
volumes: [
hostPathVolume(mountPath: "/var/run/docker.sock",
[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach edited a comment on JENKINS-1877 Re: Explanatory message at prepare for shutdown Seconded.The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true...To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow. Maybe the menu item shouldn't even read "Prepare for shutdown" but "Cease all operation" instead? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-1877) Explanatory message at prepare for shutdown
Title: Message Title Steffen Breitbach commented on JENKINS-1877 Re: Explanatory message at prepare for shutdown Seconded. The worst part of the message is the "shutdown" part. I also got calls from users "why the Jenkins is shutting down" when this absolutely wasn't true... To me the best solution would be a default message (maybe the shutdown one) being displayed as long as not specified otherwise and the ability to override this somehow. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38624) MSBuild Projects no longer work after upgrading to 1.8.0
Title: Message Title Parag Thakur commented on JENKINS-38624 Re: MSBuild Projects no longer work after upgrading to 1.8.0 We moved back to 1.5 to solve the issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39662) NPE with multi-config project
Title: Message Title Daniel Lo Nigro commented on JENKINS-39662 Re: NPE with multi-config project Might be using GitHubProjectProperty incorrectly. Can look through code on GitHub to see how other plugins use it: https://github.com/search?q=getProperty%28GithubProjectProperty.class%29=Code=%E2%9C%93 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39663) Allow issue template to be customised per-job
Title: Message Title Daniel Lo Nigro created an issue Jenkins / JENKINS-39663 Allow issue template to be customised per-job Issue Type: Improvement Assignee: Daniel Lo Nigro Components: github-issues-plugin Created: 2016/Nov/11 6:58 AM Priority: Minor Reporter: Daniel Lo Nigro Currently there's just one template server-side. Instead, the template should be configurable per-job. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39662) NPE with multi-config project
Title: Message Title Daniel Lo Nigro created an issue Jenkins / JENKINS-39662 NPE with multi-config project Issue Type: Bug Assignee: Daniel Lo Nigro Components: github-issues-plugin Created: 2016/Nov/11 6:54 AM Priority: Minor Reporter: Daniel Lo Nigro When using the GitHub Issues Plugin with a multi-config project, a NullPointerException is thrown: java.lang.NullPointerException at org.jenkinsci.plugins.githubissues.GitHubIssueNotifier.getRepoForJob(GitHubIssueNotifier.java:58) at org.jenkinsci.plugins.githubissues.GitHubIssueNotifier.perform(GitHubIssueNotifier.java:90) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Build step 'Create GitHub issue on failure' marked build as failure
[JIRA] (JENKINS-38703) [INFO] Deploying artifact not workign with http forwarding proxy
Title: Message Title Eyal Ben Moshe commented on JENKINS-38703 Re: [INFO] Deploying artifact not workign with http forwarding proxy After upgrading to version 2.8.1 of the Artifactory Plugin, in case there are Artifactory servers that should not be accessed by Jenkins through the proxy, you can check the "Bypass proxy" option for those Artifactory servers in Jenkins Manage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38703) [INFO] Deploying artifact not workign with http forwarding proxy
Title: Message Title Kıvanç Sahici commented on JENKINS-38703 Re: [INFO] Deploying artifact not workign with http forwarding proxy Jenkins Artifactory plugin 2.8.1 has been released and the problem has been solved for me Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39640) SQLPlus Script Runner Plugin - Unable to execute scripts
Title: Message Title Phumlani Mchunu updated an issue Jenkins / JENKINS-39640 SQLPlus Script Runner Plugin - Unable to execute scripts Change By: Phumlani Mchunu Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39214) "Goals and Opptions" and "Root POM" not written to config.xml
Title: Message Title olamy commented on JENKINS-39214 Re: "Goals and Opptions" and "Root POM" not written to config.xml Well that's weird. I had a quick look and cannot reproduce with hpi:run. I will have a try later with a real jenkins distribution (and I guess an upgrade of the plugin as well not with a fresh new install). There is no real changes related which is even worst. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39661
Investigate performance of Pipeline /activity and /runs REST endpoint
Change By:
James Dumay
The {{/activity}} and {{/runs}} endpoints have been reported to take up to 28 seconds on some Jenkins masters.Tracing through the code, it looks like {{io.jenkins.blueocean.service.embedded.rest.RunContainerImpl#get}} will *load all the runs* using {{hudson.model.Job#getBuilds()}} for the Job *then apply applies the pagination*.However, there is a method {{hudson.model.Job#getBuilds(hudson.model.Fingerprint.RangeSet)}} that will allow us to fetch a range of data which would be suitable for pagination.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-38882) Avoid browser cache busting after Jenkins restart
Title: Message Title James Dumay commented on JENKINS-38882 Re: Avoid browser cache busting after Jenkins restart Tom FENNELLY LMK when this should go in the sprint (or not) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39609) Cache /blue/rest/classes calculation
Title: Message Title James Dumay commented on JENKINS-39609 Re: Cache /blue/rest/classes calculation Jesse Glick essentially blue/rest/classes returns a list of the extension points that Blue Ocean is interested in. So if the extensions available change (e.g. a new plugin was installed that has extensions) we'd like to invalidate a cache. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32938) The Usage Statistics option is randomly displayed in the global configuration page.
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-32938 The Usage Statistics option is randomly displayed in the global configuration page. Change By: Ben Walding The Usage Statistics option is displayed (without a heading) under the * Maven Project Configuation* section in the Jenkins global configuration page. It looks hidden and it is rather This lack of categorisation makes the option less noticeable which may be perceived as unethical / hidden . In OSS: h4. Current Location !usage-stats-oss.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32938) The Usage Statistics option is randomly displayed in the global configuration page.
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-32938 The Usage Statistics option is randomly displayed in the global configuration page. Change By: Ben Walding The Usage Statistics option is randomly displayed (without a heading) under the Maven in Jenkins global configuration page.It looks hidden and it is rather unethical.In OSS:!usage-stats-oss.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36283) PR builds customization
Title: Message Title James Dumay commented on JENKINS-36283 Re: PR builds customization Cosima Laube we at CloudBees need parity with Github for Blue Ocean so we are considering picking this up. Unfortunately I can't share an ETA with you but it is on our radar. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Tom FENNELLY if you feel comfortable picking this kinda thing up then you can. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39661
Investigate performance of Pipeline /activity and /runs REST endpoint
Change By:
James Dumay
The {{/activity}} and {{/runs}} endpoints have been reported to take up to 28 seconds on some Jenkins masters.Tracing through the code, it looks like {{io.jenkins.blueocean.service.embedded.rest.RunContainerImpl#get}} will * load all the runs * using {{hudson.model.Job#getBuilds()}} for the Job * then apply the pagination * .However, there is a method {{hudson.model.Job#getBuilds(hudson.model.Fingerprint.RangeSet)}} that will allow us to fetch a range of data which would be suitable for pagination.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint I've linked the Customer Data here that is on the internal CloudBees tracker. I am only referencing this here so we can keep the development of Blue Ocean out in the open and still respond to these requests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay edited a comment on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint I've linked the Customer Data here that is on the internal CloudBees tracker - non-employees will be able to see it . I am only referencing this here so we can keep the development of Blue Ocean out in the open and still respond to these requests. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay created an issue Jenkins / JENKINS-39661 Investigate performance of Pipeline /activity and /runs REST endpoint Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/11 3:00 AM Priority: Major Reporter: James Dumay The /activity and /runs endpoints have been reported to take up to 28 seconds on some Jenkins masters. Tracing through the code, it looks like io.jenkins.blueocean.service.embedded.rest.RunContainerImpl#get will load all the runs using hudson.model.Job#getBuilds() for the Job then apply the pagination. However, there is a method hudson.model.Job#getBuilds(hudson.model.Fingerprint.RangeSet) that will allow us to fetch a range of data which would be suitable for pagination. Add Comment
[JIRA] (JENKINS-39655) Adding JIRA plugin throws NullPointerException
Title: Message Title Radek Antoniuk commented on JENKINS-39655 Re: Adding JIRA plugin throws NullPointerException what JIRA URL did you specify? what plugin version did you use? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow updated an issue Jenkins / JENKINS-39637 How to remove jsessionid on the url when logging in Change By: Yun Ken Chow Whenever I login to Jenkins using my AD account, I will be redirected to this url http://serverName:8080/jenkins/;jsessionid=.serverName and the page says Not Found.How do I eliminate this? Referring to the attachment "Capture.PNG" , checking that option in Wildfly configuration does not help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39656) [Questrion] Version Information
Title: Message Title Goran Sarenkapa commented on JENKINS-39656 Re: [Questrion] Version Information How does it depend on the Version of Jenkins? (I have tried Jenkins ver. 1.634 and 2.3), i am just wondering if you knew why versioneye says that the latest version is 1.22 when it is in fact 2.1.8. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow edited a comment on JENKINS-39637 Re: How to remove jsessionid on the url when logging in !wildfly.PNG|thumbnail! Yes, I am running Jenkins within Wildfly (JBoss). When you mentioned 2.4, is that the version for Jenkins? Is there any fixes for the version (1.653) that I'm using or the only solution is that I'll have to upgrade Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow edited a comment on JENKINS-39637 Re: How to remove jsessionid on the url when logging in !wildfly.PNG|thumbnail! Yes, I am running Jenkins within Wildfly (JBoss). Mine is showing version When you mentioned 2. 7.1 but I am still seeing 4, is that :( the version for Jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow commented on JENKINS-39637 Re: How to remove jsessionid on the url when logging in Yes, I am running Jenkins within Wildfly (JBoss). Mine is showing version 2.7.1 but I am still seeing that Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow updated an issue Jenkins / JENKINS-39637 How to remove jsessionid on the url when logging in Change By: Yun Ken Chow Attachment: wildfly.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow updated an issue Jenkins / JENKINS-39637 How to remove jsessionid on the url when logging in Change By: Yun Ken Chow Attachment: wildfly.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39637) How to remove jsessionid on the url when logging in
Title: Message Title Yun Ken Chow updated an issue Jenkins / JENKINS-39637 How to remove jsessionid on the url when logging in Change By: Yun Ken Chow Attachment: wildfly.PNG Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39659) When I start a build I want it to be shown somewhere prominently
Title: Message Title James Dumay commented on JENKINS-39659 Re: When I start a build I want it to be shown somewhere prominently Thanks Daniel Beck I agree this would be a great addition to the dashboard. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39660) Blue Ocean weather icons are difficult to distinguish at smaller sizes
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-39660 Blue Ocean weather icons are difficult to distinguish at smaller sizes Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/11 1:04 AM Priority: Minor Reporter: Daniel Beck Blue Ocean weather icons are difficult to distinguish at smaller sizes. Example: https://github.com/jenkins-infra/rating/pull/10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39659) When I start a build I want it to be shown somewhere prominently
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-39659 When I start a build I want it to be shown somewhere prominently Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/11 1:04 AM Priority: Minor Reporter: Daniel Beck If I start a build, chances are I care about the result. BO should show me the result of "my" build somewhere, perhaps on the dashboard, like a "favorite light", or "notification" of sorts. Add Comment This message was
[JIRA] (JENKINS-39633) Jenkins Failed To start After Pipeline Plugin Update
Title: Message Title Evan Pratama closed an issue as Fixed Jenkins / JENKINS-39633 Jenkins Failed To start After Pipeline Plugin Update Change By: Evan Pratama Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39641) workflow-multibranch does not correctly install
Title: Message Title Evan Pratama commented on JENKINS-39641 Re: workflow-multibranch does not correctly install I got a kind of similar issue: JENKINS-39633, Jesse Glick commented on my issue to update the plugins manually. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title Vincent Privat commented on JENKINS-39651 Re: FileNotFoundException when scanning compiler warnings in multibranch pipeline Sure ! The description is updated as well, we found it was incorrect usage but the error was not clear. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title
Vincent Privat updated an issue
Jenkins / JENKINS-39651
FileNotFoundException when scanning compiler warnings in multibranch pipeline
Change By:
Vincent Privat
We used warnings plugin in a multibranch pipeline Jenkinsfile for a Maven Java project as follows:{code:java} stage('Build') { maven '-DskipTests clean install -P TOMCAT' maven '-DskipTests clean install -P WAS' step([$class: 'WarningsPublisher', parserConfigurations: [[parserName: 'AspectJ Compiler (ajc)'], [parserName: 'Java Compiler (javac)']]]) }{code}This is incorrect usage (we found later that we must use "consoleParsers" instead of "parserConfigurations"), but Jenkins reports an unclear error in the job summary for each parser:Ajc Warnings: 0 warnings from one analysis.During parsing an error has been reported.Java Warnings: 0 warnings from one analysis.During parsing an error has been reported.The error is the same: the plugin tries to open a directory (as a file ?) and face FileNotFoundException: {noformat} Module : Parsing of file /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA failed due to an exception:java.io.FileNotFoundException: /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA (Is a directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195)at java.io.FileInputStream.(FileInputStream.java:138)at hudson.plugins.warnings.parser.ParserRegistry.createReader(ParserRegistry.java:325)at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281)at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:261)at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:44)at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325)at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283)at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:241)at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:200)at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996)at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:400)at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:298)at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68)at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280)at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59)at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221)at
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title
Vincent Privat updated an issue
Jenkins / JENKINS-39651
FileNotFoundException when scanning compiler warnings in multibranch pipeline
Change By:
Vincent Privat
We used warnings plugin in a multibranch pipeline Jenkinsfile for a Maven Java project as follows:{ { code:java} stage('Build') { maven '-DskipTests clean install -P TOMCAT' maven '-DskipTests clean install -P WAS' step([$class: 'WarningsPublisher', parserConfigurations: [[parserName: 'AspectJ Compiler (ajc)'], [parserName: 'Java Compiler (javac)']]]) } {code } } This is incorrect usage (we found later that we must use "consoleParsers" instead of "parserConfigurations"), but Jenkins reports an unclear error in the job summary for each parser:Ajc Warnings: 0 warnings from one analysis.During parsing an error has been reported.Java Warnings: 0 warnings from one analysis.During parsing an error has been reported.The error is the same: the plugin tries to open a directory (as a file ?) and face FileNotFoundException:Module : Parsing of file /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA failed due to an exception: java.io.FileNotFoundException: /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA (Is a directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.plugins.warnings.parser.ParserRegistry.createReader(ParserRegistry.java:325) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:261) at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:44) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283) at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:241) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:200) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:400) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:298) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title
Vincent Privat updated an issue
Jenkins / JENKINS-39651
FileNotFoundException when scanning compiler warnings in multibranch pipeline
Change By:
Vincent Privat
We use used warnings plugin in a multibranch pipeline Jenkinsfile for a Maven Java project as follows: {{ stage('Build') { maven '-DskipTests clean install -P TOMCAT' maven '-DskipTests clean install -P WAS' step([$class: 'WarningsPublisher', parserConfigurations: [[parserName: 'AspectJ Compiler (ajc)'], [parserName: 'Java Compiler (javac)']]]) } }} It works fine This is incorrect usage (we found later that we must use "consoleParsers" instead of "parserConfigurations") , but Jenkins reports an unclear error in the job summary for each parser:Ajc Warnings: 0 warnings from one analysis.During parsing an error has been reported.Java Warnings: 0 warnings from one analysis.During parsing an error has been reported.The error is the same: the plugin tries to open a directory (as a file ?) and face FileNotFoundException:Module : Parsing of file /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA failed due to an exception: java.io.FileNotFoundException: /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA (Is a directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.plugins.warnings.parser.ParserRegistry.createReader(ParserRegistry.java:325) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:261) at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:44) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283) at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:241) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:200) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:400) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:298) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title Neil Rhine commented on JENKINS-38937 Re: GitHub API cache is not working Any updates here or suggestions to mitigate? Our organization is also constantly hitting the API limit on all of the indexing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean commented on JENKINS-39628 Re: Handle skipped stages and parallels in the Pipeline Graph James Dumay – Initial idea Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39628) Handle skipped stages and parallels in the Pipeline Graph
Title: Message Title Brody Maclean updated an issue Jenkins / JENKINS-39628 Handle skipped stages and parallels in the Pipeline Graph Change By: Brody Maclean Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev commented on JENKINS-38996 Re: Java on Jenkins crashes unexpectedly R. Tyler Croy - You've been autoassigned as a Ruby Runtime Plugin component lead in JIRA Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title R. Tyler Croy commented on JENKINS-38996 Re: Java on Jenkins crashes unexpectedly Why was this assigned t ome? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39633) Jenkins Failed To start After Pipeline Plugin Update
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39633 Jenkins Failed To start After Pipeline Plugin Update Change By: Jesse Glick Component/s: pipeline-input-step-plugin Component/s: workflow-multibranch-plugin Component/s: core Component/s: pipeline Labels: jenkins jenkins2.3 pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-39633) Jenkins Failed To start After Pipeline Plugin Update
Title: Message Title Jesse Glick commented on JENKINS-39633 Re: Jenkins Failed To start After Pipeline Plugin Update Already fixed, update Pipeline: Multibranch and Pipeline: Input Step. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39571) Jenkins doesn't start after plugin update
Title: Message Title Jesse Glick resolved as Incomplete No log from the failed startup seems to be attached. Jenkins / JENKINS-39571 Jenkins doesn't start after plugin update Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-39633) Jenkins Failed To start After Pipeline Plugin Update
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-39633 Jenkins Failed To start After Pipeline Plugin Update Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39478) Select box / Dropdown component
Title: Message Title James Dumay updated JENKINS-39478 Jenkins / JENKINS-39478 Select box / Dropdown component Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39658) Include failed step's error to it's log
Title: Message Title James Dumay commented on JENKINS-39658 Re: Include failed step's error to it's log Need to understand scope Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39658) Include failed step's error to it's log
Title: Message Title James Dumay commented on JENKINS-39658 Re: Include failed step's error to it's log Vivek Pandey here's the example Sam Van Oort gave https://github.com/jenkinsci/pipeline-stage-view-plugin/blob/master/rest-api/src/main/java/com/cloudbees/workflow/rest/external/ErrorExt.java#L62 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Daniel Beck commented on JENKINS-39360 Re: Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins I see no need to make this configurable. It should be straightforward to achieve a similar result with UnprotectedRootAction / DirectoryBrowserSupport (just don't be an idiot and allow path traversal). The approach chosen in Jenkins was to retain compatibility with existing URLs, but if it's a different file, it should be straightforward enough. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39658) Include failed step's error to it's log
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39658 Include failed step's error to it's log Change By: James Dumay Sprint: arctic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39627) Alignment of cog is off on Result
Title: Message Title Josh McDonald started work on JENKINS-39627 Change By: Josh McDonald Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39658) Include failed step's error to it's log
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-39658 Include failed step's error to it's log Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Nov/10 9:51 PM Priority: Major Reporter: Vivek Pandey A pipeline step's failure does not get reported in it's log. For example archiver step failure gets reported in overall run's log. As discussed with Sam Van Oort, a possible hack around it would be to use failed step's flowNode's ErrorAction, FlowNode.getError().getError().getMessage() and append it to the step's log. In blueocean API, step's log is AnnotatedLargeText, and it can be served in streaming fashion, it should be done in such a way to correctly append it to the end of step's log. Add Comment
[JIRA] (JENKINS-39627) Alignment of cog is off on Result
Title: Message Title James Dumay assigned an issue to Josh McDonald Jenkins / JENKINS-39627 Alignment of cog is off on Result Change By: James Dumay Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title Daniel Lo Nigro closed an issue as Not A Defect Jenkins / JENKINS-39636 Could not initialize class org.jfree.chart.JFreeChart Change By: Daniel Lo Nigro Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title
Daniel Lo Nigro commented on JENKINS-39636
Re: Could not initialize class org.jfree.chart.JFreeChart
Oleg Nenashev - This is the log at /var/log/jenkins/jenkins.log:
Running from: /usr/share/jenkins/jenkins.war
Nov 10, 2016 1:39:37 PM Main deleteWinstoneTempContents
WARNING: Failed to delete the temporary Winstone file /tmp/winstone/jenkins.war
Nov 10, 2016 1:39:38 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Logging initialized @1137ms
Nov 10, 2016 1:39:38 PM winstone.Logger logInternal
INFO: Beginning extraction from war file
Nov 10, 2016 1:39:38 PM org.eclipse.jetty.util.log.JavaUtilLog warn
WARNING: Empty contextPath
Nov 10, 2016 1:39:38 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-9.2.z-SNAPSHOT
Nov 10, 2016 1:39:39 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
Jenkins home directory: /var/lib/jenkins found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
Nov 10, 2016 1:39:40 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started w.@1530c739{/,file:/var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenkins/war}
Nov 10, 2016 1:39:40 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started ServerConnector@7161d8d1{HTTP/1.1}{0.0.0.0:8080}
Nov 10, 2016 1:39:40 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started @3644ms
Nov 10, 2016 1:39:40 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Nov 10, 2016 1:39:41 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Nov 10, 2016 1:39:41 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Nov 10, 2016 1:39:41 PM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
INFO: Initializing Bouncy Castle security provider.
Nov 10, 2016 1:39:42 PM jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
INFO: Bouncy Castle security provider initialized.
Nov 10, 2016 1:39:53 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Nov 10, 2016 1:39:54 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
INFO: Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping
Nov 10, 2016 1:39:55 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Nov 10, 2016 1:39:56 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Nov 10, 2016 1:39:56 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Nov 10, 2016 1:39:57 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 43529
Nov 10, 2016 1:39:57 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Nov 10, 2016 1:39:57 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Download metadata
Nov 10, 2016 1:39:57 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Download metadata. 8 ms
Nov 10, 2016 1:39:58 PM org.springframework.context.support.AbstractApplicationContext prepareRefresh
INFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@37895331: display name [Root WebApplicationContext]; startup date [Thu Nov 10 13:39:58 PST 2016]; root of context hierarchy
Nov 10, 2016 1:39:58 PM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
INFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@37895331]:
[JIRA] (JENKINS-38862) jenkins-slave not connecting to master when not launched with root
Title: Message Title Oleg Nenashev commented on JENKINS-38862 Re: jenkins-slave not connecting to master when not launched with root So JNLP2 protocol gets accepted and then the slave fails Oct 10 14:45:12 userbxxy02 java: INFOS: Trying protocol: JNLP2-connect Oct 10 14:45:12 userbxxy02 java: oct. 10, 2016 2:45:12 PM hudson.remoting.jnlp.Main$CuiListener status Oct 10 14:45:12 userbxxy02 java: INFOS: Connected Oct 10 14:45:16 userbxxy02 java: oct. 10, 2016 2:45:16 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run Oct 10 14:45:16 userbxxy02 java: GRAVE: I/O error in channel channel Please ensure your user has a write access to the folder Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Change By: Oleg Nenashev Component/s: perforce-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title Ulli Hafner commented on JENKINS-39651 Re: FileNotFoundException when scanning compiler warnings in multibranch pipeline Can you please wrap your blocks in the description with noformat tags? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38834) Freestyle jobs hang in 2.19.1 on Windows 10 Nodes
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38834 Freestyle jobs hang in 2.19.1 on Windows 10 Nodes Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev assigned an issue to R. Tyler Croy Jenkins / JENKINS-38996 Java on Jenkins crashes unexpectedly Change By: Oleg Nenashev Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38996 Java on Jenkins crashes unexpectedly Change By: Oleg Nenashev Component/s: ruby-runtime Component/s: ruby-runtime-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38996 Java on Jenkins crashes unexpectedly Change By: Oleg Nenashev Labels: jenkins rub Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-38996 Java on Jenkins crashes unexpectedly Change By: Oleg Nenashev Labels: jenkins rub Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title Oleg Nenashev commented on JENKINS-38996 Re: Java on Jenkins crashes unexpectedly I assume it's somehow related to the Ruby Runtime plugin. Maybe here: https://github.com/jenkinsci/ruby-runtime-plugin/blob/70045022426fd55d6f765086e56c5e2d5e2a498e/src/main/java/ruby/RubyPluginRuntimeResolver.java#L24 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title
Oleg Nenashev edited a comment on JENKINS-38996
Re: Java on Jenkins crashes unexpectedly
Interesting info: ``` {noformat} --- T H R E A D ---Current thread (0x14796800): JavaThread "Handling GET /jenkins/job/NBS/job/02_DiffLog/descriptorByName/jenkins.plugins.publish_over_ssh.BapSshRetry/checkRetries from 10.244.17.37 : http-nio-8080-exec-10" daemon [_thread_in_Java, id=10040, stack(0x2b31e7cfc000,0x2b31e7dfd000)]Register to memory mapping:RAX=0x0006c38079d0 is an oopruby.RubyPlugin - klass: 'ruby/RubyPlugin'RBX={method} {0x2b31d3ca7100} 'castReference' '(Ljava/lang/Class;Ljava/lang/Object;)Ljava/lang/Object;' in 'java/lang/invoke/MethodHandleImpl'RCX=0x2b31baa6c440 is at begin+12 in a stubMethodHandle::interpreter_entry::_linkToStatic [0x2b31baa6c434, 0x2b31baa6c458[ (36 bytes)RDX=0x0006c38079d0 is an oopruby.RubyPlugin - klass: 'ruby/RubyPlugin'RSP=0x2b31e7df5ba0 is pointing into the stack for thread: 0x14796800RBP=0x2b31ea053c10 is pointing into metadataRSI=0x0007c08d63b0 is pointing into metadataRDI=0x0007c000b4b8 is pointing into metadataR8 =0x0030 is an unknown valueR9 =0x0006c25b7140 is an oopjava.lang.Class - klass: 'java/lang/Class'R10=0x0007c02fe058 is pointing into metadataR11=0xf811ac76 is an unknown valueR12=0x is an unknown valueR13=0x2b31e7df5b90 is pointing into the stack for thread: 0x14796800R14=0x2b31e7df5c48 is pointing into the stack for thread: 0x14796800R15=0x14796800 is a thread ``` {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38996) Java on Jenkins crashes unexpectedly
Title: Message Title
Oleg Nenashev commented on JENKINS-38996
Re: Java on Jenkins crashes unexpectedly
Interesting info: ``` --- T H R E A D --- Current thread (0x14796800): JavaThread "Handling GET /jenkins/job/NBS/job/02_DiffLog/descriptorByName/jenkins.plugins.publish_over_ssh.BapSshRetry/checkRetries from 10.244.17.37 : http-nio-8080-exec-10" daemon [_thread_in_Java, id=10040, stack(0x2b31e7cfc000,0x2b31e7dfd000)] Register to memory mapping: RAX=0x0006c38079d0 is an oop ruby.RubyPlugin
klass: 'ruby/RubyPlugin' RBX= {method} {0x2b31d3ca7100} 'castReference' '(Ljava/lang/Class;Ljava/lang/Object;)Ljava/lang/Object;' in 'java/lang/invoke/MethodHandleImpl' RCX=0x2b31baa6c440 is at begin+12 in a stub MethodHandle::interpreter_entry::_linkToStatic [0x2b31baa6c434, 0x2b31baa6c458[ (36 bytes) RDX=0x0006c38079d0 is an oop ruby.RubyPlugin
klass: 'ruby/RubyPlugin' RSP=0x2b31e7df5ba0 is pointing into the stack for thread: 0x14796800 RBP=0x2b31ea053c10 is pointing into metadata RSI=0x0007c08d63b0 is pointing into metadata RDI=0x0007c000b4b8 is pointing into metadata R8 =0x0030 is an unknown value R9 =0x0006c25b7140 is an oop java.lang.Class
klass: 'java/lang/Class' R10=0x0007c02fe058 is pointing into metadata R11=0xf811ac76 is an unknown value R12=0x is an unknown value R13=0x2b31e7df5b90 is pointing into the stack for thread: 0x14796800 R14=0x2b31e7df5c48 is pointing into the stack for thread: 0x14796800 R15=0x14796800 is a thread ```
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39044) NPE thrown when firing upstream jobs
Title: Message Title Oleg Nenashev commented on JENKINS-39044 Re: NPE thrown when firing upstream jobs On the other hand, https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java#L139 assumes that threshold is somehow not specified in your job Please provide your job configuration. Do you also use any Job Generators to create such config? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38330 Use the declarative model to show all stages and parallels to be executed Change By: James Dumay Sprint: pacific, 1.0-b05/b-06, tasman arctic Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay started work on JENKINS-38330 Change By: James Dumay Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay updated JENKINS-38330 Jenkins / JENKINS-38330 Use the declarative model to show all stages and parallels to be executed Change By: James Dumay Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39044) NPE thrown when firing upstream jobs
Title: Message Title Oleg Nenashev edited a comment on JENKINS-39044 Re: NPE thrown when firing upstream jobs It is a bug in the ReverseBuildTrigger plugin. Jenkins API explicitly prohibits passing null: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Result.java#L129-L131 . Hence there is a bug in the core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39044) NPE thrown when firing upstream jobs
Title: Message Title Oleg Nenashev commented on JENKINS-39044 Re: NPE thrown when firing upstream jobs It is a bug in the ReverseBuildTrigger plugin. Jenkins API explicitly prohibits passing null: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Result.java#L129-L131 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39311) Create Job form not visible on Windows multiple browser
Title: Message Title Daniel Beck commented on JENKINS-39311 Re: Create Job form not visible on Windows multiple browser Is this locale dependent? What happens if you configure your browser to send en or en_US as Accept-Language? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39054) Shell interpreter doesn't work on windows when PATH to sh.exe contains a space
Title: Message Title Oleg Nenashev commented on JENKINS-39054 Re: Shell interpreter doesn't work on windows when PATH to sh.exe contains a space ping Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39163) Not able to delete agent
Title: Message Title Oleg Nenashev commented on JENKINS-39163 Re: Not able to delete agent Please provide a full stacktrace. The interesting part is missing Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39125) Windows: Cannot change Maven custom tool installer due to slave file locking
Title: Message Title Oleg Nenashev commented on JENKINS-39125 Re: Windows: Cannot change Maven custom tool installer due to slave file locking Ping Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39360) Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins
Title: Message Title Oleg Nenashev commented on JENKINS-39360 Re: Allow ALLOWED_JNLPJARS_FILES to be configurable by plugins Originally there was a plan to make it configurable, but the approach has been rejected by the Security team IIRC. CC Daniel Beck Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39164) CommandInterpreter return value fix: causes incompatibility with Env-inject plugin in Jenkins v2.26
Title: Message Title Daniel Beck commented on JENKINS-39164 Re: CommandInterpreter return value fix: causes incompatibility with Env-inject plugin in Jenkins v2.26 Cannot reproduce. Pristine Jenkins 2.30 instance. Install Envinject 1.93.1. Create a freestyle job with the following configuration: false return [foo: bar, baz: qux] false true true true false true false false false false env Build output (excerpt, removed useless variables from env output): Started by user admin [EnvInject] - Loading node environment variables. [EnvInject] - Preparing an environment for the build. [EnvInject] - Keeping Jenkins system variables. [EnvInject] - Keeping Jenkins build variables. [EnvInject] - Evaluating the Groovy script content [EnvInject] - Injecting contributions. Building in workspace /Users/danielbeck/JENKINS-39164-Home/workspace/JENKINS-39164 [JENKINS-39164] $ /bin/sh -xe /var/folders/39/ggldtdps6034ct7d_y6x4_v8gn/T/hudson3991272038220173596.sh + env SHELL=/bin/bash TERM=xterm-256color CLICOLOR=yes BUILD_TAG=jenkins-JENKINS-39164-1 USER=danielbeck baz=qux JOB_NAME=JENKINS-39164 foo=bar EXECUTOR_NUMBER=1 NODE_LABELS=master BUILD_NUMBER=1 Finished: SUCCESS So… how can this issue be reproduced? Or what else am I missing? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38330) Use the declarative model to show all stages and parallels to be executed
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-38330 Use the declarative model to show all stages and parallels to be executed Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title Oleg Nenashev commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" The fix has been integrated towards jenkins-2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38692) Add extra fine grained logging to JNLPv4 protocol
Title: Message Title Oleg Nenashev commented on JENKINS-38692 Re: Add extra fine grained logging to JNLPv4 protocol The fix has been integrated towards jenkins-2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev edited a comment on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics The fix has been integrated towards jenkins- 2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title Oleg Nenashev commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug The fix has been integrated towards jenkins-2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39543) Improve the caller/callee correlation diagnostics
Title: Message Title Oleg Nenashev commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics The fix has been integrated towards 2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38692) Add extra fine grained logging to JNLPv4 protocol
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38692 Re: Add extra fine grained logging to JNLPv4 protocol Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39289) Better diagnostics on "Backing channel is disconnected"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39289 Re: Better diagnostics on "Backing channel is disconnected" Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39150) Improve remoting channel diagnostics in Support Core
Title: Message Title Oleg Nenashev commented on JENKINS-39150 Re: Improve remoting channel diagnostics in Support Core The fix on the remoting side has been integrated towards 2.31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39543) Improve the caller/callee correlation diagnostics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39543 Re: Improve the caller/callee correlation diagnostics Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39617) Remoting Engine will fail to establish connection if one of the parameter URLs is malformed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39617 Re: Remoting Engine will fail to establish connection if one of the parameter URLs is malformed Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39596) JNLPSlave fails to connect with Java WebStart call
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39596 Re: JNLPSlave fails to connect with Java WebStart call Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39290) Provide escape hatch for a possible NIO remoting bug
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39290 Re: Provide escape hatch for a possible NIO remoting bug Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39617) Remoting Engine will fail to establish connection if one of the parameter URLs is malformed
Title: Message Title Oleg Nenashev resolved as Fixed The fix has been integrated towards 2.31 Jenkins / JENKINS-39617 Remoting Engine will fail to establish connection if one of the parameter URLs is malformed Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-39150) Improve remoting channel diagnostics in Support Core
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39150 Re: Improve remoting channel diagnostics in Support Core Code changed in jenkins User: Oleg Nenashev Path: pom.xml http://jenkins-ci.org/commit/jenkins/7a948d399585d201c4132597aed5723a495acf69 Log: Update remoting to 2.31 in the Jenkins core. (#2628) The change introduces one serious bugfix (JENKINS-39596) and a bunch of various diagnostics improvements. Bugfixes: JENKINS-39596(https://issues.jenkins-ci.org/browse/JENKINS-39596) - Jenkins URL in `hudson.remoting.Engine` was always `null` since `3.0`. It was causing connection failures of Jenkins JNLP agents when using Java Web Start. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) JENKINS-39617(https://issues.jenkins-ci.org/browse/JENKINS-39617) - `hudson.remoting.Engine` was failing to establish connection if one of the URLs parameter in parameters was malformed. (PR #131(https://github.com/jenkinsci/remoting/pull/131)) Improvements: JENKINS-39150(https://issues.jenkins-ci.org/browse/JENKINS-39150) - Add logic for dumping diagnostics across all the channels. (PR #122(https://github.com/jenkinsci/remoting/pull/122), PR #125(https://github.com/jenkinsci/remoting/pull/125)) JENKINS-39543(https://issues.jenkins-ci.org/browse/JENKINS-39543) - Improve the caller/callee correlation diagnostics in thread dumps. (PR #119(https://github.com/jenkinsci/remoting/pull/119)) JENKINS-39290(https://issues.jenkins-ci.org/browse/JENKINS-39290) - Add the `org.jenkinsci.remoting.nio.NioChannelHub.disabled` flag for disabling NIO (mostly for debugging purposes). (PR #123(https://github.com/jenkinsci/remoting/pull/123)) JENKINS-38692(https://issues.jenkins-ci.org/browse/JENKINS-38692) - Add extra logging to help diagnosing `IOHub` Thread spikes. (PR #116(https://github.com/jenkinsci/remoting/pull/116)) JENKINS-39289(https://issues.jenkins-ci.org/browse/JENKINS-39289) - When a proxy fails, report what caused the channel to go down. (PR #128(https://github.com/jenkinsci/remoting/pull/128)) Add Comment
[JIRA] (JENKINS-39596) JNLPSlave fails to connect with Java WebStart call
Title: Message Title Oleg Nenashev updated JENKINS-39596 The fix has been intergrated towards 2.31 Jenkins / JENKINS-39596 JNLPSlave fails to connect with Java WebStart call Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Elmar Weber commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails I forgot: They get however cleaned up after a while, I think around 12h or so automatically. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
