[JIRA] (JENKINS-58687) Tomcat deployment fails when using deploy plugin
Title: Message Title Robin Jansohn commented on JENKINS-58687 Re: Tomcat deployment fails when using deploy plugin Mike Sollanych your problem is different (I'm guessing the same as JENKINS-58667). For the Tomcat URL please don't add a trailing slash (and don't add the /manager part), e.g. in your case http://REDACTED:8080. It should be enough to simply re-save the job configuration with 1.14 to get it working again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200976.1564286728000.4869.1564642500393%40Atlassian.JIRA.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Frederico Pratas commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi, After some digging with the p4 team support we (Jose Valverde and I) managed to isolate and reproduce the credential issue. Another bug has been created to track this JENKINS-58745 Chris Carr you may want to follow up in case the issue matches your setup as well. Thanks, Frederico Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.4866.1564642380156%40Atlassian.JIRA.
[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Ocean blue
Title: Message Title ashish mishra updated an issue Jenkins / JENKINS-58747 Parameters: This property type is not supported - Ocean blue Change By: ashish mishra Attachment: Annotation 2019-08-01 134712.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201050.1564641236000.4863.1564642080129%40Atlassian.JIRA.
[JIRA] (JENKINS-51799) When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics
Title: Message Title Kent Granström commented on JENKINS-51799 Re: When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics PING... Anyone maintaining this plugin? I have hit the same problem when trying to add more than one report Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191249.1528446169000.4861.1564641840173%40Atlassian.JIRA.
[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Ocean blue
Title: Message Title
ashish mishra updated an issue
Jenkins / JENKINS-58747
Parameters: This property type is not supported - Ocean blue
Change By:
ashish mishra
*Ocean blue*: While adding downstream build job using my multibranch pipeline, there is option for parameters but it says *This property type is not supported.*I think its better to add some kind of link that says why its not supported. I tried adding parameter in script but that didn't work either.My downstream job is using BuildWithParameter plugin where i already set it up my variable unable to receive it from upstream. Script upstream multi-branch pipeline script : {code:java}stage('isHotfix') { steps { build(job: 'some-freestyle-downstream-job', parameters: [string(name: 'PARAM_BRANCH_NAME', value: "my_string")], wait: true) } }{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201050.1564641236000.4858.1564641360749%40Atlassian.JIRA.
[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Ocean blue
Title: Message Title ashish mishra updated an issue Jenkins / JENKINS-58747 Parameters: This property type is not supported - Ocean blue Change By: ashish mishra Attachment: Annotation 2019-08-01 133452.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201050.1564641236000.4856.1564641360549%40Atlassian.JIRA.
[JIRA] (JENKINS-58301) Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
Title: Message Title Tyrone Grech commented on JENKINS-58301 Re: Kubernetes Plugin Repeated Socket Ping Timeout Exceptions We are also encountering this issue fairly often in our CI system running: On premises Kubernetes cluster on version 1.14.1 Jenkins version 2.186 Kubernetes Plugin version 1.17.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200367.1562076713000.4852.1564641240497%40Atlassian.JIRA.
[JIRA] (JENKINS-58747) Parameters: This property type is not supported - Ocean blue
Title: Message Title
ashish mishra created an issue
Jenkins / JENKINS-58747
Parameters: This property type is not supported - Ocean blue
Issue Type:
Bug
Assignee:
Ivan Sugonyak
Attachments:
Annotation 2019-08-01 132736.jpg
Components:
build-with-parameters-plugin, pipeline
Created:
2019-08-01 06:33
Environment:
Jenkins: 2.187 Blue Ocean: 1.18 Blue Ocean Pipeline Editor: 1.18 Build With Parameters: 1.4
Priority:
Minor
Reporter:
ashish mishra
Ocean blue: While adding downstream build job using my multibranch pipeline, there is option for parameters but it says This property type is not supported. I think its better to add some kind of link that says why its not supported. I tried adding parameter in script but that didn't work either. My downstream job is using BuildWithParameter plugin where i already set it up my variable unable to receive it from upstream. Script :
stage('isHotfix') {
steps {
build(job: 'some-freestyle-downstream-job', parameters: [string(name: 'PARAM_BRANCH_NAME', value: "my_string")], wait: true)
}
}
[JIRA] (JENKINS-35982) EC2 Plugin: High CPU in hudson.plugins.ec2.win.winrm.WindowsProcess
Title: Message Title Raihaan Shouhell assigned an issue to Raihaan Shouhell Jenkins / JENKINS-35982 EC2 Plugin: High CPU in hudson.plugins.ec2.win.winrm.WindowsProcess Change By: Raihaan Shouhell Assignee: Francis Upton Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171928.1466020962000.4847.1564640460722%40Atlassian.JIRA.
[JIRA] (JENKINS-35982) EC2 Plugin: High CPU in hudson.plugins.ec2.win.winrm.WindowsProcess
Title: Message Title Raihaan Shouhell commented on JENKINS-35982 Re: EC2 Plugin: High CPU in hudson.plugins.ec2.win.winrm.WindowsProcess Mika Karjalainen can you try with the latest snapshot? https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ec2/1.45-rc1024.cafa05a12c08/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171928.1466020962000.4828.1564640400281%40Atlassian.JIRA.
[JIRA] (JENKINS-52440) High CPU usage caused by WindowsProcess input copy threads in ec2-plugin
Title: Message Title Raihaan Shouhell assigned an issue to Raihaan Shouhell Jenkins / JENKINS-52440 High CPU usage caused by WindowsProcess input copy threads in ec2-plugin Change By: Raihaan Shouhell Assignee: Francis Upton Raihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192265.1531164484000.4824.1564640221810%40Atlassian.JIRA.
[JIRA] (JENKINS-52440) High CPU usage caused by WindowsProcess input copy threads in ec2-plugin
Title: Message Title Raihaan Shouhell commented on JENKINS-52440 Re: High CPU usage caused by WindowsProcess input copy threads in ec2-plugin Hi Shubham Dhoka this should be fixed in the latest incremental could you try this build https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/ec2/1.45-rc1024.cafa05a12c08/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192265.1531164484000.4812.1564640221012%40Atlassian.JIRA.
[JIRA] (JENKINS-52440) High CPU usage caused by WindowsProcess input copy threads in ec2-plugin
Title: Message Title Raihaan Shouhell updated JENKINS-52440 Jenkins / JENKINS-52440 High CPU usage caused by WindowsProcess input copy threads in ec2-plugin Change By: Raihaan Shouhell Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192265.1531164484000.4821.1564640221544%40Atlassian.JIRA.
[JIRA] (JENKINS-52440) High CPU usage caused by WindowsProcess input copy threads in ec2-plugin
Title: Message Title Raihaan Shouhell started work on JENKINS-52440 Change By: Raihaan Shouhell Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192265.1531164484000.4816.1564640221297%40Atlassian.JIRA.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Pavel Roskin commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies Thank you, Jesse Glick! I was able to fix the issue in stash notifier with sshd-core bundling by updating the git dependency. It's very nice to see your PR merged already! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194562.1539080849000.4807.1564639800336%40Atlassian.JIRA.
[JIRA] (JENKINS-51799) When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-51799 When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics Change By: Kent Granström Comment: PING... Anyone maintaining this plugin? I have hit the same problem when trying to add more than one report Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191249.1528446169000.4805.1564638900202%40Atlassian.JIRA.
[JIRA] (JENKINS-51799) When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics
Title: Message Title Kent Granström commented on JENKINS-51799 Re: When using SLOCcount plugin to vizualize two different xml reports it shows data from only one report in two graphics PING... Anyone maintaining this plugin? I have hit the same problem when trying to add more than one report Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191249.1528446169000.4802.1564635900964%40Atlassian.JIRA.
[JIRA] (JENKINS-58746) Add Blog Post for code phase 2
Title: Message Title Jack Shen created an issue Jenkins / JENKINS-58746 Add Blog Post for code phase 2 Issue Type: Bug Assignee: Jack Shen Components: working-hours-plugin Created: 2019-08-01 02:33 Labels: gsoc-2019 Priority: Minor Reporter: Jack Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this disc
[JIRA] (JENKINS-35656) Inconsistent timezone display
Title: Message Title Olivier Lamy stopped work on JENKINS-35656 Change By: Olivier Lamy Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171502.1465766909000.4796.1564625404019%40Atlassian.JIRA.
[JIRA] (JENKINS-44065) Offline agents prevent on-demand provisioning
Title: Message Title Raihaan Shouhell commented on JENKINS-44065 Re: Offline agents prevent on-demand provisioning I think i misunderstood this ticket I assumed I there was a cap of 2 and 2 instances were marked temp offline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181605.149392629.4792.1564618980160%40Atlassian.JIRA.
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title
Joel Brown updated an issue
Jenkins / JENKINS-58745
P4Groovy p4.run() does not locate credentials in folder
Change By:
Joel Brown
When credentials to use are in a folder, using them in a script with p4.run() will not find the credential.Repro:create a folder.within the folder, create a credential and a pipleline job.The job's script references the credential in the folder.{ \ { script{}} \ {{ def ws = [$class: 'ManualWorkspaceImpl', name: "jenkins-${NODE_NAME}-${JOB_NAME}", }}{{ spec: [view: "//depot/main/utilities/AppUtilities/src/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]}} \ {{ def p4 = p4(credential: 'build-u18-20182', workspace: ws)}} \ {{ def output = p4.run('sync')}} \ {{ }}} A p4sync step using the same credential succeeds. console log:[Pipeline] Start of Pipeline[Pipeline] nodeRunning on [Jenkins|http://jbrown-swarmu18.das.perforce.com:8080/computer/(master)/] in /var/lib/jenkins/jobs/pipelines/jobs/simple sync/workspace[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] p4[Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentialsFinished: FAILURE
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsu
[JIRA] (JENKINS-58745) P4Groovy p4.run() does not locate credentials in folder
Title: Message Title
Joel Brown created an issue
Jenkins / JENKINS-58745
P4Groovy p4.run() does not locate credentials in folder
Issue Type:
Improvement
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-07-31 22:43
Labels:
P4_VERIFY
Priority:
Major
Reporter:
Joel Brown
When credentials to use are in a folder, using them in a script with p4.run() will not find the credential. Repro: create a folder. within the folder, create a credential and a pipleline job. The job's script references the credential in the folder. {{ script{}} {{ def ws = [$class: 'ManualWorkspaceImpl', name: "jenkins-${NODE_NAME}-${JOB_NAME}", }} {{ spec: [view: "//depot/main/utilities/AppUtilities/src/... //jenkins-${NODE_NAME}-${JOB_NAME}/..."]]}} {{ def p4 = p4(credential: 'build-u18-20182', workspace: ws)}} {{ def output = p4.run('sync')}} {{ }}} console log: [Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in /var/lib/jenkins/jobs/pipelines/jobs/simple sync/workspace[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] p4[Pipeline] } [Pipeline] // script[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: P4: Task Exception: Invalid credentials Finished: FAILURE
[JIRA] (JENKINS-31237) Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error
Title: Message Title Alex Rodriguez commented on JENKINS-31237 Re: Parameterized Remote Trigger evaluates Credential password for tokens, prints password to log on error I recently just changed my remote password to one that contains a $ character and am now seeing this issue consistently with the same behavior. Here are my current core and plugin versions: Jenkins core: 2.179 Credentials Plugin: 2.2.0 Parameterized Remote Trigger Plugin: 3.0.8 Not only does authentication not work when using complex passwords with special characters, but even worse it leaks the entire username and password to the console log, something that using the stored jenkins credentials should never do given the permission separation from administering credentials and simply viewing a log. It's disconcerting to me that this bug was filed almost 4 years ago and not a single movement has happened on this defect. Am I possibly missing an unmarked duplicate issue here, or is this really the only mention of this deal breaking bug? Can anyone else perhaps take a look at this bug again? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165942.1446052599000.4782.1564610160156%40Atlassian.JIRA.
[JIRA] (JENKINS-58744) Parameters passed null when job is run through timer, even though default is blank
Title: Message Title Nitin Surana updated an issue Jenkins / JENKINS-58744 Parameters passed null when job is run through timer, even though default is blank Change By: Nitin Surana Summary: Parameters passed null when job is run through timer , even through though default is blank Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201046.1564609828000.4779.1564609860208%40Atlassian.JIRA.
[JIRA] (JENKINS-58744) Parameters passed null when job is run through timer even through default is blank
Title: Message Title Nitin Surana created an issue Jenkins / JENKINS-58744 Parameters passed null when job is run through timer even through default is blank Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner, pipeline Created: 2019-07-31 21:50 Priority: Minor Reporter: Nitin Surana Create a jenkinsfile job with build parameters Make sure the default value of these params is blank. Create a cron to run the jobs Manually, trigger the jobs and notice the build param values goes blank as expected. When the jobs are "started by timer", then the pipeline throws error for build params being Null. The same happens for jobs triggered through jenkins github-webhook, the buildParams are null instead of their default blank. Add Comment
[JIRA] (JENKINS-58687) Tomcat deployment fails when using deploy plugin
Title: Message Title
Mike Sollanych commented on JENKINS-58687
Re: Tomcat deployment fails when using deploy plugin
I can duplicate the problem with my Jenkins instance, running 2.176.2 with the Deploy To Container plugin 1.14; downgrading to 1.13 solves the issue for me. I am certain that my Tomcat manager is running and functional; no config for the working job had changed except for upgrading this plugin. Relevant logs with 1.14: [DeployPublisher][INFO] Attempting to deploy 1 war file(s) [DeployPublisher][INFO] Deploying /var/lib/jenkins/workspace/Processor Development (PD)/config-database/Testing Test and Deploy (from Master)/Lab/build/install/Lab.war to container Tomcat 7.x Remote with context lab ERROR: Build step failed with exception org.codehaus.cargo.container.ContainerException: Failed to redeploy [/var/lib/jenkins/workspace/Processor Development (PD)/config-database/Testing Test and Deploy (from Master)/Lab/build/install/Lab.war] {{ at org.codehaus.cargo.container.tomcat.internal.AbstractTomcatManagerDeployer.redeploy(AbstractTomcatManagerDeployer.java:188)}} {{ at hudson.plugins.deploy.CargoContainerAdapter.deploy(CargoContainerAdapter.java:81)}} {{ at hudson.plugins.deploy.CargoContainerAdapter$DeployCallable.invoke(CargoContainerAdapter.java:167)}} {{ at hudson.plugins.deploy.CargoContainerAdapter$DeployCallable.invoke(CargoContainerAdapter.java:136)}} {{ at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3050)}} {{ at hudson.remoting.UserRequest.perform(UserRequest.java:212)}} {{ at hudson.remoting.UserRequest.perform(UserRequest.java:54)}} {{ at hudson.remoting.Request$2.run(Request.java:369)}} {{ at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)}} {{ at java.util.concurrent.FutureTask.run(FutureTask.java:266)}} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} {{ at java.lang.Thread.run(Thread.java:748)}} {{ Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to pd-jenkins-ls1}} {{ at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)}} {{ at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)}} {{ at hudson.remoting.Channel.call(Channel.java:957)}} {{ at hudson.FilePath.act(FilePath.java:1070)}} {{ at hudson.FilePath.act(FilePath.java:1059)}} {{ at hudson.plugins.deploy.CargoContainerAdapter.redeployFile(CargoContainerAdapter.java:133)}} {{ at hudson.plugins.deploy.PasswordProtectedAdapterCargo.redeployFile(PasswordProtectedAdapterCargo.java:95)}} {{ at hudson.plugins.deploy.DeployPublisher.perform(DeployPublisher.java:113)}} {{ at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)}} {{ at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)}} {{ at hudson.model.Build$BuildExecution.post2(Build.java:186)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)}} {{ at hudson.model.Run.execute(Run.java:1843)}} {{ at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:429)}} Caused by: java.io.FileNotFoundException: http://REDACTED:8080/null/list {{ at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1890)}} {{ at sun.net.www.protocol.http.HttpURLConnecti
[JIRA] (JENKINS-58728) Skip rerunning tests on release
Title: Message Title Jesse Glick resolved as Fixed done in https://github.com/jenkinsci/bom/commit/c6e2febf115f12781ca49aa9c0aba733a32bb4c1 Jenkins / JENKINS-58728 Skip rerunning tests on release Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201023.1564489333000.4772.1564604160098%40Atlassian.JIRA.
[JIRA] (JENKINS-58743) Remove need to store master key in filesystem
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-58743 Remove need to store master key in filesystem Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-07-31 20:04 Priority: Minor Reporter: Matt Sicker The existing implementation of ConfidentialStore in Jenkins relies on a secret key that is stored inside JENKINS_HOME/secrets/master.key which is used for encrypting the keys used to encrypt various other secrets. This key file is really only required during startup as the key is loaded into memory and used for unlocking the confidential store which allows for encrypting and decrypting data elsewhere in Jenkins. Add Comment
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-58656 Wrapper process leaves zombie when no init process present Change By: Devin Nusbaum Labels: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.4770.1564603200216%40Atlassian.JIRA.
[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title
Jesse Glick commented on JENKINS-54346
Re: tee keeps file open
I am neither the author of the patch, nor the maintainer of the plugin. There is a trivial workaround for some use cases: replace
tee('output.txt') {
sh 'some command'
}
with
sh 'some command >output.txt 2>&1'
Of course this is not possible if you were redirecting output from multiple nested steps that could not be coalesced.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195001.1540906753000.4756.1564602840408%40Atlassian.JIRA.
[JIRA] (JENKINS-54346) tee keeps file open
Title: Message Title Tom Skrainar commented on JENKINS-54346 Re: tee keeps file open We just started using tee() in a workflow, and in less than 24h, one agent leaked enough descriptors to hit the per-process limit. Use of tee() in this workflow was fundamental to the workflow itself, so this is a huge blocker for us (considering an agent restart is required to resolve). Jesse Glick any update on https://github.com/jenkinsci/pipeline-utility-steps-plugin/pull/62 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195001.1540906753000.4742.1564602060409%40Atlassian.JIRA.
[JIRA] (JENKINS-58606) Add info about backup plugins to support bundle
Title: Message Title Owen Wood updated JENKINS-58606 Jenkins / JENKINS-58606 Add info about backup plugins to support bundle Change By: Owen Wood Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200766.1563824088000.4737.1564601880327%40Atlassian.JIRA.
[JIRA] (JENKINS-58606) Add info about backup plugins to support bundle
Title: Message Title Owen Wood commented on JENKINS-58606 Re: Add info about backup plugins to support bundle https://github.com/jenkinsci/support-core-plugin/pull/181 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200766.1563824088000.4739.1564601880375%40Atlassian.JIRA.
[JIRA] (JENKINS-58606) Add info about backup plugins to support bundle
Title: Message Title Owen Wood started work on JENKINS-58606 Change By: Owen Wood Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200766.1563824088000.4733.1564601400275%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent edited a comment on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). I do have it working with a "secret text" token.However, there is an issue with the Credentials integration because if I attempt to click the "Add..." button from the job configuration page, it either does nothing, or allows me to enter the new credential information but won't actually save it.##01 - Click Add -> Jenkins## !image-2019-07-31-12-27-28-291.png|width=646,height=133!##02 - Add new Super Secret Text Token## !image-2019-07-31-12-23-33-121.png|width=629,height=488! ###03 - Attempt to select (no SuperSecretTextTestToken listed)### !image-2019-07-31-12-36-07-816.png|width=644,height=132! ###04 - Check Credential store###(no SuperSecretTextTestToken listed) !image-2019-07-31-12-33-57-056.png|width=515,height=370! !image-2019-07-31-12-31-11-944.png|width=374,height=215!I can add it if I go to the Credential manager first. I do see a warning however, in this case that even if I pick a valid "secret text" credential for SonarQube even though the secret text credential works fine: !image-2019-07-31-12-40-23-490.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4729.1564598520205%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent commented on JENKINS-58061 Re: Can't configure SonarQube User Token (text field replaced with credentials drop-down). I do have it working with a "secret text" token. However, there is an issue with the Credentials integration because if I attempt to click the "Add..." button from the job configuration page, it either does nothing, or allows me to enter the new credential information but won't actually save it. ##01 - Click Add -> Jenkins## ##02 - Add new Super Secret Text Token## ###03 - Attempt to select (no SuperSecretTextTestToken listed)### ###04 - Check Credential store### (no SuperSecretTextTestToken listed) I can add it if I go to the Credential manager first. I do see a warning however, in this case that even if I pick a valid "secret text" credential for SonarQube even though the secret text credential works fine: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4726.1564598460182%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-40-23-490.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4725.1564598460169%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-36-07-816.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4723.1564598220120%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-35-23-304.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4721.1564598160428%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-33-57-056.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4719.1564598040137%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-31-11-944.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4717.1564597920200%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-27-28-291.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4715.1564597680133%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-25-25-766.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4712.1564597560247%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-25-22-755.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4711.1564597560214%40Atlassian.JIRA.
[JIRA] (JENKINS-58061) Can't configure SonarQube User Token (text field replaced with credentials drop-down).
Title: Message Title Jeff VIncent updated an issue Jenkins / JENKINS-58061 Can't configure SonarQube User Token (text field replaced with credentials drop-down). Change By: Jeff VIncent Attachment: image-2019-07-31-12-23-33-121.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200082.1560824562000.4709.1564597440150%40Atlassian.JIRA.
[JIRA] (JENKINS-54537) Scripted Pipeline does not work due to tags
Title: Message Title Ronald Gundlach-Chmara updated an issue Jenkins / JENKINS-54537 Scripted Pipeline does not work due to tags Change By: Ronald Gundlach-Chmara Comment: Looks like the change was introduced in this commit: https://github.com/jenkinsci/rundeck-plugin/commit/42880f7fbe466c11f74e63949945c08d4ccf24b6#diff-965511c16416a9a65a279663d96b9290 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195309.1541669457000.4707.1564597380630%40Atlassian.JIRA.
[JIRA] (JENKINS-58742) IOException: Unexpected Fingerprint type
Title: Message Title Jeff VIncent created an issue Jenkins / JENKINS-58742 IOException: Unexpected Fingerprint type Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-07-31 18:18 Environment: Ubuntu 18.04.2 Oracle Java 8 (v1.8.0_212-b10) Tomcat8 Jenkins LTS 2.176.2 Maven 3.6.1 Jenkins Plugins: ace-editor 1.1 ant 1.9 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 authorize-project 1.3.0 badge 1.8 bitbucket 1.1.10 bitbucket-oauth 0.9 blueocean 1.18.0 blueocean-autofavorite 1.2.4 blueocean-bitbucket-pipeline 1.18.0 blueocean-commons 1.18.0 blueocean-config 1.18.0 blueocean-core-js 1.18.0 blueocean-dashboard 1.18.0 blueocean-display-url 2.3.0 blueocean-events 1.18.0 blueocean-git-pipeline 1.18.0 blueocean-github-pipeline 1.18.0 blueocean-i18n 1.18.0 blueocean-jira 1.18.0 blueocean-jwt 1.18.0 blueocean-personalization 1.18.0 blueocean-pipeline-api-impl 1.18.0 blueocean-pipeline-editor 1.18.0 blueocean-pipeline-scm-api 1.18.0 blueocean-rest 1.18.0 blueocean-rest-impl 1.18.0 blueocean-web 1.18.0 bouncycastle-api 2.17 branch-api 2.5.4 build-timeout 1.19 build-with-parameters 1.4 cloudbees-bitbucket-branch-source 2.4.5 cloudbees-folder 6.9 cmakebuilder 2.6.1 command-launcher 1.3 conditional-buildstep 1.3.6 config-file-provider 3.6.2 configurationslicing 1.47 copyartifact 1.42.1 coverity 1.11.4 credentials 2.2.0 credentials-binding 1.19 dashboard-view 2.10 display-url-api 2.3.1 docker-commons 1.15 docker-workflow 1.18 dtkit-api 2.1.1-1 durable-task 1.30 email-ext 2.66 envinject 2.2.0 envinject-api 1.6 external-monitor-job 1.7 favorite 2.3.2 git 3.11.0 git-client 2.8.0 git-server 1.7 github 1.29.4 github-api 1.95 github-branch-source 2.5.5 gitlab-oauth 1.4 gitlab-plugin 1.5.12 gradle 1.33 greenballs 1.15 groovy 2.2 groovy-postbuild 2.5 groovy-remote 0.2 h2-api 1.4.199 handlebars 1.1.1 handy-uri-templates-2-api 2.1.7-1.0 htmlpublisher 1.18 icon-shim 2.0.3 jackson2-api 2.9.9.1 javadoc 1.5 jdk-tool 1.3 JDK_Parameter_Plugin 1.0 jenkins-design-language 1.18.0 jira 3.0.8 job-dsl 1.74 jquery 1.12.4-0 jquery-detached 1.2.1 jsch 0.1.55.1 junit 1.28 ldap 1.20 lockable-resources 2.5 mailer 1.24 managed-scripts 1.4 mapdb-api 1.0.9.0 mashup-portlets-plugin 1.1.0 matrix-auth 2.4.2 matrix-combinations-parameter 1.3.0 matrix-groovy-execution-strategy 1.0.7 matrix-project 1.14 maven-dependency-update-trigger 1.5 maven-plugin 3.3 mercurial 2.8 momentjs 1.1.1 multi-slave-config-plugin 1.2.0 nexus-artifact-uploader 2.10 p4 1.10.3 pam-auth 1.5.1 par
[JIRA] (JENKINS-54537) Scripted Pipeline does not work due to tags
Title: Message Title Ronald Gundlach-Chmara commented on JENKINS-54537 Re: Scripted Pipeline does not work due to tags Looks like the change was introduced in this commit: https://github.com/jenkinsci/rundeck-plugin/commit/42880f7fbe466c11f74e63949945c08d4ccf24b6#diff-965511c16416a9a65a279663d96b9290 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195309.1541669457000.4701.1564597080220%40Atlassian.JIRA.
[JIRA] (JENKINS-41845) Suppress default pipeline output
Title: Message Title Jesse Glick commented on JENKINS-41845 Re: Suppress default pipeline output Ravi Godavarthi this has little or nothing to do with Scripted vs. Declarative Pipeline syntax. You can use either the “classic” or Blue Ocean UIs to display execution results. (B.O. does impose certain restrictions on the structure of flow graphs which it is able to display; Declarative syntax is designed to only produce graphs which follow those restrictions, though you can do the same from Scripted syntax with a bit of care.) At any rate, removing a lot of clutter from logs is a valid goal. new to plugin development, let me know how I can help This would be a patch to workflow-job-plugin, probably tested only interactively (mvn hpi:run) since I do not know of a straightforward way to automate it. I would try patching src/main/resources/org/jenkinsci/plugins/workflow/job/console/NewNodeConsoleNote/script.js to offer some sort of button to toggle display of pipeline-new-node spans, ideally persisting this preference in the browser. (It could also be stored in a UserProperty but that would require some more complicated Java plumbing I do not want to go into right now.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178692.1486564607000.4683.1564596660428%40Atlassian.JIRA.
[JIRA] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Doug Whitfield commented on JENKINS-48525 Re: Perforce plugin doesn't sync William Brode we did not get the logs in that particular case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187142.1513120856000.4668.1564592700561%40Atlassian.JIRA.
[JIRA] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title William Brode commented on JENKINS-48525 Re: Perforce plugin doesn't sync Doug Whitfield or Arkady English - what was the resolution of your issue? We are seeing similar behavior so it could help us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187142.1513120856000.4666.1564590842238%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen commented on JENKINS-57955 Re: Clean and sync incorrectly follows junction/directory symlinks on Windows P4Java's reconcile supports 'symlinks' not 'junctions'. Please use: mklink /D "%WORKSPACE%\3rdparty" "C:\Jenkins\3rdparty" 'D' for a Directory Symlink. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4639.1564589880279%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Rob Graham commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation I think I have spoken too soon, our problem may still be there. Frustratingly we have evidence that BlueOcean 1.17 (which we were running for a couple of weeks without problem) used sse-gateway 1.17 but installing BlueOcean 1.17 now seems to pull in sse-gateway 1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.4643.1564589880366%40Atlassian.JIRA.
[JIRA] (JENKINS-44065) Offline agents prevent on-demand provisioning
Title: Message Title Nate Gallaher commented on JENKINS-44065 Re: Offline agents prevent on-demand provisioning Raihaan Shouhell Are you saying that the behavior has been fixed to now provision up to the instance cap? My example case had an instance cap and would not provision past 1 instance even though the instance cap was 2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181605.149392629.4632.1564589640451%40Atlassian.JIRA.
[JIRA] (JENKINS-44065) Offline agents prevent on-demand provisioning
Title: Message Title Nate Gallaher updated JENKINS-44065 Jenkins / JENKINS-44065 Offline agents prevent on-demand provisioning Change By: Nate Gallaher Resolution: Not A Defect Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181605.149392629.4634.1564589640478%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen reopened an issue Possible issue when cleaning up symbolic links on Windows. Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Resolution: Fixed Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4627.1564587300383%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen assigned an issue to Matthew Smeeth Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Assignee: Paul Allen Matthew Smeeth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4623.1564587120324%40Atlassian.JIRA.
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-57955 Clean and sync incorrectly follows junction/directory symlinks on Windows Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4620.1564587120259%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Devin Nusbaum commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation FWIW I opened https://github.com/jenkinsci/sse-gateway-plugin/pull/34 to give the timer threads in sse-gateway meaningful names to make it easier to understand whether that plugin really is the problem (I don't know what that plugin actually does). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.4615.1564586520216%40Atlassian.JIRA.
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Shashank Goel updated an issue Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Change By: Shashank Goel Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201043.1564584295000.4612.1564585320086%40Atlassian.JIRA.
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Shashank Goel updated an issue Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Change By: Shashank Goel Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201043.1564584295000.4611.1564585080821%40Atlassian.JIRA.
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Shashank Goel updated an issue Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Change By: Shashank Goel I've more than a dozen environment with similar build configuration and artifacts to be uploaded from the Jenkins server. I pull up the code from SVN and then modifies it according to the target Environment (taking target Environment Name as parameters from User) and then modifies that environment-specific details in the artifacts and then upload it to the target server using Publish over SSH plugin. Now, this was okay until I had 6 Environment but the servers are increasing day-by-day for me and it is hard to configure the target server every time. ANd Moreover, I have 12 such build jobs. It would be helpful if I could configure Environment Variables in the Server Name and then the plugin could actually search for the server in the list of configured servers. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201043.1564584
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Shashank Goel updated an issue Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Change By: Shashank Goel Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201043.1564584295000.4609.1564584360262%40Atlassian.JIRA.
[JIRA] (JENKINS-58741) Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin
Title: Message Title Shashank Goel created an issue Jenkins / JENKINS-58741 Ability to use Environment Variables in Server Name and Label in Publish to SSH Server Plugin Issue Type: Bug Assignee: Unassigned Components: publish-over-ssh-plugin Created: 2019-07-31 14:44 Environment: Jenkins 2.138.1 Publish over SSH 1.20.1 Labels: publish-over-ssh Priority: Minor Reporter: Shashank Goel I've more than a dozen environment with similar build configuration and artifacts to be uploaded from the Jenkins server. I pull up the code from SVN and then modifies it according to the target Environment (taking target Environment Name as parameters from User) and then modifies that environment-specific details in the artifacts and then upload it to the target server using Publish over SSH plugin. Now, this was okay until I had 6 Environment but the servers are increasing day-by-day for me and it is hard to configure the target server every time. ANd I have 12 such build jobs. It would be helpful if I could configure Environment Variables in the Server Name and then the plugin could actually search for the server in the list of configured servers.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Rob Graham commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Downgrading to BlueOcean 1.17 (which in turn uses sse-gateway 1.17) appears to have resolved our issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.4605.1564583460276%40Atlassian.JIRA.
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies I filed a PR for that last suggestion. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194562.1539080849000.4595.1564582500319%40Atlassian.JIRA.
[JIRA] (JENKINS-58740) NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute
Title: Message Title Kyle Cronin updated JENKINS-58740 https://github.com/jenkinsci/kubernetes-plugin/pull/571 Jenkins / JENKINS-58740 NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute Change By: Kyle Cronin Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201041.1564580209000.4591.1564581660108%40Atlassian.JIRA.
[JIRA] (JENKINS-58740) NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute
Title: Message Title
Kyle Cronin created an issue
Jenkins / JENKINS-58740
NullPointerException rendering kubernetes cloud configuration due to missing pod label field attribute
Issue Type:
Bug
Assignee:
Kyle Cronin
Components:
kubernetes-plugin
Created:
2019-07-31 13:36
Environment:
kubernetes-plugin=1.17.3
Labels:
plugin kubernetes-plugin configure
Priority:
Minor
Reporter:
Kyle Cronin
NullPointerException because pod labels repeater tag is missing field attribute
"${%Pod Labels}" field="podLabels">
"true" addCaption="${%Add Pod Label}"
deleteCaption="${%Delete Pod Label}" />
Jul 31, 2019 1:24:29 PM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /$stapler/bound/47f1d8ad-2867-4408-874b-e509636d2185/render. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class hudson.model.Hudson' in thread 'Handling POST /$stapler/bound/47f1d8ad-2867-4408-874b-e509636d2185/render from 172.17.0.1 : qtp1717159510-91 KubernetesCloud/Descr
[JIRA] (JENKINS-53957) hpi bundles transitive dependencies of test scope dependencies
Title: Message Title Jesse Glick commented on JENKINS-53957 Re: hpi bundles transitive dependencies of test scope dependencies Pavel Roskin I suppose you mean 1.19, not 1.9. Your use of dependency:tree shows clearly that the problem is in your POM, not in the plugin. (maven-hpi-plugin simply follows Maven’s directions here about what scope a dependency is in.) It seems to stem from having a dependency on an ancient version of the git plugin which itself had a faulty POM, in turn due to a faulty POM in git-client. (As far back as I can easily follow history, this seems to have been fixed in 2013. The ssh-agent plugin’s POM does bundle sshd-core.jar, but in that case it is correct since it sets pluginFirstClassLoader: it is not using the copy from the core module. But any plugin depending on ssh-agent must exclude this dependency since Maven does not grok that situation. Maybe could be fixed by making it optional in ssh-agent, not sure.) Short of updating the git dependency, it can be worked around easily: diff --git a/pom.xml b/pom.xml index 2d6ca7b..dd133c8 100644 --- a/pom.xml +++ b/pom.xml @@ -92,6 +92,12 @@ git 2.0 jar + + +org.apache.sshd +sshd-core + + org.jenkins-ci.plugins What would be useful, I think, is for maven-hpi-plugin to at least issue a notice in the build log when it is bundling something other than the plugin JAR in WEB-INF/lib/*.jar. Perhaps this should at logged at info level for direct (expressed) dependencies and warning level for indirect dependencies. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58604) Full Stage View only showing one
Title: Message Title Brian J Murrell commented on JENKINS-58604 Re: Full Stage View only showing one Perhaps related, because maybe the stage view is actually only even finding the one single build and not all of them, but the Average stage times: are wrong. They are always the same as the only stage being shown. That tells me that this is not a display problem but a data access problem and that the stage view is showing all of the builds that it can find and it's only finding one. But why? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.4520.1564577460283%40Atlassian.JIRA.
[JIRA] (JENKINS-58739) NPE for group projects MRs
Title: Message Title Parichay Barpanda started work on JENKINS-58739 Change By: Parichay Barpanda Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201040.1564575005000.4517.1564575061511%40Atlassian.JIRA.
[JIRA] (JENKINS-58739) NPE for group projects MRs
Title: Message Title Parichay Barpanda updated JENKINS-58739 Jenkins / JENKINS-58739 NPE for group projects MRs Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201040.1564575005000.4518.1564575061525%40Atlassian.JIRA.
[JIRA] (JENKINS-58739) NPE for group projects MRs
Title: Message Title Parichay Barpanda created an issue Jenkins / JENKINS-58739 NPE for group projects MRs Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-07-31 12:10 Labels: gsoc-2019 Priority: Minor Reporter: Parichay Barpanda This error is due to fetching of owner field which is only available in the api of user and not in case of group. Add Comment
[JIRA] (JENKINS-57955) Clean and sync incorrectly follows junction/directory symlinks on Windows
Title: Message Title Kieron Kierzo commented on JENKINS-57955 Re: Clean and sync incorrectly follows junction/directory symlinks on Windows This still is not fixed unfortunately Karl Wirth i'm on version 1.10.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199936.1560247579000.4515.1564571520278%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Rob Graham commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation We have also had an issue that looks extremely similar to this, still investigating but we did what Devin Nusbaum recommended and have possibly tracked it to the fix for this issue https://issues.jenkins-ci.org/browse/JENKINS-51057 in the sse-gateway-plugin which is a dependency of BlueOcean (a plugin I notice you also have Kyle Manna) I was able to accelarate thread creation by kicking off a very simple build multiple times and following progress with the BlueOcean UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.4510.1564571160208%40Atlassian.JIRA.
[JIRA] (JENKINS-58659) ZipExtractionInstaller should ignore timestamp if URL changes
Title: Message Title Anders Hammar updated an issue Jenkins / JENKINS-58659 ZipExtractionInstaller should ignore timestamp if URL changes Change By: Anders Hammar Background:We're using the Custom Tools Plugin to define misc custom tools in our Jenkins environment. Typically we use "Install automatically" and use the "Extract *.zip/*.tar.gz" installer to download the tool archive. The archive is typically hosted in our Nexus instance and we specify the exact version, like this:http://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.0/nifty-tool-1.0.0.tar.gz(In this example we're pointing at a Maven artifact, but it could be any URL.)When there is a new version of the tool we just update the ULR and Jenkins will update automatically.Problem:The problem is when we want to downgrade to an earlier version. For example, we havehttp://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.1/nifty-tool-1.0.1.tar.gzbut want to change back to the oldhttp://nexus.acme.org/content/repositories/releases/org/acme/jenkins/nifty-tool/1.0.0/nifty-tool-1.0.0.tar.gzIn this case the older version is not automatically installed, but we need to manually go in on every slave and remove the .timestamp file to force a downgrade.Suggested Improvement:The current behavior where only a newer archive is downloaded and installed is suitable when the URL doesn't change but one just updates the archive (overwriting the old file). But if the URL changes, the archive should be installed regardless of the timestamp. A different URL should always indicate a different archive.The change should be done in hudson. tool. FilePath.installIfNecessaryFrom(). The current javadoc says that if the timestamp of the archive doesn't match the local timestamp it is re-extracted, which is not fully correct. JENKINS-16215 changed this behavior so that the local timestamp value is use as if-modified-since header on the UrlConnection. So a downgrade to an earlier/older archive from an Http URL will never happen.A possible impl solution is to store the URL in the timestamp file and use that to check if the URL has changed. If it has, always re-extract regardless of the local timestamp. Add Comment
[JIRA] (JENKINS-58738) It is not possible to choose a job to trigger with Bitbucket Webhook
Title: Message Title Pawel Podbielski created an issue Jenkins / JENKINS-58738 It is not possible to choose a job to trigger with Bitbucket Webhook Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin, bitbucket-plugin Created: 2019-07-31 10:57 Environment: Jenkins 2.176 Bitbucket cloud Labels: plugin pipeline bitbucket bitbucket-branch-source-plugin bitbucket-plugin webhook multibranch Priority: Major Reporter: Pawel Podbielski I'm using Jenkins 2.176 with Bitbucket cloud and bitbucket-branch-source-plugin 2.4.0. Follow https://support.cloudbees.com/hc/en-us/articles/11553051-How-to-Trigger-Multibranch-Jobs-from-Bitbucket-Server- and everything works for me. But in my organization, I have often the situation that I have one Repository in bitbucket and e.g 2 Jenkins Multibranchpieline job. I don't want to trigger both project i.e when PR appear. Is there any way to specify which job should be triggered in such a case?
[JIRA] (JENKINS-37981) ec2-plugin makes Jenkins crash (Core dump attached)
Title: Message Title Raihaan Shouhell closed an issue as Cannot Reproduce Stale issue if this is still and issue please reopen and use a more updated version of the software Jenkins / JENKINS-37981 ec2-plugin makes Jenkins crash (Core dump attached) Change By: Raihaan Shouhell Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174124.1473164527000.4483.1564565400402%40Atlassian.JIRA.
[JIRA] (JENKINS-44065) Offline agents prevent on-demand provisioning
Title: Message Title Raihaan Shouhell resolved as Not A Defect It provisions up to the cap. The feature is a cost savings / managing feature allowing nodes to be marked offline and provisioning a new one only leads to having more than the cap nodes online at once Jenkins / JENKINS-44065 Offline agents prevent on-demand provisioning Change By: Raihaan Shouhell Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181605.149392629.4479.1564565341044%40Atlassian.JIRA.
[JIRA] (JENKINS-50523) setami doesn't update global config file
Title: Message Title Raihaan Shouhell resolved as Not A Defect Jenkins / JENKINS-50523 setami doesn't update global config file Change By: Raihaan Shouhell Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189588.152269220.4476.1564565220371%40Atlassian.JIRA.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Raihaan Shouhell resolved as Fixed The session auto refreshes if expired now Jenkins / JENKINS-48096 EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance Change By: Raihaan Shouhell Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186661.1511004471000.4468.1564565163482%40Atlassian.JIRA.
[JIRA] (JENKINS-56840) WinRM role in pipeline execution
Title: Message Title Raihaan Shouhell closed an issue as Not A Defect Jenkins / JENKINS-56840 WinRM role in pipeline execution Change By: Raihaan Shouhell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198500.1554149488000.4458.1564564080406%40Atlassian.JIRA.
[JIRA] (JENKINS-58279) Sonar gerrit plugin fails with ClassCastException on java 11
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-58279 Sonar gerrit plugin fails with ClassCastException on java 11 Change By: Baptiste Mathus Labels: java11 java11-compatibility triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200343.1561971112000.4455.1564561800278%40Atlassian.JIRA.
[JIRA] (JENKINS-58737) `Workspace missing` exception caught during Jenkins job run
Title: Message Title gowsalai m created an issue Jenkins / JENKINS-58737 `Workspace missing` exception caught during Jenkins job run Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-07-31 07:57 Environment: Linux Labels: pipeline Priority: Major Reporter: gowsalai m Getting "Exception caught: missing workspace /var/lib/jenkins-slave/workspace/SMOKE_TEST on Slave-LG-32" the exception, in scripted groovy pipeline execution. As part of the build stage, we are running a docker container which executes the test cases and we see that the test case terminates abruptly and logs which are copied to the workspace also lost. In our case, we want to explicitly clean up the workspace after copying the logs. In which cases the workspace gets cleaned up?. How to avoid this cleanup?. Add Comment
[JIRA] (JENKINS-58736) Accessing "/assets" without asset name throws a 500
Title: Message Title Wadeck Follonier created an issue Jenkins / JENKINS-58736 Accessing "/assets" without asset name throws a 500 Issue Type: Bug Assignee: Wadeck Follonier Components: core Created: 2019-07-31 07:23 Priority: Minor Reporter: Wadeck Follonier Initially reported by Vikas Gupta. When we do not pass an asset name (=empty), there is a charAt method calls that throws a StringIndexOutOfBoundsException. This results in the stack trace being displayed in the Oops page (=angry Jenkins). Add Comment
