[JIRA] (JENKINS-53148) downstream job nolonger triggered
Title: Message Title dan tran commented on JENKINS-53148 Re: downstream job nolonger triggered I am not able to scale down to reproduce the issue. Ended up to install latest pipeline-maven-plugin and enable org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener to finer to trouble shoot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title John Arnold commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume Devin Nusbaum See https://issues.jenkins-ci.org/secure/attachment/43981/867.tar.gz for a build folder. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title John Arnold updated an issue Jenkins / JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume Change By: John Arnold Attachment: 867.tar.gz Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53377) pipeline zip step fails with absolute path
Title: Message Title
Mark Pictor created an issue
Jenkins / JENKINS-53377
pipeline zip step fails with absolute path
Issue Type:
Bug
Assignee:
rsandell
Components:
pipeline-utility-steps-plugin
Created:
2018-08-31 23:19
Priority:
Minor
Reporter:
Mark Pictor
It appears that the zip step prepends an absolute path to the zip file name when trying to upload, resulting in an error if you passed in an absolute path. In scripted jenkinsfile:
zip zipFile: "${WORKSPACE}/my.zip", archive: true, dir: "${WORKSPACE}/some/dir"
Console output:
...
[Pipeline] zip
Writing zip file of /var/build/workspace/job_branch-123random123/some/dir to /var/build/workspace/job_branch-123random123/my.zip
Zipped 7 entries.
Archiving /var/build/workspace/job_branch-123random123/my.zip
Retrying upload after: java.io.FileNotFoundException: /var/build/workspace/job_branch-123random123/var/build/workspace/job_branch-123random123/my.zip (No such file or directory)
### Retry repeats many times ###
Retrying upload after: java.io.FileNotFoundException: /var/build/workspace/job_branch-123random123/var/build/workspace/job_branch-123random123/my.zip (No such file or directory)
Aborted by User Name
[Pipeline] }
...
[JIRA] (JENKINS-51791) git polling fails to detect changes when build uses multiple repos
Title: Message Title Rob Miles commented on JENKINS-51791 Re: git polling fails to detect changes when build uses multiple repos We are experiencing this issue too, it's a major blocker for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46163) Pipeline CPS Groovy does not seem to support spread '*' operator
Title: Message Title Justin Rainwater commented on JENKINS-46163 Re: Pipeline CPS Groovy does not seem to support spread '*' operator I just ran into this as well and I'm disappointed to see this was closed as a dupe when it's a different command. Any solution Andrew Bayer? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53376) Dimensions Build error
Title: Message Title lee myungsun created an issue Jenkins / JENKINS-53376 Dimensions Build error Issue Type: Bug Assignee: Unassigned Components: dimensionsscm-plugin Created: 2018-08-31 22:11 Environment: window7(x86) jdk1.8 dimensions14.3.1 explorer11 Priority: Minor Reporter: lee myungsun Started by user ITSM Admin Building in workspace C:\Jenkins\workspace\test [DIMENSIONS] Running checkout on master... [DIMENSIONS] Running build in 'C:\Jenkins\workspace\test'... [DIMENSIONS] Checking out project "030:303_xxx_PJT"... [DIMENSIONS] Checking out directory 'C:\Users\\buildtest'... FATAL: Unable to run checkout callout (IOException: Exception during checkout (DimensionsRuntimeException: Dimensions command 'UPDATE /BRIEF /DIR="C:\Users\\buildtest"/WORKSET="030:303_xxx_PJT" /PERMS=WRITABLE/USER_DIR="C:\Jenkins\workspace\test" /OVERWRITE /NOMETADATA' failed (DimensionsRuntimeException: Using Current Project '030:303__PJT'. Using 'C:\Jenkins\workspace\test\' as the Project work area. Warning: Path 'C:\Users\mingxuan.li\buildtest' is invalid (it cannot be mapped to the root location 'C:\Jenkins\workspace\test\') COR0006431E Error: Directory Path 'C:\Users\\buildtest' is invalid. Getting Project: 0.02 sec ))) Finished: FAILURE
[JIRA] (JENKINS-50947) Could not attach 'nodes/master/pipeline-timings.txt' to support bundle
Title: Message Title Joshua Hoblitt commented on JENKINS-50947 Re: Could not attach 'nodes/master/pipeline-timings.txt' to support bundle I'm see the same exception: Could not attach ''nodes/master/pipeline-timings.txt'' to support bundle java.io.IOException: dax/dax_webserv #1 did not yet start at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:1125) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$PipelineTimings$1.writeTo(CpsFlowExecution.java:1881) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:305) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:275) at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:759) at java.lang.Thread.run(Thread.java:748) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53375) Edit pipeline icon missing if user does not have Job.Create permission
Title: Message Title Amide tex updated an issue Jenkins / JENKINS-53375 Edit pipeline icon missing if user does not have Job.Create permission Change By: Amide tex Environment: Jenkins - 2.121.3Java - 1.8.0_181 Blue Ocean - 1.8.2 Server running on UbuntuTested on latest Firefox version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53375) Edit pipeline icon missing if user does not have Job.Create permission
Title: Message Title Amide tex assigned an issue to Amide tex Jenkins / JENKINS-53375 Edit pipeline icon missing if user does not have Job.Create permission Change By: Amide tex Assignee: Kohsuke Kawaguchi Amide tex Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42533) Trying to unexport an object that's already unexported
Title: Message Title Jeff Thompson resolved as Fixed Released in the latest 3.26 version of Remoting. Merged to go into the next Jenkins release. Jenkins / JENKINS-42533 Trying to unexport an object that's already unexported Change By: Jeff Thompson Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52945) Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2
Title: Message Title Jeff Thompson updated JENKINS-52945 Released in the latest 3.26 version of Remoting. Merged to go into the next Jenkins release. Jenkins / JENKINS-52945 Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2 Change By: Jeff Thompson Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53375) Edit pipeline icon missing if user does not have Job.Create permission
Title: Message Title Amide tex created an issue Jenkins / JENKINS-53375 Edit pipeline icon missing if user does not have Job.Create permission Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: 2018-08-31_21-59-28.png, firefox_2018-08-31_21-54-43.png, firefox_2018-08-31_21-57-45.png Components: blueocean-pipeline-editor-plugin, blueocean-plugin, matrix-project-plugin Created: 2018-08-31 20:11 Environment: Jenkins - 2.121.3 Java - 1.8.0_181 Server running on Ubuntu Tested on latest Firefox version Labels: jenkins blueocean user-experience icon permission matrix Priority: Minor Reporter: Amide tex With the Matrix Authorization Strategy Plugin enabled to manage permissions at the project level, as expected, a user needs the Job.Configure permission to be able to edit pipelines on Blue Ocean. But without the global Job.Create permission, users can't see the Edit icon on the Blue Ocean interface. Users can still access the pipeline-editor by using the "http://jenkins:8080/blue/organizations/jenkins/pipeline-editor/project/master/" URL. Therefore, to configure pipelines with Blue Oceans, users need 2 permissions : Global : Jenkins.Create (to be able to see the Edit icon) Project : Jenkins.Configure (to be able to access the URL)
[JIRA] (JENKINS-52114) Declarative Pipeline Parallel Stages Post Events non-deterministic
Title: Message Title Andrew Bayer updated JENKINS-52114 Ok, this change will be in 1.3.2, which is releasing momentarily! Jenkins / JENKINS-52114 Declarative Pipeline Parallel Stages Post Events non-deterministic Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53316) Use Jackson 2.8.11 in Declarative
Title: Message Title Andrew Bayer updated JENKINS-53316 Jenkins / JENKINS-53316 Use Jackson 2.8.11 in Declarative Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus commented on JENKINS-53215 Re: Secure defaults not being configured for Jenkins out of the box Associated PR is ready to review (and had a green build in CI). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Title: Message Title Nenad Miksa commented on JENKINS-26659 Re: file permissions aren't protected after archive/unarchive I've reported it here: https://issues.jenkins-ci.org/browse/JENKINS-53374 You were correct - it was not the same issue, I just observed the same result on my system, but after creating the minimal reproducing sample, I've seen that it's actually a completely different feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53374) file permissions are lost after unstashing on windows node
Title: Message Title
Nenad Miksa created an issue
Jenkins / JENKINS-53374
file permissions are lost after unstashing on windows node
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2018-08-31 18:44
Environment:
Jenkins 2.140 Pipeline 2.5
Priority:
Minor
Reporter:
Nenad Miksa
Consider the following script:
node( 'macos' ) {
sh 'rm -rf *'
sh 'echo "int main() { return 0; }" > test.cpp'
sh 'mkdir bin && gcc test.cpp -o bin/test'
sh "ls -l bin"
stash name:'test', includes: "bin/*"
}node( 'windows' ) {
unstash 'test'
stash name:'test2', includes: 'bin/*'
}node( 'linux' ) {
sh 'rm -rf *'
unstash 'test2'
sh "ls -l bin"
}
It produces the following output:
Started by user Nenad Mikša
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] node
Running on macpro2 in /opt/jenkins/workspace/Test
[Pipeline] {
[Pipeline] sh
[Test] Running shell script
+ rm -rf bin test.cpp
[Pipeline] sh
[Test] Running shell script
+ echo 'int main() { return 0; }'
[Pipeline] sh
[Test] Running shell script
+ mkdir bin
+ gcc test.cpp -o bin/test
[Pipeline] sh
[Test] Running shell script
+ ls -l bin
total 16
-rwxr-xr-x 1 pero staff 4248 Aug 31 20:40 test
[Pipeline] stash
Stashed 1 file(s)
[Pipeline] }
[Pipeline] // node
[Pipeline] node
Running on Jabba in
[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title Oleg Nenashev commented on JENKINS-17116 Re: gracefull job termination I believe it is going to land in the next weekly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title Oleg Nenashev updated JENKINS-17116 Jenkins / JENKINS-17116 gracefull job termination Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17116) gracefull job termination
Title: Message Title Oleg Nenashev started work on JENKINS-17116 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Title: Message Title Daniel Beck closed an issue as Won't Fix It's not the same issue if it affects completely different commands. Please file a new issue. Jenkins / JENKINS-26659 file permissions aren't protected after archive/unarchive Change By: Daniel Beck Status: Reopened Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26659) file permissions aren't protected after archive/unarchive
Title: Message Title Nenad Miksa reopened an issue The same issue happens with stash/unstash with Jenkins 2.140 and Pipeline 2.5 Jenkins / JENKINS-26659 file permissions aren't protected after archive/unarchive Change By: Nenad Miksa Resolution: Won't Fix Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33979) github-organization-folder-plugin checks out code using HTTPS and not SSH
Title: Message Title Asaf Peleg commented on JENKINS-33979 Re: github-organization-folder-plugin checks out code using HTTPS and not SSH Jesse Glick does this Advanced button no longer exist? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Tomas Salazar commented on JENKINS-49720 Re: NVM wrapper hard-coded path whch version of jenkins are you using ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53373) Executor#doStop() operation and ProcessKiller termination should have access to the Run's TaskListener instance
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-53373 Executor#doStop() operation and ProcessKiller termination should have access to the Run's TaskListener instance Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-08-31 17:48 Labels: diagnostics executors Priority: Major Reporter: Oleg Nenashev Follow-up to https://github.com/jenkinsci/jenkins/pull/3414#issuecomment-417659656 In the current API and logic implementation, ProcessTable and Executor instances do not have a way to send messages to Jenkins build logs in the case of particular events like task termination. It would be great to somehow expand APIs so that it becomes possible. Add Comment
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Enrique Canales updated an issue Jenkins / JENKINS-53146 TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step Change By: Enrique Canales Component/s: customtools-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53146) TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step
Title: Message Title Enrique Canales commented on JENKINS-53146 Re: TOOLNAME_HOME Variable Not Available For Use in Freestyle Build Step I think you are correct here. I'll remove the custom_tools plugin specifically from the ticket. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser There is a help icon at the script text field. The name is fileName. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52945) Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2
Title: Message Title Jesse Glick updated JENKINS-52945 Fix integrated into master of Remoting. Next we need a release of that, then for it to be picked up in the core POM. Jenkins / JENKINS-52945 Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2 Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44824) "minimum" of f:repeatableProperty is inherit from ancestors
Title: Message Title Devin Nusbaum updated JENKINS-44824 Jenkins / JENKINS-44824 "minimum" of f:repeatableProperty is inherit from ancestors Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: https://jenkins.io/changelog/#v2.139 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-37599 f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) Change By: Devin Nusbaum Released As: Jenkins Core 2 https://jenkins . io/changelog/#v2. 139 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52945) Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2
Title: Message Title Jesse Glick stopped work on JENKINS-52945 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title Devin Nusbaum updated JENKINS-37599 Looks like the fix was recently released in Jenkins 2.139. Thanks ikedam! Jenkins / JENKINS-37599 f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52945) Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2
Title: Message Title Jesse Glick updated JENKINS-52945 Jenkins / JENKINS-52945 Attempt to (de-)serialize anonymous class com.cloudbees.plugins.credentials.CredentialsScope$2 Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37599) f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry)
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-37599 f:repeatable mishandles minimum (was: Custom Groovy Script for Promoted Builds always includes bogus classpath entry) Change By: Devin Nusbaum Released As: Jenkins Core 2.139 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser ok I have download it. (I don't know what is the README (CI badge)) in order to use the name of the parsed file in my groovy script, do you know what is the keyword to use ? (I don't find a groovy script part in the documentation) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Jesse Glick stopped work on JENKINS-50591 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Jesse Glick updated JENKINS-50591 Jenkins / JENKINS-50591 Files and paths with ampersand cause exception Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50591) Files and paths with ampersand cause exception
Title: Message Title Jesse Glick updated JENKINS-50591 Jenkins / JENKINS-50591 Files and paths with ampersand cause exception Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException We have found this NPE is triggered here : https://github.com/carlossg/jenkins-kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/DefaultInProvisioning.java#L19 As for some reason we have nodes created without associated computers (all our templates are configured with 1 or more executors) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner edited a comment on JENKINS-52058 Re: Provide report filename as variable to Groovy parser It's a link in the Jira comment above ;-)and in the README (CI badge). https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser It's a link in the Jira comment above https://ci.jenkins.io/job/Plugins/job/warnings-plugin/job/5.0/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53286) Enable Sentry user capturing
Title: Message Title Baptiste Mathus updated JENKINS-53286 Jenkins / JENKINS-53286 Enable Sentry user capturing Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53372) Update Groovy to v2.5.x
Title: Message Title Allan Lewis created an issue Jenkins / JENKINS-53372 Update Groovy to v2.5.x Issue Type: Improvement Assignee: Allan Lewis Components: core Created: 2018-08-31 15:15 Priority: Major Reporter: Allan Lewis Jenkins currently bundles Groovy 2.4.11, which was released in April 2017. Groovy 2.5.0 was released in May 2018 and includes a number of new features; the latest patch release is 2.5.2, released August 2018. This ticket proposes upgrading Groovy to the latest in the 2.5 series as a step to upgrading to v3 - see JENKINS-51823. Add Comment
[JIRA] (JENKINS-53304) Data loss when running on newly pulled version of the evergreen image
Title: Message Title Baptiste Mathus updated JENKINS-53304 Jenkins / JENKINS-53304 Data loss when running on newly pulled version of the evergreen image Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53215) Secure defaults not being configured for Jenkins out of the box
Title: Message Title Baptiste Mathus updated JENKINS-53215 Jenkins / JENKINS-53215 Secure defaults not being configured for Jenkins out of the box Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks. but in readme.md file there is a link to the online documentation and I presume that in documentation there is the link for the 5.X warning plugin HPI file but I don't succeed to find it. it maybe something obvious but I don't find it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException for some reason that's all we get, even though we are logging at the finest level: 2018-08-31 14:15:05.698+ [id=203] WARNING o.c.j.p.k.KubernetesCloud#provision: Failed to count the # of live instances on Kubernetes java.lang.NullPointerException 2018-08-31 14:15:05.725+ [id=203] INFO... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41704) Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException
Title: Message Title Kevin Foster commented on JENKINS-41704 Re: Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException After an upgrade to Jenkins ver. 2.121.3 I started getting the same errors on the cppcheck plugin. org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/cppcheck/WEB-INF/lib/cppcheck.jar!/org/jenkinsci/plugins/cppcheck/CppcheckResult/index.jelly:4:62: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.cppcheck.CppcheckResult Please let me know if you need the entire stack trace. Thank you Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52016) Build parameters & env variables not working to Publish Over SSH
Title: Message Title Ayappan Perumal updated an issue Jenkins / JENKINS-52016 Build parameters & env variables not working to Publish Over SSH Change By: Ayappan Perumal Attachment: $7475F403A56A076E.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52016) Build parameters & env variables not working to Publish Over SSH
Title: Message Title Ayappan Perumal commented on JENKINS-52016 Re: Build parameters & env variables not working to Publish Over SSH Sorry for the late response. If you see the first image, the "$" variables are put into the Publish over SSH plugin. But they are not getting set inside this plugin because of which no files are copied over. I am attaching the older log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53368) Custom workspace-volume
Title: Message Title Carlos Sanchez commented on JENKINS-53368 Re: Custom workspace-volume I think you can already do that, have you tried ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Carlos Sanchez commented on JENKINS-53370 Re: Failed to count the # of live instances on Kubernetes - NullPointerException what's the full log and stack trace? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden We just met with Mandie Smith and agreed on the following: she is going to do some checks and add tests in this feature area Because we can only reproduce it using the production deployed backend, it's very likely we should first upgrade the backend to latest before delving into this too much. I can see for instances commits like cc9ed7e60d441ecdea8737af8aac43a022ef92c1 or 21733e1228f9341b755d4727cc3ab08e52221352 or 7ac8b77de9a4f648916fc57dcaf6c48b02552831 that could well be fixes for just that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitSCM checkout returns same values on second different call
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53346 GitSCM checkout returns same values on second different call Change By: Mark Waite Summary: GitScm GitSCM checkout returns same values on second different call Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitScm checkout returns same values on second different call
Title: Message Title Mark Waite commented on JENKINS-53346 Re: GitScm checkout returns same values on second different call I've confirmed that the bug exists as reported. The map returned by the second checkout has the same values as the map returned by the first checkout. Refer to the Jenkinsfile in my JENKINS-53346 test branch for an alternative to obtain the same information using a shell call. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitScm checkout returns same values on second different call
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-53346 GitScm checkout returns same values on second different call Change By: Mark Waite Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53346) GitScm checkout returns same values on second different call
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53346 GitScm checkout returns same values on second different call Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser There is no process, see documentation. Best way is to use copy and past and then use the new API. It will not take much time to understand the differences. There are also some examples used in my tests. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title iostrym commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser thanks a lot. is there a migration process to retrieve my old parser ? or do I need to do manual copy paste ? groovy scripts and regular _expression_ could be conserved from my old parser ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53362) Update documentation for junit Pipeline step return value
Title: Message Title Jesse Glick commented on JENKINS-53362 Re: Update documentation for junit Pipeline step return value FTR introduced in JENKINS-27395 by Andrew Bayer. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53362) Update documentation for junit Pipeline step return value
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-53362 Update documentation for junit Pipeline step return value Yes, at a minimum JUnitResultsStep/help.html should document this. Perhaps some edits to jenkins.io as well, TBD. Change By: Jesse Glick Summary: Update documentation for junit pipeline Pipeline step return value Issue Type: Improvement Bug Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser No, much simpler: use the provided link in the README to download the latest HPI. Note: the format and API of the parsers has changed, so you old parsers will not work! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Dominik Bartholdi commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin cool, please just open a PR that will for sure speedup things - thanks!!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53371) Credentials user/pw shown in plain text using bash and single quote
Title: Message Title
Steve Boardwell updated an issue
Jenkins / JENKINS-53371
Credentials user/pw shown in plain text using bash and single quote
Change By:
Steve Boardwell
h3. Problem Experienced on latest LTS with all plugins updated. Username and Password credentials are being shown in plain text when: * single quote is contained in the username and/or password * bash is used as a shellh3. How to reproducePipeline expects some credentials with ID 'both-user-and-pw' containing single quotes, for example, username = "user'name", password = "pass'word" (Given, username with a single quote are not to be expected, but for the sake of completeness...){noformat}node('master') {try {withCredentials([usernamePassword(credentialsId: 'both-user-and-pw', passwordVariable: 'myPw', usernameVariable: 'myUser')]) {echo '---'echo "WORKING: Normal 'sh' step masks credentials"echo '---'sh 'echo "user=${myUser} password=${myPw}"'echo '---'echo "WORKAROUND: 'bash' without 'set -x' credentials."echo '---'sh '#!/bin/bash\necho "user=${myUser} password=${myPw}"'echo '---'echo "BUG: 'bash' with 'set -x' credentials."echo '---'sh '#!/bin/bash\nset -x\necho "user=${myUser} password=${myPw}"'}} finally {cleanWs()}}{noformat}Results in:{noformat}---[Pipeline] echoWORKING: Normal 'sh' step masks credentials[Pipeline] echo---[Pipeline] sh[EXP-steve-pipeline-test] Running shell script+ echo user= password=user= password=[Pipeline] echo---[Pipeline] echoWORKAROUND: 'bash' without 'set -x' credentials.[Pipeline] echo---[Pipeline] sh[EXP-steve-pipeline-test] Running shell scriptuser= password=[Pipeline] echo---[Pipeline] echoBUG: 'bash' with 'set -x' credentials.[Pipeline] echo---[Pipeline] sh[EXP-steve-pipeline-test] Running shell script+ echo 'user=user'\''name password=pass'\''word'user= password={noformat}
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer edited a comment on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin You can find a first shot here: https://github.com/srempfer/config-file-provider-plugin/commit/3d08654f9ac5f65105fc21c157e7e853106d3538 If you wish I could create a PR which you could review... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53371) Credentials user/pw shown in plain text using bash and single quote
Title: Message Title
Steve Boardwell created an issue
Jenkins / JENKINS-53371
Credentials user/pw shown in plain text using bash and single quote
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2018-08-31 12:31
Priority:
Major
Reporter:
Steve Boardwell
Problem Username and Password credentials are being shown in plain text when:
single quote is contained in the username and/or password
bash is used as a shell
How to reproduce Pipeline expects some credentials with ID 'both-user-and-pw' containing single quotes, for example, username = "user'name", password = "pass'word" (Given, username with a single quote are not to be expected, but for the sake of completeness...)
node('master') {
try {
withCredentials([usernamePassword(credentialsId: 'both-user-and-pw', passwordVariable: 'myPw', usernameVariable: 'myUser')]) {
echo '---'
echo "WORKING: Normal 'sh' step masks credentials"
echo '---'
sh 'echo "user=${myUser} password=${myPw}"'
echo '---'
echo "WORKAROUND: 'bash' without 'set -x' credentials."
echo '---'
sh '#!/bin/bash\necho "user=${myUser} password=${myPw}"'
echo '---'
echo "BUG: 'bash' with 'set -x' credentials."
echo '---'
sh
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title
Sebastian Lopez updated an issue
Jenkins / JENKINS-53370
Failed to count the # of live instances on Kubernetes - NullPointerException
Change By:
Sebastian Lopez
Seems to be similar to JENKINS- 40452 41847 , but we're using Kubernetes plugin version 1.8.4.The plugin cannot determine the status of existing pods, and no new pods are provisioned. {code:java}Aug 31, 2018 12:22:15 PM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionFailed to count the # of live instances on Kubernetesjava.lang.NullPointerException{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title
Sebastian Lopez updated an issue
Jenkins / JENKINS-53370
Failed to count the # of live instances on Kubernetes - NullPointerException
Change By:
Sebastian Lopez
Seems to be similar to [ JENKINS-40452 |https://issues.jenkins-ci.org/browse/JENKINS-40452] , but we're using Kubernetes plugin version 1. 8. 4. 8 and a version of kubernetes- The plugin where 40452 is supposed to be fixed cannot determine the status of existing pods, and no new pods are provisioned . {code:java} Feb 08 Aug 31 , 2017 2 2018 12 : 52 22 : 10 15 PM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionINFO: Excess workload after pending Spot instances: 1Feb 08, 2017 2:52:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionWARNING: Failed provisionFailed to count the # of live instances on Kubernetesjava.lang.NullPointerException at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:668)at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:513)at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701)at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:307)at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:60)at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:796)at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)at java.lang.Thread.run(Thread.java:745) {code}
Add Comment
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez updated an issue Jenkins / JENKINS-53370 Failed to count the # of live instances on Kubernetes - NullPointerException Change By: Sebastian Lopez Environment: Jenkins ver. 2.107.3kubernetes-plugin 0 1 . 10 8.4 Kubernetes 1.8 .4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez updated an issue Jenkins / JENKINS-53370 Failed to count the # of live instances on Kubernetes - NullPointerException Change By: Sebastian Lopez Environment: Jenkins ver. 2. 32 107 . 2 3 kubernetes-plugin 0.10Kubernetes 1. 4. 8 .4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53370) Failed to count the # of live instances on Kubernetes - NullPointerException
Title: Message Title Sebastian Lopez created an issue Jenkins / JENKINS-53370 Failed to count the # of live instances on Kubernetes - NullPointerException Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-31 12:26 Environment: Jenkins ver. 2.32.2 kubernetes-plugin 0.10 Kubernetes 1.4.8 Priority: Major Reporter: Sebastian Lopez Seems to be similar to JENKINS-40452, but we're using Kubernetes 1.4.8 and a version of kubernetes-plugin where 40452 is supposed to be fixed. Feb 08, 2017 2:52:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision INFO: Excess workload after pending Spot instances: 1 Feb 08, 2017 2:52:10 PM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision WARNING: Failed to count the # of live instances on Kubernetes java.lang.NullPointerException at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:668) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:513) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:701) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:307) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:60) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:796) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Stefan Rempfer commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin You can find a first shot here: https://github.com/srempfer/config-file-provider-plugin/commit/3d08654f9ac5f65105fc21c157e7e853106d3538 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53365) any plugin depending on junit plugin is forced to depend on scm-api
Title: Message Title James Nord updated JENKINS-53365 Jenkins / JENKINS-53365 any plugin depending on junit plugin is forced to depend on scm-api Change By: James Nord Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51057) EventDispatcher and ConcurrentLinkedQueue ate my JVM
Title: Message Title
Jon Sten commented on JENKINS-51057
Re: EventDispatcher and ConcurrentLinkedQueue ate my JVM
As a temporary workaround, here's a script which will go through and look for old event dispatchers:
// First of, due to groovy and private field in super classes, we need to
// change visibility of retryQueue so that we can use reflection instead...
def retryQueueField = org.jenkinsci.plugins.ssegateway.sse.EventDispatcher.getDeclaredField('retryQueue')
retryQueueField.setAccessible(true)
def sessions = Jenkins.instance.servletContext.this$0._sessionHandler._sessionCache._sessions
println("There are ${sessions.size()} sessions...")
def numEventsRemoved = 0
def numEventDispatchersPurged = 0
sessions.each{id, session->
def eventDispatchers = session.sessionData._attributes['org.jenkinsci.plugins.ssegateway.sse.EventDispatcher']
if (eventDispatchers) {
println("Sessions ${id} has a ssegateway EventDispatcher map...")
eventDispatchers.findAll{k, v -> k.startsWith('jenkins-blueocean-core-js')}.each { dispatcherId, dispatcher ->
def retryQueue = retryQueueField.get(dispatcher) // Need to use reflection since retryQueue is private in super class...
if (retryQueue.isEmpty()) {
println(" Found one EventDispatcher, '${dispatcherId}', it has no retry events.")
} else {
def oldestAge = (System.currentTimeMillis() - retryQueue.peek().timestamp)/1000
if (oldestAge > 300) {
println(" Found one EventDispatcher, '${dispatcherId}', its oldest retry event is ${oldestAge} seconds old, it contains ${retryQueue.size()} retry events, removing events and unsubscribing.")
numEventsRemoved += retryQueue.size()
numEventDispatchersPurged++
dispatcher.unsubscribeAll()
retryQueue.clear()
} else {
println(" Found one EventDispatcher, its oldest retry event is ${oldestAge} seconds old, so sparing it for now...")
}
}
}
}
}
println("Removed ${numEventsRemoved} retry events from ${numEventDispatchersPurged} EventDispatchers!")
Btw, I've verified this bug in a fresh Jenkins install (2.121.3) and with latest version of Blue Ocean (1.8.2) which pulls SSE-gateway (1.15).
Add Comment
[JIRA] (JENKINS-53369) HTML Publisher plugin - an excess numerals in the report link naming
Title: Message Title Ihar Slabodkin updated an issue Jenkins / JENKINS-53369 HTML Publisher plugin - an excess numerals in the report link naming Change By: Ihar Slabodkin Summary: HTML Publisher plugin- an excess numerals in the report link naming Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53369) HTML Publisher plugin
Title: Message Title Ihar Slabodkin created an issue Jenkins / JENKINS-53369 HTML Publisher plugin Issue Type: Bug Assignee: Richard Bywater Attachments: image-2018-08-31-14-48-05-883.png, image-2018-08-31-14-55-47-530.png Components: htmlpublisher-plugin Created: 2018-08-31 12:03 Environment: OS for Jenkins (master node): CentOS release 6.8 ( 2.6.32-642.6.1.el6.x86_64) OS for slave node: Windows Server 2016 version 1607 Jenkins 2.121.3; Oracle JDK 1.8.0_144 x64; HTML Publisher 1.16 Priority: Major Reporter: Ihar Slabodkin The Jenkins + HTML Publisher made a copy of report from folder on windows slave machine to Jenkins machine (master) into a folder with incorrect naming. I assume that it happens due to encoding issue for "spaces" in the "Report Title" field. Jenkins as Master runs directly and stored HTML reports locally. All test automation tests he run s on windows slave machine (Windows Server 2016 version 1607) via JNLP-4 connection. HTML Publisher configuration: Console output: 16:38:15 [htmlpublisher] Archiving HTML reports...16:38:15 [htmlpublisher] Archiving at BUILD level c:/workspace/TA_MAIN/ta-10/chrome/regression/TA_reports to /var/lib/jenkins/jobs/TAMAIN/builds/80293/htmlreports/Main_20Test_20Report*16:38:15* [htmlpublisher] Archiving at BUILD level c:/workspace/TAMAIN/ta-10/chrome/regression/TA_RERUN_reports to /var/lib/jenkins/jobs/TA_MAIN/builds/80293/htmlreports/Rerun_20Test_20Report As you could see the Jenkins creates a folder structure with "20" numerals in the naming that looks like an unicode for spaces. Besides of this the
[JIRA] (JENKINS-53368) Custom workspace-volume
Title: Message Title Thore Paetsch created an issue Jenkins / JENKINS-53368 Custom workspace-volume Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-08-31 12:01 Priority: Minor Reporter: Thore Paetsch Currently there is always a mount of an emptyDir-volume in /home/jenkins. This comes automatically from plugin code. Because an emptyDir-volume is not persistent the agent has to download the full sources from the Git repository every time a build is started. Afterwards the downloaded sources are thrown away. It would be nice to have the opportunity to choose a volume that is mounted as workspace-volume so you could pick your own nfs-volume which includes the workspace with all downloaded projects. With a persistent workspace like that, the Git checkout would only update the sources, saving a lot of build time and network traffic. In addition with a nfs-volume we could have a workspace shared across all hosts and used by many agents at the same time (RWX access), saving storage and avoiding conflicts compared to a persistent-volume. Currently defining a volume in a scripted pipeline with mountpath /home/jenkins in the podTemplate resolves in java.nio exceptions and the plugin code says it is simply ignored. My suggestion: if the podTemplate defines a volume which is mounted in /home/jenkins it replaces the emptyDir otherwise mounted by plugin code. If there already is a way to mount a custom workspace-volume which I somehow overlooked please let me know.
[JIRA] (JENKINS-53367) SonarQube code analysis not working
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53367 SonarQube code analysis not working Change By: Daniel Gront The SonarQube server is no longer working with the following issue: *10:09:18* 10:09:19.099 ERROR: Error during SonarQube Scanner execution *10:09:18* 10:09:19.099 ERROR: File HpToolsAborter/Program.cs can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53367) SonarQube code analysis not working
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-53367 SonarQube code analysis not working Change By: Daniel Gront The SonarQube server is no longer working with the following issue: *10:09:18* 10:09:19.099 ERROR: Error during SonarQube Scanner execution*10:09:18* 10:09:19.099 ERROR: File HpToolsAborter/Program.cs can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53367) SonarQube code analysis not working
Title: Message Title Daniel Gront created an issue Jenkins / JENKINS-53367 SonarQube code analysis not working Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-08-31 11:57 Labels: Infrastructure Priority: Major Reporter: Daniel Gront The SonarQube server is no longer working with the following issue: 10:09:18 10:09:19.099 ERROR: Error during SonarQube Scanner execution*10:09:18* 10:09:19.099 ERROR: File HpToolsAborter/Program.cs can't be indexed twice. Please check that inclusion/exclusion patterns produce disjoint sets for main and test files Add Comment
[JIRA] (JENKINS-53366) [CopyArtifact] fails when using latestSavedBuild selector from Multi-Configuration project
Title: Message Title armin novak created an issue Jenkins / JENKINS-53366 [CopyArtifact] fails when using latestSavedBuild selector from Multi-Configuration project Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 2018-08-31 11:46 Environment: copy artifact plugin 1.41 jenkins 2.121.3 Priority: Major Reporter: armin novak Copy Artifact stopped working with latestSavedBuild selector, but only from Multi-Configuration projects. Specifically, it looks like the `keep forever` from the project is no longer inherited by the sub configurations. A workaround is setting `keep forever` for each configuration (which is no real solution when there are lots of configurations for each build) Add Comment
[JIRA] (JENKINS-53247) Support JCasC in Config File Provider Plugin
Title: Message Title Dominik Bartholdi commented on JENKINS-53247 Re: Support JCasC in Config File Provider Plugin OK, i'll update to LTS 2.60.x as soon as I can - hopefully in the next couple of days... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53365) any plugin depending on junit plugin is forced to depend on scm-api
Title: Message Title James Nord started work on JENKINS-53365 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53365) any plugin depending on junit plugin is forced to depend on scm-api
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-53365 any plugin depending on junit plugin is forced to depend on scm-api Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53365) any plugin depending on junit plugin is forced to depend on scm-api
Title: Message Title James Nord created an issue Jenkins / JENKINS-53365 any plugin depending on junit plugin is forced to depend on scm-api Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2018-08-31 11:09 Priority: Minor Reporter: James Nord https://github.com/jenkinsci/junit-plugin/pull/88/files#r214318972 junit-1.22.1 made workflow-api a non optioanl dependency and yet excluces SCM-api from the dependencies. This means any plugin depending on junit is forced to declare a dependency on scm-api for no reason other than to get the damn thing to pass tests (InjectedTest and allow mvn hpi:run to work) as Jenkins will start and as scm-api is excluded the workflow-api is started and fails as scm-api is not included. [INFO] Running InjectedTest [ERROR] Tests run: 10, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 16.146 s <<< FAILURE! - in InjectedTest [ERROR] testPluginActive(org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests) Time elapsed: 0.006 s <<< ERROR! java.lang.Error: Plugin workflow-api failed to start at org.jvnet.hudson.test.PluginAutomaticTestBuilder$OtherTests.testPluginActive(PluginAutomaticTestBuilder.java:99) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at junit.framework.TestCase.runTest(TestCase.java:176) at junit.framework.TestCase.runBare(TestCase.java:141) at junit.framework.TestResult$1.protect(TestResult.java:122) at junit.framework.TestResult.runProtected(TestResult.java:142) at
[JIRA] (JENKINS-53364) github-oauth-plugin -Simpler 403 page
Title: Message Title Arthur Clément created an issue Jenkins / JENKINS-53364 github-oauth-plugin -Simpler 403 page Issue Type: Improvement Assignee: Sam Gleske Components: github-oauth-plugin Created: 2018-08-31 10:17 Priority: Minor Reporter: Arthur Clément When a GitHub user outside an authorized organization log in into Jenkins, his access is denied but he has still a view on the Jenkins web UI (with no rights). A simple 403 page without any Jenkins menu display would enhance the feeling of a strong "access denied". I make this request because this was a remark from an external security audit of our tools. The idea is to reduce the attack surface. Add Comment
[JIRA] (JENKINS-53363) >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Title: Message Title Carlos Sanchez commented on JENKINS-53363 Re: >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing noted https://github.com/jenkinsci/kubernetes-plugin/blob/master/CHANGELOG.md#1121 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53363) >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Title: Message Title Gareth Healy commented on JENKINS-53363 Re: >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing I expected that to be the response, which is fine. But, can this be noted in the change log / docs / somewhere? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53363) >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Title: Message Title Carlos Sanchez resolved as Won't Do Jenkins / JENKINS-53363 >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing Change By: Carlos Sanchez Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53363) >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Title: Message Title Carlos Sanchez commented on JENKINS-53363 Re: >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing 1.12.1 upgraded the kubernetes client to 4.0.0 which I assume no longer supports k8s 1.5 because it's too old, so you would need to upgrade your cluster to continue using newer versions of the plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34564) Give the ability to choose how the multibranch subprojects will be named.
Title: Message Title diewu qin commented on JENKINS-34564 Re: Give the ability to choose how the multibranch subprojects will be named. Anyone can tell me if this issue fixed? I use parameter " -Djenkins.branch.WorkspaceLocatorImpl.PATH_MAX=20 " but did not work, and my jenkins version is 2.89.4. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak edited a comment on JENKINS-49720 Re: NVM wrapper hard-coded path btw [~atoms] I also noticed * new version of plugin installed * new options on job appeared (as I confirmed above), so it means new version got installed * but in plugin page, I can still see the update available of the nvm-wrapper plugin (I guess you forgot to change the version somewhere or something related to this0 this Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49720) NVM wrapper hard-coded path
Title: Message Title Pavel Novak commented on JENKINS-49720 Re: NVM wrapper hard-coded path btw Tomas Salazar I also noticed new version of plugin installed new options on job appeared (as I confirmed above), so it means new version got installed but in plugin page, I can still see the update available of the nvm-wrapper plugin (I guess you forgot to change the version somewhere or something related to this0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53363) >= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Title: Message Title
Gareth Healy created an issue
Jenkins / JENKINS-53363
>= 1.12.1 fails to delete pods on OpenShift 3.5 due to DeleteOptions missing
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-08-31 09:14
Environment:
1.12.1
Priority:
Major
Reporter:
Gareth Healy
I get the following error when using the k8s plugin >= 1.12.1 against the following OCP version. As the pods are not deleted, the slave pods start to build up and need to be manually cleaned up.
openshift v3.5.5.31.19
kubernetes v1.5.2+43a9be4
If i downgrade to 1.12.0, everything works as expected. Logs:
Aug 31, 2018 10:03:37 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave deleteSlavePod
WARNING: Failed to delete pod for agent pipeline-engineering-staging-pre/rhel-jenkins-jnlp-maven-jz2rf: Failure executing: DELETE at: https://kubernetes.default/api/v1/namespaces/pipeline-engineering-staging-pre/pods/rhel-jenkins-jnlp-maven-jz2rf. Message: no kind "DeleteOptions" is registered for version "meta/v1". Received status: Status(apiVersion=v1, code=500, details=null, kind=Status, message=no kind "DeleteOptions" is registered for version "meta/v1", metadata=ListMeta(_continue=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=null, status=Failure,
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden Mandie Smith any idea of why the version could be chosen differently? The only thing I can thing about is the fact we have many UL on the official backend at https://evergreen.jenkins.io, when we have only one locally when testing. I do not know the backend service code enough for this part to form a hypothesis on what could lead to this. To clarify my previous comment: the new UL41 fixes this issue by working around it by forcing docker-commons all the time. So one will not be able to reproduce this issue using https://evergreen.jenkins.io. But because our tests are not failing for this case, this means we could well get back to this situation sooner than we hope (well, I do hope we get back to it soon so that we fix it now, and not when we have more users...). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53318) Version for a given plugin should be taken from environments first when overridden
Title: Message Title Baptiste Mathus commented on JENKINS-53318 Re: Version for a given plugin should be taken from environments first when overridden OK, so 1) I confirm this one is really critical, I could not get a publicly running evergreen instance trying again just now. Not blocking anymore since I merged https://github.com/jenkins-infra/evergreen/commit/f7cb1f9fad38a4d36a9798dcd0960353b23604fa and it just got pushed as a new UL. 2) What actually concerns me even more right now is I realized no test is failing. So I do not understand why when running locally a docker-cloud flavor, docker-commons gets installed correctly as 1.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52215) Jenkins authentication issue with Azure ADDS
Title: Message Title Jie Shen resolved as Done Jenkins / JENKINS-52215 Jenkins authentication issue with Azure ADDS Change By: Jie Shen Status: In Progress Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52215) Jenkins authentication issue with Azure ADDS
Title: Message Title Jie Shen commented on JENKINS-52215 Re: Jenkins authentication issue with Azure ADDS Thanks for all your contribution! Badal Kotecha Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
