[JIRA] (JENKINS-54005) Trying to unexport an object that's already unexported (is back)
Title: Message Title Federico Naum created an issue Jenkins / JENKINS-54005 Trying to unexport an object that's already unexported (is back) Issue Type: Bug Assignee: Jeff Thompson Attachments: log.log Components: remoting, remoting-kafka-plugin Created: 2018-10-11 05:52 Environment: Jenkins 2.141 -(remoting 3.26) kafka-remoting-plugin compiled against remoting 3.26 Priority: Minor Reporter: Federico Naum I thought this was fixed in remoting 3.26 under https://issues.jenkins-ci.org/browse/JENKINS-42533 But today I got this stack trace again when one of my kafka nodes was idle (not running any job) just out of the blue it got INFO: ConnectedINFO: Connected[Channel reader thread: planet] INFO org.apache.kafka.clients.Metadata - Cluster ID: isxhuhJhRGGNrKyNAeNZHg[Channel reader thread: planet] INFO org.apache.kafka.clients.consumer.internals.AbstractCoordinator - [Consumer clientId=consumer-2, groupId=jenkinssecure.8081.planet-id] Discovered group coordinator sydjenkikafka01.al.com.au:9092 (id: 2147483647 rack: null)[kafka-producer-network-thread | producer-2] INFO org.apache.kafka.clients.Metadata - Cluster ID: isxhuhJhRGGNrKyNAeNZHgOct 11, 2018 3:42:18 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class net.bull.javamelody.RemoteCallHelper$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ Oct 11,
[JIRA] (JENKINS-54004) Stage graph in Blue Ocean not showing all stages for large workflows (redux)
Title: Message Title Josh McDonald closed an issue as Duplicate Seems after creating this I regained the ability to comment on the original. I've got no idea why and don't want to spend time on figuring it out. Jenkins / JENKINS-54004 Stage graph in Blue Ocean not showing all stages for large workflows (redux) Change By: Josh McDonald Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53900) Stage graph in Blue Ocean not showing all stages for large workflows
Title: Message Title Josh McDonald commented on JENKINS-53900 Re: Stage graph in Blue Ocean not showing all stages for large workflows (meta: apparently I can comment here again. Weird.) I don't think this is related to paging, as this was causing issues in the past (JENKINS-41205) and the solution was to set the limit to 10,000 nodes. Not sure what else could be causing it, without a pipeline I can run that demonstrates the issue Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42161) Jenkins builds all jobs when user intends for one
Title: Message Title Daniel Alejandro Hernández commented on JENKINS-42161 Re: Jenkins builds all jobs when user intends for one Is there a way to do not to build the jobs for the first time or at least to match the branch as well? I am having serious issues with this since first time all jobs are been triggered and in our infrastructure the workspaces are allocated in a Docker container which this can be deleted once the container does not exists the rest which is critical is in AWS EBS (Jenkins configuration, jobs definition and so on). Our jobs are triggered using regular _expression_ for the tags which starts by ":" , right? is quite complex our process but fully automatic the CI/CD until production but I found weakness in this plugin by not matching correctly the branch or what ever pattern we set in addition to the GIT URL. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54004) Stage graph in Blue Ocean not showing all stages for large workflows (redux)
Title: Message Title Josh McDonald created an issue Jenkins / JENKINS-54004 Stage graph in Blue Ocean not showing all stages for large workflows (redux) Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-10-11 05:25 Priority: Critical Reporter: Josh McDonald Creating a new issue to follow-up from JENKINS-53900 because there's something weird going on with Jira that stops me from replying to that issue in particular. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-54003) Removing a kafka node and recreating a node with the same name again fails
Title: Message Title Federico Naum created an issue Jenkins / JENKINS-54003 Removing a kafka node and recreating a node with the same name again fails Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-10-11 04:46 Environment: Jenkins 2.141 remoting-kafka-plugin-1.1.0 Priority: Minor Reporter: Federico Naum After removing a Kafka agent from the nodes page and adding a node with the same name fails with: error in launching a slave. This is probably a bug in Jenkins.error in launching a slave. This is probably a bug in Jenkins.hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown: Command Close created at at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1038) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:1271) at hudson.remoting.Channel$1.handle(Channel.java:565) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:87) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to overtake at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.Request.call(Request.java:202) at hudson.remoting.Channel.call(Channel.java:954) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:622) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:465) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher$1.call(KafkaComputerLauncher.java:88) at io.jenkins.plugins.remotingkafka.KafkaComputerLauncher$1.call(KafkaComputerLauncher.java:74) at
[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
Title: Message Title
David Grochowski edited a comment on JENKINS-53881
Re: aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
I'm using the plugin in a declarative pipeline in a multibranch job.Invocation looks like:steps {withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') {sh "run-tests.sh"}}The (scrubbed) console output:Pull request #XX updated04:03:18 Connecting to https://api.github.com using XX/**Obtained Jenkinsfile from XXRunning in Durability level: MAX_SURVIVABILITYorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 179: Missing required parameter: "namePrefixes" @ line 179, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^WorkflowScript: 192: Missing required parameter: "namePrefixes" @ line 192, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^WorkflowScript: 202: Missing required parameter: "namePrefixes" @ line 202, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^3 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE
Add Comment
[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
Title: Message Title
David Grochowski edited a comment on JENKINS-53881
Re: aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
I'm using the plugin in a declarative pipeline in a multibranch job. Invocation looks like:steps {withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') {sh "run-tests.sh"}} The (scrubbed) console output:Pull request #XX updated04:03:18 Connecting to https://api.github.com using XX/**Obtained Jenkinsfile from XXRunning in Durability level: MAX_SURVIVABILITYorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 179: Missing required parameter: "namePrefixes" @ line 179, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^WorkflowScript: 192: Missing required parameter: "namePrefixes" @ line 192, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^WorkflowScript: 202: Missing required parameter: "namePrefixes" @ line 202, column 17. withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/XX/XX', recursive: true, regionName: 'us-east-1') { ^3 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE
Add Comment
[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
Title: Message Title
David Grochowski edited a comment on JENKINS-53881
Re: aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
I'm using the plugin in a declarative pipeline in a multibranch job. The (scrubbed) console output: {{ Pull request #XX updated }} {{ 04:03:18 Connecting to https://api.github.com using XX/** }} {{ Obtained Jenkinsfile from }}{{ XX }}{{}} {{ Running in Durability level: MAX_SURVIVABILITY }} {{ org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: }} {{ WorkflowScript: 179: Missing required parameter: "namePrefixes" @ line 179, column 17. }} {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/ }}{{ XX }}{{ /XX ', recursive: true, regionName: 'us-east-1') { }} {{ ^ }}{{ WorkflowScript: 192: Missing required parameter: "namePrefixes" @ line 192, column 17. }} {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/ }}{{ XX }}{{ /XX ', recursive: true, regionName: 'us-east-1') { }} {{ ^ }}{{ WorkflowScript: 202: Missing required parameter: "namePrefixes" @ line 202, column 17. }} {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/ }}{{ XX }}{{ /XX ', recursive: true, regionName: 'us-east-1') { }} {{ ^ }}{{ 3 errors }}{{ at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) }} {{ at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) }} {{ at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) }} {{ at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) }} {{ at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) }} {{ at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) }} {{ at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) }} {{ at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) }} {{ at groovy.lang.GroovyShell.parse(GroovyShell.java:700) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560) }} {{ at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521) }} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330) }} {{ at hudson.model.ResourceController.execute(ResourceController.java:97) }} {{ at hudson.model.Executor.run(Executor.java:429) }} {{ Finished: FAILURE }}
Add Comment
[JIRA] (JENKINS-53881) aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
Title: Message Title
David Grochowski commented on JENKINS-53881
Re: aws-parameter-store-plugin 1.2.0 is not backwards compatible with 1.1.0 in pipeline jobs
I'm using the plugin in a declarative pipeline in a multibranch job. The (scrubbed) console output: Pull request #XX updated 04:03:18 Connecting to https://api.github.com using XX/** Obtained Jenkinsfile from }}{{XX{{}} Running in Durability level: MAX_SURVIVABILITY org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 179: Missing required parameter: "namePrefixes" @ line 179, column 17. {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/}}XX', recursive: true, regionName: 'us-east-1') { {{ ^}}WorkflowScript: 192: Missing required parameter: "namePrefixes" @ line 192, column 17. {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/}}XX', recursive: true, regionName: 'us-east-1') { {{ ^}}WorkflowScript: 202: Missing required parameter: "namePrefixes" @ line 202, column 17. {{ withAWSParameterStore(credentialsId: '', naming: 'basename', path: '/}}XX', recursive: true, regionName: 'us-east-1') { {{ ^}}3 errorsat org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) {{ at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)}} {{ at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)}} {{ at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)}} {{ at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)}} {{ at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)}} {{ at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)}} {{ at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)}} {{ at groovy.lang.GroovyShell.parse(GroovyShell.java:700)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:131)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:125)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:560)}} {{ at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:521)}} {{ at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:330)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:429)}} Finished: FAILURE
Add Comment
[JIRA] (JENKINS-54002) Jenkins shows kafka agent as connected even when the "Remote root directory" is not accessible
Title: Message Title Federico Naum created an issue Jenkins / JENKINS-54002 Jenkins shows kafka agent as connected even when the "Remote root directory" is not accessible Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-10-11 03:56 Environment: Jenkins 2.141 remoting-kafka-plugin-1.1.0 Priority: Minor Reporter: Federico Naum Jenkins shows kafka agent as connected even when the "Remote root directory" is not accessible As a result, jobs get assigned to that node and jobs fail with: // Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to overtakeAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to overtake at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at hudson.FilePath.mkdirs(FilePath.java:1244) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:154) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:198) at org.jenkinsci.plugins.durabletask.BourneShellScript$ShellController.(BourneShellScript.java:190) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:111) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:86) at
[JIRA] (JENKINS-53000) Add support for GCP templates
Title: Message Title Zhan Su commented on JENKINS-53000 Re: Add support for GCP templates This is going to be really useful. In particular I am looking to using local SSD, which seems a perfect match with short-lived preemptive slaves which does a lot of local I/O. And it definitely makes sense to add it through template. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-54001) Jenkins master does not reflect kafka agent disconnection
Title: Message Title Federico Naum created an issue Jenkins / JENKINS-54001 Jenkins master does not reflect kafka agent disconnection Issue Type: Bug Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-10-11 00:55 Environment: Jenkins 2.141 - kafka-plugin-1.1.0 Priority: Minor Reporter: Federico Naum When the agent remoting process on a kafka node dies (or is manually killed), Jenkins master does not show that on the nodes page Only once a job is trying to run in that agent, it will get marked as offline. To repro this, connect an agent using kafka, then kill the process in the node and check the nodes page (http://jenkins:8081/computer/), you'll see the node is still online. Seems like a heartbeat/keepalive mechanism will be needed, but not sure if this is possible. with the current architecture. Add Comment
[JIRA] (JENKINS-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus commented on JENKINS-53964 Re: Drop uuid_checksum_uniq unique key constraint PR merged, new backend image built, now in the deployment pipe, almost there but not yet, waiting on https://github.com/jenkins-infra/jenkins-infra/pull/1157 to be merged and then pushed to the production branch. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus commented on JENKINS-53964 Re: Drop uuid_checksum_uniq unique key constraint Closing this as I'll followup anyway with that open PR, and reopen if something is wrong. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53964) Drop uuid_checksum_uniq unique key constraint
Title: Message Title Baptiste Mathus updated JENKINS-53964 Jenkins / JENKINS-53964 Drop uuid_checksum_uniq unique key constraint Change By: Baptiste Mathus Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52123) Adjust sse-gateway to the now configurable location for tasks logging
Title: Message Title Baptiste Mathus commented on JENKINS-52123 Re: Adjust sse-gateway to the now configurable location for tasks logging Just filed https://github.com/jenkins-infra/evergreen/pull/319/ to reenable the test that was disabled waiting for sse-gateway:1.16 to land into Evergreen. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53965) ConsoleLog is missing build output
Title: Message Title Jesse Glick resolved as Incomplete OK? I am not sure what the effect of using things like /dev/stderr would be, as the durable task wrapper script effectively does something like sh your-script > some-log-file.txt 2>&1 Jenkins / JENKINS-53965 ConsoleLog is missing build output Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-53983) Per-instance tainting still serves the tainted level if you're "coming from" a lower level
Title: Message Title Baptiste Mathus updated JENKINS-53983 Jenkins / JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title
Brian Moyle edited a comment on JENKINS-53965
Re: ConsoleLog is missing build output
[~jglick] thanks - I've updated the original code for readability.I've also convinced myself this is not a Jenkins issue.In the qt5base 5.6.2 configure script, the "-v" option seems to be causing problems... specifically, it appears the following code in the configure script might be the culprit:{code:none}unset tty[ "$OPT_VERBOSE" = "yes" ] && tty=/dev/stderreval "`LC_ALL=C $TEST_COMPILER $SYSROOT_FLAG $TEST_COMPILER_CXXFLAGS -xc++ -E -v - < /dev/null 2>&1 > /dev/null | $AWK "$awkprog" | tee $tty`"unset tty{code}If I remove the "-v" option, the problem goes away. I suspect the "tee /dev/stderr" in verbose mode causes an issue that looks similar to calling "ftruncate()" on stdout, which has the side-effect of resetting the log to the beginning of the file.For what it's worth, my groovy build invocation groovy is essentially:{code:none}build_all.sh{code}If, rather than remove the "-v" option from configure, I instead change my pipeline groovy invocation to look like this:{code:none}build_all.sh 2>&1 | cat{code}the issue also goes away (having it go through a pipe seems to prevent stdout from getting reset as well).Feel free to close this as a non-issue.Thanks for the 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title
Brian Moyle edited a comment on JENKINS-53965
Re: ConsoleLog is missing build output
[~jglick] thanks - I've updated the original code for readability.I've also convinced myself this is not a Jenkins issue.In the qt5base 5.6.2 configure script, the "-v" option seems to be causing problems... specifically, it appears the following code in the configure script might be the culprit:{code:none}unset tty[ "$OPT_VERBOSE" = "yes" ] && tty=/dev/stderreval "`LC_ALL=C $TEST_COMPILER $SYSROOT_FLAG $TEST_COMPILER_CXXFLAGS -xc++ -E -v - < /dev/null 2>&1 > /dev/null | $AWK "$awkprog" | tee $tty`"unset tty{code}If I remove the "-v" option, the problem goes away. I suspect the "tee /dev/stderr" in verbose mode causes an issue that looks is similar to calling "ftruncate()" on stdout, which has the side-effect of resetting the log to the beginning of the file.For what it's worth, my build invocation groovy is essentially:{code:none}build_all.sh{code}If, rather than remove the "-v" option from configure, I instead change my pipeline invocation to look like this:{code:none}build_all.sh 2>&1 | cat{code}the issue also goes away (having it go through a pipe seems to prevent stdout from getting reset as well).Feel free to close this as a non-issue.Thanks for the 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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title Brian Moyle commented on JENKINS-53965 Re: ConsoleLog is missing build output Jesse Glick thanks - I've updated the original code for readability. I've also convinced myself this is not a Jenkins issue. In the qt5base 5.6.2 configure script, the "-v" option seems to be causing problems... specifically, it appears the following code in the configure script might be the culprit: unset tty [ "$OPT_VERBOSE" = "yes" ] && tty=/dev/stderr eval "`LC_ALL=C $TEST_COMPILER $SYSROOT_FLAG $TEST_COMPILER_CXXFLAGS -xc++ -E -v - < /dev/null 2>&1 > /dev/null | $AWK "$awkprog" | tee $tty`" unset tty If I remove the "-v" option, the problem goes away. I suspect the "tee /dev/stderr" in verbose mode causes an issue that looks is similar to calling "ftruncate()" on stdout, which has the side-effect of resetting the log to the beginning of the file. For what it's worth, my build invocation groovy is essentially: build_all.sh If, rather than remove the "-v" option from configure, I instead change my pipeline invocation to look like this: build_all.sh 2>&1 | cat the issue also goes away (having it go through a pipe seems to prevent stdout from getting reset as well). Feel free to close this as a non-issue. Thanks for the help! Add Comment This message
[JIRA] (JENKINS-53965) ConsoleLog is missing build output
Title: Message Title
Brian Moyle updated an issue
Jenkins / JENKINS-53965
ConsoleLog is missing build output
Change By:
Brian Moyle
I have run into an issue with the Console Output often failing to include build failure messages, due to the output being truncated.In an attempt to discover why our builds were failing, I discovered the transient durable jenkins-log.txt file(s) - they appear to be removed upon completion of the build.(e.g., ... /project@tmp/durable-472431c5/jenkins-log.txt)I also noticed I could tail the file to eventually find failures in our build, and in the process, I realized this file seems to be getting reset/truncated, and the remaining log messages appear to start from the beginning of the file. I'm assuming this may explain the lack of progress in the Console Output, which stops progressing beyond this point, and is often missing important build failure information.I don't know what causes it, but I have tried a "tail -F jenkins-log.txt >> saved_log.txt 2>&1" on the file, and see something similar to: { { code:none} [... snip ...] }} {{ >>> qt5base 5.6.2 Configuring }} {{ /usr/bin/install -m 0644 -D package/qt5/qt5base//qmake.conf /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qmake.conf }} {{ /usr/bin/install -m 0644 -D package/qt5/qt5base//qplatformdefs.h /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2/mkspecs/devices/linux-buildroot-g++/qplatformdefs.h }} {{ (cd /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/build/qt5base-5.6.2; PATH="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/sbin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin:/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/snap/bin" PKG_CONFIG="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/pkg-config" PKG_CONFIG_LIBDIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot/usr/lib/pkgconfig" PKG_CONFIG_SYSROOT_DIR="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot" MAKEFLAGS=" – -- V=1 -j29" ./configure -v -prefix /usr -hostprefix /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr -headerdir /usr/include/qt5 -sysroot /var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/arm-buildroot-linux-gnueabihf/sysroot -plugindir /usr/lib/qt/plugins -examplesdir /usr/lib/qt/examples -no-rpath -nomake tests -device buildroot -device-option CROSS_COMPILE="/var/lib/jenkins/workspace/top_project/sub_project/ver_4.7.3/output/host/usr/bin/arm-cortexa9_neon-linux-gnueabihf-" -device-option BR_COMPILER_CFLAGS="-D_LARGEFILE_SOURCE
[JIRA] (JENKINS-54000) Support for Taglist Maven Plugin
Title: Message Title Jason Faust created an issue Jenkins / JENKINS-54000 Support for Taglist Maven Plugin Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-10-10 21:49 Priority: Minor Reporter: Jason Faust Support for the Taglist Maven Plugin would be convent. https://www.mojohaus.org/taglist-maven-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-48484) gerrit trigger doesn't match files/paths on clean merge
Title: Message Title Thierry Barthelemy commented on JENKINS-48484 Re: gerrit trigger doesn't match files/paths on clean merge Hi, Is there any update on this bug? I also encountered that issue when setting Paths in the Gerrit Trigger part and having a clean merge (with no file listed in the gerrit File section) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53999) Set default choices based on query string parameters.
Title: Message Title ian ursino created an issue Jenkins / JENKINS-53999 Set default choices based on query string parameters. Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2018-10-10 21:05 Priority: Minor Reporter: ian ursino Functionality like in the build with parameters plugin where choices can be defaulted (in this case contingent on their existence) using query string parameters. see: https://wiki.jenkins.io/display/JENKINS/Build+With+Parameters+Plugin Add Comment
[JIRA] (JENKINS-53983) Per-instance tainting still serves the tainted level if you're "coming from" a lower level
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level Change By: Baptiste Mathus _NOTE: I've added a [reproducer test case|https://github.com/jenkins-infra/evergreen/pull/316/commits/bf5a61c5312642efecb3007cf61a8903d5e59c08], and this issue matches my experience from testing it locally when I see the rollback work, and then still re-upgrade to the tainted level after going away from it previously. But I'm still not 100% sure of the diagnosis, so keep this in mind below._h3. Problem statementWhen an instance taints a given update level (after a failure to upgrade), then it correctly gets the previous non tainted UL.But then, when asking the backend again, passing the previous UL as parameter (i.e. the good one, the one *before* the just tainted one), then the backend will still serve an answer to upgrade to the tainted level. From a user standpoint, this will surface through the following behavior: * Imagine we are on UL 50.* UL51 is pushed* Instance updates to UL51 and is unable to restart* Instance informs the backend UL51 was a failure (aka _taints_ it)* Instance goes back to UL50 from UL51* Instance updates to UL51, fails...* Loop back to a few lines above, and so on h3. Expected behaviorOnce _per-instance tainted_, a given UL should never be proposed again to a given instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53983) Per-instance tainting still serves the tainted level if you're "coming from" a lower level
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level Change By: Baptiste Mathus _NOTE: I've added a [reproducer test case|https://github.com/jenkins-infra/evergreen/pull/316/commits/bf5a61c5312642efecb3007cf61a8903d5e59c08], and this issue matches my experience from testing it locally when I see the rollback work, and then still re-upgrade to the tainted level after going away from it previously. But I'm still not 100% sure of the diagnosis, so keep this in mind below._h3. Problem statementWhen an instance taints a given update level (after a failure to upgrade), then it correctly gets the previous non tainted UL.But then, when asking the backend again, passing the previous UL as parameter (i.e. the good one, the one *before* the just tainted one), then the backend will still serve an answer to upgrade to the tainted level.From a user standpoint, this will surface through the following behavior:* Imagine we are on UL 50.* UL51 is pushed* Instance updates to UL51 and is unable to restart* Instance informs the backend UL51 was a failure (aka _taints_ it)* Instance goes back to UL50 from UL51* Instance updates to UL51, fails...* Loop back to a few lines above, and so on . I.e. the instance will do UL50->UL51->UL50->UL51, etc. h3. Expected behaviorOnce _per-instance tainted_, a given UL should never be proposed again to a given instance. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-53998) Warning logged on startup
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-53998 Warning logged on startup Issue Type: Bug Assignee: Stefan Brausch Components: core, jobconfighistory-plugin Created: 2018-10-10 20:26 Environment: 2.138.2 Priority: Minor Reporter: Daniel Beck 2.138.2 backported JEP-214/Uplink telemetry, and with it, an extension that calls save from its constructor. When Job Config History is installed, that results in the following warning being logged on the first startup during the save call: https://gist.github.com/daniel-beck/140e11878479d5c2eef882f54c4ed33d It's not obviously a bad idea to call save there (IMO), but there probably should be a check in JCH to not do elaborate processing during startup. Unsure. Add Comment
[JIRA] (JENKINS-53997) TFS plugin should have option to delete workspace at end of job
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-53997 TFS plugin should have option to delete workspace at end of job Issue Type: Improvement Assignee: redsolo Components: tfs-plugin, ws-cleanup-plugin Created: 2018-10-10 20:11 Environment: Jenkins-2.121.3 tfs-plugin-5.133.0 ws-cleanup-plugin-0.34 Priority: Minor Reporter: Ian Williams We are using tfs-plugin in conjunction with ws-cleanup-plugin as a post-build-step. The ws-cleanup plugin deletes the Jenkins workspace at the end of the job. However, TFS retains the tfvc workspace on back-end side and entry remains in the Cache/VersionControl.config There should be a Jenkins post-build step option to delete the TFVC workspace. This is cleaner than extending the ws-cleanup plugin. Add Comment
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-46507
Re: Parallel Pipeline random java.lang.InterruptedException
[~chamshoff] Without seeing your Jenkinsfile, it's hard to say, but my guess would be that you are hitting [the 5 minute timeout here|https://github.com/jenkinsci/workflow-cps-plugin/blob/a67af1db1eb7b83c287243547b8c6b0d452fd3c3/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThread.java#L178] because your code is waiting for a network response or similar in a method that doesn't respond to being interrupted (so it doesn't fail until the next step is invoked which notices that the thread was interrupted, assuming your stack trace is original to the OP's). I would highly recommend not making direct HTTP calls in your Jenkinsfile /Shared Library even if it seems like it works fine in some cases. You can create a bash script that does whatever you want (curl, java -jar yourRestClient.jar, etc.) and call that script using the {{sh}} or {{bat}} steps which run asynchronously and are not subject to a 5 minute timeout.[~ncrmnt] Based on those logs, there does appear to be a network issue with the remoting layer involved as well. I will check through the build files you sent to see if they give any indication of a root cause that we can address.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Devin Nusbaum commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Christoph Amshoff Without seeing your Jenkinsfile, it's hard to say, but my guess would be that you are hitting the 5 minute timeout here because your code is waiting for a network response or similar in a method that doesn't respond to being interrupted (so it doesn't fail until the next step is invoked which notices that the thread was interrupted, assuming your stack trace is original to the OP's). I would highly recommend not making direct HTTP calls in your Jenkinsfile even if it seems like it works fine in some cases. You can create a bash script that does whatever you want (curl, java -jar yourRestClient.jar, etc.) and call that script using the sh or bat steps which run asynchronously and are not subject to a 5 minute timeout. Andrew a Based on those logs, there does appear to be a network issue with the remoting layer involved as well. I will check through the build files you sent to see if they give any indication of a root cause that we can address. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Brian Villanueva commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs Running a full pipeline might take a long time... especially if you have 10s or 100s that are affected by the issue. Does anyone know if there's a way to alter the config proactively (manually) via the job's XML file? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53996) Plugin version 2.7 is not backwards compatible with versions <= 2.6
Title: Message Title Sergii Borsuk assigned an issue to Sergii Borsuk Jenkins / JENKINS-53996 Plugin version 2.7 is not backwards compatible with versions <= 2.6 Change By: Sergii Borsuk Assignee: Max Gelman Sergii Borsuk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53996) Plugin version 2.7 is not backwards compatible with versions <= 2.6
Title: Message Title Sergii Borsuk created an issue Jenkins / JENKINS-53996 Plugin version 2.7 is not backwards compatible with versions <= 2.6 Issue Type: Bug Assignee: Max Gelman Components: contrast-continuous-application-security-plugin Created: 2018-10-10 19:34 Priority: Blocker Reporter: Sergii Borsuk In the plugin version 2.7, the parameter used to start an application with the contrast agent changed to Dcontrast.override.appversion=applicationUUID%BUILD_NUMBER% At the same time job configurations for plugin versions <= 2.6 use this parameter: Dcontrast.override.appversion=applicationName%BUILD_NUMBER% Add Comment
[JIRA] (JENKINS-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Christoph Amshoff commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Same issue here... We're having a quite small Jenkinsfile that calls a RESTful service, which takes (depending on parameters) few seconds up to an hour or more to complete. The JSON returned by the service should be attached to the build, that's why it's called synchronously. The longer the service call takes, the more likely the InterruptedException occurs. There are no parallel steps in our pipeline, so I'm pretty sure it's related to the long-running step. The REST call is done by some selfmade Groovy function and classes in our shared library, basically setting up a HttpURLConnection instance. However, that works nicely in fast service calls, so I don't think there is an issue in this code. Let me know if I can help with any files/logs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title David Taylor commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) Claus Schneider thank you for the plugin recommendation. we will look at this and see what works! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title Claus Schneider commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) You can consider using https://wiki.jenkins.io/display/JENKINS/Pretested+Integration+Plugin if it matches your needs. If not feel free to propose your missing needs.. It is using the credentials from the Git SCM plugin and uses it in the "publisher". It supports http/windows .. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53995) Parallel workflow shows green while running, NOT blue ocean.
Title: Message Title Brian Kruger created an issue Jenkins / JENKINS-53995 Parallel workflow shows green while running, NOT blue ocean. Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2018-10-10 at 11.48.49 AM - running.png, Screen Shot 2018-10-10 at 11.50.01 AM - done.png, Screen Shot 2018-10-10 at 11.52.23 AM - docker launch.png Components: workflow-aggregator-plugin Created: 2018-10-10 19:07 Environment: jenkins 2.146, openjdk 1.8.0.181, amazon linux 2/kubernetes, kubernetes-plugin. Priority: Minor Reporter: Brian Kruger Similar to the issues here: https://issues.jenkins-ci.org/browse/JENKINS-53587 https://issues.jenkins-ci.org/browse/JENKINS-53311 Using the pipeline script in 53587 - If you run this in a non-blue-ocean, it'll show everything as passing while executing, despite the job running All previous jobs were removed.. I've observed this also in a script I wrote to test multiple docker containers for basic functionality where they're green before being fired up. Enclosed pictures are what my docker image testing job looks like visually when it's spun up (all green, despite there not even being containers launched yet), and then also the script from 53587 - launched and completed. When it fails, it does go red, but it's green until then. I don't know if this is intended behavior to have it green, but it's confusing to our developers and even to myself to some extent where this should more show a pending state of some-sort rather than all green. I also used the workflow-aggregator as the component since this seems to do the import of
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Damian Szczepanik assigned an issue to Tibor Digana Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Damian Szczepanik Assignee: Damian Szczepanik Tibor Digana Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53987) java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String
Title: Message Title Damian Szczepanik closed an issue as Fixed You have reported issue to wrong plugin Jenkins / JENKINS-53987 java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String Change By: Damian Szczepanik Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53982) Include version in Jenkins.war and *.hpi file names
Title: Message Title Daniel Beck closed an issue as Won't Do Will require an overhaul of quite a bit of infra to make work, and it doesn't seem worth the effort. Perhaps as part of some redesign, but not useful standalone. You're not supposed to download Jenkins manually anyway Jenkins / JENKINS-53982 Include version in Jenkins.war and *.hpi file names Change By: Daniel Beck Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53978) Less than sign (<) not correctly parsed in Agent Configuration History files
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-53978 Less than sign (<) not correctly parsed in Agent Configuration History files Change By: Daniel Beck Component/s: jobconfighistory-plugin 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53726) Rename of the plugin
Title: Message Title J Knurek edited a comment on JENKINS-53726 Re: Rename of the plugin When I found it and linked to it here, I only briefly looked at it, and thought maybe some if it isn't relevant anymore. But after reading through it again, I'd say most of it is, and maybe this ticket should be closed as a duplicate of JENKINS-52663 * my guess is that the ticket was closed just at the end of gsoc as it was part of the final phase sprint, and not because it was no longer relevant Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53726) Rename of the plugin
Title: Message Title J Knurek commented on JENKINS-53726 Re: Rename of the plugin When I found it and linked to it here, I only briefly looked at it, and thought maybe some if it isn't relevant anymore. But after reading through it again, I'd say most of it is, and maybe this ticket should be closed as a duplicate of JENKINS-52663 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title David Taylor commented on JENKINS-28335 Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support) any updates would be appreciated. my team is working on pipelines and we need this plugin to be updated in order to push back to Bitbucket from windows without using ssh keys. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-45927) CauseOfBlockage of items in Queue is extremely verbose
Title: Message Title Alex Taylor commented on JENKINS-45927 Re: CauseOfBlockage of items in Queue is extremely verbose Daniel Beck would it not make more sense to just count the number of agents which do not have the label and then return that number? Then you could find out the names(if needed) from the build console log itself rather than from the hover over in the build queue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Jenkins PR build for download at https://ci.jenkins.io/job/Core/job/jenkins/job/PR-3689/2/artifact/org/jenkins-ci/main/jenkins-war/2.147-rc27437.1590be3ff083/jenkins-war-2.147-rc27437.1590be3ff083.war Perhaps those watchers with ability to patch and build their own Firefox could check whether form submission buttons in this Jenkins build address the problem? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53994 Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Change By: Nikolas Falco Attachment: schedule_build_page_exception.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco edited a comment on JENKINS-53994 Re: Parameters that use own descriptor to check/fill fields returns 404 in schedule release page [~oleg_nenashev] I know that you had mark yourself as retired developer of this plugin (and you are usually busy) but the solution is really fast and already proposed [here|https://github.com/jenkinsci/release-plugin/pull/31] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53967) Looking for option to find git push user
Title: Message Title Mark Waite updated JENKINS-53967 Jenkins / JENKINS-53967 Looking for option to find git push user Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53967) Looking for option to find git push user
Title: Message Title Mark Waite updated JENKINS-53967 Thanks for your question, but questions are best asked in chat or in the appropriate mailing list. A question in chat or on a mailing list will be seen by many more people than a question in the bug tracker. Jenkins / JENKINS-53967 Looking for option to find git push user Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco commented on JENKINS-53994 Re: Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Oleg Nenashev I know that you mark yourself as retired developer of this plugin (and you are usually busy) but the solution is really fast and already proposed here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-53994 Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Issue Type: New Feature Assignee: Oleg Nenashev Components: release-plugin Created: 2018-10-10 16:56 Environment: Jenkins 2.121.3 release-plugin 2.10.1 Priority: Major Reporter: Nikolas Falco If I define a new parameters like validation string parameter that use a regex to validate the user input it performs a doCheckXYZ method of its descriptor. In the Schedule Release Page (action page) the HTTP request returns 404 because the URL is relative to the action page $JENKINS_URL/jobs/XYZ/release instead of the project. Add Comment
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted I'll need to get back on this. Will need to spin up a new cluster in 1.11 to test again tomorrow. Could just have been the bad mount. Thanks very much for the leads ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the \ { { hostPathVolume} } from the \ { { podTemplate} } ? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the {hostPathVolume} from the {podTemplate}? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie updated an issue
Jenkins / JENKINS-53297
Kubernetes v1.11 - ChannelClosed after job delaying aborted
Change By:
David Currie
I've Jenkins running on Kubernetes Cluster (Bluemix IKS).I am using the kubernetes plugin to create dynamic agents.The jenkins connection with agent is made in the standard way: - Jenkins URL: jenkins:8080- Jenkins Tunnel: jenkins-agent:5 When i start a job, the agent connect with Jenkins master successfully. But he keeps long time and not execute pipeline steps. Agent logs: {code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorAug 29, 2018 12:07:02 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins-slave-n39mq-9zgzzAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.23Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://jenkins:8080/]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-agent Agent port: 5 Identity: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-agent:5Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: ConnectedAug 29, 2018 12:12:09 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave$SlaveDisconnector callINFO: Disabled slave engine reconnects.Aug 29, 2018 12:12:09 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: hudson.remoting.ChannelClosedException: Channel "unknown": Protocol stack cannot write data anymore. ChannelApplicationLayer reports that the NIO Channel is closed at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1038) at hudson.remoting.Channel.close(Channel.java:1439)
[JIRA] (JENKINS-45502) Add concept of "interesting" to SCMHead and SCMRevision
Title: Message Title Nikolas Falco commented on JENKINS-45502 Re: Add concept of "interesting" to SCMHead and SCMRevision Stephen Connolly I'm interessed about you idea of scalar instead of boolean returned from a possible new API SCMSourceContext.skipEvent (or Build). In case of scalar the people that configure a job how could know which are value contributed by each SCMEventFilter and how this impact the final value of the scalar to match against the cute-off? I'm asking because recently I had implement release as pipeline and to avoid trigger multiple builds with something similar of JENKINS-41048 (here) I skip some kinds of events (more details here) but this marks the branch (master) to remove. This feature is required for our organisation and seems froosen from long time. I have budget to implement this and I would some clarification to propose something of acceptable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53726) Rename of the plugin
Title: Message Title Pham Vu Tuan commented on JENKINS-53726 Re: Rename of the plugin J Knurek the ticket you gave is marked as "Closed", should I re-open it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53993) Provide recursive processing of jobs referenced in jobcopy plugin
Title: Message Title David Klimesh created an issue Jenkins / JENKINS-53993 Provide recursive processing of jobs referenced in jobcopy plugin Issue Type: Improvement Assignee: Unassigned Components: jobcopy-builder-plugin Created: 2018-10-10 16:09 Priority: Minor Reporter: David Klimesh Would it be possible to add a feature to this plugin that allowed for it to recursively process all jobs that are called by the copied job. This would include jobs triggered as a build step and a post build action. Add Comment
[JIRA] (JENKINS-53726) Rename of the plugin
Title: Message Title J Knurek commented on JENKINS-53726 Re: Rename of the plugin I think the "definition of done" from this ticket is probably relevant here: https://issues.jenkins-ci.org/browse/JENKINS-52663 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Alok Rajiv commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Hi David, About the docker builds I was thinking on the same grounds. But, before we reach that step the issue is the builder containers spawned up for the job itself is the issue. Currently, jenkins master doesn't see the slave builder container ready status. My error is `Timed out waiting for container to become ready!` Is the Kubernetes Pod Template, using docker daemon underneath? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53992) Multiple use of xml file in plots
Title: Message Title
Tim Schlüter updated an issue
Jenkins / JENKINS-53992
Multiple use of xml file in plots
Change By:
Tim Schlüter
If I use one xml-file in more than one plot the plugin isn't working anymore. It simply doesn't store the values anymore. I try to generate one plot for and one for from this data which is stored in one file:{code:java} 343284 102031 274552 45862{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title David Currie commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Is that Jenkinsfile just an example or what you're actually trying to achieve? You shouldn't need a Docker socket in order to use helm. That is not to say that this isn't a problem in other scenarios e.g. when trying to use the daemon on the Kubernetes node to perform Docker builds. In that case, you could look at using kaniko or fall back to Docker-in-Docker. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53992) Multiple use of xml file in plots
Title: Message Title Tim Schlüter created an issue Jenkins / JENKINS-53992 Multiple use of xml file in plots Issue Type: Bug Assignee: Veaceslav Gaidarji Components: plot-plugin Created: 2018-10-10 15:40 Priority: Major Reporter: Tim Schlüter If I use one xml-file in more than one plot the plugin isn't working anymore. It simply doesn't store the values anymore. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53991) cron job trigger for multibranchPipelineJob DSL
Title: Message Title
Stanislav Pugachov created an issue
Jenkins / JENKINS-53991
cron job trigger for multibranchPipelineJob DSL
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-multibranch-plugin
Created:
2018-10-10 15:30
Environment:
Jenkins ver. 2.138 Pipeline: Multibranch 2.20
Priority:
Minor
Reporter:
Stanislav Pugachov
Hi, I'm using multiBranchPipeline DSL to create a jobs like that:
multibranchPipelineJob('${jobName}') {
branchSources {
git {
remote('${repo}')
credentialsId('${credentialsId}')
includes('${branches}')
}
}
orphanedItemStrategy {
discardOldItems {
numToKeep(20)
}
}
configure {
it / factory(class: 'org.jenkinsci.plugins.workflow.multibranch.WorkflowBranchProjectFactory') {
owner(class: 'org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject', reference: '../..')
scriptPath('${jenkinsfilePath}')
}
}
}
Everything works fine, but now I want to trigger job automatically by cron. According to docs I can use https://jenkinsci.github.io/job-dsl-plugin/#path/multibranchPipelineJob-triggers-cron But it doesnt work for me. I'm adding this to DSL snippet:
triggers {cron('@daily')}
[JIRA] (JENKINS-53990) Pipeline scheduling errors do not show up in Blue Ocean
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-53990 Pipeline scheduling errors do not show up in Blue Ocean Issue Type: Bug Assignee: Unassigned Attachments: Selection_567.png Components: blueocean-plugin Created: 2018-10-10 15:17 Priority: Minor Reporter: R. Tyler Croy Some Pipeline errors not showing up in Blue Ocean. In the screenshotted Pipeline, there was a system failure on the Jenkins side when trying to handle the scheduling of a node.: Resuming build at Wed Oct 10 14:33:36 GMT 2018 after Jenkins restart Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Resuming build at Wed Oct 10 14:43:26 GMT 2018 after Jenkins restart Waiting to resume part of Core » jenkins » PR-3689 #1: ??? Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of Core » jenkins » PR-3689 #1: ‘win2012-79a800’ is offline Waiting to resume part of
[JIRA] (JENKINS-53990) Pipeline scheduling errors do not show up in Blue Ocean
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-53990 Pipeline scheduling errors do not show up in Blue Ocean Change By: R. Tyler Croy Attachment: Selection_567.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50532) Failing nested parallel stages are marked green
Title: Message Title Daniel Kurzynski commented on JENKINS-50532 Re: Failing nested parallel stages are marked green Phil Segal No. Unfortunately not. This is also still an issue for us. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53199) Docker plugin should be configured to be capable of running Docker-in-docker
Title: Message Title R. Tyler Croy commented on JENKINS-53199 Re: Docker plugin should be configured to be capable of running Docker-in-docker I assume that dockerNode works in Declarative, that's a prerequisite here Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53965) ConsoleLog is missing build output
Title: Message Title
Jesse Glick commented on JENKINS-53965
Re: ConsoleLog is missing build output
And durable-task and workflow-durable-task-step plugins. Without a way to reproduce from scratch, I am afraid this is not actionable. BTW use {code:none}…{code} in JIRA to suppress markup in long blocks of monospaced text.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-52199) Investigate on consumer pooling, NIO options
Title: Message Title Pham Vu Tuan stopped work on JENKINS-52199 Change By: Pham Vu Tuan Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52954) Agent can recover to run jobs after it disconnects
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52954 Agent can recover to run jobs after it disconnects Change By: Pham Vu Tuan Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52877) Implement PingThread in agent
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-52877 Implement PingThread in agent Change By: Pham Vu Tuan Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53989) Provision Kafka node for Jenkins master
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53989 Provision Kafka node for Jenkins master Issue Type: New Feature Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-10-10 14:53 Priority: Major Reporter: Pham Vu Tuan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53984) Parallel task is showing the wrong status since moving to nested parallels.
Title: Message Title
Phil Segal updated an issue
Jenkins / JENKINS-53984
Parallel task is showing the wrong status since moving to nested parallels.
Change By:
Phil Segal
We have recently moved from a single set of parallel nodes to 2 sets of nested parallel nodes:Pseudo representation:parallel : { ( parallel batTests someTests (), parallel buckTests otherTests () )or :parallel( fork1 = { doStuff parallel otherStuff } , fork2, fork3 ) Whilst I understand that Blue Ocean is not able to render the whole workflow, worryingly it no longer shows the correct status for the individual steps/tasks. We have examples of passing builds showing red and failing builds showing as green. This is obviously fairly fundamental issue for using BO.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google 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-53506) Update all installed plugins to latest version
Title: Message Title Jesse Glick commented on JENKINS-53506 Re: Update all installed plugins to latest version Possible to do such updates today (evergreen PR 312), but cumbersome—requires a lot of time in a text editor copying and pasting stuff into the spec section (being careful not to paste anything into status where it will be discarded), iteratively running the goal to propose updates, which produces a ton of noise since the current _javascript_ tool does not grok some details of the version syntax actually used by both Maven and the Jenkins plugin manager. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53984) Parallel task is showing the wrong status since moving to nested parallels.
Title: Message Title Phil Segal updated an issue Jenkins / JENKINS-53984 Parallel task is showing the wrong status since moving to nested parallels. Change By: Phil Segal Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-50532) Failing nested parallel stages are marked green
Title: Message Title Phil Segal commented on JENKINS-50532 Re: Failing nested parallel stages are marked green Did you find any workaround for this? We are trying to use nested parallels and our statuses are dodgy 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Jesse Glick commented on JENKINS-53767 Re: Offer plugin management tooling There is already a tool which understands how to update versions of components including incremental versions from a specified branch (such as origin master); as per JENKINS-51929, it would “just” need a shim to also read/write the JEP-309 format. That is only going to be useful, however, if the file is actually listing all the plugins you are bundling, as discussed in JENKINS-53506. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53199) Docker plugin should be configured to be capable of running Docker-in-docker
Title: Message Title Baptiste Mathus commented on JENKINS-53199 Re: Docker plugin should be configured to be capable of running Docker-in-docker Should be helped AIUI by https://github.com/jenkins-infra/evergreen/pull/295#issuecomment-428579402 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53987) java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String
Title: Message Title Tyler Jones updated an issue Jenkins / JENKINS-53987 java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String Change By: Tyler Jones Tests pass, failure on creating report. please let me know if you need more info Using CFPropertyList 3.0.0 Using concurrent-ruby 1.0.5Using i18n 0.9.5Using multi_json 1.13.1Using activesupport 3.2.22.5Using public_suffix 3.0.2Using addressable 2.5.2Using awesome_print 1.8.0Using json 2.1.0Using mini_portile2 2.3.0Using nokogiri 1.8.2Using ffi 1.9.23Using childprocess 0.9.0Using rubyzip 1.2.1Using selenium-webdriver 3.11.0Using tomlrb 1.2.6Using appium_lib 9.7.1Using builder 3.2.3Using bundler 1.16.0Using mini_mime 1.0.0Using rack 2.0.4Using rack-test 1.0.0Using xpath 3.0.0Using capybara 2.18.0Using chunky_png 1.3.6Using cliver 0.3.2Using diff-lcs 1.3Using gherkin 2.12.2Using multi_test 0.1.2Using cucumber 1.3.20Using unf_ext 0.0.7.5Using unf 0.1.4Using domain_name 0.5.20170404Using multipart-post 2.0.0Using faraday 0.14.0Using oily_png 1.2.0Using oj 2.18.2Using websocket-extensions 0.1.3Using websocket-driver 0.7.0Using poltergeist 1.17.0Using eyes_selenium 2.39.0Using git 1.3.0Using highline 1.7.10Using http-cookie 1.0.3Using multi_xml 0.6.0Using httparty 0.11.0Using ios-deploy 1.5.0Using mime-types-data 3.2016.0521Using mime-types 3.1Using naturally 2.1.0Using net-ssh 4.2.0Using net-scp 1.2.1Using net-sftp 2.1.2Using netrc 0.11.0Using rest-client 2.0.2Using rspec-support 3.7.1Using rspec-core 3.7.1Using rspec-expectations 3.7.0Using rspec-mocks 3.7.0Using rspec 3.7.0Using simctl 1.6.3Using testrail 0.0.3 11 scenarios (11 passed)147 steps (147 passed)47m46.176s[AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins1679286573190577668.sh1.5.20[RC]531[EnvInject] - Injecting environment variables from a build step.[EnvInject] - Injecting as environment variables the properties file path 'propsfile'[EnvInject] - Variables injected successfully.[AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash -l /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins5375350845591340827.sh**no build info added** TestRun Id used:TestCaseId: 179162TestCaseId: 264293TestCaseId: 179163TestCaseId: 264296TestCaseId: 179272TestCaseId: 179271TestCaseId:TestCaseId: 179161TestCaseId:TestCaseId: 264299TestCaseId: 264297[description-setter] Description set: MODULE= APP_VERSION=1.5.20[RC] ANDROID_BUILD_NUMBER=531 DEVICE_NAME=Pixel2-9-QA DEVICE_VERSION=9.0Archiving artifacts[Cucumber Tests] Parsing results.[Cucumber Tests] parsing features_report.jsonERROR: Build step failed with exceptionAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mac_mini_10.10.0.213at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:952)at hudson.FilePath.act(FilePath.java:998)at hudson.FilePath.act(FilePath.java:987)at
[JIRA] (JENKINS-53988) skipDefaultCheckout not honored in Pull Requests
Title: Message Title Scott Matthews created an issue Jenkins / JENKINS-53988 skipDefaultCheckout not honored in Pull Requests Issue Type: Bug Assignee: Unassigned Components: workflow-multibranch-plugin, workflow-scm-step-plugin Created: 2018-10-10 14:24 Environment: Jenkins Ver = 2.121.2 workflow-scm-step-plugin = 2.6 Priority: Minor Reporter: Scott Matthews I have searched for a few hours on information on this but come up with nothing so apologies if there is a simple answer to this. The issue is this: I have a pipeline that I disable the default checkout using skipDefaultCheckout() option. This works fine for a branch build however when I run a PR build it seems to be ignored. It looks like any PR build forces a sparse checkout and merges master at the start. This breaks some of my logic later in the pipeline that uses git diff. Is this a bug or is it desired behavior? It feels like a bug but if it is desired behavior perhaps there is a better way to achieve what I want which I can explain more in detail if this is the right place to do so. (maybe better a question for stackoverflow).
[JIRA] (JENKINS-53987) java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String
Title: Message Title Tyler Jones updated an issue Jenkins / JENKINS-53987 java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String Change By: Tyler Jones Tests pass, failure on creating report. please let me know if you need more info 11 scenarios (11 passed)147 steps (147 passed)47m46.176s[AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins1679286573190577668.sh1.5.20[RC]531[EnvInject] - Injecting environment variables from a build step.[EnvInject] - Injecting as environment variables the properties file path 'propsfile'[EnvInject] - Variables injected successfully.[AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash -l /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins5375350845591340827.sh**no build info added** TestRun Id used:TestCaseId: 179162TestCaseId: 264293TestCaseId: 179163TestCaseId: 264296TestCaseId: 179272TestCaseId: 179271TestCaseId:TestCaseId: 179161TestCaseId:TestCaseId: 264299TestCaseId: 264297[description-setter] Description set: MODULE= APP_VERSION=1.5.20[RC] ANDROID_BUILD_NUMBER=531 DEVICE_NAME=Pixel2-9-QA DEVICE_VERSION=9.0Archiving artifacts[Cucumber Tests] Parsing results.[Cucumber Tests] parsing features_report.jsonERROR: Build step failed with exceptionAlso: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mac_mini_10.10.0.213at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737)at hudson.remoting.UserResponse.retrieve(UserRequest.java:313)at hudson.remoting.Channel.call(Channel.java:952)at hudson.FilePath.act(FilePath.java:998)at hudson.FilePath.act(FilePath.java:987)at org.jenkinsci.plugins.cucumber.jsontestsupport.DefaultTestResultParserImpl.parseResult(DefaultTestResultParserImpl.java:100)at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parseResult(CucumberJSONParser.java:101)at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.publishReport(CucumberTestResultArchiver.java:134)at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberTestResultArchiver.perform(CucumberTestResultArchiver.java:113)at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)at hudson.model.Build$BuildExecution.post2(Build.java:186)at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)at hudson.model.Run.execute(Run.java:1752)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429)java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.Stringat gherkin.JSONParser.step(JSONParser.java:131)at gherkin.JSONParser.parse(JSONParser.java:51)at org.jenkinsci.plugins.cucumber.jsontestsupport.CucumberJSONParser.parse(CucumberJSONParser.java:78)at
[JIRA] (JENKINS-53987) java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String
Title: Message Title Tyler Jones created an issue Jenkins / JENKINS-53987 java.lang.ClassCastException: java.lang.Boolean cannot be cast to java.lang.String Issue Type: Bug Assignee: Damian Szczepanik Components: cucumber-reports-plugin Created: 2018-10-10 14:22 Environment: Jenkins ver. 2.111 Priority: Blocker Reporter: Tyler Jones Tests pass, failure on creating report. 11 scenarios (11 passed) 147 steps (147 passed) 47m46.176s [AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins1679286573190577668.sh 1.5.20[RC] 531 [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path 'propsfile' [EnvInject] - Variables injected successfully. [AS1_Android_Client_Tests_Release_Candidate] $ /bin/bash -l /var/folders/jy/nvtds44j51997l5n0dc_cnp8gp/T/jenkins5375350845591340827.sh *no build info added* TestRun Id used: TestCaseId: 179162 TestCaseId: 264293 TestCaseId: 179163 TestCaseId: 264296 TestCaseId: 179272 TestCaseId: 179271 TestCaseId: TestCaseId: 179161 TestCaseId: TestCaseId: 264299 TestCaseId: 264297 [description-setter] Description set: MODULE= APP_VERSION=1.5.20[RC] ANDROID_BUILD_NUMBER=531 DEVICE_NAME=Pixel2-9-QA DEVICE_VERSION=9.0 Archiving artifacts [Cucumber Tests] Parsing results. [Cucumber Tests] parsing features_report.json ERROR: Build step failed with exception Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to mac_mini_10.10.0.213 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel.call(Channel.java:952) at hudson.FilePath.act(FilePath.java:998) at
[JIRA] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title Alex Earl commented on JENKINS-26439 Re: Build does not abort when «Send files or execute commands over SSH» fails Maybe I can provide an option that will fail the build if there is a non-zero exit status. This would keep the current default, but allow people who want this behavior to have it. I'll look into it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49446) Regression with 1.15 and WithContainerStep
Title: Message Title Nicolas De Loof closed an issue as Not A Defect Jenkins / JENKINS-49446 Regression with 1.15 and WithContainerStep Change By: Nicolas De Loof Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49446) Regression with 1.15 and WithContainerStep
Title: Message Title Nicolas De Loof commented on JENKINS-49446 Re: Regression with 1.15 and WithContainerStep docker-workflow plugin comes with constraints, which unfortunately never have been clearly documented. Those are pretty comparable to https://github.com/knative/docs/blob/master/build/builder-contract.md But there's no way we support arbitrary docker images and entrypoint script. Adapt your docker images so they fit into our model Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-50196 Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom Change By: Vincent Latombe Assignee: Carlos Sanchez Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title Vincent Latombe updated JENKINS-50196 Jenkins / JENKINS-50196 Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom Change By: Vincent Latombe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53986) Lastest Git Tag is not pulled if you build first with a specific tag
Title: Message Title Edward Croft created an issue Jenkins / JENKINS-53986 Lastest Git Tag is not pulled if you build first with a specific tag Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-10 13:57 Environment: Test Priority: Minor Reporter: Edward Croft In a freestyle project using a Git source, if you first build a job with a specific tag, then build with 'latest tag' (/tags/), it will be stuck with the specific tag you specified before. Recreation steps: 1) Repository URL (simple project with 1 small file): https://github.com/ediso74/Tagging.git 2) Refspec: +refs/tags/:refs/remotes/origin/tags/ 3) Branch Specifier: */tags/v1.1 4. Execute Windows build command (unix also): more junk.txt 5. Build When you click on build, you will see: Revision: 352e66e7b09157983fc0a2c73339e99257be5fa6 refs/remotes/origin/tags/v1.1 Console log: ... C:\Users\ediso\.jenkins\workspace\Tagging>more junk.txt Going to Tag this file version with Tag v1.1 6. Change Branch Specifier: */tags/* 7. Build nothing changes Other notes: 1) If you create a new commit with a new tag, it will show the latest tag.
[JIRA] (JENKINS-49446) Regression with 1.15 and WithContainerStep
Title: Message Title Mark Russell commented on JENKINS-49446 Re: Regression with 1.15 and WithContainerStep This issue is stopping up from upgrading this plugins. Is anyone looking at it? Is there any chance for a solution on 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-53985) Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302
Title: Message Title Oliver Schuhmacher created an issue Jenkins / JENKINS-53985 Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302 Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-10-10 13:32 Environment: Jenkins 2.138.1 org.jenkins-ci.plugins:hp-application-automation-tools-plugin:5.5 Labels: MicroFocus ALM Priority: Minor Reporter: Oliver Schuhmacher It is not possible to connect to HP ALM server using the above mentioned pluigin. INFO: 'Upload test result to ALM' Post Build Step is being invoked by xxx. INFO: 1 test result file found. INFO: Start to upload C:\xx\xx\xx\xx\builds\16\testng\testng-results.xml INFO: Start to parse file: C:\xx\xx\xx\xx\builds\16\testng\testng-results.xml INFO: parse resut file succeed. INFO: Start to login to ALM Server. Start login to ALM server. Login to ALM Server at https://xxx/qcbin/ failed. Status Code: 302 WARN: there's exception while uploading C:\xx\xx\xx\xx\builds\16\testng\testng-results.xml. INFO: 'Upload test result to ALM' Completed. Build step 'Upload test result to ALM' changed build result to UNSTABLE Finished: UNSTABLE
[JIRA] (JENKINS-53984) Parallel task is showing the wrong status since moving to nested parallels.
Title: Message Title
Phil Segal created an issue
Jenkins / JENKINS-53984
Parallel task is showing the wrong status since moving to nested parallels.
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-10-10 13:27
Priority:
Minor
Reporter:
Phil Segal
We have recently moved from a single set of parallel nodes to 2 sets of nested parallel nodes: Pseudo representation: parallel: { parallel batTests(), parallel buckTests() } Whilst I understand that Blue Ocean is not able to render the whole workflow, worryingly it no longer shows the correct status for the individual steps/tasks. We have examples of passing builds showing red and failing builds showing as green. This is obviously fairly fundamental issue for using BO.
Add Comment
[JIRA] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title
Stephan Watermeyer commented on JENKINS-26439
Re: Build does not abort when «Send files or execute commands over SSH» fails
Here are working example. Just set the variable $ServerName I would expect that the pipeline does not continue if the sshPublisher plugin returns with something != 0
pipeline {
agent any
stages {
stage('Do sth remote') {
steps {
cleanWs notFailBuild: true
sshPublisher(publishers: [sshPublisherDesc(configName: "$ServerName", transfers: [sshTransfer(excludes: '', execCommand: '''
echo "i am a failure"
exit 9 ''', execTimeout: 18000, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)])
}
}
stage('Do sth on jenkins') {
steps {
echo "Should not run any more"
}
}
}
}
Outcome:
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Do sth remote)
[Pipeline] cleanWs
[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] done
[Pipeline] step
SSH: Connecting from host [53d1c1e2cbf8]
SSH: Connecting with configuration [swpsws47] ...
SSH: EXEC: STDOUT/STDERR from command [
echo "i am a failure"
exit 9
] ...
i am a failure
SSH: EXEC: completed after 201 ms
SSH: Disconnecting configuration [swpsws47] ...
ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [9]]
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Do sth on jenkins)
[Pipeline] echo
Should not run any more
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: UNSTABLE
Add Comment
[JIRA] (JENKINS-26439) Build does not abort when «Send files or execute commands over SSH» fails
Title: Message Title
Stephan Watermeyer commented on JENKINS-26439
Re: Build does not abort when «Send files or execute commands over SSH» fails
I am encountering simliar issues. I am executing some bash kung-fu on the target server and if this fails, i would like to exit the "step"/plugin with a RC != 0. The pipeline does not respect that the step has failed and continues the pipeline, so that the following step fails.
[Pipeline] step
SSH: Connecting from host [53d1c1e2cbf8]
SSH: Connecting with configuration [swpsws47] ...
SSH: EXEC: STDOUT/STDERR from command [
if [ -d /export/yyy/install/xxxmx-soapui/ ]; then
cd /export/yyy/install/xxxmx-soapui/
rm -fv /export/yyy/install/soapui.tar.gz
tar -zcf ../soapui.tar.gz ./*
else
echo "This build does not contain SoapUI tests to execute. Please update your branch!"
exit 9
fi ] ...
This build does not contain SoapUI tests to execute. Please update your branch!
SSH: EXEC: completed after 201 ms
SSH: Disconnecting configuration [swpsws47] ...
ERROR: Exception when publishing, exception message [Exec exit status not zero. Status [9]]
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Download Tests)
[Pipeline] sh
[xxx-smoketest-swpsws47] Running shell script
+ wget -q http://swpsws47/yyy/install/soapui.tar.gz
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Verify Server Ready)
Stage "Verify Server Ready" skipped due to earlier failure(s)
The pipeline looks like
pipeline {
agent any
stages {
stage('Prepare Tests') {
steps {
cleanWs notFailBuild: true
sshPublisher(publishers: [sshPublisherDesc(configName: "$ServerName", transfers: [sshTransfer(excludes: '', execCommand: '''
if [ -d /export/yyy/install/xxxmx-soapui/ ]; then
cd /export/yyy/install/xxxmx-soapui/
rm -fv /export/yyy/install/soapui.tar.gz
tar -zcf ../soapui.tar.gz ./*
else
echo "This build does not contain have SoapUI tests to execute. Please update your branch!"
exit 9
fi ''', execTimeout: 18000, flatten: false, makeEmptyDirs: false, noDefaultExcludes: false, patternSeparator: '[, ]+', remoteDirectory: '', remoteDirectorySDF: false, removePrefix: '', sourceFiles: '')], usePromotionTimestamp: false, useWorkspaceInPromotion: false, verbose: false)])
}
}
stage('Download Tests') {
steps {
sh 'wget -q http://$ServerName/yyy/install/soapui.tar.gz'
sh 'tar -xzf soapui.tar.gz --directory .'
}
}
stage('Verify Server Ready') {
...
}
}
}
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox https://github.com/jenkinsci/jenkins/pull/3689 the hack version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox https://github.com/scherler/jenkins/tree/JENKINS-53462 I created a callback and in case we have a submit type we look up the parent form and submit it. ...I know but those 9 line of code is based on different approaches and to not break the universe I implemented like as-is. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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-53983) Per-instance tainting still serves the tainted level if you're "coming from" a lower level
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-53983 Per-instance tainting still serves the tainted level if you're "coming from" a lower level Change By: Baptiste Mathus _NOTE: I've added a [reproducer test case|https://github.com/jenkins-infra/evergreen/pull/316/commits/bf5a61c5312642efecb3007cf61a8903d5e59c08], and this issue matches my experience from testing it locally when I see the rollback work, and then still re-upgrade to the tainted level after going away from it previously. But I'm still not 100% sure of the diagnosis, so keep this in mind below._h3. Problem statementWhen an instance taints a given update level (after a failure to upgrade), then it correctly gets the previous non tainted UL.But then, when asking the backend again, passing the previous UL as parameter (i.e. the good one, the one *before* the just tainted one), then the backend will still serve an answer to upgrade to the tainted level.h3. Expected behaviorOnce _per-instance tainted_ , a given UL should never be proposed again to a given instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google 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
