[JIRA] (JENKINS-58609) Copy existing job does not clone the repository
Title: Message Title Daniel Beck commented on JENKINS-58609 Re: Copy existing job does not clone the repository As a workaround, round-trip the config.xml once (first GET then POST) and it should be cleared up. This might end up simply needing to be documented. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200770.1563861253000.19949.1563951240133%40Atlassian.JIRA.
[JIRA] (JENKINS-38126) Credentials dropdown empty on git scm
Title: Message Title Matthias Flock commented on JENKINS-38126 Re: Credentials dropdown empty on git scm This issue is still relevant with Jenkins ver. 2.176.2, git plugin 3.0.0-rc and Authorize Project 1.3.0 It has been almost 3 years since this was reported and there is nothing more than a workaround? Is there an alternative to the Authorize Project 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174282.1473669042000.19929.1563949200498%40Atlassian.JIRA.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Arun Gupta commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated Hi, yes the issue is resolved in the 1.44 version of the EC2 Plugin. Happy to get the ticket 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.19924.1563945180424%40Atlassian.JIRA.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Arun Gupta resolved as Fixed Jenkins / JENKINS-57348 EC2 Plugin not working when AWS Keys are rotated Change By: Arun Gupta Status: Open Resolved Resolution: Fixed Released As: 1.44 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.19926.1563945180447%40Atlassian.JIRA.
[JIRA] (JENKINS-58628) jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues
Title: Message Title
Porter Bassett created an issue
Jenkins / JENKINS-58628
jira-plugin not working from pipeline job: jiraIssueSelector doesn't find any issues
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-plugin
Created:
2019-07-24 05:09
Environment:
Jenkins ver. 2.138.2 jira-plugin version 3.0.3
Labels:
pipeline
Priority:
Major
Reporter:
Porter Bassett
jira-plugin works fine from a freestyle job, but is not working properly from a pipeline job. I am comparing a freestyle job using the {{"JIRA: Update relevant issues" }}post-build step with a pipeline job using the jiraIssueSelector pipeline step. When run on a commit with a commit message of "DEVO-2398 DEVO-2399", the freestyle job correctly gives me the output
[JIRA] Updating issue DEVO-2399 [JIRA] Updating issue DEVO-2398
When I run against the same commit message in the pipeline job, the jiraIssueSelector is not able to identify the Jira items. I put the following in my Jenkinsfile:
{{def issueKeys = jiraIssueSelector(issueSelector: [$class: 'DefaultIssueSelector']) }}
echo "${issueKeys.size()}"
and I get the output
[JIRA] (JENKINS-58397) Error in Jenkins home screen as "java.lang.AssertionError: InstanceIdentity is missing its singleton"
Title: Message Title Subramanya Jagannath commented on JENKINS-58397 Re: Error in Jenkins home screen as "java.lang.AssertionError: InstanceIdentity is missing its singleton" Oleg Nenashev Any update on this issue? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200522.1562661058000.19920.1563942600100%40Atlassian.JIRA.
[JIRA] (JENKINS-57348) EC2 Plugin not working when AWS Keys are rotated
Title: Message Title Raihaan Shouhell commented on JENKINS-57348 Re: EC2 Plugin not working when AWS Keys are rotated Arun Gupta Has it worked out for 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199124.1557188451000.19918.1563942300168%40Atlassian.JIRA.
[JIRA] (JENKINS-58627) jenkins slave getting terminated with version 2.176.2
Title: Message Title Chethan Mahabaleswara created an issue Jenkins / JENKINS-58627 jenkins slave getting terminated with version 2.176.2 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-07-24 04:05 Environment: Windows 2012, Java 1.8.0_211, Jenkins 2.176.2 Priority: Major Reporter: Chethan Mahabaleswara Hi, Jenkins slave is geting terminated with new version 2.176.2 as explained below OS - windows 2012 R2 (both Master and Slave) Java - 1.8.0_211 (both Mater and Salve) Jenkins Version - 2.176.2 Launch Method - Java Web start, JNLP(Launch by connecting it to the Master) Issue - I have a project in Jenkins which fails mainly because the slave terminates after 'Starting ServiceWrapper in the CLI mode' during execution.Finds a child process conhost.exe and failed due to Killing as fallback. This is happening only for a project/ pipeline, where I have python script which pings a internal URL (https://URL/ping), invokes the network emulator tool installed, adjust the network latency and also write to a file/ push to ELK. I have a internet proxy set up using .pac file. It completes all the steps in project, at the end the slave terminates, marking the build as failure Note - We also have another old version of jenkins 2.76 installed where the same project/ pipeline works with out any issue. Now we want to upgrade to latest jenkins we are seeing issue with slave getting terminated. I now have to close the network emulator tool every time and restart the jenkins service to bring it back online. Error as obsreved in Jenkins-slave.wrapper.log:- 2019-07-24 03:51:59,751 INFO - Stopping jenkinsslave-e__jenkins 2019-07-24 03:51:59,751 DEBUG - ProcessKill 6872 2019-07-24 03:51:59,860 INFO - Found child process: 6408 Name: conhost.exe 2019-07-24 03:51:59,8
[JIRA] (JENKINS-58626) the response code of "Authentication required" should be 401
Title: Message Title Davy Ni updated an issue Jenkins / JENKINS-58626 the response code of "Authentication required" should be 401 Change By: Davy Ni When a jenkins api is called without authentication info, jenkins return 403 error code. According to RFC 2616, jenkins should return 401. This bug makes my Jira webhook not working. My Jira webhook is created like this: [http://username:passw...@jenkins.x.com/view/ci-megalodon-master/job/provision2/buildWithParameters.|http://dev:yodoo...@jenkins.ut.feikongbao.cn/view/ci-megalodon-master/job/provision2/buildWithParameters.] Jira first call this webhook without authentication info, if webhook return 401, Jira will then call webwook with authentication info. But as jenkins return 403, the Jira webhook just failed. Reference about 401 &403:[https://tools.ietf.org/html/rfc2616#section-10.4.2][http://www.dirv.me/blog/2011/07/18/understanding-403-forbidden/index.html] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200794.156393893.19914.1563940080145
[JIRA] (JENKINS-46123) Restart fails on Windows master with slaves connected. "SEVERE: Restarting VM as requested by username" (Windows service not running as local system account)
Title: Message Title Chethan Mahabaleswara commented on JENKINS-46123 Re: Restart fails on Windows master with slaves connected. "SEVERE: Restarting VM as requested by username" (Windows service not running as local system account) Hi, I have a similar issue. Can someone guide me about possible fix ? OS - windows 2012 R2 (both Master and Slave) Java - 1.8.0_211 (both Mater and Salve) Jenkins Version - 2.176.2Slave Launch Method - Java Web start, JNLP(Launch by connecting it to the Master) Issue - I have a project in Jenkins which fails mainly because the slave terminates after 'Starting ServiceWrapper in the CLI mode' during execution.Finds a child process conhost.exe and failed due to Killing as fallback. This is happening only for a project/ pipeline, where I have python script which pings a internal URL (https://URL/ping), invokes the network emulator tool installed, adjust the network latency and also write to a file/ push to ELK. I have a internet proxy set up using .pac file. It completes all the steps in project, at the end the slave terminates, marking the build as failure Note - We also have another old version of jenkins 2.76 installed where the same project/ pipeline works with out any issue. Now we want to upgrade to latest jenkins but facing issue with slave getting terminated. I now have to close the network emulator tool every time and restart the jenkins service to bring it back online. Error as obsreved in Jenkins-slave.wrapper.log:- 2019-07-24 03:51:59,751 INFO - Stopping jenkinsslave-e__jenkins 2019-07-24 03:51:59,751 DEBUG - ProcessKill 6872 2019-07-24 03:51:59,860 INFO - Found child process: 6408 Name: conhost.exe 2019-07-24 03:51:59,892 INFO - Stopping process 6408 2019-07-24 03:51:59,907 INFO - Send SIGINT 6408 2019-07-24 03:51:59,907 WARN - SIGINT to 6408 failed - Killing as fallback 2019-07-24 03:51:59,907 INFO - Stopping process 6872 2019-07-24 03:51:59,907 INFO - Send SIGINT 6872 2019-07-24 03:51:59,907 WARN - SIGINT to 6872 failed - Killing as fallback 2019-07-24 03:51:59,907 INFO - Finished jenkinsslave-e__jenkins 2019-07-24 03:51:59,907 DEBUG - Completed. Exit code is 0 Error as obsreved in jenkins-slave.error.log:- Jul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusJul 24, 2019 3:57:23 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Terminated Jul 24, 2019 3:57:23 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1040) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:209) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:816) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1800(BIONetworkLayer.java:48) at org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:264) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.
[JIRA] (JENKINS-58626) the response code of "Authentication required" should be 401
Title: Message Title Davy Ni created an issue Jenkins / JENKINS-58626 the response code of "Authentication required" should be 401 Issue Type: Bug Assignee: Kseniia Nenasheva Components: security-inspector-plugin Created: 2019-07-24 03:28 Priority: Minor Reporter: Davy Ni When a jenkins api is called without authentication info, jenkins return 403 error code. According to RFC 2616, jenkins should return 401. This bug makes my Jira webhook not working. My Jira webhook is created this: http://username:passw...@jenkins.x.com/view/ci-megalodon-master/job/provision2/buildWithParameters. Jira first call this webhook without authentication info, if webhook return 401, Jira will then call webwook with authentication info. But as jenkins return 403, the Jira webhook just failed. Reference about 401 &403: https://tools.ietf.org/html/rfc2616#section-10.4.2 http://www.dirv.me/blog/2011/07/18/understanding-403-forbidden/index.html Add Comment
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title Rajiv Jandial updated an issue Jenkins / JENKINS-58621 EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status Change By: Rajiv Jandial Labels: Jenkins-ec2-fleet-version-1.9.2 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200787.1563913663000.19906.1563936240204%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Cuong Tran commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Was this property added to the agent or the master? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.19862.1563934380856%40Atlassian.JIRA.
[JIRA] (JENKINS-34876) Git Parameters not working for Pipeline projects and Jenkinsfile from SCM
Title: Message Title Julian Mosquera commented on JENKINS-34876 Re: Git Parameters not working for Pipeline projects and Jenkinsfile from SCM it looks like is a problem in scripted pipeline. When i changed the script to declarative it worked 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170541.1463478053000.19836.1563930960546%40Atlassian.JIRA.
[JIRA] (JENKINS-58609) Copy existing job does not clone the repository
Title: Message Title Long Nguyen commented on JENKINS-58609 Re: Copy existing job does not clone the repository Thank Daniel Beck. I think "Use API" should be fixed, it doesn't mean if you couldn't do anything on job which has just created. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200770.1563861253000.19833.1563929640116%40Atlassian.JIRA.
[JIRA] (JENKINS-58625) Use milestone to cancel older builds
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58625 Use milestone to cancel older builds Issue Type: Improvement Assignee: Jesse Glick Components: bom Created: 2019-07-24 00:18 Priority: Minor Reporter: Jesse Glick Try using the trick from JENKINS-43353 to avoid repeated builds from the same branch. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title Paul Eipper commented on JENKINS-58624 Re: docker.withRegistry doesn't use build environment Of note: I tried setting a docker tool location, with override on the slave to "/usr/local", but it still failed to find the docker command. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200791.1563924433000.19827.1563925980045%40Atlassian.JIRA.
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title Paul Eipper commented on JENKINS-58624 Re: docker.withRegistry doesn't use build environment Probably related to https://issues.jenkins-ci.org/browse/JENKINS-47415 since it fails in the fingerprint. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200791.1563924433000.19826.1563924600043%40Atlassian.JIRA.
[JIRA] (JENKINS-58624) docker.withRegistry doesn't use build environment
Title: Message Title
Paul Eipper created an issue
Jenkins / JENKINS-58624
docker.withRegistry doesn't use build environment
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-commons-plugin
Created:
2019-07-23 23:27
Environment:
Jenkins 2.176.2, linux master, agent on macOS 10.13.6
Priority:
Major
Reporter:
Paul Eipper
When running a pipeline script like this:
node('docker') {
def CURRENT_VERSION
def builtImage
stage('Clone repository') {
checkout scm
}
stage('Output version') {
CURRENT_VERSION = sh (returnStdout: true,
script: 'python "${SCRIPTS}/version.py" show all'
).trim()
}
stage('Build image') {
builtImage = docker.build("${DOCKER_IMAGE}:${CURRENT_VERSION}", ".")
}
stage('Push image') {
docker.withRegistry("${DOCKER_REGISTRY}", "${DOCKER_CREDENTIALS}") {
builtImage.push()
}
}
}
The build fails on the docker.withRegistry stage with error docker command not found:
Successfully built 8e4939ceb3f6
Successfully tagged org/project:2.5.2.112-1-g3cab587
[Pipeline] dockerFingerprintFrom
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExe
[JIRA] (JENKINS-58623) Software caused connection abort: recv failed Error
Title: Message Title kyusun lee created an issue Jenkins / JENKINS-58623 Software caused connection abort: recv failed Error Issue Type: Task Assignee: Unassigned Components: maven-plugin Created: 2019-07-23 23:08 Environment: Windows/ maven / tomcat Priority: Minor Reporter: kyusun lee First of all I'm not perfect in english. sorry. I have problem with install jenkins on my system. When I try to build I have this problem. I don't know why I have Caused by: java.net.SocketException: Software caused connection abort: recv failed problem. Is anyone can help me? Thank you. Started by user unknown or anonymous Running as SYSTEM Building in workspace C:\Program Files (x86)\Jenkins\jobs\bqsPlus\workspace Updating https://BEQUS-SVR/svn/bequs/bqsPlusWeb at revision '2019-07-23T15:03:26.635 +0900' --quiet Using sole credentials pochul2423/** in realm ‘< https://bequs-svr:443 > VisualSVN Server’ At revision 243 No changes for https://bequs-svr/svn/bequs/bqsPlusWeb since the previous build [bqsPlusWeb] $ cmd.exe /C '""C:\Program Files (x86)\Jenkins\tools\hudson.tasks.Maven_MavenInstallation\maven\bin\mvn.cmd"' clean install && exit %%ERRORLEVEL%%" [INFO] Scanning for projects... [INFO] [INFO] --< bqsPlusWeb:bqsPlusWeb >--- [INFO] Building bqsPlusWeb 0.0.1-SNAPSHOT [INFO] ---[ war ][WARNING] The POM for ext:ojdbc6:jar:1.0.0 is missing, no dependency information available[WARNING] The POM for bqsPlus:bqsPlus:jar:0.0.11-SNAPSHOT is missing, no dependency information available[WARNING] The POM for ext:kr.cipher:jar:1.0.0 is missing, no dependency information available[WARNING] The POM for ext:ezPDFExportFile:jar:1.0.0 is missing, no dependency information available[WA
[JIRA] (JENKINS-58622) Throw Exceptions From Library If Errors
Title: Message Title Natasha Stopa commented on JENKINS-58622 Re: Throw Exceptions From Library If Errors Partially addressed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/43. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200788.1563920142000.19821.1563923160195%40Atlassian.JIRA.
[JIRA] (JENKINS-58622) Throw Exceptions From Library If Errors
Title: Message Title Natasha Stopa created an issue Jenkins / JENKINS-58622 Throw Exceptions From Library If Errors Issue Type: Task Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-23 22:15 Labels: plugin-manager gsoc-2019 Priority: Minor Reporter: Natasha Stopa If there are errors in the CLI or library, an exception should be thrown and propagated up. Add Comment
[JIRA] (JENKINS-58622) Throw Exceptions From Library If Errors
Title: Message Title Natasha Stopa started work on JENKINS-58622 Change By: Natasha Stopa 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200788.1563920142000.19820.1563920160246%40Atlassian.JIRA.
[JIRA] (JENKINS-57562) EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC
Title: Message Title Oleg Nenashev updated JENKINS-57562 Jenkins / JENKINS-57562 EC2Cloud crashes with NPE when instanceCapStr is not passed from JCasC Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: ec2-1.44 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199473.1558362521000.19818.1563919740366%40Atlassian.JIRA.
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title
Rajiv Jandial updated an issue
Jenkins / JENKINS-58621
EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Change By:
Rajiv Jandial
Hi - I have an AWS box with ec2-fleet plugin installed in it. I have an "active" spot instance id ( Screen Shot 2019-07-23 at 2.21.59 PM.png) , however, on the Jenkins main page, none of the spot fleet instances are listed (Screen Shot 2019-07-23 at 2.21.59 PM.png).Also, while configuring the job, when I chose "Restrict where this project can be run" as "ec2-fleet" as label , I see this message -" {color:# FF ff }!http://10.201.255.203:8080/static/02001b0c/images/none.gif|width=1,height=16![Label ec2-fleet|http://10.201.255.173:8080/label/ec2-fleet/] is serviced by no nodes and 1 cloud. Permissions or other restrictions provided by plugins may prevent this job from running on those nodes{color} " - (Screen Shot 2019-07-23 at 2.23.54 PM.png).At this time , this plugin is not able to do anything for us to spin up spot instance. Raising this bug as blocker. Jenkins ec2-fleet version - 1.9.2 Thanks,Rajiv
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...@
[JIRA] (JENKINS-58621) EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status
Title: Message Title Rajiv Jandial created an issue Jenkins / JENKINS-58621 EC2-Fleet plugin does not list any spot instances under EC2 Fleet Status Issue Type: Bug Assignee: Chad Schmutzer Attachments: Screen Shot 2019-07-23 at 2.21.59 PM.png, Screen Shot 2019-07-23 at 2.22.35 PM.png, Screen Shot 2019-07-23 at 2.23.54 PM.png Components: ec2-fleet-plugin Created: 2019-07-23 20:27 Priority: Critical Reporter: Rajiv Jandial Hi - I have an AWS box with ec2-fleet plugin installed in it. I have an "active" spot instance id ( Screen Shot 2019-07-23 at 2.21.59 PM.png) , however, on the Jenkins main page, none of the spot fleet instances are listed (Screen Shot 2019-07-23 at 2.21.59 PM.png). Also, while configuring the job, when I chose "Restrict where this project can be run" as "ec2-fleet" as label , I see this message -" Label ec2-fleet is serviced by no nodes and 1 cloud. Permissions or other restrictions provided by plugins may prevent this job from running on those nodes " - (Screen Shot 2019-07-23 at 2.23.54 PM.png). At this time , this plugin is not able to do anything for us to spin up spot instance. Raising this bug as blocker. Thanks,Rajiv
[JIRA] (JENKINS-58402) On Windows slaves, any call of dependency check tool results in "The input line is too long" error
Title: Message Title Christoph Amshoff updated JENKINS-58402 Dependency-Check version 5.2.0 works fine, consider issue fixed. Jenkins / JENKINS-58402 On Windows slaves, any call of dependency check tool results in "The input line is too long" error Change By: Christoph Amshoff 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200527.1562668975000.19767.1563913440582%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title
Sergei Parshev created an issue
Jenkins / JENKINS-58620
MPL shared library logic execution caused CPS mismatch warning
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2019-07-23 20:22
Environment:
Jenkins 2.176.2 with minimal plugins to execute pipeline shared libraries (git, pipeline, pipeline shared libs).
Labels:
pipeline cps groovy workflow-cps mpl
Priority:
Minor
Reporter:
Sergei Parshev
We found a change that prints an annoying warning about the CPS mismatch during running the MPL module: https://github.com/griddynamics/mpl/issues/31
Running on Jenkins in /var/jenkins_home/workspace/mpl-master
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] fileExists
expected to call org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.evaluate but wound up catching Checkout.run; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/
We're not quite sure how to fix that in the library, but realized that the issue is related to the change JENKINS-31314 introduced in workflow-cps-2.71. Reproduce is quite simple - just need to install the minimal latest jenkins, add required git & shared lib plugins, attach mpl library from github and create a simple jenkins job to build the mpl. It will fail (no Maven
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Tobias Gruetzmacher edited a comment on JENKINS-42209 Re: Support for locking of multiple resource labels/groups This feature is already available for pipeline jobs. I would be willing to incorporate this feature for legacy jobs if anybody want to write it (maybe based on [https://github.com/jenkinsci/lockable-resources-plugin/pull/38]?) - I won't implement it, because I only use pipeline jobs nowadays... (Feel free to reopen this issue when starting work on 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179096.148763696.19741.1563908880328%40Atlassian.JIRA.
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Tobias Gruetzmacher closed an issue as Won't Do Jenkins / JENKINS-42209 Support for locking of multiple resource labels/groups Change By: Tobias Gruetzmacher Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179096.148763696.19727.1563908821509%40Atlassian.JIRA.
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Tobias Gruetzmacher commented on JENKINS-42209 Re: Support for locking of multiple resource labels/groups This feature is already available for pipeline jobs. I would be willing to incorporate this feature for legacy jobs if anybody want to write it (maybe based on https://github.com/jenkinsci/lockable-resources-plugin/pull/38?) - I won't implement it, because I only use pipeline jobs nowadays... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179096.148763696.19713.1563908760309%40Atlassian.JIRA.
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Tobias Gruetzmacher assigned an issue to Unassigned Jenkins / JENKINS-42209 Support for locking of multiple resource labels/groups Change By: Tobias Gruetzmacher Assignee: Tobias Gruetzmacher 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179096.148763696.19699.1563908520367%40Atlassian.JIRA.
[JIRA] (JENKINS-42209) Support for locking of multiple resource labels/groups
Title: Message Title Tobias Gruetzmacher assigned an issue to Tobias Gruetzmacher Jenkins / JENKINS-42209 Support for locking of multiple resource labels/groups Change By: Tobias Gruetzmacher Assignee: Antonio Muñiz Tobias Gruetzmacher 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179096.148763696.19685.1563908460698%40Atlassian.JIRA.
[JIRA] (JENKINS-55579) I suggest to add an ability to disable dashboard widget or deactivate plugin at all
Title: Message Title Kanstantsin Shautsou commented on JENKINS-55579 Re: I suggest to add an ability to disable dashboard widget or deactivate plugin at all As administrator i'm not interested in widgets because they are fixed width size. Separate page is more useful (already exists). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196743.1547475231000.19682.1563907140363%40Atlassian.JIRA.
[JIRA] (JENKINS-54495) Better handling of GitHub Organization folder scan to avoid API quota
Title: Message Title Eugene G commented on JENKINS-54495 Re: Better handling of GitHub Organization folder scan to avoid API quota This is very important. If an organization has tons of old repos and more than 50 repos with Jenkinsfiles it becomes crazy to maintain the list of repos in this small filter field. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195265.1541518348000.19675.1563906420412%40Atlassian.JIRA.
[JIRA] (JENKINS-58619) execute commands such as git inside jenkins DSL plugin for dynamic parameters
Title: Message Title SR updated an issue Jenkins / JENKINS-58619 execute commands such as git inside jenkins DSL plugin for dynamic parameters Change By: SR Summary: execute commands such as git inside jenkins DSL plugin having for dynamic parameters 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200785.1563905144000.19673.1563905340176%40Atlassian.JIRA.
[JIRA] (JENKINS-58619) execute commands such as git inside jenkins DSL plugin having dynamic parameters
Title: Message Title SR created an issue Jenkins / JENKINS-58619 execute commands such as git inside jenkins DSL plugin having dynamic parameters Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin, groovy-plugin Created: 2019-07-23 18:05 Environment: Jenkins ver. 2.164.2 Active Choices Plug-in 2.1 Labels: jenkins ActiveChoices Plugins groovy-script Priority: Minor Reporter: SR Would like to generate dynamic choices from git repository. So, within groovySrcipt's script section, properties([ parameters([ [$class: 'ChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: 'Choose env', name: 'ENVIRONMENT', sandbox: true, script: 'return["none","dev","int","prod"]' ] script: [ $class: 'GroovyScript', fallbackScript: [ classpath: [], sandbox: true, script: 'return[\'Environment not found\']' ], script: [ classpath: [], ] ], [$class: 'CascadeChoiceParameter', choiceType: 'PT_SINGLE_SELECT', description: 'Choose snapshot for selected env', name: 'SNAPSHOT', referencedParameters: 'ENVIRONMENT', script: [ $class: 'GroovyScript', fallbackScript: [ classpath: [], sandbox: true, script: 'return["FAILED"]' ], script: [ classpath: [], sandbox: true, script: """ def snapshotsL = "git tag -l --sort=v:refname \"v*-SNAPSHOT\" | tai
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Guilherme Emiliano Zanella commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins I do this and the error has gone. Thank you for help! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.19644.1563900300885%40Atlassian.JIRA.
[JIRA] (JENKINS-58573) 100% CPU remoting.jar or slave.jar on EC2 (connection refused)
Title: Message Title Gunter Grodotzki commented on JENKINS-58573 Re: 100% CPU remoting.jar or slave.jar on EC2 (connection refused) Removing `ec2-plugin` as possible culprit. I launched a EC2 instance (same config) and manually attached it as a permanent node. Eventually it started crashing again. I am seeing the following in the logs: jenkins-slave.2.log:2019-07-23T13:16:10.220+ WARNING hudson.Proc$LocalProc join: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information jenkins-slave.2.log:2019-07-23T13:28:54.652+ WARNING hudson.Proc$LocalProc join: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information But while not ideal that should not cause remoting.jar to crash completely? I will try a slightly different setup with Debian 10 and OpenJDK11 to eliminate os issues. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200725.1563549166000.19618.1563898020121%40Atlassian.JIRA.
[JIRA] (JENKINS-58573) 100% CPU remoting.jar or slave.jar on EC2 (connection refused)
Title: Message Title Gunter Grodotzki updated an issue Jenkins / JENKINS-58573 100% CPU remoting.jar or slave.jar on EC2 (connection refused) Change By: Gunter Grodotzki Component/s: ec2-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200725.1563549166000.19615.1563897840243%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Dénes Zsolt edited a comment on JENKINS-57899 Re: Jira site configuration lost after a reboot happens every time, after jenkins restart. For example if a plugin installed/updated and you have to restart tzhe the jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.19608.1563896760463%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Dénes Zsolt commented on JENKINS-57899 Re: Jira site configuration lost after a reboot happens every time, after jenkins restart. For example if a plugin installed/updated and you have to restart tzhe jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.19601.1563896700214%40Atlassian.JIRA.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title Jesse Glick commented on JENKINS-26481 Re: Mishandling of binary methods accepting Closure Ilguiz Latypov this ought to have been addressed (in the form of a warning) by JENKINS-31314. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160147.1421607875000.19464.1563896282740%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Jeff Thompson commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins That explains your observations, Guilherme Emiliano Zanella. The change went into the 2.185 weekly release. You've got the latest LTS release, which doesn't have this change. You could request this change be backported to the next incremental release of the LTS. I would be hesitant to backport this, given its experimental nature and we have a report of the change not fixing things for someone. You could switch from using the LTS line to the weekly. See [LTS Release Line](https://jenkins.io/download/lts/) for more information. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.19441.1563895384239%40Atlassian.JIRA.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-26481
Re: Mishandling of binary methods accepting Closure
Another limit is still annoying because it silently returns from a NonCPS method calling a CPS method. {code:java}@NonCPSpublic static String readCurrentVersion(String fileContent) {def xml = new XmlSlurper().parseText( Strings. deBOM(fileContent))String retval = "${xml.metadata.version}"xml = nullreturn retval}// Omitted @NonCPS herepublic static CharSequence deBOM(CharSequence s) {[...]return s}{code}Calling readCurrentVersion from the above unexpectedly returned the entire fileContent. This is probably another unexpected behaviour but seems worth mentioning 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160147.1421607875000.19300.1563893447289%40Atlassian.JIRA.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title
Ilguiz Latypov edited a comment on JENKINS-26481
Re: Mishandling of binary methods accepting Closure
Another limit is still annoying because it silently returns from a NonCPS method calling a CPS method. {code:java}@NonCPSpublic static String readCurrentVersion(String fileContent) {def xml = new XmlSlurper().parseText(Strings.deBOM(fileContent))String retval = "${xml.metadata.version}"xml = nullreturn retval}// Omitted @NonCPS herepublic static CharSequence deBOM(CharSequence s) {[...]return s}{code}Calling updateMyXML readCurrentVersion from the above unexpectedly returned the entire fileContent. This is probably another unexpected behaviour but seems worth mentioning 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160147.1421607875000.19163.1563893441300%40Atlassian.JIRA.
[JIRA] (JENKINS-26481) Mishandling of binary methods accepting Closure
Title: Message Title
Ilguiz Latypov commented on JENKINS-26481
Re: Mishandling of binary methods accepting Closure
Another limit is still annoying because it silently returns from a NonCPS method calling a CPS method.
@NonCPS
public static String readCurrentVersion(String fileContent) {
def xml = new XmlSlurper().parseText(Strings.deBOM(fileContent))
String retval = "${xml.metadata.version}"
xml = null
return retval
}
// Omitted @NonCPS here
public static CharSequence deBOM(CharSequence s) {
[...]
return s
}
Calling updateMyXML from the above unexpectedly returned the entire fileContent. This is probably another unexpected behaviour but seems worth mentioning 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160147.1421607875000.19026.1563893405768%40Atlassian.JIRA.
[JIRA] (JENKINS-58618) Only ignores PRs from untrusted sources "once"
Title: Message Title Brian J Murrell created an issue Jenkins / JENKINS-58618 Only ignores PRs from untrusted sources "once" Issue Type: Bug Assignee: Unassigned Attachments: image-2019-07-23-10-30-22-210.png Components: basic-branch-build-strategies-plugin Created: 2019-07-23 14:39 Environment: Jenkins ver. 2.176.2 Priority: Critical Reporter: Brian J Murrell Note: setting to Critical as this exposes serious security issues. The Ignore change requests flagged as originating from an untrusted source build strategy: seems to only work on the first commit to a PR from an untrusted source. If a somebody with the appropriate permissions executes a Build Now on that PR, presumably because they have done a code inspection looking for nefarious use of the build and test resources, any subsequent pushes to that PR, even from untrusted sources will get automatically built, without the need for somebody to again go execute a Build Now. This of course means that such a PR could introduce nefarious use, without review, after having it's first commit in the PR approved and built. Every new commit to a PR from an untrusted source needs to be prevented from building until somebody approves it with an explicit Build Now click. Otherwise this whole option becomes much less useful.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Brian J Murrell updated an issue Jenkins / JENKINS-53752 Block PRs from forks from untrusted users Change By: Brian J Murrell Attachment: image-2019-07-23-10-28-00-893.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194259.1537809356000.18995.1563892140501%40Atlassian.JIRA.
[JIRA] (JENKINS-53752) Block PRs from forks from untrusted users
Title: Message Title Brian J Murrell commented on JENKINS-53752 Re: Block PRs from forks from untrusted users Isn't this option: supposed to achieve what is being asked for in this 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194259.1537809356000.19002.1563892140587%40Atlassian.JIRA.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title Jesse Glick commented on JENKINS-39667 Re: PIpeline job ignores custom workspace location Just use the dir or ws steps as needed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176244.1478864055000.18988.1563892081554%40Atlassian.JIRA.
[JIRA] (JENKINS-58116) "Request too large" in p4-plugin 1.10 (works with 1.9.7)
Title: Message Title Paul Allen commented on JENKINS-58116 Re: "Request too large" in p4-plugin 1.10 (works with 1.9.7) Released in 1.10.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200161.1561031961000.18985.1563892081357%40Atlassian.JIRA.
[JIRA] (JENKINS-57870) Request too large for server memory since 10.1.0
Title: Message Title Paul Allen commented on JENKINS-57870 Re: Request too large for server memory since 10.1.0 Released in 1.10.3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199833.1559782353000.18979.1563892020293%40Atlassian.JIRA.
[JIRA] (JENKINS-58504) P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type
Title: Message Title Paul Allen updated JENKINS-58504 Released in 1.10.3 Jenkins / JENKINS-58504 P4 Plugin tries to make depot location of Jenkinsfile available regardless of SCM type Change By: Paul Allen Status: In Review Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200647.1563234801000.18976.1563891960323%40Atlassian.JIRA.
[JIRA] (JENKINS-58288) Integrate Cloud API implementation with Helm chart
Title: Message Title Long Nguyen started work on JENKINS-58288 Change By: Long Nguyen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200352.1562008698000.18974.1563891840076%40Atlassian.JIRA.
[JIRA] (JENKINS-57668) Implement Cloud API to provision Kafka agents
Title: Message Title Long Nguyen updated JENKINS-57668 Jenkins / JENKINS-57668 Implement Cloud API to provision Kafka agents Change By: Long Nguyen 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199601.1558718371000.18972.1563891780174%40Atlassian.JIRA.
[JIRA] (JENKINS-58218) Support JCasC
Title: Message Title Long Nguyen resolved as Done Jenkins / JENKINS-58218 Support JCasC Change By: Long Nguyen Status: Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200278.1561572456000.18973.1563891780217%40Atlassian.JIRA.
[JIRA] (JENKINS-34580) Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs
Title: Message Title Arnaud Richard commented on JENKINS-34580 Re: Enable downstream test result aggregation in Pipeline jobs like in Buildflow jobs Considering that pipeline is now THE way to go with Jenkins, the feature would greatly simplify the flow for people implementing pipeline for specific usage. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170201.1462312461000.18949.1563891060406%40Atlassian.JIRA.
[JIRA] (JENKINS-57796) Checkmarx affected by JEP-200
Title: Message Title Liran Stern commented on JENKINS-57796 Re: Checkmarx affected by JEP-200 Hello We have just uploaded 8.90.4 which should fix an additional case of "Failed to serialize...". We hope this will fix the problem you are facing. It should be on the site within 1-2 days. I'd appreciate if you share your experience with that plugin version. I apologize for the inconvenience, Liran 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199746.1559317468000.18932.1563888240267%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Guilherme Emiliano Zanella commented on JENKINS-55945 Re: Got IllegalStateException while restart Jenkins Jeff Thompson Says I have the Jenkins 2.176.2. About Jenkins 2.176.2 [Jenkins].pdf 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.18910.1563886560628%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Guilherme Emiliano Zanella updated an issue Jenkins / JENKINS-55945 Got IllegalStateException while restart Jenkins Change By: Guilherme Emiliano Zanella Attachment: About Jenkins 2.176.2 [Jenkins].pdf 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.18879.1563886442168%40Atlassian.JIRA.
[JIRA] (JENKINS-55945) Got IllegalStateException while restart Jenkins
Title: Message Title Guilherme Emiliano Zanella updated an issue Jenkins / JENKINS-55945 Got IllegalStateException while restart Jenkins Change By: Guilherme Emiliano Zanella Attachment: About Jenkins 2.176.2 [Jenkins].pdf 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197354.1549278137000.18852.1563886441783%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer commented on JENKINS-57899 Re: Jira site configuration lost after a reboot I had the same issue with jira-plugin 3.0.8 Question: what do you mean by "reboot"? - restart of jenkins or reboot of the machine? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.18844.1563886200441%40Atlassian.JIRA.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jakov Sosic commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines It seems that adding $JAVA_HOME in Global properties indeed fixes this! Since I run CentOS 7, this is what I've added: Name: JAVA_HOME Value: /usr/lib/jvm/jre-1.8.0-openjdk 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196395.1545434467000.18808.1563886020859%40Atlassian.JIRA.
[JIRA] (JENKINS-47449) support-core bundles jsr305 annotations
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-47449 support-core bundles jsr305 annotations Change By: Allan BURDAJEWICZ Assignee: Steven Christou Allan BURDAJEWICZ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185896.1508157391000.18785.1563885180836%40Atlassian.JIRA.
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title ASHOK MOHANTY commented on JENKINS-39667 Re: PIpeline job ignores custom workspace location Quick question.. We are using Jenkins 2.121.3 (& planning to upgrade to 2.164.3). Can I use custom workspace in Multibranch/Script 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176244.1478864055000.18788.1563885180997%40Atlassian.JIRA.
[JIRA] (JENKINS-41118) Allow custom workspaces in declarative pipeline
Title: Message Title ASHOK MOHANTY commented on JENKINS-41118 Re: Allow custom workspaces in declarative pipeline Quick question.. We are using Jenkins 2.121.3 (& planning to upgrade to 2.164.3). Can I use custom workspace in Multibranch/Script 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177875.1484616066000.18773.1563884820337%40Atlassian.JIRA.
[JIRA] (JENKINS-47027) "Not valid UTF8" when using umlauts in Failure cause management
Title: Message Title Stephan Pauxberger commented on JENKINS-47027 Re: "Not valid UTF8" when using umlauts in Failure cause management This seems to be a problem in encoding the form values. I solved that by switching to POST, see: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/109 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185408.1506001816000.18770.1563884520131%40Atlassian.JIRA.
[JIRA] (JENKINS-58617) URL in BlueOcean are not shown as links in Tests tab as it is in Pipeline tab.
Title: Message Title Jesús Lunar Pérez created an issue Jenkins / JENKINS-58617 URL in BlueOcean are not shown as links in Tests tab as it is in Pipeline tab. Issue Type: Bug Assignee: Ivan Meredith Attachments: pipeline_tab.png, tests_tab.png Components: blueocean-display-url-plugin Created: 2019-07-23 12:06 Environment: 1.17.0 Core 2.180 Priority: Minor Reporter: Jesús Lunar Pérez As we can see in attached images, URL links are shown properly as links in Pipeline tab but not in Tests tabs. Add Comment
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-51552 Cannot replay pipelines - files are read-only Change By: Karl Wirth Labels: P4_B pipeline replay P4_VERIFY 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.18759.1563883200435%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title
Karl Wirth commented on JENKINS-51552
Re: Cannot replay pipelines - files are read-only
Hi Erez Arbell - Thanks for all your help. I have been able to reproduce the problem with the following setup: (1) Submit //depot/lib_autoload/libs/src/com/f/v/Utils.groovy
#!groovy
package com.f.v
class Utils implements Serializable {
static void main()
{
println("This is in Utils Library")
}
static void test()
{
println("This is test in Utils in the Library")
}
}
(2) Define a pipeline job with groovy code in GUI editor:
// Define globals
def fLibts{
try {
node ('master') {
Lib = loadFLib()
def buildData = Lib.com.f.v.Utils.test();
}
}
catch (e) {
throw e
}
echo "Running some tests here..."
}// Load a specific Library
def loadFLib() {
def p4ClientFormat = "jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-flib"
return loadLibrary(
identifier: 'f@1',
clientFormat: p4ClientFormat,
p4Mapping: "//depot/lib_autoload/libs/src/com/f/v/... //${p4ClientFormat}/src/com/f/v/...\n"
)
}// Generic Library Loader
def loadLibrary(args)
{
def lib = library(
identifier: args.identifier,
retriever: legacySCM([
$class: 'PerforceScm',
credential: 'JenkinsMaster',
populate: [
$class: 'AutoCleanImpl',
delete: true,
modtime: false,
pin: '',
quiet: false,
replace: true
],
workspace: manualSpec(
charset: 'none',
name: args.clientFormat,
pinHost: false,
spec: clientSpec(
allwrite: false, backup: false, clobber: true, compress: false, line: 'LOCAL',
locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE',
view: args.p4Mapping
)
)
])
)
return lib
}
(3) Run the job. (4) When you use the 'Replay' option for the same job you see:
11:21:41 P4: saving built changes.
11:21:41 ... p4 client -o jenkins-master-JENKINS-57314-ExplicitLocalLib-Replay-2-flib
+11:21:41 ... p4 info
+11:21:41 ... p4 info
+11:21:41 ... p4 client -o jenkins-master-JENKINS-57314-ExplicitLocalLib-Replay-2-flib
+11:21:41 ... done
11:21:41
11:21:41 Replacing contents of src/com/f/v/Utils.groovy
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] End of Pipeline
java.nio.file.AccessDeniedException: /var/lib/jenkins/jobs/JENKINS-57314-ExplicitLocalLib-Replay/builds/25/libs/f/src/com/f/v/Utils.groovy
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixEx
[JIRA] (JENKINS-58616) Weblogic Deployment Issue
Title: Message Title Jegath Kumar updated an issue Jenkins / JENKINS-58616 Weblogic Deployment Issue Change By: Jegath Kumar Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200780.1563882376000.18749.1563882540489%40Atlassian.JIRA.
[JIRA] (JENKINS-58616) Weblogic Deployment Issue
Title: Message Title Jegath Kumar created an issue Jenkins / JENKINS-58616 Weblogic Deployment Issue Issue Type: Bug Assignee: Raphael CHAUMIER Attachments: config.xml, Jenkins.docx Components: weblogic-deployer-plugin Created: 2019-07-23 11:46 Priority: Minor Reporter: Jegath Kumar Hi Team , We are new to Jenkins and try to explore the ear deployment in the weblogic server using Jenkins. We are trying to deploy the ear file in to my local web logic server (12.2.1.1) from my local windows machine. I am getting below error from the console out put . Remote directory configured in plugin xml configuration must be set for library deployment. Please check your configuration. java.io.IOException: Remote directory configured in plugin xml configuration must be set for library deployment at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.deploy(DeploymentTaskServiceImpl.java:226) at org.jenkinsci.plugins.deploy.weblogic.task.DeploymentTaskServiceImpl.perform(DeploymentTaskServiceImpl.java:178) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin.perform(WeblogicDeploymentPlugin.java:303) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1840) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) I have attached the all related files in tick
[JIRA] (JENKINS-58600) can't resolve libraries of form vX.X.0
Title: Message Title Mark Waite edited a comment on JENKINS-58600 Re: can't resolve libraries of form vX.X.0 I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself. Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library?Does it return to correct function if you revert to the plugin versions before the last successful clone of a tagged pipeline shared library?Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch? Refer to JENKINS-48061 as a possible source of additional information about using tagged non-tip references to pipeline shared libraries. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200759.1563798042000.18745.1563880500136%40Atlassian.JIRA.
[JIRA] (JENKINS-58600) can't resolve libraries of form vX.X.0
Title: Message Title Mark Waite edited a comment on JENKINS-58600 Re: can't resolve libraries of form vX.X.0 I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself. Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library? If Does it return to correct function if you revert to the plugin versions before the last successful clone of a tagged pipeline shared library?Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch? Refer to JENKINS-48061 as a possible source of additional information about using tagged references to pipeline shared libraries. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200759.1563798042000.18740.1563880380318%40Atlassian.JIRA.
[JIRA] (JENKINS-58600) can't resolve libraries of form vX.X.0
Title: Message Title Mark Waite commented on JENKINS-58600 Re: can't resolve libraries of form vX.X.0 I'm more suspicious that the issue may be a result of recent changes in scm-api and branch-api, but I'm not able to spend the necessary time currently to do that investigation myself. Which plugins have been updated on your installation since the last successful clone of a tagged pipeline shared library? If you revert to the plugin versions before the last successful clone of a tagged pipeline shared library? Has there been a commit to the affected pipeline shared library which has now caused the tagged commit to no longer be the tip of a branch? Refer to JENKINS-48061 as a possible source of additional information about using tagged references to pipeline shared libraries. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200759.1563798042000.18738.1563880020106%40Atlassian.JIRA.
[JIRA] (JENKINS-58612) some plugins does not install
Title: Message Title
Mark Waite edited a comment on JENKINS-58612
Re: some plugins does not install
This is not a bug. Please don't use the Jenkins issue tracker to request help with configuration errors. When a bug report is misused to request help with a configuration error, it relies on a very small group of readers of bug reports to assist when a much larger group is available to assist on the Jenkins user mailing list and the Jenkins chat channels.I confirmed that Jenkins 2.176.2 starts and downloads all the suggested plugins as expected when the {{Install Suggested Plugins}} button is selected.Follow the instructions which are listed in the error message and install the plugins that are listed as "Fix this plugin first". Also, assure that you are running a supported version of Jenkins, either Java 8 or Java 11. The Jenkins project does not support Java 9, Java 10, Java 12, or Java 13.The plugin versions installed when I installed the suggested plugins with Jenkins 2.176.2 were:{ normal noformat }antisamy-markup-formatter:1.5apache-httpcomponents-client-4-api:4.5.5-3.0authentication-tokens:1.3bouncycastle-api:2.17branch-api:2.5.3build-timeout:1.19cloudbees-folder:6.9command-launcher:1.3credentials:2.2.0credentials-binding:1.19display-url-api:2.3.1docker-commons:1.15docker-workflow:1.18durable-task:1.30email-ext:2.66git:3.10.1git-client:2.8.0github:1.29.4github-api:1.95github-branch-source:2.5.4git-server:1.7gradle:1.33handlebars:1.1.1jackson2-api:2.9.9.1jdk-tool:1.3jquery-detached:1.2.1jsch:0.1.55junit:1.28ldap:1.20lockable-resources:2.5mailer:1.23mapdb-api:1.0.9.0matrix-auth:2.4.2matrix-project:1.14momentjs:1.1.1pam-auth:1.5.1pipeline-build-step:2.9pipeline-github-lib:1.0pipeline-graph-analysis:1.10pipeline-input-step:2.10pipeline-milestone-step:1.3.1pipeline-model-api:1.3.9pipeline-model-declarative-agent:1.1.1pipeline-model-definition:1.3.9pipeline-model-extensions:1.3.9pipeline-rest-api:2.11pipeline-stage-step:2.3pipeline-stage-tags-metadata:1.3.9pipeline-stage-view:2.11plain-credentials:1.5resource-disposer:0.13scm-api:2.6.3script-security:1.61ssh-credentials:1.17.1ssh-slaves:1.30.1structs:1.19subversion:2.12.2timestamper:1.10token-macro:2.8workflow-aggregator:2.6workflow-api:2.35workflow-basic-steps:2.18workflow-cps:2.72workflow-cps-global-lib:2.14workflow-durable-task-step:2.32workflow-job:2.33workflow-multibranch:2.21workflow-scm-step:2.9workflow-step-api:2.20workflow-support:3.3ws-cleanup:0.37{ normal noformat }
Add Comment
[JIRA] (JENKINS-58612) some plugins does not install
Title: Message Title Mark Waite updated JENKINS-58612 Jenkins / JENKINS-58612 some plugins does not install Change By: Mark Waite 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200775.1563870744000.18734.1563879720239%40Atlassian.JIRA.
[JIRA] (JENKINS-58612) some plugins does not install
Title: Message Title
Mark Waite updated JENKINS-58612
This is not a bug. Please don't use the Jenkins issue tracker to request help with configuration errors. When a bug report is misused to request help with a configuration error, it relies on a very small group of readers of bug reports to assist when a much larger group is available to assist on the Jenkins user mailing list and the Jenkins chat channels. I confirmed that Jenkins 2.176.2 starts and downloads all the suggested plugins as expected when the Install Suggested Plugins button is selected. Follow the instructions which are listed in the error message and install the plugins that are listed as "Fix this plugin first". Also, assure that you are running a supported version of Jenkins, either Java 8 or Java 11. The Jenkins project does not support Java 9, Java 10, Java 12, or Java 13. The plugin versions installed when I installed the suggested plugins with Jenkins 2.176.2 were: {normal} antisamy-markup-formatter:1.5 apache-httpcomponents-client-4-api:4.5.5-3.0 authentication-tokens:1.3 bouncycastle-api:2.17 branch-api:2.5.3 build-timeout:1.19 cloudbees-folder:6.9 command-launcher:1.3 credentials:2.2.0 credentials-binding:1.19 display-url-api:2.3.1 docker-commons:1.15 docker-workflow:1.18 durable-task:1.30 email-ext:2.66 git:3.10.1 git-client:2.8.0 github:1.29.4 github-api:1.95 github-branch-source:2.5.4 git-server:1.7 gradle:1.33 handlebars:1.1.1 jackson2-api:2.9.9.1 jdk-tool:1.3 jquery-detached:1.2.1 jsch:0.1.55 junit:1.28 ldap:1.20 lockable-resources:2.5 mailer:1.23 mapdb-api:1.0.9.0 matrix-auth:2.4.2 matrix-project:1.14 momentjs:1.1.1 pam-auth:1.5.1 pipeline-build-step:2.9 pipeline-github-lib:1.0 pipeline-graph-analysis:1.10 pipeline-input-step:2.10 pipeline-milestone-step:1.3.1 pipeline-model-api:1.3.9 pipeline-model-declarative-agent:1.1.1 pipeline-model-definition:1.3.9 pipeline-model-extensions:1.3.9 pipeline-rest-api:2.11 pipeline-stage-step:2.3 pipeline-stage-tags-metadata:1.3.9 pipeline-stage-view:2.11 plain-credentials:1.5 resource-disposer:0.13 scm-api:2.6.3 script-security:1.61 ssh-credentials:1.17.1 ssh-slaves:1.30.1 structs:1.19 subversion:2.12.2 timestamper:1.10 token-macro:2.8 workflow-aggregator:2.6 workflow-api:2.35 workflow-basic-steps:2.18 workflow-cps:2.72 workflow-cps-global-lib:2.14 workflow-durable-task-step:2.32 workflow-job:2.33 workflow-multibranch:2.21 workflow-scm-step:2.9 workflow-step-api:2.20 workflow-support:3.3 ws-cleanup:0.37{normal}
Jenkins / JENKINS-58612
some plugins does not install
Change By:
Mark Waite
Status:
Open Fixed but Unreleased
Resolution:
Not A Defect
[JIRA] (JENKINS-58602) Some secret values are getting displayed in the kubernetes pod spec
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58602 Some secret values are getting displayed in the kubernetes pod spec Change By: Jesse Glick Labels: security 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200762.1563807538000.18730.1563879660709%40Atlassian.JIRA.
[JIRA] (JENKINS-58614) Jenkins exception in running Octane Pipeline job
Title: Message Title Daniel Gront assigned an issue to Radi Berkovich Jenkins / JENKINS-58614 Jenkins exception in running Octane Pipeline job Change By: Daniel Gront Assignee: Daniel Gront Radi Berkovich 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200777.1563876498000.18726.1563877800243%40Atlassian.JIRA.
[JIRA] (JENKINS-58613) Octane pipeline trigger fails when root job has a duplicate name in Jenkins
Title: Message Title Daniel Gront assigned an issue to Radi Berkovich Jenkins / JENKINS-58613 Octane pipeline trigger fails when root job has a duplicate name in Jenkins Change By: Daniel Gront Assignee: Daniel Gront Radi Berkovich 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200776.1563876126000.18723.1563877740271%40Atlassian.JIRA.
[JIRA] (JENKINS-58615) incrementals:update ignores imported BOMs
Title: Message Title Jesse Glick commented on JENKINS-58615 Re: incrementals:update ignores imported BOMs mvn versions:display-dependency-updates does not mention the BOM either, so this might be an issue upstream in versions-maven-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200778.1563876677000.18717.1563877260042%40Atlassian.JIRA.
[JIRA] (JENKINS-58605) in pom.xml must not point to plugins.jenkins.io
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-58605 Change By: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200765.1563823331000.18714.1563877200657%40Atlassian.JIRA.
[JIRA] (JENKINS-58605) in pom.xml must not point to plugins.jenkins.io
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58605 Jenkins / JENKINS-58605 in pom.xml must not point to plugins.jenkins.io Change By: Ivan Fernandez Calvo 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200765.1563823331000.18716.1563877200695%40Atlassian.JIRA.
[JIRA] (JENKINS-58615) incrementals:update ignores imported BOMs
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58615 incrementals:update ignores imported BOMs Issue Type: Bug Assignee: Unassigned Components: incrementals-tools Created: 2019-07-23 10:11 Priority: Minor Reporter: Jesse Glick UpdateMojo seems to make no mention of BOMs imported in dependencyManagement. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58614) Jenkins exception in running Octane Pipeline job
Title: Message Title Alberto Stevanato created an issue Jenkins / JENKINS-58614 Jenkins exception in running Octane Pipeline job Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-07-23 10:08 Environment: Jenkins ver. 2.150.2 MF Plugin 5.8 Octane CP10 on-Prem Labels: plugin jenkins pipeline octane Priority: Major Reporter: Alberto Stevanato Hello, Excecuting a job connected to Octane (from the tool or from Jenkins) causes some exceptions that kills the entire server. The issue happens when executing a job that triggers Gherkin tests on a Kubernetes pod through Maven goals. Tests are executed and Gherkin Results are generated (through the Octane Cucumber JVM). The first exception (arose when above results are not generated) is: Caused by: java.lang.RuntimeException: Failed to serialize com.microfocus.application.automation.tools.octane.actions.cucumber.CucumberTestResultsAction#workspace for class com.microfocus.application.automation.tools.octane.actions.cucumber.CucumberTestResultsAction at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) While the exception that stopped the service seems to be: java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1085) at com.microfocus.application.automation.tools.octane.CIJenkinsServicesImpl.getOctaneLogFile(CIJenkinsServicesImpl.java:566) at com.microfocus.application.automation.tools.o
[JIRA] (JENKINS-58613) Octane pipeline trigger fails when root job has a duplicate name in Jenkins
Title: Message Title Alberto Stevanato created an issue Jenkins / JENKINS-58613 Octane pipeline trigger fails when root job has a duplicate name in Jenkins Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-07-23 10:02 Environment: Jenkins ver. 2.150.2 MF Plugin 5.8 Octane CP10 on-Prem Labels: plugin jenkins pipeline octane Priority: Critical Reporter: Alberto Stevanato Hello, When configuring a pipeline in Octane to point to a job which has the same on another job (in a different location) Octane fails in triggering the pointed job, while it triggers the second one. Example Job 1: my/job/in/Jenkins --> root job for Octane Job 2: my/other/job/in/Jenkins --> root job for Octane Creating a Pipeline on Job 1 and triggering on Octane, it starts the second and data are not sent back. Running the first one from Jenkins, means having partial results back. Adding the pipeline, Octane correctly sees the jobs path, however. Don’t know if this is an expected behavior or not.
[JIRA] (JENKINS-58611) Implement method comparison for var-args
Title: Message Title Akram Ben Aissi commented on JENKINS-58611 Re: Implement method comparison for var-args Have some common points with: https://issues.jenkins-ci.org/browse/JENKINS-56758 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200772.1563868512000.18620.1563875880223%40Atlassian.JIRA.
[JIRA] (JENKINS-24387) Support parsing output of $(tput sgr0)
Title: Message Title Vlad Aginsky commented on JENKINS-24387 Re: Support parsing output of $(tput sgr0) raised to major, hopefully to get attention. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156907.1408693623000.18614.1563875820627%40Atlassian.JIRA.
[JIRA] (JENKINS-24387) Support parsing output of $(tput sgr0)
Title: Message Title Vlad Aginsky updated an issue Jenkins / JENKINS-24387 Support parsing output of $(tput sgr0) Change By: Vlad Aginsky 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156907.1408693623000.18612.1563875820596%40Atlassian.JIRA.
[JIRA] (JENKINS-20481) Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary)
Title: Message Title P4 commented on JENKINS-20481 Re: Successful builds fails at the end (Could not initialize class hudson.util.jna.GNUCLibrary) We've got the same issue here. Master: Windows Server 2012 R2, Jenkins v2.176.2, jdk1.8.0_172 Agent: Windows 10, jre1.8.0_221 Jul 23, 2019 10:59:14 AM hudson.plugins.signal_killer.SignalKiller kill SEVERE: Can't kill process! java.lang.UnsatisfiedLinkError: Unable to load library 'c': Native library (win32-x86/c.dll) not found in resource path ([]) at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:303) at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:427) at com.sun.jna.Library$Handler.(Library.java:179) at com.sun.jna.Native.loadLibrary(Native.java:569) at com.sun.jna.Native.loadLibrary(Native.java:544) at hudson.util.jna.GNUCLibrary.(GNUCLibrary.java:115) at hudson.plugins.signal_killer.SignalKiller.sendSignal(SignalKiller.java:56) at hudson.plugins.signal_killer.SignalKiller.kill(SignalKiller.java:35) at hudson.util.ProcessTree$OSProcess.killByKiller(ProcessTree.java:248) at hudson.util.ProcessTree$WindowsOSProcess.killRecursively(ProcessTree.java:525) at hudson.util.ProcessTree.killAll(ProcessTree.java:172) at hudson.Proc$LocalProc.destroy(Proc.java:385) at hudson.Proc$LocalProc.join(Proc.java:358) at hudson.Launcher$RemoteLaunchCallable$1.join(Launcher.java:1324) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:929) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:903) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:855) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Add Comment
[JIRA] (JENKINS-57996) Parameter JIRA_ISSUES cannot get all jira-ids if commit message cannot show in changes' summary.
Title: Message Title jack lee updated an issue Jenkins / JENKINS-57996 Parameter JIRA_ISSUES cannot get all jira-ids if commit message cannot show in changes' summary. Change By: jack lee Parameter 粗文本Parameter JIRA_ISSUES cannot get all jira-ids if commit message has multiple lines. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200011.1560395584000.18597.1563874800135%40Atlassian.JIRA.
[JIRA] (JENKINS-58602) Some secret values are getting displayed in the kubernetes pod spec
Title: Message Title Vincent Latombe updated JENKINS-58602 Jenkins / JENKINS-58602 Some secret values are getting displayed in the kubernetes pod spec Change By: Vincent Latombe 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200762.1563807538000.18595.1563872220238%40Atlassian.JIRA.
[JIRA] (JENKINS-58612) some plugins does not install
Title: Message Title waqas kamran created an issue Jenkins / JENKINS-58612 some plugins does not install Issue Type: Task Assignee: Mark Waite Attachments: image-2019-07-23-12-31-32-386.png Components: git-plugin Created: 2019-07-23 08:32 Environment: Jenkins Ver : 2.176.2 Priority: Critical Reporter: waqas kamran I am ruuning jenkins using war . but i am not able to install Git plugin . I am getting following error . GitHub plugin version 1.29.4Jenkins Git plugin version 3.10.1 failed to load. Fix this plugin first. Add Comment
[JIRA] (JENKINS-49330) JIRA Update relevant issues failing
Title: Message Title jack lee assigned an issue to jack lee Jenkins / JENKINS-49330 JIRA Update relevant issues failing Change By: jack lee Assignee: jack lee 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188193.1517530992000.18576.1563870660622%40Atlassian.JIRA.
[JIRA] (JENKINS-49330) JIRA Update relevant issues failing
Title: Message Title jack lee assigned an issue to ben patterson Jenkins / JENKINS-49330 JIRA Update relevant issues failing Change By: jack lee Assignee: jack lee ben patterson 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188193.1517530992000.18579.1563870660825%40Atlassian.JIRA.
[JIRA] (JENKINS-57899) Jira site configuration lost after a reboot
Title: Message Title Christoph Fetzer updated an issue Jenkins / JENKINS-57899 Jira site configuration lost after a reboot Change By: Christoph Fetzer Environment: jira-plugin 3.0.7 jira-plugin 3.0.8 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199864.1559853126000.18547.1563869220615%40Atlassian.JIRA.
[JIRA] (JENKINS-58611) Implement method comparison for var-args
Title: Message Title Akram Ben Aissi updated an issue Jenkins / JENKINS-58611 Implement method comparison for var-args Change By: Akram Ben Aissi Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200772.1563868512000.18543.1563868620288%40Atlassian.JIRA.
[JIRA] (JENKINS-58611) Implement method comparison for var-args
Title: Message Title Akram Ben Aissi created an issue Jenkins / JENKINS-58611 Implement method comparison for var-args Issue Type: Improvement Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-07-23 07:55 Priority: Minor Reporter: Akram Ben Aissi Hi, our custom DSL for Groovy contains 2 methods named the same way, but with a different number of arguments: myMethod(boolean watch, String...args) myMethod(String...args) While trying to call the method from a pipeline, I got the following exception: ``` java.lang.IllegalStateException: cannot compare public com.openshift.jenkins.plugins.OpenShiftDSL$Result com.openshift.jenkins.plugins.OpenShiftDSL.exec(java.lang.Object[]) to public com.openshift.jenkins.plugins.OpenShiftDSL$Result com.openshift.jenkins.plugins.OpenShiftDSL.exec(boolean,java.lang.Object[]) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyCallSiteSelector.isMoreSpecific(GroovyCallSiteSelector.java:291) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyCallSiteSelector.findMatchingMethod(GroovyCallSiteSelector.java:203) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovyCallSiteSelector.method(GroovyCallSiteSelector.java:150) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:90) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:156) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:160) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17) at WorkflowScript.run(WorkflowScript:13) at com.openshift.jenkins.plugins.OpenShiftDSL.withProject(jar:file:/var/lib/jenkins/plugins/openshift-client/WEB-INF/lib/openshift-client.jar!/com/openshift/jenkins/plugins/OpenShiftDSL.groovy:395) ``` It seems that this is due to an incomplete implementation of the method comparison in GroovyCallSiteSelector class. A TODO is still present in the code at the following line: https://github.com/jenkinsci
