[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Harry G. commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Oleg Nenashev any plans for getting this into LTS? We are still suffering and it's been a while since 2.223... Thanks a lot! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.22046.1588690020227%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Harry G. commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Jesse Glick and no matter if it is seen as reasonable use - it's just a pure regression if jobs working ever since suddenly need minutes or hours of loading time and screens are broken... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.22037.1588689960258%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep edited a comment on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since [https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins] mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21989.1588686840044%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21988.1588686780043%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep updated an issue Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: ickersep Summary: Error after update to 2.222.3 with pinned plugins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21987.1588686660065%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Change By:
ickersep
After upgrading to 2.222.3 (from 2. 2 204 . 04. 2) Jenkins fails to load properly and displays this error:{{java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer}} \ {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} \ {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} \ {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} \ {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} \ {{ at hudson.model.Queue._withLock(Queue.java:1399)}} \ {{ at hudson.model.Queue.withLock(Queue.java:1276)}} \ {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} \ {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} \ {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} \ {{ at hudson.model.Hudson.(Hudson.java:85)}} \ {{ at hudson.model.Hudson.(Hudson.java:81)}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}}{{Caused: hudson.util.HudsonFailedToLoad}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} {{$ java -version}}{{java version "1.8.0_201"}}{{Java(TM) SE Runtime Environment (build 1.8.0_201-b09)}}{{Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)}}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep created an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-05 13:23
Environment:
Ubuntu 18.04
Priority:
Major
Reporter:
ickersep
After upgrading to 2.222.3 (from 2.2.04.2) Jenkins fails to load properly and displays this error: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} {{ at hudson.model.Queue._withLock(Queue.java:1399)}} {{ at hudson.model.Queue.withLock(Queue.java:1276)}} {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} {{ at hudson.model.Hudson.(Hudson.java:85)}} {{ at hudson.model.Hudson.(Hudson.java:81)}} {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}} Caused: hudson.util.HudsonFailedToLoad {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} $ java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 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.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) 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.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 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.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) 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.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title akostadinov commented on JENKINS-48428 Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin I think it is related to using spaces in job name. This is using groovy file: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy" FATAL: command execution failed java.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 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.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) 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.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 more Build step 'Execute Groovy script' marked build as failure This is using script: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title akostadinov commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 Yeah, I can confirm that keeping the file name `log` even though it is compressed, keeps things working. Can't it just create a symlink log -> log.gz ? Jesse Glick, any plan to fix it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11723.1586958301070%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Change By: akostadinov Attachment: manage_roles.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.11165.1586890860375%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov updated an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Change By: akostadinov Attachment: manage_roles.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205774.1586890711000.11162.1586890802432%40Atlassian.JIRA.
[JIRA] (JENKINS-61902) Slave roles not respected with Authorize Project plugin
Title: Message Title akostadinov created an issue Jenkins / JENKINS-61902 Slave roles not respected with Authorize Project plugin Issue Type: Bug Assignee: ikedam Attachments: assign_roles.png, manage_roles.png Components: authorize-project-plugin Created: 2020-04-14 18:58 Priority: Critical Reporter: akostadinov Using Authorize Project plugin I have setting we have "Project Default build Authorization" set to "Run as User who Triggered Build". Then I have project roles letting particular users to run specific jobs. To allow said people to also build on the nodes I assign to them Slave role (see assign_roles.png). That Slave role is allowed to build on ".*" nodes (see manage_roles.png). But still when project is triggered from such a user, in the queue a message can be seen: > 'myusername' lacks permission to run on 'my-node-name-1' My workaround is to allow global Agent/Build permission to everybody but this is not ideal. Jenkins 2.190.3 Authorize Project 1.3.0 Role-based Authorization Strategy 2.13 Add Comment
[JIRA] (JENKINS-59979) Script Security: JCasC ScriptApproval does not apply until Jenkins reboot
Title: Message Title akostadinov commented on JENKINS-59979 Re: Script Security: JCasC ScriptApproval does not apply until Jenkins reboot For me it worked properly on Jenkins 2.190, casc plugin 1.36 and Script Security plugin 1.68. security: scriptApproval: approvedSignatures: - method java.net.URI getHost Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202784.1572381545000.9445.1586685600278%40Atlassian.JIRA.
[JIRA] (JENKINS-60965) Not able to build changes in multipipeline branch
Title: Message Title tiainpa commented on JENKINS-60965 Re: Not able to build changes in multipipeline branch Any update to this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204428.1580868959000.7999.1586341380125%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Harry G. commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Confirmed in 2.225 by setting up a test job with 10 runs and huuuge html descriptions: load time is fast again descriptions are truncated build parameters are not overlayed So this is resolved and can be closed! We are eagerly waiting for the LTS that brings it to our productive Jenkins. Thanks a lot Oleg Nenashev for driving it forward! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.5503.1583934780208%40Atlassian.JIRA.
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title davidkarlsen commented on JENKINS-60343 Re: java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax I'm seeing this as well in: JENKINS-61339 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.3586.1583796660183%40Atlassian.JIRA.
[JIRA] (JENKINS-61153) Agent hangs after startup when two jobs start simultaneously
Title: Message Title bjbishop commented on JENKINS-61153 Re: Agent hangs after startup when two jobs start simultaneously Voted! This issue bit us again today. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204683.1582133697000.978.1583530320245%40Atlassian.JIRA.
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Change By: davidkarlsen Environment: CloudBees Jenkins Enterprise 2.176.4.3-rollingk8s 1.13.9 kubernetes plugin 1.18.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204926.1583368328000.5983.1583368500185%40Atlassian.JIRA.
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Issue Type: Bug Assignee: Unassigned Attachments: buildPod.yaml Components: kubernetes-plugin Created: 2020-03-05 00:32 Environment: CloudBees Jenkins Enterprise 2.176.4.3-rolling k8s 1.13.9 Priority: Minor Reporter: davidkarlsen I have a buildPod as attached. Two things: 1) workspace path includes branch names etc - this makes it non-constant and hard to automate 2) I use subpath to get the correct folder mounted at /docker-entrypoint-initdb.d in the mysql container, but it actually has no content - even if the path is correct (same volume shows up in the node container). Add Comment
[JIRA] (JENKINS-61339) volumemount of workspace using subpath fails
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-61339 volumemount of workspace using subpath fails Change By: davidkarlsen Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204926.1583368328000.5982.1583368380251%40Atlassian.JIRA.
[JIRA] (JENKINS-60857) Wildcard certificates rejected by Winstone after Jetty update
Title: Message Title johmart updated an issue Jenkins / JENKINS-60857 Wildcard certificates rejected by Winstone after Jetty update Change By: johmart Environment: Jenkins 2.217 on CentOS 6.10Jenkins 2.204.3 LTS on Windows Server 2012 R2Wildcard-SSL-Certificate in Java-Keystore in PKCS12 format Jenkins 2.204.3 LTS on Ubuntu 18.04.4 LTS Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204231.1579860751000.2192.1583134620776%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Harry G. commented on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
Thanks a lot! For me at first this didn't work, as our description contains html tables and still breaks out in width. So addes max-with which then works for me for desktop (probably not perfect for mobile) td.build-row-cell > div > .build-link { max-height: 3em; max-width: 320px; overflow-y: hidden; } td.build-row-cell > div.desc { max-height: 5em; max-width: 320px; overflow-y: hidden; } What remains is the high loading time, in my example few minutes on FF and more on Chrome, forever on IE.
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.203294.1574852635000.7573.1581444720444%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Harry G. edited a comment on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
Thanks a lot! For me at first this didn't work, as our description contains html tables and still breaks out in width.So addes I added max-with which then works for me for desktop (probably not perfect for mobile){{td.build-row-cell > div > .build-link {}}{{ max-height: 3em;}}{{ max-width: 320px;}}{{ overflow-y: hidden;}}{{}}}{{td.build-row-cell > div.desc {}}{{ max-height: 5em;}}{{ max-width: 320px;}}{{ overflow-y: hidden;}}{{}}}What remains is the high loading time, in my example few minutes on FF and more on Chrome, forever on IE.
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.203294.1574852635000.7579.1581444720534%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen closed an issue as Not A Defect Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Status: Open Closed 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.203882.1578301543000.8491.1580335200392%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Indeed the old dependency check plugin shadowed the dependency track one and everything works as designed. (However the name and version parameters don't show in the pipeline-syntax ui - but that's unrelated). Thanks! 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.203882.1578301543000.8487.1580335140143%40Atlassian.JIRA.
[JIRA] (JENKINS-60849) pipeline build step, wait until build is scheduled
Title: Message Title akostadinov created an issue Jenkins / JENKINS-60849 pipeline build step, wait until build is scheduled Issue Type: New Feature Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2020-01-23 21:27 Labels: pipeline Priority: Major Reporter: akostadinov I need to easily navigate between upstream and downstream builds. Presently it is easy to navigate from downstream to upstream build because downstream build has upstream build as a cause. But navigating from upstream to downstream build is complicated when `wait: false` is used in the build step. When `wait` it is set to false, a build is triggered. But there is no way for the pipeline to know which build that was. When `wait` is false, the returned value is `org.codehaus.groovy.runtime.NullObject`. What will be useful is to have a parameter where build is triggered, then step waits until it has an id and returns only then. Or is there any other easy way to figure out triggered builds? Add Comment
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Attachment: Screenshot 2020-01-22 at 14.17.14.png 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.203882.1578301543000.3790.1579700760324%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Our config section looks a "little strange" - double up with settings. What could cause 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.203882.1578301543000.3792.1579700760352%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen updated an issue Jenkins / JENKINS-60643 Auto-create project for maven-based jobs Change By: davidkarlsen Environment: plugin version: 2.2.0jenkins: CloudBees Jenkins Enterprise 2.176.4.3-rolling 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.203882.1578301543000.8036.1579009320232%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen edited a comment on JENKINS-60643 Re: Auto-create project for maven-based jobs When I visit the /pipeline-syntax page, only these parameters are documented:dependencyTrackPublisher: Publish results to Dependency-TrackprojectIdType:StringartifactType:StringartifactTypeType:String installed plugin version: 2.2.0 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.203882.1578301543000.8033.1579009260248%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs When I visit the /pipeline-syntax page, only these parameters are documented: dependencyTrackPublisher: Publish results to Dependency-Track projectId Type:String artifact Type:String artifactType Type:String 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.203882.1578301543000.8030.1579009200138%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs I get: WorkflowScript: 102: Invalid parameter "projectVersion", did you mean "projectId"? @ line 102, column 121. .edb.fs.tac.jfr.srv:jfr-srv", projectVer ^ when running: dependencyTrackPublisher artifact: 'bom.xml', artifactType: 'bom', projectId: "com.edb.fs.tac.jfr.srv:jfr-srv", projectVersion: "10.1.0-SNAPSHOT" 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.203882.1578301543000.8027.1579009080198%40Atlassian.JIRA.
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title davidkarlsen commented on JENKINS-60643 Re: Auto-create project for maven-based jobs Hm - I get: Missing required parameter: "projectId" @ line 114, column 9. dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom' when running with: dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom' 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.203882.1578301543000.6893.1578869100196%40Atlassian.JIRA.
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador assigned an issue to leemeador Jenkins / JENKINS-60654 Add option to ignore bundled plugins Change By: leemeador Assignee: Natasha Stopa leemeador 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.203896.1578335562000.2939.1578335700325%40Atlassian.JIRA.
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60654 Add option to ignore bundled plugins Change By: leemeador URL: https://groups.google.com/forum/#!msg/jenkinsci-dev/8VnvgOVeVIs/9HG0JpfDDAAJ 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.203896.1578335562000.2937.1578335700290%40Atlassian.JIRA.
[JIRA] (JENKINS-60653) Don't treat requested and dependency plugins the same for download
Title: Message Title leemeador assigned an issue to leemeador Jenkins / JENKINS-60653 Don't treat requested and dependency plugins the same for download Change By: leemeador Assignee: Natasha Stopa leemeador 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.203895.1578334517000.2941.1578335700388%40Atlassian.JIRA.
[JIRA] (JENKINS-60654) Add option to ignore bundled plugins
Title: Message Title leemeador created an issue Jenkins / JENKINS-60654 Add option to ignore bundled plugins Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2020-01-06 18:32 Labels: plugin-manager Priority: Minor Reporter: leemeador The use of bundled plugins in today's Jenkins is not well documented. In trying to find information about their usage, via the developers' email list, it was suggested my best bet might be to ignore bundled plugins alltogether. The question I have is whether Jenkins today installs all bundled plugins at startup time. And that could be at initial startup (the very first time after an install) or at every time the war starts running. The impact relates to when the plugin installation manager cli tool (or the install plugins shell script) run. The next paragraph is next to impossible to understand because its so circular. If update manger cli (or script) runs after bundled plugins have been installed automatically, it will take into account the plugins that are installed and the bundled ones are irrelevant. Then plugins might get put back when bundled ones get installed on the next startup. If iupdate manager cli (or script) runs before bundled plugins are installed, and they really are being installed, then the plugins installed by the update manager (or script) will get replaced when the bundled ones get installed. Proposal It's not clear to me that there is any solution to choosing versions for this circular sort of situation. So what I propose is to allow the user to have the plugin manager cli consider bundled plugins by default or, optionally by command line option, ignore bundled plugins completely. Ignoring means not collecting the list of bundled plugins. They will not be
[JIRA] (JENKINS-60653) Don't treat requested and dependency plugins the same for download
Title: Message Title leemeador created an issue Jenkins / JENKINS-60653 Don't treat requested and dependency plugins the same for download Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2020-01-06 18:15 Labels: plugin-manager Priority: Minor Reporter: leemeador The install plugins shell script will ALWAYS download a plugin that is requested. It will only download a dependency plugin, one needed by a requested plugin recursively, if that plugin is not already installed in a version equal or greater than the one required. The current plugin installation manager cli tool treats requested and dependency plugins identically in this regard. Neither requested nor dependency plugins are downloaded if the plugin is already installed and the required version is less than the installed version for that plugin. Change to download a requested plugin even if it is already installed and use the version calculated already using requested and dependency versions. Note that the script will download a plugin more than once since it does version comparisons (for dependency plugins) as it finds the dependencies. The cli tool adds the plugin to the "download list" as it find the dependencies and downloads only once for each plugin. I don't think we should change the cli tool to download multiple times for a single plugin but here are the cases in which the install plugins script it will do that. I may not have thought of all the possible cases: 1) If a plugin is requested more than once, it will be downloaded multiple times. Only the last version downloaded (last version in the requested plugin list) will remain. Note that requesting plugins in txt files, yaml files and via command line option does not make it clear what order
[JIRA] (JENKINS-60643) Auto-create project for maven-based jobs
Title: Message Title
davidkarlsen created an issue
Jenkins / JENKINS-60643
Auto-create project for maven-based jobs
Issue Type:
Improvement
Assignee:
Steve Springett
Components:
dependency-track-plugin
Created:
2020-01-06 09:05
Labels:
ux usability pipeline auto
Priority:
Minor
Reporter:
davidkarlsen
Currently the plugin/pipeline configuration requires an existing project by defining projectId. I think it would be smoother to auto-create project, and read name/version from pom-files like: name: ${groupId}-${artifactId} version: ${version} then the entry-barrier would be lowered and it would be easier to adopt DT at larger scale.
Add Comment
[JIRA] (JENKINS-60214) Plugin installation manager does not work with other update sites
Title: Message Title leemeador commented on JENKINS-60214 Re: Plugin installation manager does not work with other update sites I found some bugs in the 1st PR after it was merged: 1) If you use the command line option to supply an experimental update center, it generates an incorrect URL from which to load the update-center.json. (There is an improper "update-center.actual.json" embedded it it.) 2) If you supply an update center that has a long URL, such as the version specific update centers at cloudbees, it does not generate the correct URL for loading plugin files. The old algorithm was just removing the last part of the URL and finding plugins below that path. 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.203187.1574190061000.1889.1577998440196%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Cloud Configuration Length Cap
Title: Message Title jwnmulder commented on JENKINS-60409 Re: Cloud Configuration Length Cap Running jenkins with -Dorg.eclipse.jetty.server.Request.maxFormContentSize=100" did resolve the issue 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.203466.1575915955000.13097.1576681500330%40Atlassian.JIRA.
[JIRA] (JENKINS-60265) Kubernetes plugin: java.net.MalformedURLException: unknown protocol
Title: Message Title davidkarlsen created an issue Jenkins / JENKINS-60265 Kubernetes plugin: java.net.MalformedURLException: unknown protocol Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-11-25 11:26 Environment: CloudBees Jenkins Enterprise 2.176.4.3-rolling Plugin version: 1.18.3 Priority: Minor Reporter: davidkarlsen When I click "test connection" from the master configuration page it works fine, but when scheduling a build I get: [Bitbucket] Build result notified java.net.MalformedURLException: unknown protocol: proxy.evry.com at java.net.URL.(URL.java:600) at java.net.URL.(URL.java:490) at java.net.URL.(URL.java:439) at io.fabric8.kubernetes.client.utils.HttpClientUtils.getProxyUrl(HttpClientUtils.java:212) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:145) at io.fabric8.kubernetes.client.utils.HttpClientUtils.createHttpClient(HttpClientUtils.java:63) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:51) at io.fabric8.kubernetes.client.BaseClient.(BaseClient.java:43) at io.fabric8.kubernetes.client.DefaultKubernetesClient.(DefaultKubernetesClient.java:84) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.parseFromYaml(PodTemplateUtils.java:517) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:554) at org.csanchez.jenkins.plugins.kubernetes.PodTemplateUtils.validateYamlContainerNames(PodTemplateUtils.java:544) at
[JIRA] (JENKINS-60214) Plugin installation manager does not work with other update sites
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with other update sites Change By: leemeador I've found that jenkins-plugin-manager-1.0.1 fails when not used against updates.jenkins.io. For example, the Cloudbees update center fails because that site has no update-center.actual.json file available there. There seems to be is an update-center.json for all of the update centers .The actual file has pure json content while the non-actual file has a wrapper around the json which is "updateCenter.post( ... json goes here ... );" Someone said that has to do with allowing the file to be more easily compatible with browsers use of _javascript_. I don't know if the best thing is to get Cloudbees to add the non-actual file or change the code to remove the wrapper text in in the non-actual file and use it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to
[JIRA] (JENKINS-60214) Plugin installation manager does not work with other update sites
Title: Message Title leemeador updated an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with other update sites Change By: leemeador Summary: Plugin installation manager does not work with Cloudbees other update site sites 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.203187.1574190061000.5363.1574368500073%40Atlassian.JIRA.
[JIRA] (JENKINS-60214) Plugin installation manager does not work with Cloudbees update site
Title: Message Title leemeador created an issue Jenkins / JENKINS-60214 Plugin installation manager does not work with Cloudbees update site Issue Type: Improvement Assignee: leemeador Components: plugin-installation-manager-tool Created: 2019-11-19 19:01 Labels: plugin-manager Priority: Minor Reporter: leemeador I've found that jenkins-plugin-manager-1.0.1 fails when used against the Cloudbees update center because that site has no update-center.actual.json file available there. There is an update-center.json. The actual file has pure json content while the non-actual file has a wrapper around the json "updateCenter.post( ... json goes here ... );" Someone said that has to do with allowing the file to be more easily compatible with browsers use of _javascript_. I don't know if the best thing is to get Cloudbees to add the non-actual file or change the code to remove the wrapper text in in the non-actual file and use it. Add Comment
[JIRA] (JENKINS-60202) Error when --Jenkins-update-manager value has trailing slash
Title: Message Title leemeador created an issue Jenkins / JENKINS-60202 Error when --Jenkins-update-manager value has trailing slash Issue Type: Improvement Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-11-18 17:36 Labels: plugin-manager Priority: Minor Reporter: leemeador Command line like this: java -jar jenkins-plugin-manager-1.0.1.jar -f plugins.txt --verbose --plugin-download-directory ~/plugins --no-download --list --war /usr/lib/jenkins/jenkins.war --jenkins-update-center https://jenkins-updates.cloudbees.com/ fails with stack trace containing java.io.FileNotFoundException: https://jenkins-updates.cloudbees.com//update-center.json Remove the trailing slash from the desired update center and it accepts the supplied update center. (This is the workaround) Add Comment
[JIRA] (JENKINS-56183) Attempt to (de-)serialize anonymous class: jenkins-core-2.150.3.jar
Title: Message Title leemeador commented on JENKINS-56183 Re: Attempt to (de-)serialize anonymous class: jenkins-core-2.150.3.jar We are on 2.164 and getting a similar message in the build agent log /computer//log Agent successfully connected and online Oct 31, 2019 9:57:07 AM [ssh] Connection established in 2.247 seconds. Oct 31, 2019 10:08:07 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class hudson.FilePath$2; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:13:39 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:13:40 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 31, 2019 10:14:57 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ 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
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio updated JENKINS-59745 Thanks, Thomas Draebing for reporting and also fixing this. Jenkins / JENKINS-59745 Error when trying to vote on label in multibranch pipeline (0.3.4) Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed Released As: gerrit-code-review-0.3.5 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio updated JENKINS-59745 Jenkins / JENKINS-59745 Error when trying to vote on label in multibranch pipeline (0.3.4) Change By: lucamilanesio 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.202464.1570786202000.187.1571909940930%40Atlassian.JIRA.
[JIRA] (JENKINS-59745) Error when trying to vote on label in multibranch pipeline (0.3.4)
Title: Message Title lucamilanesio started work on JENKINS-59745 Change By: lucamilanesio 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.202464.1570786202000.185.1571909940698%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Just FYI, looks fine again: https://jenkins.thetaphi.de/view/Lucene-Solr/rssAll 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.1155.1568190120224%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Thanks. The chAnge looks fine, but not tested. Just for completeness: the Jenkins URL was of course defined, otherwise other stuff would have been broken, too. 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.201604.1567266415000.6018.1567538640158%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path example: Should look like this: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201604.1567266415000.3578.1567267440050%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Here is an example: https://jenkins.thetaphi.de/view/Lucene-Solr/rssAll 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.201604.1567266415000.3577.1567267200129%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler created an issue Jenkins / JENKINS-59167 rssAll feed no longer contains Jenkins server URL, only incorrect relative path Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-08-31 15:46 Labels: regression Priority: Minor Reporter: Uwe Schindler Since you fixed JENKINS-58595, the rssAll feed no longer has the server name. Before this fix it was only showing the server HTTP address and no path in the href elements, now it's other way round. The HTTP-address is missing and only an (incorrect) relative link is shown. Not sure why it no longer shows full href. This still breaks our monitoring tools. Add Comment
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API
Title: Message Title davidkarlsen commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations when calling Kubernetes API what's strange also is that this only happens when declaring a yaml/yamlFile in a declarative pipeline, not if it is defined as a podTemplate on jenkins master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196186.1544542592000.2669.1567084620289%40Atlassian.JIRA.
[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade
Title: Message Title Uwe Schindler commented on JENKINS-58595 Re: rssAll feed doesn't have published field after 2.176.2 upgrade Is there any schedule for the fix? Apache Lucene's analysis of build failures is affected by this issue: https://lists.apache.org/thread.html/f6c2073a47b1d1cac9549129a522e439d23f598407a7d4ebb5c01036@%3Cdev.lucene.apache.org%3E 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.200752.1563783758000.4561.1566123015025%40Atlassian.JIRA.
[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade
Title: Message Title
Uwe Schindler edited a comment on JENKINS-58595
Re: rssAll feed doesn't have published field after 2.176.2 upgrade
This not only broked broke the dates, but also the {{}} elements are missing the entry path. It only shows Jenkin's base URLs, but the URL paths are missing. After looking at the PR, I think that should be fixed, too.
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.200752.1563783758000.1711.1565698200187%40Atlassian.JIRA.
[JIRA] (JENKINS-58595) rssAll feed doesn't have published field after 2.176.2 upgrade
Title: Message Title Uwe Schindler commented on JENKINS-58595 Re: rssAll feed doesn't have published field after 2.176.2 upgrade not only broked the dates, also the elements are missing the entry path. It only shows Jenkin's base URLs, but the URL paths are missing. After looking at the PR, I think that should be fixed, too. 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.200752.1563783758000.1706.1565698140206%40Atlassian.JIRA.
[JIRA] (JENKINS-58664) Add pipeline function to obscure credentials inFile
Title: Message Title
citizenkahn created an issue
Jenkins / JENKINS-58664
Add pipeline function to obscure credentials inFile
Issue Type:
New Feature
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2019-07-25 18:22
Priority:
Minor
Reporter:
citizenkahn
Problem The plugin hides secrets from the jenkins console but when a using complex tool chain the secrets may be stored in some tool's log and later published as build output. For example: the following uses ansible and a junit output callback to generate junit xml which will include secrets.
withCredentials([usernamePassword(credentialsId: 'my-test-user',
passwordVariable: 'USER',
usernameVariable: 'PASSWORD')]) {
withEnv([
"ANSIBLE_STDOUT_CALLBACK=junit",
"JUNIT_OUTPUT_DIR=${env.WORKSPACE}"
]) {
try {
ansiblePlaybook(
playbook:"ansible/playbooks/steps.yml",
extraVars: [
user: USER,
password: PASSWORD
]
)
} finally {
junit 'steps.*xml'
}
}
}
Recommendation Whereas
It seem unreasonable/impossible for the plugin to understand all tool chains
Only the binding plugin can properly know all secrets to hide
The addition of an exposed
[JIRA] (JENKINS-58564) Blue Ocean visualization should indicate parallel stages killed with fastFail
Title: Message Title leemeador created an issue Jenkins / JENKINS-58564 Blue Ocean visualization should indicate parallel stages killed with fastFail Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-07-18 22:12 Environment: 2.164 Priority: Minor Reporter: leemeador When you have a parallel section, and one of the parallel stages fails, and you have fail fast set, All the other parallel stages (that haven't completed) show a message "sending interrupt ..." in the log when they are killed. It would be nice if the visualization let it be easy to see which of the parallel stages died on their own and which were killed because a different on died. Let's say the little circle turns grey. Then you could easily see which one has the log you need to look at to see why it failed. I suspect there is some complexity if two stages fail around the same time and then tell each other to die. Maybe this case can't easily be handled. Even if not, it is my opinion that solving the case where only one failed on its own would be useful. Maybe its as simple as putting that grey circle up if the log for that parallel stage has a message about "sending interrupt..." though I doubt that's the real indicator. (If there were two to fail at the same time there would be too many grey circles.)
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Component/s: _unsorted Component/s: core 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.198931.1556177657000.1690.1562231820062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-5318) Allow default view at user level
Title: Message Title Dimitar Sakarov commented on JENKINS-5318 Re: Allow default view at user level +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.135407.1263928162000.58.1562081223828%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55788) Error when configuring Kubernetes Plugin v1.14.3
Title: Message Title liyatikal commented on JENKINS-55788 Re: Error when configuring Kubernetes Plugin v1.14.3 You need to create a role for cluster-admin for your user: kubectl create clusterrolebinding permissive-binding --clusterrole=cluster-admin --user=admin --user=kubelet --group=system:serviceaccounts 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.197177.1548456723000.10481.1561628880252%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Julien Carsique commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Baptiste Gaillard Thank you! However, this ticket is missing a stack trace for accuracy. The PR you submitted does not match our current install while we do have the same/similar issue. As I wrote in the PR thread: we're encountering the same issue symptom with lower plugin versions (see https://jira.nuxeo.com/browse/NXBT-2867). Our current versions are: CloudBees Jenkins Enterprise 2.164.3.2-rolling Git client plugin 2.7.6 Git plugin 3.9.3 SCM API Plugin 2.4.0 What is your stacktrace and reproduction case please? Is it the same? java.io.IOException: Cannot retrieve Git metadata for the build at org.jenkinsci.plugins.github.util.BuildDataHelper.getCommitSHA1(BuildDataHelper.java:87) at org.jenkinsci.plugins.github.status.sources.BuildDataRevisionShaSource.get(BuildDataRevisionShaSource.java:32) at org.jenkinsci.plugins.github.status.GitHubCommitStatusSetter.perform(GitHubCommitStatusSetter.java:135) Caused: org.jenkinsci.plugins.github.common.CombineErrorHandler$ErrorHandlingException at org.jenkinsci.plugins.github.common.CombineErrorHandler.handle(CombineErrorHandler.java:74) at org.jenkinsci.plugins.github.status.GitHubCommitStatusSetter.perform(GitHubCommitStatusSetter.java:164) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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) when running step([$class: 'GitHubCommitStatusSetter', reposSource: [$class: 'ManuallyEnteredRepositorySource', url: repos_url], contextSource: [$class: 'ManuallyEnteredCommitContextSource', context: '...'], statusResultSource: [$class: 'ConditionalStatusResultSource', results: [[$class: 'AnyBuildResult', message: status_msg.get(status), state: status)
[JIRA] (JENKINS-56457) Regression in timestamper 1.9: Start of maven plugins is logged with different format
Title: Message Title
leemeador commented on JENKINS-56457
Re: Regression in timestamper 1.9: Start of maven plugins is logged with different format
Seeing a similar issue. CB Jenkins 2.164, Timestamp plugin 1.9. If I go to build job and append /timestamps/?appendlog=HH:mm:ss.s it does not show elapsed time and uses the long format UTC time. It looks like this: [Pipeline] sh [2019-06-14T05:36:15.738Z] + env [2019-06-14T05:36:15.738Z] + sort [2019-06-14T05:36:15.738Z] BUILD_DISPLAY_NAME=#740 [2019-06-14T05:36:15.738Z] BUILD_ID=740 [2019-06-14T05:36:15.738Z] BUILD_NUMBER=740 Similar format appears in api calls:
String query = 'elapsed=HH:mm:ss.S=-50'
BufferedReader reader = hudson.plugins.timestamper.api.TimestamperAPI.get().read(build, query)
reader.withCloseable {
while ((line = reader.readLine()) != null) {
logLines.add(line)
println "LOG line read: " + line
}
}
Output is
[Pipeline] echo
11:13:48 LOG line read: [2019-06-14T04:01:28.865Z] Removing Streams/Foundation/SequenceConsumer@tmp/
[Pipeline] echo
11:13:48 LOG line read: [2019-06-14T04:01:28.865Z] Removing Streams/Foundation/SequenceConsumerHandler/build/
[Pipeline] echo
11:13:48 LOG line read: [2019-06-14T04:01:28.865Z] Removing Streams/Foundation/SequenceConsumerHandler/com.aa.lookahead.crew.sequence.parser/SequenceMarshaller/
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title lucamilanesio updated JENKINS-54722 Jenkins / JENKINS-54722 add backlink to gerrit code review to overview page for every build Change By: lucamilanesio 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.195524.1542709701000.865.1560526380749%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title lucamilanesio edited a comment on JENKINS-54722 Re: add backlink to gerrit code review to overview page for every build This has been done with [https://github.com/jenkinsci/gerrit-code-review-plugin/commit/ca8c2fdecc954a6f6becd4f55bc03c9ea413cafb].It's going to be release released in v0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195524.1542709701000.862.1560526380699%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title lucamilanesio updated JENKINS-54722 Jenkins / JENKINS-54722 add backlink to gerrit code review to overview page for every build Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195524.1542709701000.868.1560526380794%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54722) add backlink to gerrit code review to overview page for every build
Title: Message Title lucamilanesio commented on JENKINS-54722 Re: add backlink to gerrit code review to overview page for every build This has been done with https://github.com/jenkinsci/gerrit-code-review-plugin/commit/ca8c2fdecc954a6f6becd4f55bc03c9ea413cafb. It's going to be release in v0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195524.1542709701000.859.1560526380614%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55037) Allow configuration/filtering of detected Changes
Title: Message Title lucamilanesio commented on JENKINS-55037 Re: Allow configuration/filtering of detected Changes Yes, traits would be very easy to add and implement. One extra thing that could be useful is the propagation of the event JSON into the Pipeline, so that you could take it into account during validations. Example: a WIP change may need some validation but possibly NOT run the expensive integration tests, because the change it's going to get amended anyway. WDYT? 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.196079.1544027495000.856.1560526320099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55806) Authentication may be mandatory for the wbhooks to trigger builds
Title: Message Title lucamilanesio updated JENKINS-55806 Jenkins / JENKINS-55806 Authentication may be mandatory for the wbhooks to trigger builds Change By: lucamilanesio Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197196.1548610886000.854.1560526200198%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55806) Authentication may be mandatory for the wbhooks to trigger builds
Title: Message Title lucamilanesio started work on JENKINS-55806 Change By: lucamilanesio 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.197196.1548610886000.850.1560526140313%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55806) Authentication may be mandatory for the wbhooks to trigger builds
Title: Message Title lucamilanesio updated JENKINS-55806 Jenkins / JENKINS-55806 Authentication may be mandatory for the wbhooks to trigger builds Change By: lucamilanesio 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.197196.1548610886000.852.1560526140342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55806) Authentication may be mandatory for the wbhooks to trigger builds
Title: Message Title lucamilanesio commented on JENKINS-55806 Re: Authentication may be mandatory for the wbhooks to trigger builds Resolved with https://github.com/jenkinsci/gerrit-code-review-plugin/commit/e6c56b7cda00d54a31bdc74117dcbd5013fc2612. It's going to be included in v0.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197196.1548610886000.848.1560526140288%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56661) Add suppot to discover tags
Title: Message Title lucamilanesio commented on JENKINS-56661 Re: Add suppot to discover tags Good point 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.198295.155316814.842.1560526080228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57931) Add more information about gerrit change
Title: Message Title lucamilanesio commented on JENKINS-57931 Re: Add more information about gerrit change Have you checked at the variables currently available at https://github.com/jenkinsci/gerrit-code-review-plugin ? GERRIT_CHANGE_NUMBER: it's there GERRIT_PATCHSET_NUMBER: it's contained in the BRANCH_NAME GERRIT_PATCHSET_REVISION: it's the HEAD GERRIT_CHANGE_ID: this is contained in the commit footer of HEAD 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.199905.1560152908000.839.1560526020820%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57964) Documentation unclear for node() in scripted pipeline
Title: Message Title leemeador created an issue Jenkins / JENKINS-57964 Documentation unclear for node() in scripted pipeline Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2019-06-11 15:23 Environment: n/a Labels: documentation scripted node Priority: Minor Reporter: leemeador On this page in the documentation, it describes node(). https://jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#node-allocate-node Some examples of using the operators have no quotes. Some have quotes around the individual components (eg. 'linux' || 'osx'). None have the full correct syntax (eg. 'linux || osx'). If you use the form with the quotes around the individual components, you get an error saying that node() does not allow a boolean argument. Of course, we are used to the error messaages occasionally having no useful information. I suggest changing the documentation to NOT include the example with quotes around the components. (It says exactly this: For example, "osx (10.11)" || "Windows Server") I also suggest putting something up at the top that shows a full example with an _expression_ as well as a single agent's label.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title akostadinov commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Suraj Sharma, and if you have a multiline string that function works in a surprising way. It needs to be done on the lower level by the plugin to be reliable. I actually wonder if we can have a console wrapper that will capture whatever output produced inside. Like AnsiColor Plugin. It will not be able to differentiate stdin from stderr though. 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.183003.149756330.16582.1559221921649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title akostadinov commented on JENKINS-57642 Re: Wrong parameter type and squashing its content when trigger a job I'd like to add that this is a huge problem for the job rebuild plugin. Because it seems to respect the type given by the jms-messaging-plugin instead of config.xml. This removes new lines from text parameter so job can't be effectively rebuilt. P.S. maybe second part of description needs to be changed because removing of new lines happens with String rather than Text param. Or possibly I misread it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199573.1558615641000.10145.1558622820164%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title
magnayn commented on JENKINS-49332
Re: Jenkins unable to manage webhooks of Github organization
I don't know if this is of help, and it's a bit embarrasing that the most common usecase ("I have a github org, I want to build all the projects, and have webhooks added so this is efficient/fast") is so terrible UX-wise. But: In the project configuration, top level (github organization), you need to set up the organisation name (so it finds the right projects). You need some credentials to access github. It only lists "username/password" items on the list. However : for github if you're using a personal access token, the username is irrelevant. It really should offer 'secret' types in this list. I got ours to work by (re)creating a username/password credentials as username = ORG_NAME, password = personal_access_token. This might be of help.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188195.151753948.8417.1558516200985%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
edburns edited a comment on JENKINS-56890
Re: IOException: "cannot find current thread"
Jenkins version : h1. 2.164.2 Pipeline: Basic Steps 2.15 Pipeline: Build Step 2.9 Pipeline: Groovy 2.67 Pipeline: Nodes and Processes 2.30 I am seeing this also:{quote}java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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){quote}
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.198561.1554419267000.1727.1557767160477%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
edburns edited a comment on JENKINS-56890
Re: IOException: "cannot find current thread"
Jenkins version:h1. 2.164.2 I am seeing this also:{quote}java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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){quote}
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.198561.1554419267000.1703.1557766980547%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title edburns commented on JENKINS-56890 Re: IOException: "cannot find current thread" I am seeing this also: java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 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) 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.198561.1554419267000.1667.1557766680492%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57376) Add option so the job run will NOT update GitHub PR status
Title: Message Title leemeador created an issue Jenkins / JENKINS-57376 Add option so the job run will NOT update GitHub PR status Issue Type: Improvement Assignee: Kirill Merkushev Components: github-plugin Created: 2019-05-08 17:17 Environment: 2.164 Labels: git Priority: Minor Reporter: leemeador When I have a build job and a deploy job tied to the same Enterprise GitHub repo, commits run the build job via webhook and the deploy job is run by user clicking 'build' or run from some other job. The status goes back to GitHub when either job completes. Let's say I have a pull request on the repo. The build job (multibranch pipeline) runs and sends status successful which I've configured GitHub to enable merging the pull request due to successful build. Then, someone runs a deploy job (plain pipeline) and the deployment fails due to connectivity. (I'm making this up how I want.) That sends the status back to GitHub and the pull request can no longer be merged. The branches involved matter here. When the deploy job is tied to the same branch as the pull request, the problem definitely occurs. Other branch combination may or may not be a problem. It's been enough of a problem that I've just turned off the GitHub option that only allows a merge of the PR if the Jenkins builds succeed. This enhancement request is asking for an option either via pipeline code or a checkbox on the configure job page that indicates whether the job will return status to GitHub, or not. In pipeline code, it could either be code that disables the status being sent for this one job run OR it
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
twolfart updated an issue
Jenkins / JENKINS-57180
folder "parent" in workspace not browseable
Change By:
twolfart
A folder named "parent" in the workspace is not browseable for a pipeline job. Impact: "parent" is an often used folder name in Maven projects. Example pipeline:{code}node { deleteDir() sh ("mkdir -p parent/foo") sh ("mkdir -p bar/parent") sh ("mkdir parent-foo")}{code}Note: {{deleteDir()}} is only needed to re-run the job. It is not needed for the behaviour to appear.This will create a workspace with the following folders: !workspace-example-folders.PNG! Impact: "parent" is an often used folder name in Maven projects. h3. Works as expected (i.e. shows the folder):* click on a job execution* click on workspaces* click on the listed workspace** click on folder bar - shows contents** click on folder bar/parent - shows contents** click on folder parent-foo - shows contentsh3. Does not work as expected:* click on a job execution* click on workspaces* click on the listed workspace** click on folder parent - shows the parent node step !workspace-click-on-parent.PNG|thumbnail! ** click on folder parent/foo - results in 404 !workspace-click-on-parent-subfolder.PNG|thumbnail! h3. Workarounds* use subfolder for project (i.e. project-name/parent)* rename "parent"
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach:{code:groovy}timeout(10) {waitUntil {script {def r = sh returnStatus: true, script: 'command'return r == 0}}}{code}This will retry for up to 10 minutes. ` {{ waitUntil ` }} automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach:{code:groovy}timeout(10) {waitUntil {script {def r = sh returnStatus: true, script: 'command'return r == 0}}}{code}This will retry for up to 10 minutes. `waitUntil` automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach:{ { code:groovy} timeout(10) {waitUntil {script {def r = sh returnStatus: true, script: 'command'return r == 0}}} {code } } This will retry for up to 10 minutes. `waitUntil` automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach:{{ timeout(10) {waitUntil {script {def r = sh returnStatus: true, script: 'command'return r == 0}}} }}This will retry for up to 10 minutes. `waitUntil` automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn edited a comment on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach: {{ timeout(10) {waitUntil {script {def r = sh returnStatus: true, script: 'command'return r == 0}}} }} This will retry for up to 10 minutes. `waitUntil` automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
asgeirn commented on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
Here's a different approach: timeout(10) { waitUntil { script { def r = sh returnStatus: true, script: 'command' return r == 0 } } } This will retry for up to 10 minutes. `waitUntil` automatically adds delays between the attempts.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54416) Configure Systems Page Showing Oops Page. Unable to Save
Title: Message Title gilesbaxter updated JENKINS-54416 Jenkins / JENKINS-54416 Configure Systems Page Showing Oops Page. Unable to Save Change By: gilesbaxter Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54416) Configure Systems Page Showing Oops Page. Unable to Save
Title: Message Title gilesbaxter updated JENKINS-54416 Jenkins / JENKINS-54416 Configure Systems Page Showing Oops Page. Unable to Save Change By: gilesbaxter Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title asgeirn commented on JENKINS-57206 Re: Support draft pull requests from GitHub It would appear the issue is related to the GitHub webhook - after the scheduled repository scan, the PR was detected. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title carlspring edited a comment on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 Hi, Thanks for looking into this for us! Is there any ETA for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57200) Can't access builds in BlueOcean after updating to 1.15.0
Title: Message Title carlspring commented on JENKINS-57200 Re: Can't access builds in BlueOcean after updating to 1.15.0 Hi, Thanks for looking into this for us! Is there any ETA for this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
