[JIRA] (JENKINS-56764) Pipeline fails on some AMI images / node types because of Broken Pipe
Title: Message Title Alexander Bachmeier updated an issue Jenkins / JENKINS-56764 Pipeline fails on some AMI images / node types because of Broken Pipe Change By: Alexander Bachmeier Environment: Jenkins ver. 2.164.1, kubernetes plugin 0.2.3, Kubernetes 1.12 Jenkins ver 2.190.1, Kubernetes plugin 1.21.2, EKS 1.14.9 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.8417.1579075980317%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Gregory PICOT commented on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Hi, Thank Alexander Komarov for the retry bit, we tried it on our end to secure the jnlp connexion. The retry in itself seem to work great, but since we implemented it, our containers are not stopped properly on jobs end : The kill -15 sent on job termination is not interpreted by the container, and we have to wait 10 sec for the kill -9 to really put an end to the container. This is problematic because we have a small window where the master believe the container (and the agent related) is free to use. It could then try to start a job in it, with no chance to last long. What I could figure out is that since the entrypoint is the new script, when the $ACTUAL_ENTRYPOINT is run, it is not the PID1. When the kill -15 occur, not every process are killed, so the container stays alive. I tried to add the exec command before runnning the $ACTUAL_ENTRYPOINT, it resolve the issue of the sigterm interpretation, but we loose the retry logic... I'm still trying to figure out a solution to torward properly sigterms and keep the retry. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8423.1579076220234%40Atlassian.JIRA.
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Robin Karlsson commented on JENKINS-59259 Re: sshAgent step does not survive agent disconnect/reconnect Jon Sten I've installed the attached build and confirmed that it fixes the problem. Thanks! I also found the following in the build console log, so your suspicion about JNR being used was correct: [Pipeline] sshagent 09:26:28 [ssh-agent] Using credentials jenkins (jenkins ssh key) 09:26:28 [ssh-agent] Looking for ssh-agent implementation... 09:26:28 [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) 09:26:28 $ docker exec fd174bb2336438837e17a078f3ed4072e094f1333a515a28e0ddb6f28f5c6907 ssh-agent 09:26:28 [ssh-agent] Java/JNR ssh-agent 09:26:29 [ssh-agent] Registered BouncyCastle on the remote agent 09:26:30 [ssh-agent] Started. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.8434.1579077240339%40Atlassian.JIRA.
[JIRA] (JENKINS-60777) not able to use wget.exe in jenkins windows batch command
Title: Message Title Shikha Saran closed an issue as Done Jenkins / JENKINS-60777 not able to use wget.exe in jenkins windows batch command Change By: Shikha Saran Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204038.1579066702000.8438.1579078200313%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-60736
Re: Add posibility to obtain SAML assertion after login using SAML plugin
I do not want to enter on details, I will give you a code to leak any environment variable you have on your jobs, this will workaround the mask on the logs and expose any sensitive information you have in an environment variable by putting a whitespace between characters ('123456' -> '1 2 3 4 5 6'), not think if it could be a security issue in your organization or not, in many it is.
python -c "print ' '.join('${ENV_VAR}'[::1])"
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.8440.1579078380523%40Atlassian.JIRA.
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Jon Sten commented on JENKINS-59259 Re: sshAgent step does not survive agent disconnect/reconnect Great, good to hear! Jesse made an official release of the fix yesterday, so you could use that one now, version 1.19. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.8443.1579078740183%40Atlassian.JIRA.
[JIRA] (JENKINS-60758) Is there a way to override indexes in metadata.properties to use custom index ?
Title: Message Title Ted Xiao updated JENKINS-60758 Jenkins / JENKINS-60758 Is there a way to override indexes in metadata.properties to use custom index ? Change By: Ted Xiao Status: Open Fixed but Unreleased Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204018.1578990862000.8447.1579078981886%40Atlassian.JIRA.
[JIRA] (JENKINS-60758) Is there a way to override indexes in metadata.properties to use custom index ?
Title: Message Title Ted Xiao commented on JENKINS-60758 Re: Is there a way to override indexes in metadata.properties to use custom index ? It is documented on https://plugins.jenkins.io/splunk-devops Configure Metadata section Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204018.1578990862000.8445.1579078981348%40Atlassian.JIRA.
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Artem Gryshyn commented on JENKINS-59560 Re: NPE exception on pipeline checkout step (Pipeline multibranch) Devin Nusbaum tnx, your changes fixed NPE. I tested my case with multibranch pipeline and single pipeline, nothing has broken. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202193.1569582707000.8449.1579079520562%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Gregory PICOT edited a comment on JENKINS-59790 Re: Container cannot connect to node because it doesn't exist Hi,Thank [~akom] for the retry bit, we tried it on our end to secure the jnlp connexion. The retry in itself seem seems to work great, but since we implemented it, our containers are not stopped properly on jobs doesn't end properly :The kill -15 sent on job termination is not correctly interpreted by the container, and we have to wait 10 sec for the a kill -9 to really put an end to the container.This is problematic because we have a small window where the master believe the container (and the agent related) is free to use. It could then try to start a job in it, with no chance to last long.What I could figure out is that since the entrypoint is the new script, when the $ACTUAL_ENTRYPOINT is run, it is not the PID1 PID 1, and the jar is not linked to our new entrypoint (since is it started by exec command) .When the kill -15 occur, not every process are killed, so the container stays alive.I tried to add the exec command before runnning the $ACTUAL_ENTRYPOINT, it resolve the issue of the sigterm interpretation, but we loose the retry logic...I'm still trying to figure out a solution to torward properly sigterms and keep the retry. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.goog
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title ethorsa commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO So this can be closed I guess. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.8461.1579083721703%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title ethorsa commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO So this can be closed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.8474.1579083721997%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title ethorsa edited a comment on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO So this can be closed ? I guess. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.8497.1579083722286%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title ethorsa updated an issue Jenkins / JENKINS-58207 2.181 JNA update breaks NegotiateSSO Change By: ethorsa Comment: So this can be closed I guess. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.8500.1579083722324%40Atlassian.JIRA.
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title Markus Stoll commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO I explicitly tested again with installing v1.4 using the jenkins plugin manager. Everything is working like a charme for me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200266.1561541748000.8513.1579083840524%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Alexander Karpov commented on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects We also have the problem. We use Jenkins v 2.204.1 and HashiCorp Vault Plugin v 3.0.0 and Hashicorp Vault Pipeline 1.3 The problem is very serious for us. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202571.1571380365000.8526.1579084140824%40Atlassian.JIRA.
[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter
Title: Message Title Max Matissek created an issue Jenkins / JENKINS-60779 Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter Issue Type: Bug Assignee: Devin Nusbaum Components: pipeline-build-step-plugin Created: 2020-01-15 10:50 Priority: Trivial Reporter: Max Matissek The Pipeline build step logs a message after Updating zu Version 2.10. Example: Pipeline-Command: build job: 'testjob', parameters: [string(name: 'SELECTEDVERSION', value: artifactUrl)] After the update of the "Pipeline: Build Step" Plugin to Verison 2.10 I get the Message "The parameter 'SELECTEDVERSION' did not have the type expected by testjob. Converting to Extensible Choice". There was suggestion to create a bug for that in JENKINS-60216. Add Comment
[JIRA] (JENKINS-60216) Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible
Title: Message Title Max Matissek commented on JENKINS-60216 Re: Pipeline Build Step should automatically convert mistyped parameters to the correct type where possible Devin Nusbaum I've created Bug JENKINS-60779 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203189.1574194043000.8552.1579085520803%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title Christian Häussler created an issue Jenkins / JENKINS-60780 support unlimited subfolder hierarchy Issue Type: Bug Assignee: John Flynn Components: requests-plugin Created: 2020-01-15 11:36 Environment: CloudBees Jenkins Enterprise 2.164.32.0.1-fixed Priority: Critical Reporter: Christian Häussler We are using no flat folder hierarchy which leads to pending requests deleting not the job itself but everything under the top two folders resulting in accidently deleting several subfolders/jobs at once. -> extend HttpResponse doCreateXXXRequest(StaplerRequest request, StaplerResponse response) functions to support unlimited subfolder hierarchy Add Comment
[JIRA] (JENKINS-60781) support a list of email addresses
Title: Message Title Christian Häussler updated an issue Jenkins / JENKINS-60781 support a list of email addresses Change By: Christian Häussler Priority: Critical Minor We are using no flat folder hierarchy which leads Currently it is only possible to pending requests deleting not the job itself but everything under the top two folders resulting in accidently deleting several subfolders/jobs at once set one admin email address . In our company we have several Jenkins Admins we would like to inform -> extend HttpResponse doCreateXXXRequest(StaplerRequest request, StaplerResponse response) functions the field to support unlimited subfolder hierarchy a (comma separated?) list of email addresses Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this messa
[JIRA] (JENKINS-60781) support a list of email addresses
Title: Message Title Christian Häussler created an issue Jenkins / JENKINS-60781 support a list of email addresses Issue Type: Bug Assignee: John Flynn Components: requests-plugin Created: 2020-01-15 11:37 Environment: CloudBees Jenkins Enterprise 2.164.32.0.1-fixed Priority: Critical Reporter: Christian Häussler We are using no flat folder hierarchy which leads to pending requests deleting not the job itself but everything under the top two folders resulting in accidently deleting several subfolders/jobs at once. -> extend HttpResponse doCreateXXXRequest(StaplerRequest request, StaplerResponse response) functions to support unlimited subfolder hierarchy Add Comment
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Artem Gryshyn commented on JENKINS-59560 Re: NPE exception on pipeline checkout step (Pipeline multibranch) Devin Nusbaum I'm not sure I get you right, but if you mean Pipeline: Job - version is 2.35 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202193.1569582707000.8589.1579088820205%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title Oleg Nenashev commented on JENKINS-60725 Re: "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 FYI Ramon Leon Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8601.1579089900158%40Atlassian.JIRA.
[JIRA] (JENKINS-60682) Improve scriptApproval ux
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60682 Improve scriptApproval ux Change By: Oleg Nenashev Component/s: script-security-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203926.1578432846000.8603.1579089960197%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60678 ComputerLauncher: Detection of AdoptOpenJDK 11 fails Change By: Oleg Nenashev Labels: java11-compatibility Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203922.1578411341000.8605.1579089960280%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60725 "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Change By: Oleg Nenashev Labels: adoptopenjdk java11 java11-compatibility Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8607.1579090020183%40Atlassian.JIRA.
[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running linux container under windows host
Title: Message Title
Robert Hecker commented on JENKINS-60473
Re: Docker pipeline: 'absolute path' error when running linux container under windows host
Hello Together, in the meantime i found more details why it is not working on a Jenkins Master which is installed on Windows. I got now extended messages on the execution log, which points more clearer to the Problem. The interesting part of the log is:
[Pipeline] withDockerContainer
Jenkins does not seem to be running inside a container
$ docker run -d -t -w /d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test/ -v D:/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test/:/d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test/ -v D:/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test@tmp/:/d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test@tmp/ -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e node:7-alpine cat
$ docker top 0c8e23cea55f3e827eb013a74fed9b28e0585a5a243bef9ec897441dfc320a60
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] sh
sh: can't create /d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test@tmp/durable-f0f56139/jenkins-log.txt: nonexistent directory
sh: can't create /d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test@tmp/durable-f0f56139/jenkins-result.txt.tmp: nonexistent directory
mv: can't rename '/d/Sandbox_GIT/Jenkins_Plugin/docker-workflow-plugin-master/work/workspace/test@tmp/durable-f0f56139/jenkins-result.txt.tmp': No such file or directory
process apparently never started in D:\Sandbox_GIT\Jenkins_Plugin\docker-workflow-plugin-master\work\workspace\test@tmp\durable-f0f56139
[Pipeline] }
For me it seems that some folders are not existing, and due this he can not create the file. Following 2 Folders exist on my Windows Master:
D:\Sandbox_GIT\Jenkins_Plugin\docker-workflow-plugin-master\work\workspace\test
D:\Sandbox_GIT\Jenkins_Plugin\docker-workflow-plugin-master\work\workspace\test@tmp
What needs to be changed in the Plugin, to get this working?
Add Comment
[JIRA] (JENKINS-60381) Remove old, deprecated remoting protocols
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-60381 Remove old, deprecated remoting protocols Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203430.1575564508000.8610.1579090080524%40Atlassian.JIRA.
[JIRA] (JENKINS-59220) Implement a method in EnvVars that extends putAll() to filter null values
Title: Message Title Oleg Nenashev updated JENKINS-59220 Jenkins / JENKINS-59220 Implement a method in EnvVars that extends putAll() to filter null values Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201671.1567592904000.8624.1579090147559%40Atlassian.JIRA.
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Oleg Nenashev updated JENKINS-59412 Jenkins / JENKINS-59412 Clarify that build history does not include pipeline stages Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201973.1568739433000.8618.1579090147449%40Atlassian.JIRA.
[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp
Title: Message Title Oleg Nenashev updated JENKINS-60634 Jenkins / JENKINS-60634 Define WORKSPACE_TMP=.../workspace/jobname@tmp Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203871.157808103.8621.1579090147499%40Atlassian.JIRA.
[JIRA] (JENKINS-60579) Impossible to have an invisible property on View that is persisted on save
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-60579 Impossible to have an invisible property on View that is persisted on save Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203704.1577183535000.8626.1579090210367%40Atlassian.JIRA.
[JIRA] (JENKINS-60579) Impossible to have an invisible property on View that is persisted on save
Title: Message Title Oleg Nenashev commented on JENKINS-60579 Re: Impossible to have an invisible property on View that is persisted on save A. Jard if you would like ti get it backported to LTS, please mark it as an LTS candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203704.1577183535000.8628.1579090212368%40Atlassian.JIRA.
[JIRA] (JENKINS-42658) computer.getOSDescription() throws NPE if slave is off-line
Title: Message Title Oleg Nenashev updated JENKINS-42658 Jenkins / JENKINS-42658 computer.getOSDescription() throws NPE if slave is off-line Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179609.1489149605000.8634.1579090212889%40Atlassian.JIRA.
[JIRA] (JENKINS-42658) computer.getOSDescription() throws NPE if slave is off-line
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-42658 computer.getOSDescription() throws NPE if slave is off-line Change By: Oleg Nenashev Labels: lts-candidate newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179609.1489149605000.8631.1579090212827%40Atlassian.JIRA.
[JIRA] (JENKINS-56152) Improve dependency errors message
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-56152 Improve dependency errors message Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.214 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197598.1550189094000.8636.1579090260246%40Atlassian.JIRA.
[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames
Title: Message Title Ronny Borchert commented on JENKINS-51285 Re: Active Directory plugin does not work with scandic usernames With TFS plugin and latest of all version I got this too, seems a connection issue. FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.com
[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames
Title: Message Title
Ronny Borchert edited a comment on JENKINS-51285
Re: Active Directory plugin does not work with scandic usernames
With TFS plugin and latest of all version I got this too, seems a connection issue.{noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java. util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java. net.ConnectException: Connection timed out: connect ]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203) Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.goog
[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames
Title: Message Title
Ronny Borchert edited a comment on JENKINS-51285
Re: Active Directory plugin does not work with scandic usernames
With TFS plugin and latest of all version I got this too, seems a connection issue. Our Jenkins is running on Windows Server. {noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965
[JIRA] (JENKINS-51285) Active Directory plugin does not work with scandic usernames
Title: Message Title
Ronny Borchert edited a comment on JENKINS-51285
Re: Active Directory plugin does not work with scandic usernames
With TFS plugin and latest of all version I got this too, seems a connection issue. Our Jenkins is running on Windows Server. I ask our IT and told me that DC was down for this time. {noformat}FATAL: hudson.plugins.active_directory.CacheAuthenticationException: Authentication failed because there was a problem caching user DOMAIN\NAME; nested exception is java.util.concurrent.ExecutionException: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect]java.net.ConnectException: Connection timed out: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.reflect.GeneratedMethodAccessor644.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.sun.jndi.ldap.Connection.createSocket(Connection.java:350) at com.sun.jndi.ldap.Connection.(Connection.java:203)Caused: javax.naming.CommunicationException: url.url.url.com:3268 [Root exception is java.net.ConnectException: Connection timed out: connect] at com.sun.jndi.ldap.Connection.(Connection.java:216) at com.sun.jndi.ldap.LdapClient.(LdapClient.java:137) at com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1615) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749) at com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319) at com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192) at com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:151) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:668) at hudson.plugins.active_directory.ActiveDirectorySecurityRealm$DescriptorImpl.bind(ActiveDirectorySecurityRealm.java:599) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:370) at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider$1.call(ActiveDirectoryUnixAuthenticationProvider.java:340) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350)Caused: java.util.concurrent.ExecutionException at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289) at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276) at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111) at com.google.common.util.concurrent.Uninterruptibles.getUninterruptibly(Uninterruptibles.java:132) at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2381) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at co
[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp
Title: Message Title Jesse Glick commented on JENKINS-60634 Re: Define WORKSPACE_TMP=.../workspace/jobname@tmp Resolved in core for freestyle and similar builds; PR remains open for Pipeline. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203871.157808103.8715.1579094281089%40Atlassian.JIRA.
[JIRA] (JENKINS-60634) Define WORKSPACE_TMP=.../workspace/jobname@tmp
Title: Message Title Jesse Glick updated JENKINS-60634 Jenkins / JENKINS-60634 Define WORKSPACE_TMP=.../workspace/jobname@tmp Change By: Jesse Glick Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203871.157808103.8714.1579094280938%40Atlassian.JIRA.
[JIRA] (JENKINS-60686) Communication problem jenkins <=> slave due to: Illegal base64 character 2a (probably in console output ?)
Title: Message Title Jose Carlos Alavez Gonzalez commented on JENKINS-60686 Re: Communication problem jenkins <=> slave due to: Illegal base64 character 2a (probably in console output ?) We have the same issue in Jenkins 2.204.1 but with: java.lang.IllegalArgumentException: Illegal base64 character 20 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203930.1578473868000.8718.1579095300351%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-60725 "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8722.1579095421266%40Atlassian.JIRA.
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Fabian Bosch commented on JENKINS-60342 Re: Include support to BitBucket Pull Request +1 for this featureRequest. please consider to increase priority on this one. seems to me like this would be the biggest benefit compared to other 3rd party plugins and reason to use it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203356.157528517.8727.1579095540828%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title
Ramon Leon commented on JENKINS-60725
Re: "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Hi ethorsa, yes, it's telemetry. Although the information is not sent because the statistics are disabled, Jenkins warn you using the log. This symptom is because a plugin is using this class and AdoptOpenJDK doesn't have it, because it's sun's specific implementation. It may be a problem or not, it depends on the root cause. I would need the stack traces to be able to analyze each missed class. For the first stack trace from Hazim Malik, it is expected: https://github.com/javamelody/javamelody/blob/master/javamelody-core/src/main/java/net/bull/javamelody/FilterContext.java#L349
private static boolean isMojarraAvailable() {
try {
Class.forName("com.sun.faces.application.ActionListenerImpl");
return true;
} catch (final Throwable e) { // NOPMD
return false;
}
}
So we should upgrade the ignored places adding this one I cannot find out any culprit from the second stack trace. Maybe Jenkins master is running on an Oracle JDK and the agent is running with AdoptOpenJDK or another one?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and st
[JIRA] (JENKINS-60770) Provide different echarts versions
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-60770 Provide different echarts versions Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/echarts-api-plugin/releases/tag/echarts-api-4.4.0-8-beta1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204031.1579027576000.8748.1579097460354%40Atlassian.JIRA.
[JIRA] (JENKINS-60770) Provide different echarts versions
Title: Message Title Ulli Hafner assigned an issue to Andreas Pabst Jenkins / JENKINS-60770 Provide different echarts versions Change By: Ulli Hafner Assignee: Ulli Hafner Andreas Pabst Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204031.1579027576000.8746.1579097460286%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60738 Override github hook url is not being saved Change By: Avihay Tsayeg Trying to override the jenkins url at "override hook url" is failing. The adress is being not saved and the original jenkins url is showed instead.This happen manually at the ui and using the jenkins as configuration code plugin . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.8754.1579098300353%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Avihay Tsayeg updated an issue Jenkins / JENKINS-60738 Override github hook url is not being saved Change By: Avihay Tsayeg Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.8756.1579098300390%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title ethorsa commented on JENKINS-60725 Re: "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 The Master and majority of the agents are running on AdopOpenJDK. However, there are some remaining Windows agents with Oracle JDK left (and of course the Linux agents are using OpenJDK). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8758.1579098540212%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title ethorsa updated an issue Jenkins / JENKINS-60725 "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Change By: ethorsa Attachment: telemetry.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8762.1579099200264%40Atlassian.JIRA.
[JIRA] (JENKINS-60686) Communication problem jenkins <=> slave due to: Illegal base64 character 2a (probably in console output ?)
Title: Message Title oliva imlinga commented on JENKINS-60686 Re: Communication problem jenkins <=> slave due to: Illegal base64 character 2a (probably in console output ?) it seems that in our case the problem occurs, if some of the post-build-actions fail. if the tests are not run on a slave (due to the up-to-date-check). then either running post-build action for collecting junit-testcase-results or code-coverage (jacoco) fails and the job ends in the error described above. of course, this is a problem within job configuration / gradle job, but it would be very nice, if the error is reported within the console in jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203930.1578473868000.8766.1579099260159%40Atlassian.JIRA.
[JIRA] (JENKINS-60725) "Added a missed class for missing class telemetry" on AdoptOpenJDK 11
Title: Message Title ethorsa commented on JENKINS-60725 Re: "Added a missed class for missing class telemetry" on AdoptOpenJDK 11 Ramon Leon I've added full stacktraces for both classes. From a first look they seem same as Hazim Malik ones. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203974.1578649121000.8768.1579099380156%40Atlassian.JIRA.
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Kalle Niemitalo commented on JENKINS-60342 Re: Include support to BitBucket Pull Request The older Bitbucket Branch Source plugin already supports the pr:opened, pr:merged, pr:declined, pr:deleted, and pr:reviewer:approved events from Bitbucket Server webhooks (HookEventType.java, NativeServerPullRequestHookProcessor.java), so this is necessary for feature parity. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203356.157528517.8773.1579099560268%40Atlassian.JIRA.
[JIRA] (JENKINS-60772) Microsoft Edge identified as Chrome
Title: Message Title evernat commented on JENKINS-60772 Re: Microsoft Edge identified as Chrome Identifying the new Microsoft Edge as a Chrome browser is not really false, as Edge says itself in its user-agent. By the way, I see that the given user agent example is Edge on Linux. Anyway, it's fixed now in javamelody-core and will be released in 1.82. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204033.1579035877000.8782.1579099620481%40Atlassian.JIRA.
[JIRA] (JENKINS-60772) Microsoft Edge identified as Chrome
Title: Message Title evernat updated JENKINS-60772 Jenkins / JENKINS-60772 Microsoft Edge identified as Chrome Change By: evernat Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204033.1579035877000.8785.1579099680307%40Atlassian.JIRA.
[JIRA] (JENKINS-57177) Add tags discovery to Blueocean dashboard
Title: Message Title Nikolay Bryskiun started work on JENKINS-57177 Change By: Nikolay Bryskiun Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198928.1556168543000.8788.1579100040901%40Atlassian.JIRA.
[JIRA] (JENKINS-57177) Add tags discovery to Blueocean dashboard
Title: Message Title Nikolay Bryskiun updated JENKINS-57177 Jenkins / JENKINS-57177 Add tags discovery to Blueocean dashboard Change By: Nikolay Bryskiun Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198928.1556168543000.8790.1579100040971%40Atlassian.JIRA.
[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter
Title: Message Title Devin Nusbaum commented on JENKINS-60779 Re: Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter I think the best thing to do in this case would be to change to this block to not log anything or change the description when the class name of the parameter definition is ExtensibleChoiceParameterDefinition. It still makes sense to do the conversion, which IIUC goes through this code to make sure the specified parameter is one of the options, we just don't want to log a warning since the conversion is expected. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204042.1579085441000.8834.1579103940566%40Atlassian.JIRA.
[JIRA] (JENKINS-60602) Bitbucket integration with Jenkins
Title: Message Title Alex Martynenko commented on JENKINS-60602 Re: Bitbucket integration with Jenkins Hi Christian Del Monte, Do you have any updates in case? Thanks in advance. Regards, Alexander Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203827.157762360.8839.1579104120809%40Atlassian.JIRA.
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Devin Nusbaum commented on JENKINS-59560 Re: NPE exception on pipeline checkout step (Pipeline multibranch) Artem Gryshyn Yes, sorry, the artifact id of the plugin is workflow-job, but the name shown to users is Pipeline: Job Plugin. What is the GitHub plugin being configured in the attached screenshot (it doesn't look like GitHub Branch Source)? That plugin should probably be updated so that it writes an empty changelog file when there are no changes instead of leaving the changelog file empty for consistency with other SCMs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202193.1569582707000.8852.1579105980124%40Atlassian.JIRA.
[JIRA] (JENKINS-60782) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Udaya Sree created an issue Jenkins / JENKINS-60782 issue_updated trigger handler can't find "name" field in JSON Issue Type: Bug Assignee: Wisen Tanasa Components: jira-trigger-plugin Created: 2020-01-15 16:37 Priority: Blocker Reporter: Udaya Sree The library that the plugin is using is not supported for Cloud, but only for Server, as you can see in the description of the code: >Java client library (useful for any JVM languages), which allows to communicate with JIRA via its new REST API (JIRA 4.2 and newer). "name" field is blocked by Jira cloud >https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/. Error: 2020-01-07 17:30:53.262+ [id=833] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkinscb2.bcbsma.com/jira-trigger-webhook-receiver/ org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser.parse(CommentJsonParser.java:37) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser.parse(WebhookCommentEventJsonParser.groovy:40) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:71) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFun
[JIRA] (JENKINS-59560) NPE exception on pipeline checkout step (Pipeline multibranch)
Title: Message Title Artem Gryshyn commented on JENKINS-59560 Re: NPE exception on pipeline checkout step (Pipeline multibranch) Devin Nusbaum this is a https://plugins.jenkins.io/github GitHub plugin, 1.29.4 version. Also used https://plugins.jenkins.io/git Git plugin, 3.12.1 version. Git plugin was downgraded to 3.12.1 from 4.0.0 because of dependency on "Pipeline: SCM" plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202193.1569582707000.8855.1579106281362%40Atlassian.JIRA.
[JIRA] (JENKINS-59790) Container cannot connect to node because it doesn't exist
Title: Message Title Mathieu Delrocq reopened an issue Jenkins / JENKINS-59790 Container cannot connect to node because it doesn't exist Change By: Mathieu Delrocq Resolution: Won't Fix Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202520.1571136505000.8859.1579106400637%40Atlassian.JIRA.
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Andrew Feller commented on JENKINS-58705 Re: Change default working dir to /home/jenkins/agent This change should have facilitated the use case without breaking backwards compatibility for everyone else as the use of the older working directory should have been noted as a deprecated expectation. It is clear it was made without any thought to the actual impact to others with no consideration of how significant it would be. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200995.1564403053000.8867.1579106640353%40Atlassian.JIRA.
[JIRA] (JENKINS-60783) Delete pipelines for archived repositories
Title: Message Title kutzi created an issue Jenkins / JENKINS-60783 Delete pipelines for archived repositories Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-01-15 16:43 Environment: Jenkins 2.190.3 Github Branch Source Plugin 2.5.8 Priority: Minor Reporter: kutzi Currently the plugin only removes pipelines for deleted repositories. Would be nice, if that could happen for archived repositories, too Add Comment
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Andrew Feller edited a comment on JENKINS-58705 Re: Change default working dir to /home/jenkins/agent This change should have facilitated the use case without breaking backwards compatibility for everyone else as the use of the older working directory should have been noted as a deprecated expectation. It is clear it was made without any thought to the actual impact to others with no consideration as there are situation where _"just use the env var"_ is not enough of how significant it would be a solution to everything . Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200995.1564403053000.8870.1579106640399%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Seweryn Habdank-Wojewodzki commented on JENKINS-60736 Re: Add posibility to obtain SAML assertion after login using SAML plugin Thank for the answer. First of all on Linux I can even more simplify the command to env to get all variables and to set on Window. There are exactly all variables in the scope of the build. There is no SAML assertion. Could you consider option (checkbox), which would allow to export SAML assertion into set of environment variables, so the Jenkisn administrator would decide to present variables or in other companies not. I agree, that default value would be not to expose assertion as environment variable. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.8887.1579112280417%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title
Seweryn Habdank-Wojewodzki edited a comment on JENKINS-60736
Re: Add posibility to obtain SAML assertion after login using SAML plugin
Thank you for the answer.First of all on Linux I can even more simplify the command to {{env}} to get all variables and to {{set}} on Window. There are exactly all variables in the scope of the build. There is no SAML assertion.Could you consider option (checkbox), which would allow to export SAML assertion into set of environment variables, so the Jenkisn administrator would decide to present variables or in other companies not. I agree, that default value would be not to expose assertion as environment variable.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.8889.1579112280453%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title
Seweryn Habdank-Wojewodzki edited a comment on JENKINS-60736
Re: Add posibility to obtain SAML assertion after login using SAML plugin
Thank you for the answer.First of all on Linux I can even more simplify the command to { color:red} { { env}} {color} to get all variables and to { color:red} { { set}} {color} on Window. There are exactly all variables in the scope of the build. There is no SAML assertion.Could you consider option (checkbox), which would allow to export SAML assertion into set of environment variables, so the Jenkisn administrator would decide to present variables or in other companies not. I agree, that default value would be not to expose assertion as environment variable.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.8891.1579112280486%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Louis-Rémi Paquet commented on JENKINS-57888 Re: Custom log format broken by 2.177 Is there a workaround to be able to provide a ConsoleHandler formatter? If not, I'll be submitting a PR removing the overriding of it. It will still be possible to set the formatter from the command line or the logging.properties as usual. What do you think? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.8894.1579112940300%40Atlassian.JIRA.
[JIRA] (JENKINS-57888) Custom log format broken by 2.177
Title: Message Title Jesse Glick commented on JENKINS-57888 Re: Custom log format broken by 2.177 The new formatter is deliberate. There could be a Winstone option to select an alternate formatter if someone cares to write it, or perhaps just by disabling the new formatter when java.util.logging.config.file is defined. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199852.1559834581000.8900.1579113300238%40Atlassian.JIRA.
[JIRA] (JENKINS-60782) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Udaya Sree updated an issue Jenkins / JENKINS-60782 issue_updated trigger handler can't find "name" field in JSON Change By: Udaya Sree The library that the plugin is using is not supported for Cloud, but only for Server, as you can see in the description of the code: >Java client library (useful for any JVM languages), which allows to communicate with JIRA via its new REST API (JIRA 4.2 and newer). "name" field is blocked by Jira cloud > [ https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/ ] . Error:2020-01-07 17:30:53.262+ [id=833] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving [ https:// abc.com/jira-trigger-webhook-receiver/|https:// jenkinscb2.bcbsma.com/jira-trigger-webhook-receiver/ ] org.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser.parse(CommentJsonParser.java:37) at com.atlassian.jira.rest.client.internal.json.CommentJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser.parse(WebhookCommentEventJsonParser.groovy:40) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.WebhookCommentEventJsonParser$parse.call(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.processEvent(JiraWebhook.groovy:71) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook$processEvent.callCurrent(Unknown Source) at com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook.doIndex(JiraWebhook.groovy:51) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) Caused: java.lang.reflect.InvocationTargetException Class used: [https://bitbucket.org/atlassian/jira-rest-java-client/src/1cb0d4e65adf8108980069b344d54d825544d70b/core/src/main/java/com/atlassian/jira/rest/client/internal/json/JsonParseUtil.java?at=jira-rest-java-client-parent-4.0.0#lines-192]Github Code: [https://github.com/jenkinsci/jira-trigger-plugin/blob/master/src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/webhook/WebhookCommentEventJsonParser.groovy#L40https://github.com/jenkinsci/jira-trigger-plugin/blob/master/src/main/groovy/com/ceilfors/jenkins/plugins/jiratrigger/webhook/WebhookCommentEventJsonParser.groovy#L40]
[JIRA] (JENKINS-60649) Bitbucket Server Integration plugin does not work for Pipelines
Title: Message Title Trung Nguyen commented on JENKINS-60649 Re: Bitbucket Server Integration plugin does not work for Pipelines Hi Martin, Thanks for providing me with the workaround. I followed it and the webhook was created in Bitbucket Server. Now when we do a push, it automatically triggers our Jenkins pipeline. Thanks, Trung Nguyen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203891.1578329007000.8910.1579114500244%40Atlassian.JIRA.
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-60736 Re: Add posibility to obtain SAML assertion after login using SAML plugin >First of all on Linux I can even more simplify the command to env to get all variables and to set on Window. I would expect at least you use credentials to define those secrets as environment variables if you do in that way env and set would not expose those env vars https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs >Could you consider option (checkbox), which would allow to export SAML assertion into set of environment variables, so the Jenkisn administrator would decide to present variables or in other companies not. Inject environment variables on jobs it is completely out of the scope of this plugin, if you want you can create a new plugin that makes only this, inject the SAML assertion in builds. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Gro
[JIRA] (JENKINS-60736) Add posibility to obtain SAML assertion after login using SAML plugin
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-60736
Re: Add posibility to obtain SAML assertion after login using SAML plugin
>First of all on Linux I can even more simplify the command to env to get all variables and to set on Window.I would expect at least you use credentials to define those secrets as environment variables if you do in that way {code} * env {code} * and {code} * set {code} * would not expose those env vars https://support.cloudbees.com/hc/en-us/articles/203802500-Injecting-Secrets-into-Jenkins-Build-Jobs>Could you consider option (checkbox), which would allow to export SAML assertion into set of environment variables,so the Jenkisn administrator would decide to present variables or in other companies not.Inject environment variables on jobs it is completely out of the scope of this plugin, if you want you can create a new plugin that makes only this, inject the SAML assertion in builds.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203989.1578680312000.8914.1579114620162%40Atlassian.JIRA.
[JIRA] (JENKINS-56564) Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException
Title: Message Title Jeff Thompson commented on JENKINS-56564 Re: Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException a b your issue sounds different from the originally reported issue. You don't mention upgrade and the use of the Remoting transport for CLI. You may be getting a similar or even the same error message, though that isn't clear. You need to create your own ticket and provide better information instead of re-opening this one. Further, I'm able to get the CLI to work fine according to the documentation and don't see the error reported earlier. This suggests that you've probably got usage or configuration problems. Possibly network or system problems. You would need to provide a reproducible issue description. The Jenkins issue tracker is not a support forum. You may get better help from the Jenkins User email list or gitter channel. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198179.1552579984000.8916.1579116480217%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Natasha Stopa commented on JENKINS-60761 Re: Plugin manager fails to load while navigating to the manage plugins view Were you using the plugin management tool to install plugins? https://github.com/jenkinsci/plugin-installation-manager-tool Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204021.1579001055000.8919.1579117320124%40Atlassian.JIRA.
[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter
Title: Message Title Devin Nusbaum commented on JENKINS-60779 Re: Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter Max Matissek This PR will eventually produce an incremental build of the plugin with the changes in the PR (I'll try to update the comment with a link later, but the link should be available from one of the GitHub statuses once the build passes). It would be great if you could test it out in a dev environment and let us know if it fixes the issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204042.1579085441000.8922.1579120440125%40Atlassian.JIRA.
[JIRA] (JENKINS-56564) Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Jenkins / JENKINS-56564 Jenkins CLI unable to create job - hudson.cli.DiagnosedStreamCorruptionException Change By: Jeff Thompson Status: Reopened Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198179.1552579984000.8924.1579120620395%40Atlassian.JIRA.
[JIRA] (JENKINS-46376) Allow getting log through RunWrapper
Title: Message Title Devin Nusbaum updated JENKINS-46376 Jenkins / JENKINS-46376 Allow getting log through RunWrapper Change By: Devin Nusbaum Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184640.1503479569000.8933.1579121221217%40Atlassian.JIRA.
[JIRA] (JENKINS-46376) Allow getting log through RunWrapper
Title: Message Title Devin Nusbaum commented on JENKINS-46376 Re: Allow getting log through RunWrapper I'm not sure about adding direct access to build logs from the Pipeline itself. We do not want to encourage users to process large amounts of data directly in their Pipelines, as that often leads to serious performance issues. It would be great to get some examples of what users are looking for in the downstream build logs (build results, errors, etc.). Maybe we could create/expose a different step for structured cross-build communications that could be used from Pipelines that would avoid the drawbacks of direct log access. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184640.1503479569000.8928.1579121221039%40Atlassian.JIRA.
[JIRA] (JENKINS-46376) Allow getting log through RunWrapper
Title: Message Title Devin Nusbaum assigned an issue to Unassigned Jenkins / JENKINS-46376 Allow getting log through RunWrapper Change By: Devin Nusbaum Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184640.1503479569000.8943.1579121280820%40Atlassian.JIRA.
[JIRA] (JENKINS-46376) Allow getting log through RunWrapper
Title: Message Title Devin Nusbaum stopped work on JENKINS-46376 Change By: Devin Nusbaum Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184640.1503479569000.8938.1579121280746%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60761 Plugin manager fails to load while navigating to the manage plugins view Change By: Mark Waite Component/s: core Component/s: plugin-installation-manager-tool Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204021.1579001055000.8951.1579121520410%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Mark Waite commented on JENKINS-60761 Re: Plugin manager fails to load while navigating to the manage plugins view This will need much more detail to describe the conditions where the problem is seen. I ran Jenkins 2.176.2 with the command: $ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.176.2 When I connected with Internet Explorer 11, Microsoft Edge, and Google Chrome, all were able to open the plugin manager successfully. Something else must be happening in the environment where this user is running Jenkins which is not happening in my test environment. The submitter will need to provide more information or we will need to close this issue as "Cannot reproduce". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204021.1579001055000.8948.1579121520370%40Atlassian.JIRA.
[JIRA] (JENKINS-60761) Plugin manager fails to load while navigating to the manage plugins view
Title: Message Title Natasha Stopa assigned an issue to Unassigned Jenkins / JENKINS-60761 Plugin manager fails to load while navigating to the manage plugins view Change By: Natasha Stopa Assignee: Natasha Stopa Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204021.1579001055000.8953.1579121760176%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title James Nord commented on JENKINS-60694 Re: JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule 9.4.5.v20170502 -> pass 9.4.5.v20180619 -> fail from the commits between v20170502 and v20180619 and (https://github.com/eclipse/jetty.project/commits/jetty-9.4.5.v20180619) https://github.com/eclipse/jetty.project/pull/2102 looks like the prime suspect as everything else looks like a bit of build fluff Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.8956.1579123020265%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203939.1578490571000.8959.1579123080157%40Atlassian.JIRA.
[JIRA] (JENKINS-60784) Maven compilation issue
Title: Message Title gabriel henrique cavalcante updated an issue Jenkins / JENKINS-60784 Maven compilation issue Change By: gabriel henrique cavalcante Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204052.1579123161000.8962.1579123200309%40Atlassian.JIRA.
[JIRA] (JENKINS-60784) Maven compilation issue
Title: Message Title gabriel henrique cavalcante created an issue Jenkins / JENKINS-60784 Maven compilation issue Issue Type: Bug Assignee: gabriel henrique cavalcante Attachments: 2020-01-15_18-17-33.jpg Components: maven-invoker-plugin Created: 2020-01-15 21:19 Priority: Major Reporter: gabriel henrique cavalcante I have this build problem and I don't know why this is happening, could you help me with this problem? Add Comment
[JIRA] (JENKINS-60784) Maven compilation issue
Title: Message Title gabriel henrique cavalcante assigned an issue to Olivier Lamy Jenkins / JENKINS-60784 Maven compilation issue Change By: gabriel henrique cavalcante Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204052.1579123161000.8965.1579123320201%40Atlassian.JIRA.
[JIRA] (JENKINS-60784) Maven compilation issue
Title: Message Title gabriel henrique cavalcante assigned an issue to Unassigned Jenkins / JENKINS-60784 Maven compilation issue Change By: gabriel henrique cavalcante Assignee: gabriel henrique cavalcante Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204052.1579123161000.8963.1579123320128%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Jeff Richards commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths I also had this problem. In my case, I was running jenkins in a linux environment, Jenkins version 2.190.3 Branch API Plugin Version 2.5.5. This is a multibranch pipeline buidl environment with agents doing the building. In my case interestingly this was only happening on 1 of three nodes (it took me hours to figure THAT out). After much searching what I found was that when I reviewed the node log for the failing node (Manage Jenkins -> Manage Nodes -> click on node in question -> Log, I found that the /home/jenkins/workspace/workspace.txt file was noted as being corrupt. For whatever reason this meant that when the build was attempted on that node, the build directory was not the usual workspace directory (which has all branch name slashes (encoded as %2F) cases replaced with underscores). In my case, I just creaed a new workspace.txt file and then disconnected and reconnected the node. And... things started working again. So, if you're experiencing this, review the node logs. As a suggestion for improving jenkins, I would suggest that if the workspaces.txt file is corrupt, the node should be taken offline. At least then the admin has a clue that this is a node based issue, and that the node needs manual intervention for things to get back to normal. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving ema
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Tim Black commented on JENKINS-51307
Re: Declarative pipeline and docker entrypoint
Sebastian Schuberth, regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful. For example, the following pipeline code:
docker_image.inside("") { ... }
results in the following docker run command, which has inserted a cat command at the end.
docker run -t -d -u 118:124 cat
I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view th
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Tim Black edited a comment on JENKINS-51307
Re: Declarative pipeline and docker entrypoint
[~sschuberth], regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful.For example, the following pipeline code: {code:java}docker_image.inside("") { ... }{code} results in the following docker run command, which has inserted a {{cat}} command at the end. {code:java}docker run -t -d -u 118:124 cat {code}I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190642.152632149.8998.1579123680488%40Atlassian.JIRA.
[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Jesse Glick commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths I would suggest that if the workspaces.txt file is corrupt, the node should be taken offline. Better to file this as an Enhancement with label robustness in this component and Link to this issue. Of course better would be to automatically correct a corrupted file, and better still would be to figure out what corrupted it to begin with. What did the supposedly corrupt file contain? Any known steps to reproduce? Etc. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195445.1542295531000.9011.1579123800342%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title John Flynn commented on JENKINS-60780 Re: support unlimited subfolder hierarchy Thank you for the logging the issue. The issue has been fixed and should support more than one level of folder views. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204043.1579088195000.9027.1579123980369%40Atlassian.JIRA.
[JIRA] (JENKINS-60780) support unlimited subfolder hierarchy
Title: Message Title John Flynn resolved as Fixed Fixed in version 2.2.2 Jenkins / JENKINS-60780 support unlimited subfolder hierarchy Change By: John Flynn Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/requests-plugin/blob/requests-2.2.2/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message beca
