[JIRA] (JENKINS-59325) docker plugin unable to launch container as non-root user
Title: Message Title Sangeetha Venugopal created an issue Jenkins / JENKINS-59325 docker plugin unable to launch container as non-root user Issue Type: Bug Assignee: Carlos Sanchez Components: docker, docker-plugin Created: 2019-09-12 06:01 Priority: Blocker Reporter: Sangeetha Venugopal Hi Team, I am trying to launch a docker container as non root user via jenkins. But container fails to launch because of issue with docker ssh agent. I am facing no issue when am launching it as root user. Kindly help me understand what I am missing here. SYSTEM ERROR LOGS: = Trying to run container for node docker_container-000x8z6l9dv6i from image: trs-docker-local.bhisoj70.apac.nsn-net.net/scm/trs_enb_docker_image_git:v1 Started container ID 42227c468db31642154dd5dea8024495941a1a0634c974a4079f543ca1bc419b for node docker_container-000x8z6l9dv6i from image: trs-docker-local.bhisoj70.apac.nsn-net.net/scm/trs_enb_docker_image_git:v1 Failed to launch docker SSH agent :1 = Add Comment
[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch scirpt
Title: Message Title
Mateusz Wiacek created an issue
Jenkins / JENKINS-59327
No credentials specified Multibranch Pipeline - Branch scirpt
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-09-12 07:06
Priority:
Major
Reporter:
Mateusz Wiacek
Hi Team, When I am creating Multibranch Pipeline job which executes another pipeline job as a branch apparently it's not reading git credentials in branch. So in a branch which is a pipeline script, I have stage stage('git checkout') { stage('git checkout') { steps { git credentialsId: 'My credentials', poll: false, url: 'mygit.git' }} But it's falling on Windows machine with the following error. When I create just a simple pipeline job with the same stage it's working as should. From test which I did when I specified credentials in a multibranch job which is managing my script in the branch then it's working. So apparently git credentials from the stage are ignored.Steps to Reproduce: 1. Create Multibranch Job without specified git credentials with script-path where is a script. 2. In a script create step with git checkout and specified credentials 3. Run the branch script and it should fail. 4. Add in Multibranch configuration credentials and run branch script it should work. No credentials specified No credentials specifiedWiping out workspace first.Cloning the remote Git repositoryCloning with configured refspecs honoured and without tagsERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --no-tags --force --progress MyRepo.git +refs/heads/:refs/remotes/origin/" returned status code 128:stdout: stderr: mygitserver: Permission denied (publickey).fatal: Could not read from remote repository. Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Jon Sten commented on JENKINS-59259 Re: sshAgent step does not survive agent disconnect/reconnect I did some digging in the code, and to me it looks like the problem is that ExecRemoteAgent and SSHAgentStepExecution caches the launcher object. The code seems to be rather old and would probably become less buggy if StepContext was used instead, cause as far as I know that object is supposed to handle loss of underlying connections/streams. I'll see if I can gather the nervs to fix the code. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.1768.1568269861735%40Atlassian.JIRA.
[JIRA] (JENKINS-59277) Provisioning issue after upgrade to version 1.2.0
Title: Message Title Jie Shen commented on JENKINS-59277 Re: Provisioning issue after upgrade to version 1.2.0 Claas Diederichs Thanks for your information here. I have made a fix for this. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201777.1568011065000.1841.1568271180136%40Atlassian.JIRA.
[JIRA] (JENKINS-58938) Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" a
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-58938 Exception "org.kohsuke.stapler.ScriptLoadException: org.apache.commons.jelly.JellyException: Failed to load message from org.kohsuke.stapler.jelly.groovy.GroovyFacet@1374c13d" after upgrade to 2.189 Change By: Oliver Gondža Labels: lts 2.190.1 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201282.1565799462000.1874.1568272620448%40Atlassian.JIRA.
[JIRA] (JENKINS-59277) Provisioning issue after upgrade to version 1.2.0
Title: Message Title Jie Shen resolved as Fixed Jenkins / JENKINS-59277 Provisioning issue after upgrade to version 1.2.0 Change By: Jie Shen Status: Open Resolved Resolution: Fixed Released As: 1.2.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201777.1568011065000.1886.1568273641340%40Atlassian.JIRA.
[JIRA] (JENKINS-59259) sshAgent step does not survive agent disconnect/reconnect
Title: Message Title Jon Sten edited a comment on JENKINS-59259 Re: sshAgent step does not survive agent disconnect/reconnect I did some digging in the code, and to me it looks like the problem is that ExecRemoteAgent and SSHAgentStepExecution caches the launcher object. The code seems to be rather old and would probably become less buggy if StepContext was used instead, cause as far as I know that object is supposed to handle loss of underlying connections/streams. I'll see if I can gather the nervs to fix the code. [~stephenc] [~stephenconnolly] am I on the right track? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201727.1567754679000.1836.1568269980162%40Atlassian.JIRA.
[JIRA] (JENKINS-32118) Document Jenkins security settings so Robot Framework log/report can be opened
Title: Message Title
Dinesh J commented on JENKINS-32118
Re: Document Jenkins security settings so Robot Framework log/report can be opened
does anybody have permanent solution for this? I can able to resolve this as temporary by adding following in the script console in manage Jenkins System.setProperty("hudson.model.DirectoryBrowserSupport.CSP","sandbox allow-scripts; default-src 'none'; img-src 'self' data: ; style-src 'self' 'unsafe-inline' data: ; script-src 'self' 'unsafe-inline' 'unsafe-eval' ;") but every time Jenkins server restart changes disappeared. any permanent solution for this?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167087.1450344294000.1771.1568269861874%40Atlassian.JIRA.
[JIRA] (JENKINS-56090) BlueMessageEnricher: Unable to enrich message (Please log in to access {branch})
Title: Message Title
Inga Muste commented on JENKINS-56090
Re: BlueMessageEnricher: Unable to enrich message (Please log in to access {branch})
Same here.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197521.1549911611000.1839.1568270040500%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title Fredrik Bruzelius commented on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined I think this is not limited to just the "Environment variables" node property. I am using the Workspace Cleanup Plugin and would like to set the "Disable deferred wipeout on this node" property, which is also missing. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.1851.1568272200198%40Atlassian.JIRA.
[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script
Title: Message Title Matt White updated an issue Jenkins / JENKINS-59327 No credentials specified Multibranch Pipeline - Branch script Change By: Matt White Summary: No credentials specified Multibranch Pipeline - Branch scirpt script Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201878.1568271976000.1848.1568272140246%40Atlassian.JIRA.
[JIRA] (JENKINS-59326) Jenkins integration with Checkmarx
Title: Message Title
test checkmarx created an issue
Jenkins / JENKINS-59326
Jenkins integration with Checkmarx
Issue Type:
Task
Assignee:
Sergey Kadaner
Attachments:
Checkmarx.PNG
Components:
checkmarx-plugin
Created:
2019-09-12 06:17
Priority:
Minor
Reporter:
test checkmarx
I have an issue when integration Jenkins with Checkmarx. Checkmarx version: 8.90.4 Jenkins version: 2.176.3 Have provided checkmarx URL and credentials, but when try to connect using test connection it throws me error: Failed to parse json response: Unexpected character ('<' (code 60)): expected a valid value (number, String, array, object, 'true', 'false' or 'null') at [Source: (String)" Checkmarx URL is rechable from my local browser. Please provide a solution
Add Comment
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Michael Düsterhus commented on JENKINS-58383 Re: Disable aggregated analysis results This should be a server side option in the Jenkinsfile. I could imagine an extra parameter or a predefined ID that can be overridden. BTW what is the meaning of the recordIssues aggregatingResults parameter? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.1843.1568271300144%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59167 rssAll feed no longer contains Jenkins server URL, only incorrect relative path Change By: Oliver Gondža Labels: lts 2.190.1 - candidate fixed regression security-534 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201604.1567266415000.1859.1568272440253%40Atlassian.JIRA.
[JIRA] (JENKINS-59326) Jenkins integration with Checkmarx
Title: Message Title test checkmarx updated an issue Jenkins / JENKINS-59326 Jenkins integration with Checkmarx Change By: test checkmarx Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201877.1568269038000.1854.1568272381647%40Atlassian.JIRA.
[JIRA] (JENKINS-59266) Placeholder: Security fix backports to 2.190.x
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59266 Placeholder: Security fix backports to 2.190.x Change By: Oliver Gondža Labels: lts 2.190.1 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201764.1567809454000.1856.1568272381870%40Atlassian.JIRA.
[JIRA] (JENKINS-59299) Folder Computation Failure
Title: Message Title Parichay Barpanda commented on JENKINS-59299 Re: Folder Computation Failure Hi Keith Davis, I think this is either caused by internet connection issue or gitlab server is unreachable. From the logs I can see that the group cannot be fetched by the gitlab4j api. This error has shown up sometimes in the past, can you retry this? For example, select configure on the folder and wait until the form validation shows that it is valid group then select save. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201845.1568121425000.1884.1568273460211%40Atlassian.JIRA.
[JIRA] (JENKINS-58912) error when logging in after upgrade to 2.189
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-58912 error when logging in after upgrade to 2.189 Change By: Oliver Gondža Labels: lts 2.190.1 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201253.156571588.1863.1568272500383%40Atlassian.JIRA.
[JIRA] (JENKINS-46375) vSphere template definition doesn't allow environment variables to be defined
Title: Message Title pjdarton commented on JENKINS-46375 Re: vSphere template definition doesn't allow environment variables to be defined You'll be pleased to know that You are correct - this does affect the ws cleanup plugin node property, along with pretty much any other node property. I've fixed this issue in the as-yet-unreleased code, which I'm intending to release "soon" ... which will be "sooner" if you help ... ... you can get a pre-release build from here. Please try it out and let me know if it works for you - that'll help me and help speed up the official release. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184639.1503478575000.1927.1568280001648%40Atlassian.JIRA.
[JIRA] (JENKINS-59220) Implement a method in EnvVars that extends putAll() to filter null values
Title: Message Title Oleg Nenashev started work on JENKINS-59220 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201671.1567592904000.1919.156828927%40Atlassian.JIRA.
[JIRA] (JENKINS-59321) The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7
Title: Message Title
Steve Boardwell updated an issue
Jenkins / JENKINS-59321
The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7
Change By:
Steve Boardwell
The git-branch-source plugin seems to have broken with the latest update (from 2.5.3 -> 2.5.7)Steps to reproduce:* create a Multibranch Pipeline job* select GitHub as the Branch Source The update also brought about another change in the jenkins-jobs-dsl script definition, requiring the following additions to the {{github}} dsl block{noformat}repositoryUrl('')configuredByUrl(false){noformat} This is the exception I am seeing in the log.{noformat}Sep 11, 2019 9:25:49 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving https://jenkins.company.com/job/seed-job/descriptorByName/org.jenkinsci.plugins.github_branch_source.GitHubSCMSource/checkCredentialsIdjava.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at
[JIRA] (JENKINS-59328) job hangs although failed after ConcurrentModificationException of ExwsAllocateActionImpl
Title: Message Title
Roman Zwi created an issue
Jenkins / JENKINS-59328
job hangs although failed after ConcurrentModificationException of ExwsAllocateActionImpl
Issue Type:
Bug
Assignee:
Alexandru Somai
Components:
external-workspace-manager-plugin, pipeline
Created:
2019-09-12 08:11
Environment:
Jenkins 2.193 external-workspace-manager-plugin 1.20 pipeline 2.6
Priority:
Minor
Reporter:
Roman Zwi
I have a pipeline Job that does some simple checks for all nodes every 5 minutes. Sometimes (something like twice a day) this job fails with ConcurrentModificationException in ExwsAllocateActionImpl (on a Windows node while accessing a file on the network). This has been happening ever since but I didn't bother because the next build ran fine again. But since some updates (in July or August) the build hangs in a strange state after this exception. Somehow the build is still running although it is failed already. Therefore the next build doesn't run because it waits for the previous build to finish (I configured to not allow concurrent builds). I can't abort the failed build because it is already failed. So I have to delete the failed build in order to get the next build running. It doesn't happen anymore since I switched "Pipeline speed/durability override" from performance optimized to maximum durability Log: Started by timer Running in Durability level: PERFORMANCE_OPTIMIZED [Pipeline] Start of Pipeline [Pipeline] stage [Pipeline] { (master) [Pipeline] sleep Sleeping for 1 sec [Pipeline] node Running on Jenkins in /rsync/JenkinsJobs/workspace/work_ServerCheck [Pipeline] { [Pipeline] sleep Sleeping for 1 sec [Pipeline] isUnix [Pipeline] sh + df /rsync [Pipeline] sh + uptime [Pipeline] isUnix [Pipeline] isUnix [Pipeline] echo master: 37.9952316284 [Pipeline] echo we
[JIRA] (JENKINS-59329) select with doFillXXX: validation called with empty value upon page load
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-59329 select with doFillXXX: validation called with empty value upon page load Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-12 09:02 Priority: Minor Reporter: Vincent Latombe Actual behaviour When using a form select with an associated doFillXXXItems method and a doCheckXXX method, upon page load, the doCheckXXX method is called with an empty value which leads to inconsistent form validation. And when the actual select value is loaded, the check method is not called to update validation result. Expected behaviour When using a form select with an associated doFillXXXItems method and a doCheckXXX method, upon page load, the doCheckXXX method is called with the value that is currently selected in the dropdown. Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title cedric lecoz updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: cedric lecoz Attachment: jenkins_201909121030.log Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1952.1568287740452%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title cedric lecoz commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Hi Raihaan Shouhell, That's what it says, but the EC2 instance was alive, I could ssh and work away, it's just that Jenkins was not aware of it. my instances are on demand. Attached jenkins_201909121030.log a log with a bit more data 2 differences EC2 had the issue (or similar) the first one (aws-audit-ec2) had an EC2 running and terminated an hour before (so it was still showing as terminated in my EC2 console). the second one the EC2 already existed, and was just stopped. I tried to clean the log at best, but I have too many jobs running on other ec2, it's noisy. BR, Cedric. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1957.1568287740593%40Atlassian.JIRA.
[JIRA] (JENKINS-51412) waitforqualitygate directive does not work for multiple sonar analysis in pipeline
Title: Message Title Eugene Eugene commented on JENKINS-51412 Re: waitforqualitygate directive does not work for multiple sonar analysis in pipeline When will this bug be fixed? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190765.1526625247000.1905.1568276460205%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Anda Sorina Laakso commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Jim, Can you tell me where I could upload the fix for this issue? Maybe an ftp server. Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.1937.1568281860470%40Atlassian.JIRA.
[JIRA] (JENKINS-59302) Name fields of AWS Secrets Manager Secrets are not distinct
Title: Message Title Chris Kilding commented on JENKINS-59302 Re: Name fields of AWS Secrets Manager Secrets are not distinct I investigated a bit and found the following... As long as the `AwsCredentials` type implements `StringCredentials`, the ID is used for the name. But if it extends any of the other credentials types (`StandardUsernamePasswordCredentials` etc), even individually, the fallback text appears instead. I initially wondered if this could have been a bug in the credentials type definitions themselves so tried spawning some creds in the local disk-backed creds provider. But the names all worked properly, so the credentials type definitions are fine. One interesting thing is that when AWS credentials are shown in the list view, no matter what credentials interface I tell the `AwsCredentials` class to implement instead of `StringCredentials`, it is always presented as 'secret text' (with the blue key icon). So it seems that the `AwsCredentials` objects are always being treated as `StringCredentials`, even when they do not implement that type. And when they don't fit the `StringCredentials` form I guess the default descriptor message is used to fill in the blanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201850.1568146774000.1939.1568282880171%40Atlassian.JIRA.
[JIRA] (JENKINS-59330) slave workspace deleted
Title: Message Title Naresh B updated an issue Jenkins / JENKINS-59330 slave workspace deleted Change By: Naresh B Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201881.1568283425000.1943.1568283480468%40Atlassian.JIRA.
[JIRA] (JENKINS-59330) slave workspace deleted
Title: Message Title Naresh B created an issue Jenkins / JENKINS-59330 slave workspace deleted Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: github-organization-folder-plugin Created: 2019-09-12 10:17 Environment: test Priority: Minor Reporter: Naresh B Hi, I have a github organization item created on Jenkins. it has scanned the mentioned repository and created jobs for 5 active branches and initial builds were also happened on the slave but got failed due to some errors. Please note that workspace was created on slave for all these jobs. After one month i have checked and observed that worksapces of those five jobs got deleted. But jobs are still exist on jenkins webportal. Can you tell me what could be the reason? i suspect issue could be due to one of the following. child orphaned strategy (inherited -> "discard old items checkbox" is enabled but no value is mentioned for "Days to keep builds" & "Max No. of Builds to keep" the options) health metrics (Child item with worst health ->recursive checkbox is enabled) Child health metrics (Child item with worst health ->recursive checkbox is enabled) slave configuration has something called "disable deferred wipeout on this node". This was not enabled. Kindly help me know what could be the issue. Jenkins version : 2.164.1 slave : Windows server 2008
[JIRA] (JENKINS-31474) After unsuccessful terminate, ec2-plugin reaches a state where no new slaves are being initialized
Title: Message Title Willie Loyd Tandingan commented on JENKINS-31474 Re: After unsuccessful terminate, ec2-plugin reaches a state where no new slaves are being initialized I have experienced this but the timing is sporadic, and is pretty hard to replicate. Stop on terminate is turned on. When this issue occurs, the node is marked as offline in Jenkins, but the EC2 instance is still running. Since the EC2 filter only searches for stopped instances, this node will never be used. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166351.1447154637000.1946.1568286000290%40Atlassian.JIRA.
[JIRA] (JENKINS-59220) Implement a method in EnvVars that extends putAll() to filter null values
Title: Message Title Oleg Nenashev updated JENKINS-59220 Jenkins / JENKINS-59220 Implement a method in EnvVars that extends putAll() to filter null values Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201671.1567592904000.1922.1568280001013%40Atlassian.JIRA.
[JIRA] (JENKINS-59220) Implement a method in EnvVars that extends putAll() to filter null values
Title: Message Title Oleg Nenashev commented on JENKINS-59220 Re: Implement a method in EnvVars that extends putAll() to filter null values https://github.com/jenkinsci/jenkins/pull/4194 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201671.1567592904000.1925.1568280001488%40Atlassian.JIRA.
[JIRA] (JENKINS-59330) slave workspace deleted
Title: Message Title Naresh B commented on JENKINS-59330 Re: slave workspace deleted Team, Kindly prioritize this as it is a blocker for us. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201881.1568283425000.1949.1568286180150%40Atlassian.JIRA.
[JIRA] (JENKINS-59215) gerrit trigger stuck and can not trigger jobs
Title: Message Title Thorsten Möllers edited a comment on JENKINS-59215 Re: gerrit trigger stuck and can not trigger jobs I found the same problem and found a way to reproduce. For me it appears when I have a * disabled job at jenkins start time * configured with dynamic triggerIf the job is enabled and jenkins start time, I don't see the problem, even if I disable it later. If the job is disabled at start time, the problem occurs and still stays even if I enable the job later. If I remove the dynamic trigger configuration, the problem disappears. I can reproduce the problem with 2.29.0 and 2.30.0, didn't see it with 2.27.X Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201665.1567564714000.1896.1568275500327%40Atlassian.JIRA.
[JIRA] (JENKINS-59215) gerrit trigger stuck and can not trigger jobs
Title: Message Title Thorsten Möllers commented on JENKINS-59215 Re: gerrit trigger stuck and can not trigger jobs I found the same problem and found a way to reproduce. For me it appears when I have a disabled job at jenkins start time configured with dynamic trigger If the job is enabled and jenkins start time, I don't see the problem, even if I disable it later. If the job is disabled at start time, the problem occurs and still stays even if I enable the job later. If I remove the dynamic trigger configuration, the problem disappears. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201665.1567564714000.1889.1568275440519%40Atlassian.JIRA.
[JIRA] (JENKINS-59323) "java.io.IOException: Read-only file system" when saving Job Configuration
Title: Message Title Alex Earl commented on JENKINS-59323 Re: "java.io.IOException: Read-only file system" when saving Job Configuration Sounds like your JENKINS_HOME has the wrong permissions or ownership. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201874.1568248742000.1971.1568290680252%40Atlassian.JIRA.
[JIRA] (JENKINS-59279) Required context class hudson.FilePath is missing
Title: Message Title Alex Earl commented on JENKINS-59279 Re: Required context class hudson.FilePath is missing Are you calling deleteDir inside of a node block? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201810.1568028241000.1973.1568290800119%40Atlassian.JIRA.
[JIRA] (JENKINS-58601) Allow deletion of one or more entries from job's config history
Title: Message Title Robin Schulz updated JENKINS-58601 Done and released with version 1.5 on 09.09.2019. Jenkins / JENKINS-58601 Allow deletion of one or more entries from job's config history Change By: Robin Schulz Status: Open Fixed but Unreleased Resolution: Done Released As: https://github.com/jenkinsci/pipeline-config-history-plugin/blob/master/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58601) Allow deletion of one or more entries from job's config history
Title: Message Title Robin Schulz updated JENKINS-58601 Jenkins / JENKINS-58601 Allow deletion of one or more entries from job's config history Change By: Robin Schulz Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200761.1563800501000.2009.1568293920750%40Atlassian.JIRA.
[JIRA] (JENKINS-59292) org.apache.commons.jelly.JellyTagException looking at Parasoft results
Title: Message Title Alexander Mai commented on JENKINS-59292 Re: org.apache.commons.jelly.JellyTagException looking at Parasoft results That did not help I've wiped all warnings-ng files/dir, restart, re-install. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201836.1568099107000.2047.1568298420210%40Atlassian.JIRA.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Jesse Glick commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline If you have to use currentBuild.rawBuild, or import generally, then this is clearly not fixed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193173.1534855202000.2056.1568299383471%40Atlassian.JIRA.
[JIRA] (JENKINS-6856) Git builds with detached head no matter what
Title: Message Title
Mark Waite edited a comment on JENKINS-6856
Re: Git builds with detached head no matter what
Yes, the ` {{ git checkout ` }} command you used is a very good choice, especially if you're not using authenticated submodules or authenticated access to large file storage (git LFS).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136951.1277468864000.2192.1568301180499%40Atlassian.JIRA.
[JIRA] (JENKINS-59330) slave workspace deleted
Title: Message Title Alex Earl commented on JENKINS-59330 Re: slave workspace deleted Questions are generally best suited for the mailing lists. https://jenkins.io/mailing-lists/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201881.1568283425000.1969.1568290560220%40Atlassian.JIRA.
[JIRA] (JENKINS-59292) org.apache.commons.jelly.JellyTagException looking at Parasoft results
Title: Message Title Ulli Hafner commented on JENKINS-59292 Re: org.apache.commons.jelly.JellyTagException looking at Parasoft results Hmm, strange... A java.lang.AbstractMethodError indicates a library/installation problem. The abstract method is provided by a class in the warnings-ng project. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201836.1568099107000.2125.1568299980269%40Atlassian.JIRA.
[JIRA] (JENKINS-59333) customWorkspace relative definition isn't straight
Title: Message Title
NhatKhai Nguyen created an issue
Jenkins / JENKINS-59333
customWorkspace relative definition isn't straight
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-09-12 14:52
Priority:
Minor
Reporter:
NhatKhai Nguyen
When I try to use relative path to specify for customWorkspace as described in this documatation. I found that it is not clear what is it mean in the documentation mean by "workspace root on the node". For example:
pipeline { agent { node {
label 'my_pc'
customWorkspace 'hello' } }
...
}
#1 With above code, I got WORKSPACE=C:\BLD\hello #2 When I specify customWorkspace "", I got WORKSPACE=C:\BLD\workspace\my_jenkins_job_path\my_job_name M1 If the "workspace root on the node" was C:\BLD, #1 would understandable and #2 would not make sense . M2 If the "workspace root on the node" was C:\BLD\workspace\my_jenkins_job_path\my_job_name, #1 would not make sense , #2 would understandable . My personal refer M2, but both is really, really confusing to me to understand.
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title Nicholas Brown updated an issue Jenkins / JENKINS-46722 alwaysLinkToLastBuild not linking to last job result Change By: Nicholas Brown Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185068.1504796587000.2150.1568300406082%40Atlassian.JIRA.
[JIRA] (JENKINS-46722) alwaysLinkToLastBuild not linking to last job result
Title: Message Title
Nicholas Brown commented on JENKINS-46722
Re: alwaysLinkToLastBuild not linking to last job result
I'm seeing this issue. The workaround to access the report suggested by Martin Røssland does not work for me. In the build log I see:
[Pipeline] publishHTML
[htmlpublisher] Archiving HTML reports...
[htmlpublisher] Archiving at PROJECT level /var/lib/jenkins/workspace/project_code_master/clangScanBuildReports to /var/lib/jenkins/jobs/project/jobs/code/branches/master/htmlreports/clang_20scan-build_20Static_20Analysis_20Report
and as mentioned in the this Jira ticket there is no link in the sidebar of the build. Trying to directly access the report results in:
HTTP ERROR 404
Problem accessing /jobs/project/jobs/code/branches/master/htmlreports/clang_20scan-build_20Static_20Analysis_20Report/index.html. Reason:
Not Found
The publishHTML step is being used in a post failure section of stage in a pipeline:
post {
failure {
publishHTML target: [
allowMissing: false,
alwaysLinkToLastBuild: false,
keepAll: false,
reportDir: 'clangScanBuildReports',
reportFiles: 'index.html',
reportTitles: 'clang scan-build Static Analysis',
reportName: 'clang scan-build Static Analysis Report'
]
}
Add Comment
[JIRA] (JENKINS-59299) Folder Computation Failure
Title: Message Title Markus Lackner commented on JENKINS-59299 Re: Folder Computation Failure the error occured with empty "Owner" field in the Gitlab Group Section. My intention was to scan all projects/groups. Is this not supported? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201845.1568121425000.1997.1568291820172%40Atlassian.JIRA.
[JIRA] (JENKINS-59332) customWorkspace did not stay with specified path
Title: Message Title
NhatKhai Nguyen created an issue
Jenkins / JENKINS-59332
customWorkspace did not stay with specified path
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-09-12 14:35
Priority:
Minor
Reporter:
NhatKhai Nguyen
Pipeline code:
pipeline {
agent { node {
label 'my_computer'
customWorkspace 'C:\my_folder'
} }
}
If I ran this pipeline concurrently on the same agent machine (same time): Build#1 get C:\my_folder Build#2 get C:\my_folder@2 Base on the documentation of customWorkspace, I would understand that both build#1 and build#2 would use C:\my_folder instead.
Add Comment
[JIRA] (JENKINS-59274) Support pipeline search in the folder
Title: Message Title Aytunc BEKEN resolved as Fixed Fixed with release 1.3 Jenkins / JENKINS-59274 Support pipeline search in the folder Change By: Aytunc BEKEN Status: In Progress Resolved Resolution: Fixed Released As: multibranch-action-triggers-1.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-6856) Git builds with detached head no matter what
Title: Message Title
Raúl Salinas-Monteagudo commented on JENKINS-6856
Re: Git builds with detached head no matter what
Isn't it enough to do the following to get a proper branch head at some point after the checkout? It seems to work for me. git checkout -b ${GIT_BRANCH} origin/${GIT_BRANCH}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136951.1277468864000.2132.1568300405110%40Atlassian.JIRA.
[JIRA] (JENKINS-58903) Google Login Plugin - add "clientSecret" in script
Title: Message Title Ravish Kumar updated an issue Jenkins / JENKINS-58903 Google Login Plugin - add "clientSecret" in script Change By: Ravish Kumar I am using "helm" to install Jenkins over K8's. Plugins are added in values.yaml file and being referenced at installation. e.g. helm install -n jenkins stable/jenkins -f values.yaml --wait I have to add google-login-plugin "clientId" and "clientSecret" values in the yaml file.Reference - [https://github.com/helm/charts/tree/master/stable/jenkins#adding-customized-securityrealm]Reference - [https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml#L39] [|https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml#L33] Modifying "clientId" is simple, question is how to provide "clientSecret" in values.yaml ?? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-58903) Google Login Plugin - add "clientSecret" in script
Title: Message Title Ravish Kumar updated an issue Jenkins / JENKINS-58903 Google Login Plugin - add "clientSecret" in script Change By: Ravish Kumar I am using "helm" to install Jenkins over K8's. Plugins are added in values.yaml file and being referenced at installation. e.g. helm install -n jenkins stable/jenkins -f values.yaml --wait I have to add google-login-plugin "clientId" and "clientSecret" values in the yaml file.Reference - [https://github.com/helm/charts/tree/master/stable/jenkins#adding-customized-securityrealm]Reference - [https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml# L39] [|https://github.com/helm/charts/blob/master/stable/jenkins/values.yaml# L33]Modifying "clientId" is simple, question is how to provide "clientSecret" in values.yaml ?? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-59274) Support pipeline search in the folder
Title: Message Title Aytunc BEKEN started work on JENKINS-59274 Change By: Aytunc BEKEN Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201774.1567999525000.2044.1568297940456%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point:My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point.Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test. At least my way quicker freestyle build do not make use of the inner | tee | grep! On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.2041.1568297940323%40Atlassian.JIRA.
[JIRA] (JENKINS-58035) lightweight Checkouts return error code when trying to checkout jenkins file returns 404
Title: Message Title Arnaud Richard commented on JENKINS-58035 Re: lightweight Checkouts return error code when trying to checkout jenkins file returns 404 I'm running the same issue with Subversion Plug-in 2.12.2 I don't have any externals. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200054.1560729162000.2171.1568301060115%40Atlassian.JIRA.
[JIRA] (JENKINS-6856) Git builds with detached head no matter what
Title: Message Title Mark Waite commented on JENKINS-6856 Re: Git builds with detached head no matter what Yes, the `git checkout` command you used is a very good choice, especially if you're not using authenticated submodules or authenticated access to large file storage (git LFS). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136951.1277468864000.2174.1568301120798%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point: My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point. Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test. On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.2040.1568297820067%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance of pipeline build compared to freestyle
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance of pipeline build compared to freestyle I maybe got the point:My build deep inside makes use of a compiler | tee | grep,... and therefore is splitting the output into a file at one point.Not too far ago I switched from a formerly deprected warnings parser to the warnings next generation plugin and therefore had to insert another | tee - split. I'm not yet 100% sure if this exactly matches the point were buildtimes increased but at least it might be close to. I'll set up a test.At least my way quicker freestyle build do does not make use of the inner | tee | grep!On the other hand this | tee provides a list of other problems and I'd like to avoid it at any level - also for warnings next generation. Is there another way to split build output to a file and in the same step keep the return code? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201861.156818559.2045.1568298060421%40Atlassian.JIRA.
[JIRA] (JENKINS-59331) Empty 'Alias Variable' when using certificate binding
Title: Message Title Kevin Raymond created an issue Jenkins / JENKINS-59331 Empty 'Alias Variable' when using certificate binding Issue Type: Task Assignee: Unassigned Components: credentials-binding-plugin Created: 2019-09-12 12:38 Priority: Minor Reporter: Kevin Raymond plugin version 1.18 I am trying to use this certificate binding but in a simple job : keystore variable: CERTSTORE Alias Variable: MYKEY step as a standard shell script: keytool -list -v -keystore $CERTSTORE echo $MYKEY keytool -export -alias "$MYKEY" -keystore "$CERTSTORE" -rfc -file fit-kernel.cert output us + keytool -list -v -keystore Enter keystore password: * WARNING WARNING WARNING * * The integrity of the information stored in your keystore * * has NOT been verified! In order to verify its integrity, * * you must provide your keystore password. * * WARNING WARNING WARNING * Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry Alias name: 1 Creation date: Sep 12, 2019 Entry type: PrivateKeyEntry *** *** + echo + LANG=C + keytool -export -alias '' -keystore -rfc -file fit-kernel.cert Enter keystore password: * WARNING WARNING WARNING * * The integrity of the information stored in your keystore * * has NOT been verified! In order to verify its integrity, * * you must provide
[JIRA] (JENKINS-59299) Folder Computation Failure
Title: Message Title Parichay Barpanda commented on JENKINS-59299 Re: Folder Computation Failure No we do not support this. This was supported initially but there was a discrepancy, as during merge request event there is no way to determine the owner of the project without making an api call and without knowing the owner it is not possible to match the project. But api call is not recommended to be used inside scmevent class so removed this feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201845.1568121425000.2004.1568292540211%40Atlassian.JIRA.
[JIRA] (JENKINS-58903) Google Login Plugin - add "clientSecret" in script
Title: Message Title Ravish Kumar commented on JENKINS-58903 Re: Google Login Plugin - add "clientSecret" in script Ryan Campbell Additional Information - Jenkins UI encrypts the "clientSecret" using "[hudson.utils.Secret|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/Secret.java]" class and encrypted value is stored in config.xml under Jenkins home folder. Tried to perform encryption without [Jenkins Script Console|https://wiki.jenkins.io/display/JENKINS/Jenkins+Script+Console] but it's not a viable solution. How "clientSecret" be provided in values.yaml ?? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201242.1565676819000.2011.1568295540228%40Atlassian.JIRA.
[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage
Title: Message Title Pablo Gomez commented on JENKINS-47591 Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage Hi, we are facing the same issue. We have performance problems accessing from slaves to our persistent storage when we have multiple slaves running in the same node. Is there any solution or alternative? Is there any way to configure a separate claim for each pod? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186064.1508775809000.2050.1568298480284%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears edited a comment on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. [~aslaakso] I can share a drop box location but I need your email address to do so.Do you have an alternate location in mind?Jim Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.2223.1568306100318%40Atlassian.JIRA.
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. I can share a drop box location but I need your email address to do so. Do you have an alternate location in mind? Jim Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.2216.1568306040460%40Atlassian.JIRA.
[JIRA] (JENKINS-59334) Respect Log API parameters in Step Log API
Title: Message Title Robin Smith created an issue Jenkins / JENKINS-59334 Respect Log API parameters in Step Log API Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-09-12 15:37 Environment: Jenkins 2.176.1 blueocean:1.19.0 Priority: Minor Reporter: Robin Smith According to the Log API documentation, a thresholdInKB parameter can be used to restrict or increase the amount of log data returned. This parameter seems to be ignored by the Step Log API. e.g. /blue/rest/organizations/jenkins/pipelines/dummy-job/runs/1/nodes/5008/log?thresholdInKB=50 -> thresholdInKB ignored Add Comment
[JIRA] (JENKINS-59335) jenkins rpm install failure
Title: Message Title Michael Watters created an issue Jenkins / JENKINS-59335 jenkins rpm install failure Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-09-12 16:30 Environment: CentOS 7.6 with official jenkins.repo file Priority: Major Reporter: Michael Watters The jenkins rpm fails to install on a new server due to failures in the PREIN scriptlet. For example, here is the yum output when running "yum install jenkins" on a new server. jenkins-2.176.3-1.1.noarch.rpm | 74 MB 00:00:18 Running transaction check Running transaction test Transaction test succeeded Running transaction stat: cannot stat ‘/var/cache/jenkins’: No such file or directory stat: cannot stat ‘/var/log/jenkins’: No such file or directory stat: cannot stat ‘/var/lib/jenkins’: No such file or directory error: %pre(jenkins-2.176.3-1.1.noarch) scriptlet failed, exit status 1 Error in PREIN scriptlet in rpm package jenkins-2.176.3-1.1.noarch Verifying : jenkins-2.176.3-1.1.noarch 1/1 Failed: jenkins.noarch 0:2.176.3-1.1 This also causes our puppet automation to fail since the package cannot be installed.
[JIRA] (JENKINS-59288) Not able to connect to RobotFramework-SikuliLibrary
Title: Message Title Anthony Le updated an issue Jenkins / JENKINS-59288 Not able to connect to RobotFramework-SikuliLibrary Change By: Anthony Le Summary: Not able to obtain connect to RobotFramework-SikuliLibrary Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201831.1568068192000.2246.1568312940165%40Atlassian.JIRA.
[JIRA] (JENKINS-58588) Do not delete remoting.jar file on disconnect
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58588 Jenkins / JENKINS-58588 Do not delete remoting.jar file on disconnect Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.30.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200744.1563738869000.2295.1568319600586%40Atlassian.JIRA.
[JIRA] (JENKINS-59251) Update JCasC to version with security fixes
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59251 Jenkins / JENKINS-59251 Update JCasC to version with security fixes Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.30.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201714.1567697181000.2294.1568319600575%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title Jesse Glick commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message Better to use one of the other fixes, I think. isApplicable should be checked in the config GUI, but may not block the descriptor from appearing elsewhere, such as Pipeline Syntax. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.2292.1568319600554%40Atlassian.JIRA.
[JIRA] (JENKINS-59339) Required parameter 'hyperVGeneration' is missing (null)
Title: Message Title
Nick Jones created an issue
Jenkins / JENKINS-59339
Required parameter 'hyperVGeneration' is missing (null)
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-09-12 20:36
Environment:
Azure VM Agents 1.2.1
Priority:
Blocker
Reporter:
Nick Jones
Sometime between July 12th – our last successful Azure VM agent for Jenkins – and September 12th, the deployments of new agents from Jenkins stopped working. I upgraded to 1.2.1 today and tested it, and the deployment failed with the following error:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"BadRequest","message":"{\r\n \"error\": {\r\n \"code\": \"InvalidParameter\",\r\n \"message\": \"Required parameter 'hyperVGeneration' is missing (null).\",\r\n \"target\": \"hyperVGeneration\"\r\n }\r\n}"}]}
I tried downgrading to 1.2.0 in case that was the issue, but it has the same issue – suggesting that this is a new requirement on the Azure side that the Azure VM Agents plugin is not handling. This entirely blocks the usage of Azure agents, so we have no workaround but to use permanent agents or alternate clouds.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title René Scheibe commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message Ok, thanks for the feedback. I'll follow your suggestion to adapt getDisplayName() as you have a better overview of the complete code base. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.2312.1568320980140%40Atlassian.JIRA.
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title Timothy Klopotoski updated an issue Jenkins / JENKINS-59337 "No such DSL method 'call'" when calling step within dynamically loaded library a second time Change By: Timothy Klopotoski Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201888.1568317781000.2314.1568322000138%40Atlassian.JIRA.
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Paulo Grilo created an issue Jenkins / JENKINS-59336 Git plugin version 4.0.0-rc failed to load Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-09-12 19:09 Priority: Major Reporter: Paulo Grilo Update my Jenkins to ver. 2.194 and update the last week plugins versions. After all the restart, jenkins showed a warning about a security issue on the Git Client plugin. Because of that, I downgraded the Git Client plugin to the previous version. After the restart, Jenkins cannot start Jenkins Git Plugin. Re-installed again the latest Git Client plugin but the error remains. The log refers to install version 3.0.0-rc or later of the Jenkins Git client... but the only version available is 2.8.5 and 2.7.6. Can you give instructions to proceed? Share bellow the referred log error: (...) 2019-09-12 18:45:06.525+ [id=33] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 2019-09-12 18:45:06.803+ [id=35] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Jenkins Git plugin v4.0.0-rc (git) java.io.IOException: Jenkins Git plugin version 4.0.0-rc failed to load. Jenkins Git client plugin version 2.8.5 is older than required. To fix, install version 3.0.0-rc or later. at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:922) at hudson.PluginManager$2$1$1.run(PluginManager.java:544) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1118) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title Timothy Klopotoski created an issue Jenkins / JENKINS-59337 "No such DSL method 'call'" when calling step within dynamically loaded library a second time Issue Type: New Feature Assignee: Unassigned Attachments: consoleText-failing.txt, consoleText-success.txt Components: workflow-cps-global-lib-plugin, workflow-cps-plugin Created: 2019-09-12 19:49 Environment: Operating System: amazon linux 64-bit (master+workers) Jenkins version: 2.176.2 -- master image is built from official Jenkins LTS Docker image workflow-cps-plugin: 2.74 workflow-cps-global-lib-plugin: 2.15 Priority: Minor Reporter: Timothy Klopotoski My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library P which dynamically loads child library C. P is globally configured and loaded explicitly in Jenkinsfile J using `@Library()`. J --> P --> C C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy](https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy)) P contains step Z which calls X. (see [fail.groovy](https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14)) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title René Scheibe commented on JENKINS-57694 Re: BuildChooser logs a missing descriptor message What about adding the Descriptor again with isApplicable(...) always returning false? So it's not selectable in the UI but provides the counterpart to the Describable. I have add a draft pull request https://github.com/jenkinsci/git-plugin/pull/760 for it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.2285.1568319240440%40Atlassian.JIRA.
[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message
Title: Message Title
René Scheibe edited a comment on JENKINS-57694
Re: BuildChooser logs a missing descriptor message
What about adding the {{Descriptor}} again with {{isApplicable(...)}} always returning {{false}}? So it's not selectable in the UI but provides the counterpart to the {{Describable}}. I have add added a draft pull request [https://github.com/jenkinsci/git-plugin/pull/760] for it.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.2288.1568319360165%40Atlassian.JIRA.
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title
Timothy Klopotoski updated an issue
Jenkins / JENKINS-59337
"No such DSL method 'call'" when calling step within dynamically loaded library a second time
Change By:
Timothy Klopotoski
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`.*J --> P --> C*C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy ]( | https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy ] ) ) P contains step Z which calls X. (see [fail.groovy ]( | https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14 ] ) ) When J calls X() X(), no problem.But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_).On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_)So far I have found no workaround to this problem.*Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:*1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent2. Create a Pipeline job with the following pipeline script:bq. @Library('timski@master') _bq. bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credentialbq. bq. fail()3. Run the job and observe a failure.
Add Comment
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title
Timothy Klopotoski updated an issue
Jenkins / JENKINS-59337
"No such DSL method 'call'" when calling step within dynamically loaded library a second time
Change By:
Timothy Klopotoski
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`.*J --> P --> C*C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy])P contains step Z which calls X. (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14])When J calls X() X(), no problem.But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_).On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_)So far I have found no workaround to this problem.*Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:*1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent2. Create a Pipeline job with the following pipeline script:bq. @Library('timski@master') _bq. bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credentialbq. bq. fail()3. Run the job and observe a failure.
Add Comment
[JIRA] (JENKINS-32118) Document Jenkins security settings so Robot Framework log/report can be opened
Title: Message Title Andrew Grimberg commented on JENKINS-32118 Re: Document Jenkins security settings so Robot Framework log/report can be opened My team gave up on doing the work around. We just shuffle the robot logs off to a different storage static web host, along with a lot of logs that Jenkins doesn't capture for us anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.167087.1450344294000.2319.1568325421906%40Atlassian.JIRA.
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Ulli Hafner commented on JENKINS-58383 Re: Disable aggregated analysis results This should be a server side option in the Jenkinsfile. I could imagine an extra parameter or a predefined ID that can be overridden. Why not on the client side? It feels somewhat wrong to define a UI property on the server side. Maybe other users of a job want to see the aggregation? BTW what is the meaning of the recordIssues aggregatingResults parameter? It is used if you are using multiple tools per recordIssues step. Then you get only one result (link) with all warnings aggregated. Otherwise you get a result per tool. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.2275.1568318160243%40Atlassian.JIRA.
[JIRA] (JENKINS-44111) Enable Remoting work dir by default in SSH Slaves Plugin
Title: Message Title Ivan Fernandez Calvo updated JENKINS-44111 Jenkins / JENKINS-44111 Enable Remoting work dir by default in SSH Slaves Plugin Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.27 , ssh-slaves-1.30.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181737.1494225034000.2300.1568319661128%40Atlassian.JIRA.
[JIRA] (JENKINS-54897) Unexpected error in launching a agent after restart
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54897 Jenkins / JENKINS-54897 Unexpected error in launching a agent after restart Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.30.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195903.1543354941000.2298.1568319661101%40Atlassian.JIRA.
[JIRA] (JENKINS-59338) cannot provision VMs using custom image
Title: Message Title
Paulius Bulotas created an issue
Jenkins / JENKINS-59338
cannot provision VMs using custom image
Issue Type:
Bug
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2019-09-12 20:30
Environment:
CentOS 7 openjdk 1.8 Jenkins 2.176.3 plugin 1.2.1
Priority:
Minor
Reporter:
Paulius Bulotas
Hi, we are using custom image deployment, and after upgrading to 1.2.0 and 1.2.1 only NIC is created, no VM. Error contains this (from 1.2.1 use) :
"message": "{\r\n \"error\": {\r\n \"code\": \"InvalidParameter\",\r\n \"message\": \"Required parameter 'hyperVGeneration' is missing (null).\",\r\n \"target\": \"hyperVGeneration\"\r\n }\r\n}"
Add Comment
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Kunal Kannav commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Hi Uwe Schindler, We are still facing the issue. '/' is missing in the href on the RSS XML Thanks, Kunal Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201604.1567266415000.2387.1568330100280%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated but still exist
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated but still exist Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin, workflow-durable-task-step-plugin Created: 2019-09-13 00:49 Environment: kubernetes-plugin:1.17.2 workflow-durable-task-step-plugin:2.33 core:2.176.3.2 Priority: Major Reporter: Allan BURDAJEWICZ When a agent pod gets terminated (for example OOMKilled by Kubernetes) during a pipeline build in a shell step: the node remains in Jenkins, as disconnected the pipeline hangs forever the pod remains in kubernetes, in Terminated state, with OOMKilled status A manual intervention is necessary to fix this situation: Aborting the pipeline manually causes the node to be removed and the pod to eventually been deleted as well Deleting the pod manually cause the node to be removed (after about 5 minutes for some reason) and eventually the pipeline to be aborted How to Reproduce We need to simulate a pod failure when the agent is connected and building a pipeline. To reproduce this, I am using a jnlp agent with stress-ng: [dohbedoh/jnlp-stress-agent:alpine](https://hub.docker.com/r/dohbedoh/jnlp-stress-agent)
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated but still exist
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-59340
Pipeline hangs when Agent pod is Terminated but still exist
Change By:
Allan BURDAJEWICZ
When a agent pod gets terminated (for example OOMKilled by Kubernetes) during a pipeline build in a shell step:* the node remains in Jenkins, as disconnected* the pipeline hangs forever* the pod remains in kubernetes, in Terminated state, with OOMKilled statusA manual intervention is necessary to fix this situation:* Aborting the pipeline manually causes the node to be removed and the pod to eventually been deleted as well* Deleting the pod manually cause the node to be removed (after about *5 minutes* for some reason) and eventually the pipeline to be abortedh3. Expected BehaviorThe pipeline should abort automatically and the node be automatically removed.h3. How to ReproduceWe need to simulate a pod failure when the agent is connected and building a pipeline. To reproduce this, I am using a _jnlp_ agent with _stress-ng_: [dohbedoh/jnlp-stress-agent:alpine](https://hub.docker.com/r/dohbedoh/jnlp-stress-agent)* Create a pipeline that simulate an kubernetes `OOMKilled` during the build:{code}pipeline { agent {kubernetes { yaml """metadata: labels:cloudbees.com/master: "dse-team-apac"jenkins: "slave"jenkins/stress: "true"spec: containers: - name: "jnlp"image: "dohbedoh/jnlp-stress-agent:alpine"imagePullPolicy: "Always"resources: limits:memory: "128Mi"cpu: "0.2" requests:memory: "100Mi"cpu: "0.2"securityContext: privileged: truetty: true"""} } stages {stage('stress') { steps {sh "stress-ng --vm 2 --vm-bytes 1G --timeout 30s -v" }} }}{code}The pod should get OOMKilled by kubernetes:{code}$ kubectl get pod dse-team-apac-aburdajewicz-testscenario-4-10xd4-558nc-5khzjNAME READY STATUS RESTARTS AGEdse-team-apac-aburdajewicz-testscenario-4-10xd4-558nc-5khzj 0/1 OOMKilled 0 3m21s{code}And the pipeline jobs show the disconnection and hangs forever:{code}Running on dse-team-apac-aburdajewicz-testscenario-4-10xd4-558nc-5khzj in /home/jenkins/workspace/dse-team-apac/aburdajewicz/testScenario[Pipeline] {[Pipeline] stage[Pipeline] { (stress)[Pipeline] sh+ stress-ng --vm 2 --vm-bytes 1G --timeout 30s -vstress-ng: debug: [86] 2 processors online, 2 processors configuredstress-ng: info: [86] dispatching hogs: 2 vmstress-ng: debug: [86] cache allocate: default cache size: 46080Kstress-ng: debug: [86] starting stressorsstress-ng: debug: [86] 2 stressors spawnedstress-ng: debug: [89] stress-ng-vm: started [89] (instance 1)stress-ng: debug: [89] stress-ng-vm using method 'all'stress-ng: debug: [88] stress-ng-vm: started [88] (instance 0)stress-ng: debug: [88] stress-ng-vm using method 'all'Cannot contact dse-team-apac-aburdajewicz-testscenario-4-10xd4-558nc-5khzj: hudson.remoting.RequestAbortedException: java.nio.channels.ClosedChannelException{code}
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated but still exist
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated but still exist Change By: Allan BURDAJEWICZ Attachment: kubernetes-plugin-fine.log Attachment: durabletask-and-workflowdurabletask-fine.log Attachment: build.log Attachment: agent-oom-killed-description.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated but still exist
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated but still exist Change By: Allan BURDAJEWICZ Attachment: support-bundle_2019-09-13_00.50.40.zip Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.2392.1568336700110%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated Change By: Allan BURDAJEWICZ Summary: Pipeline hangs when Agent pod is Terminated but still exist Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.2394.1568336820063%40Atlassian.JIRA.
[JIRA] (JENKINS-59337) "No such DSL method 'call'" when calling step within dynamically loaded library a second time
Title: Message Title Timothy Klopotoski commented on JENKINS-59337 Re: "No such DSL method 'call'" when calling step within dynamically loaded library a second time It is worth noting that there are other ways to produce the issue, but above was the most trivial way I could find so far. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201888.1568317781000.2384.1568328300066%40Atlassian.JIRA.
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite commented on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center. The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released. You have a few choices to resolve the security issue in git client plugin 3.0.0-rc. Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center Upload git plugin 3.12.1 and git client plugin 2.8.5 into your Jenkins server from the "Advanced" tab of the "Manage Plugins" page inside "Manage Jenkins" Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the Jenkins experimental update center Upload git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 into your Jenkins server from the "Advanced" tab of the "Manage Plugins" page inside "Manage Jenkins" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite edited a comment on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center.The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released.You have a few choices to resolve the [security issue|https://jenkins.io/security/advisory/2019-09-12/] in git client plugin 3.0.0-rc.# Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center# Upload [git plugin 3.12.1|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/3.12.1/git-3.12.1.hpi] and [git client plugin 2.8.5|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/2.8.5/git-client-2.8.5.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" # Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the Jenkins experimental update center# Upload [git plugin 4.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/4.0.0-beta11/git-4.0.0-beta11.hpi] and [git client plugin 3.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/3.0.0-beta11/git-client-3.0.0-beta11.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*"If you choose git plugin 3.12.1, you are choosing the released git plugin and the most stable.If you choose git plugin 4.0.0-beta11, you are choosing the most recent pre-release git plugin with more bug fixes than are available in git plugin 3.12.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite updated JENKINS-59336 Jenkins / JENKINS-59336 Git plugin version 4.0.0-rc failed to load Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201887.1568315372000.2400.1568337300288%40Atlassian.JIRA.
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite edited a comment on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center.The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released.You have a few choices to resolve the [security issue|https://jenkins.io/security/advisory/2019-09-12/] in git client plugin 3.0.0-rc.# Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center# Upload [git plugin 3.12.1|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/3.12.1/git-3.12.1.hpi] and [git client plugin 2.8.5|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/2.8.5/git-client-2.8.5.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" # Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the [Jenkins experimental update center|https://jenkins.io/ zh doc / blog developer / 2013 publishing / 09/23/ releasing- experimental- plugins-update-center updates /]# Upload [git plugin 4.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/4.0.0-beta11/git-4.0.0-beta11.hpi] and [git client plugin 3.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/3.0.0-beta11/git-client-3.0.0-beta11.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" If you choose git plugin 3.12.1, you are choosing the released git plugin and the most stable.If you choose git plugin 4.0.0-beta11, you are choosing the most recent pre-release git plugin with more bug fixes than are available in git plugin 3.12.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite edited a comment on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center.The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released.You have a few choices to resolve the [security issue|https://jenkins.io/security/advisory/2019-09-12/] in git client plugin 3.0.0-rc.# Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center# Upload [git plugin 3.12.1|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/3.12.1/git-3.12.1.hpi] and [git client plugin 2.8.5|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/2.8.5/git-client-2.8.5.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" # Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the [Jenkins experimental update center|https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ #using-the-experimental-update-center ]# Upload [git plugin 4.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/4.0.0-beta11/git-4.0.0-beta11.hpi] and [git client plugin 3.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/3.0.0-beta11/git-client-3.0.0-beta11.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" If you choose git plugin 3.12.1, you are choosing the released git plugin and the most stable.If you choose git plugin 4.0.0-beta11, you are choosing the most recent pre-release git plugin with more bug fixes than are available in git plugin 3.12.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite edited a comment on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center.The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released.You have a few choices to resolve the [security issue|https://jenkins.io/security/advisory/2019-09-12/] in git client plugin 3.0.0-rc.# Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center# Upload [git plugin 3.12.1|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/3.12.1/git-3.12.1.hpi] and [git client plugin 2.8.5|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/2.8.5/git-client-2.8.5.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" # Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the [ Jenkins experimental update center |https://jenkins.io/zh/blog/2013/09/23/experimental-plugins-update-center/] # Upload [git plugin 4.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/4.0.0-beta11/git-4.0.0-beta11.hpi] and [git client plugin 3.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/3.0.0-beta11/git-client-3.0.0-beta11.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" If you choose git plugin 3.12.1, you are choosing the released git plugin and the most stable.If you choose git plugin 4.0.0-beta11, you are choosing the most recent pre-release git plugin with more bug fixes than are available in git plugin 3.12.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-49789) NPE when attempting to parse exception
Title: Message Title Harminder Singh reopened an issue We were getting SocketTimeoutExceptions on v1.8. So we upgraded to v2.0 recently. Since then we are getting this NullPointerException very frequently It occurs randomly at any point during upload. Sometimes after 1 build is uploaded successfully, sometimes after 5 builds uploaded successfully and so on. ERROR: [flexible-publish] Upload Android APK to Google Play (org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher@4853b58d) aborted due to exception java.lang.NullPointerException at org.jenkinsci.plugins.googleplayandroidpublisher.Util.getPublisherErrorMessage(Util.java:102) at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.publishApk(ApkPublisher.java:379) at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:194) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at org.jenkins_ci.plugins.flexible_publish.builder.FailAtEndBuilder.perform(FailAtEndBuilder.java:104) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkins_ci.plugins.flexible_publish.strategy.FailAtEndExecutionStrategy.perform(FailAtEndExecutionStrategy.java:85) at org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher.perform(ConditionalPublisher.java:206) at org.jenkins_ci.plugins.flexible_publish.FlexiblePublisher.perform(FlexiblePublisher.java:124) Jenkins / JENKINS-49789 NPE when attempting to parse exception Change By: Harminder Singh Resolution: Done Status: Closed Reopened Add Comment
