[JIRA] (JENKINS-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jochen A. Fürbacher resolved as Fixed Fixed in 2.18.3. It will be available in the update center in the next couple of hours. Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jochen A. Fürbacher Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54204) Building / Checking evergreen modify the npm dependencies
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54204 Building / Checking evergreen modify the npm dependencies Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54204) Building / Checking evergreen modify the npm dependencies
Title: Message Title Baptiste Mathus assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-54204 Building / Checking evergreen modify the npm dependencies Change By: Baptiste Mathus Assignee: R. Tyler Croy Adrien Lecharpentier 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-54235) Parameterized scheduler not triggering daily builds
Title: Message Title Deepak Puligundla created an issue Jenkins / JENKINS-54235 Parameterized scheduler not triggering daily builds Issue Type: Bug Assignee: Baptiste Mathus Components: parameterized-scheduler-plugin Created: 2018-10-25 02:59 Priority: Major Reporter: Deepak Puligundla I want my pipeline to build every day at a particular time. So, I have configured the "Build periodically with parameters" field as below 20 06 24 10 1,2,3,4,5,6,0 %name=test; date="2018-08-21 00:00:00.000" The job triggers the build for the first time only and didn't repeat it every day. Jenkins version: 2.137 Parameterized Scheduler Plugin: 0.6.2 Pipeline:Job: 2.2.2 Add Comment
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps If anyone would like to try my proposed fix, download it 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick updated JENKINS-54073 Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Jesse Glick 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54073 "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Change By: Jesse Glick Component/s: workflow-api-plugin Component/s: durable-task-plugin Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54219) dashboard-view plugin rendering broken with 2.146
Title: Message Title Daniel Beck commented on JENKINS-54219 Re: dashboard-view plugin rendering broken with 2.146 I think with Portlets it depends on the plugin implementing it, rather than Dashboard View. 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 updated JENKINS-53900 Fixed in master @ e49553f1c8792e4e6f74285d3f8377a8f4ec3d99 Jenkins / JENKINS-53900 Stage graph in Blue Ocean not showing all stages for large workflows Change By: Josh McDonald Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54221) Add an example of a certificate authentication with service-principal to documentation
Title: Message Title Yunge Zhu assigned an issue to Jie Shen Jenkins / JENKINS-54221 Add an example of a certificate authentication with service-principal to documentation Change By: Yunge Zhu Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54221) Add an example of a certificate authentication with service-principal to documentation
Title: Message Title Yunge Zhu started work on JENKINS-54221 Change By: Yunge Zhu Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title
Jesse Glick commented on JENKINS-54073
Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Actually if I correct the freestyle build script to
set +x
cat /dev/urandom | env LC_CTYPE=c tr -dc '[:alpha:]\n' | awk '{print ENVIRON["BRANCH"], $0; system("sleep .1");}'
then it produces small chunks, typically around 300b apiece, with one ack per chunk. In 2.138.x there are also flushes, which I think is an unintentional side effect of my fix of JENKINS-52729: StreamTaskListener turns on autoflush when remoted, for no apparent reason. If I disable that in Pipeline, I can get rid of flushes, and if I apply buffering, I can greatly reduce Remoting overhead.
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-54233) Pipeline Script textarea missing
Title: Message Title Andrew Gray created an issue Jenkins / JENKINS-54233 Pipeline Script textarea missing Issue Type: Bug Assignee: Unassigned Components: core, pipeline Created: 2018-10-24 22:53 Environment: Windows 10; Jenkins 2.148; pipeline plugins: latest Priority: Critical Reporter: Andrew Gray Repro steps: Create a new pipeline job Scroll down to Pipeline section Default "Pipeline script" is selected in drop down. Script text area is missing. Add Comment
[JIRA] (JENKINS-51004) slave.jar -loggingConfig argument not working as documented
Title: Message Title Jeff Thompson commented on JENKINS-51004 Re: slave.jar -loggingConfig argument not working as documented Thanks for the clear issue report. However, I haven't been able to reproduce the issue. I have Remoting 3.23 in this instance and it seems to work fine with the "-loggingConfig" parameter. My agent is also on 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-54232) Jenkins worker unable to start SPOT instance.
Title: Message Title
Andrii Petrenko updated an issue
Jenkins / JENKINS-54232
Jenkins worker unable to start SPOT instance.
Change By:
Andrii Petrenko
I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. *Jenkins Amazon EC2 Plugin version 1.39 is working well* On-Demand instance with the same settings is starting well (1.40.1).log on demand:I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1 and 1.41 Jenkins Amazon EC2 Plugin version 1.39 is working well On-Demand instance with the same settings is starting well (1.40.1). *log on demand:*{ { noformat} Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Launching instance: i-0f79d897f46bcad22 }} {{ Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: bootstrap() }} {{ Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Getting keypair... }} {{ Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Using key: Jenkins }} {{ 25:9f:b6:d8:f9:e2:a7:d8:72:f4:37:b0:f6:d8:4d:0e }} {{ -BEGIN RSA PRIVATE KEY- }} {{ MIIEpAIBAAKCAQEAs2RqjBAQKnw8I7grFSlBx21Chh4U34dsn9QhX4HUqbNcFsaV }} {{ d3FbnLaDpsYPjRbXfvapnaIOiTBvCquDiluzP4rww/SoDUg5XpiKih+wMBpgsZb }} {{ Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Authenticating as ubuntu }} {{ Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Connecting to 10.78.44.158 on port 22, with timeout 1. }} {{ Oct 18, 2018 10:41:05 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired. }} {{ Oct 18, 2018 10:41:05 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Waiting for SSH to come up. Sleeping 5. }} {{ Oct 18, 2018 10:41:10 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Connecting to 10.78.44.158 on port 22, with timeout 1. }} {{ Oct 18, 2018 10:41:20 PM hudson.plugins.ec2.EC2Cloud }} {{ INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired. }} { { noformat } } *SPOT instance (1.40.1):* only changes: set "Use spot instance"The current Spot price for a T2Large in the us-west-2a availability zone is $0.127Spot Max Bid Price: 0.2*Log with spot instance:* {noformat}Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2CloudINFO: Launching instance: nullOct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2CloudINFO: bootstrap()Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2CloudINFO: Getting keypair...Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2CloudINFO: Using key: Jenkins25:9f:b6:d8:f9:e2:a7:d8:72:f4:37:b0:f6:d8:4d:0e-BEGIN RSA PRIVATE KEY-MIIEpAIBAAKCAQEAs2RqjBAQKnw8I7grFSlBx21Chh4U34dsn9QhX4HUqbNcFsaVd3FbnLaDpsYPjRbXfvapnaIOiTBvCquDiluzP4rww/SoDUg5XpiKih+wMBpgsZbOct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2CloudINFO: Authenticating as ubuntuERROR: Unexpected error in launching an agent. This is probably a bug in
[JIRA] (JENKINS-54232) Jenkins worker unable to start SPOT instance.
Title: Message Title
Andrii Petrenko updated an issue
Jenkins / JENKINS-54232
Jenkins worker unable to start SPOT instance.
Change By:
Andrii Petrenko
I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. *Jenkins Amazon EC2 Plugin version 1.39 is working well* On-Demand instance with the same settings is starting well (1.40.1).log on demand:I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1 and 1.41 Jenkins Amazon EC2 Plugin version 1.39 is working well On-Demand instance with the same settings is starting well (1.40.1). *log on demand:*{{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Launching instance: i-0f79d897f46bcad22}} {{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: bootstrap()}} {{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Getting keypair...}} {{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Using key: Jenkins}} {{25:9f:b6:d8:f9:e2:a7:d8:72:f4:37:b0:f6:d8:4d:0e}} {{-BEGIN RSA PRIVATE KEY-}} {{MIIEpAIBAAKCAQEAs2RqjBAQKnw8I7grFSlBx21Chh4U34dsn9QhX4HUqbNcFsaV}} {{d3FbnLaDpsYPjRbXfvapnaIOiTBvCquDiluzP4rww/SoDUg5XpiKih+wMBpgsZb}} {{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Authenticating as ubuntu}} {{Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Connecting to 10.78.44.158 on port 22, with timeout 1.}} {{Oct 18, 2018 10:41:05 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.}} {{Oct 18, 2018 10:41:05 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Waiting for SSH to come up. Sleeping 5.}} {{Oct 18, 2018 10:41:10 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Connecting to 10.78.44.158 on port 22, with timeout 1.}} {{Oct 18, 2018 10:41:20 PM hudson.plugins.ec2.EC2Cloud}} {{INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.}} {{}} *SPOT instance (1.40.1):* only changes: set "Use spot instance"The current Spot price for a T2Large in the us-west-2a availability zone is $0.127Spot Max Bid Price: 0.2*Log with spot instance:* { { noformat} Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: null Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: Jenkins 25:9f:b6:d8:f9:e2:a7:d8:72:f4:37:b0:f6:d8:4d:0e -BEGIN RSA PRIVATE KEY- MIIEpAIBAAKCAQEAs2RqjBAQKnw8I7grFSlBx21Chh4U34dsn9QhX4HUqbNcFsaV d3FbnLaDpsYPjRbXfvapnaIOiTBvCquDiluzP4rww/SoDUg5XpiKih+wMBpgsZb Oct 18, 2018 10:44:06 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as ubuntu ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at
[JIRA] (JENKINS-37739) Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline
Title: Message Title Glen Raines commented on JENKINS-37739 Re: Plugin not displaying Robot Test Summary correctly if robot framework task running in parallel in pipeline Our team here would also prefer to display separate Robot Test Summaries, so a fix would be really appreciated. 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-54232) Jenkins worker unable to start SPOT instance.
Title: Message Title Andrii Petrenko created an issue Jenkins / JENKINS-54232 Jenkins worker unable to start SPOT instance. Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2018-10-24 22:01 Environment: Jenkins Version 2.147 Jenkins Amazon EC2 Plugin version: 1.40.1, 1.41 Priority: Major Reporter: Andrii Petrenko I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. Jenkins Amazon EC2 Plugin version 1.39 is working well On-Demand instance with the same settings is starting well (1.40.1). log on demand: I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1. I have a problem running jenkins worker with SPOT instance with jenkins amazon EC2 plugin version 1.40.1 and 1.41 Jenkins Amazon EC2 Plugin version 1.39 is working well On-Demand instance with the same settings is starting well (1.40.1). log on demand: Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: i-0f79d897f46bcad22 Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: Using key: Jenkins 25:9f:b6:d8:f9:e2:a7:d8:72:f4:37:b0:f6:d8:4d:0e BEGIN RSA PRIVATE KEY MIIEpAIBAAKCAQEAs2RqjBAQKnw8I7grFSlBx21Chh4U34dsn9QhX4HUqbNcFsaV d3FbnLaDpsYPjRbXfvapnaIOiTBvCquDiluzP4rww/SoDUg5XpiKih+wMBpgsZb Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as ubuntu Oct 18, 2018 10:40:55 PM hudson.plugins.ec2.EC2Cloud INFO: Connecting to 10.78.44.158 on port 22, with timeout 1. Oct 18, 2018 10:41:05 PM hudson.plugins.ec2.EC2Cloud INFO: Failed to connect via ssh: The kexTimeout (1
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Jake Wallace commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Having the same issue with version v5.142 Mapping '$/Projects/Configurator-SCM/Configurator-Wizard Dev' to local folder '/var/jenkins_home/workspace/PICAppDev/SCMWizardDev@script' in workspace 'Hudson-SCMWizardDev-MASTER'... com.microsoft.tfs.core.ws.runtime.exceptions.SOAPFault: The workspace Hudson-SCMWizardDev-MASTER;dev_appdev_service already exists on computer ffaf3eb56301. at com.microsoft.tfs.core.ws.runtime.client.SOAP12Service.examineResponseDOMForFault(SOAP12Service.java:117) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineBodyForFault(SOAPService.java:987) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:665) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:444) at ms.tfs.versioncontrol.clientservices._03._RepositorySoap12Service.createWorkspace(_RepositorySoap12Service.java:555) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:784) Caused: com.microsoft.tfs.core.exceptions.TECoreException: The workspace Hudson-SCMWizardDev-MASTER;dev_appdev_service already exists on computer ffaf3eb56301. at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:92) at com.microsoft.tfs.core.exceptions.mappers.VersionControlExceptionMapper.map(VersionControlExceptionMapper.java:43) at com.microsoft.tfs.core.clients.versioncontrol.internal.WebServiceLayer.createWorkspace(WebServiceLayer.java:792) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:1020) at com.microsoft.tfs.core.clients.versioncontrol.VersionControlClient.createWorkspace(VersionControlClient.java:950) at hudson.plugins.tfs.model.MockableVersionControlClient.createWorkspace(MockableVersionControlClient.java:114) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:81) at hudson.plugins.tfs.commands.NewWorkspaceCommand.call(NewWorkspaceCommand.java:24) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.plugins.tfs.model.Server.execute(Server.java:233) Caused: java.lang.RuntimeException at hudson.plugins.tfs.model.Server.execute(Server.java:237) at hudson.plugins.tfs.model.Workspaces.newWorkspace(Workspaces.java:109) at hudson.plugins.tfs.actions.CheckoutAction.getProject(CheckoutAction.java:144) at hudson.plugins.tfs.actions.CheckoutAction.checkout(CheckoutAction.java:59) at hudson.plugins.tfs.TeamFoundationServerScm.checkout(TeamFoundationServerScm.java:352) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:144) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:290) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
[JIRA] (JENKINS-54231) job dsl summary hides multiple jobs with the same display name
Title: Message Title mcrooney created an issue Jenkins / JENKINS-54231 job dsl summary hides multiple jobs with the same display name Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-10-24 21:41 Environment: Jenkins ver. 2.121.3 Job DSL 1.64 Priority: Minor Reporter: mcrooney Howdy there, thanks for this fine plugin! We are noticing that in a job page that uses Job DSL, where it says "Generated Items" and lists all the jobs that job generated, it will only list one job if there are multiple with the same display name. Having multiple jobs with the same display name is allowed in Jenkins, and not inherently confusing when they are placed in different folders for context, but this bug prevents us from using the summary page to see which jobs it created accurately. Looking at the code, I'm wondering if this is related to "Sort generated items by name on the seed job's summary and build pages (JENKINS-38648)": https://github.com/jenkinsci/job-dsl-plugin/compare/4aaf8e924c90...2c13f9aa4c0e. It seems to use a Set based on job name so perhaps that is the issue, though I don't completely follow what it is doing so I'm not 100% sure.
[JIRA] (JENKINS-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks commented on JENKINS-50552 Re: Pipeline projects do not trigger libvirt VM snapshot reverts. I officially give up. I can't seem to hook into enough points of the Pipeline to prevent it from re-using "dead" nodes, which means that builds will unexpectedly fail for no other reason than that the VM was reset to the original state. I'm sure there's a lot of hook points I've missed, but the documentation is a bit large and I got lost quite a few times in it trying to find how to even figure out what node of a pipeline is being executed on what VM node. The code I have right now restarts the VM if it was known to be used by the Pipeline build system during any pipeline projects, which is unfortunately not enough. I will likely revisit this once I have more knowledge, but for now it's up for grabs for anyone that wants to try their hand at 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-54230) ArrayList join produces join of only first item
Title: Message Title
Roman Ivanov updated an issue
Jenkins / JENKINS-54230
ArrayList join produces join of only first item
Change By:
Roman Ivanov
The following script produces different output:import groovy.transform.TupleConstructor@TupleConstructorclass SimpleName { String name String toString() { name { name } }c = [new SimpleName("aaa"), new SimpleName("bbb")]println c.class.nameprintln c.size()println c.join("-") In groovyConsole the output is: java.util.ArrayList2aaa-bbb In jenkins pipeline the output is:Started by user Roman IvanovRunning in Durability level: MAX_SURVIVABILITY[Pipeline] echojava.util.ArrayList[Pipeline] echo2[Pipeline] echoaaa[Pipeline] End of PipelineFinished: SUCCESS
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-54230) ArrayList join produces join of only first item
Title: Message Title
Roman Ivanov updated an issue
Jenkins / JENKINS-54230
ArrayList join produces join of only first item
Change By:
Roman Ivanov
The following script produces different output:import groovy.transform.TupleConstructor@TupleConstructorclass SimpleName { String name String toString() { name }}c = [new SimpleName("aaa"), new SimpleName("bbb")]println c.class.nameprintln c.size()println c.join("-")
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-54230) ArrayList join produces join of only first item
Title: Message Title Roman Ivanov created an issue Jenkins / JENKINS-54230 ArrayList join produces join of only first item Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2018-10-24 21:23 Priority: Minor Reporter: Roman Ivanov 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks stopped work on JENKINS-50552 Change By: Michael Dirks 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-50552) Pipeline projects do not trigger libvirt VM snapshot reverts.
Title: Message Title Michael Dirks assigned an issue to Unassigned Jenkins / JENKINS-50552 Pipeline projects do not trigger libvirt VM snapshot reverts. Change By: Michael Dirks Assignee: Michael Dirks 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps I see some issues when I compare Remoting behavior (even in a single thread) to that of a freestyle build. There are Pipe.Flush es, which should not be necessary; the Pipe.Chunk s are ~200b, rather than ~4Kb; there are long sequences of ProxyOutputStream.Ack s. I suspect the problem here is not so much with the granularity of output being produced by the durable task—changing this to, say, sending a single byte array every three seconds makes no difference from the Remoting perspective, except that the burst of little commands comes only every three seconds—as that when you have any sort of console decorator using LineTransformationOutputStream (such as when using timestamps either before or after my fix), the output becomes heavily fragmented. Therefore I am considering some sort of buffering as a final wrapper before using the stream remoting offered by StreamTaskListener. 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix I have tried to involve as many plugin as possible in Jenkins and Travis. I saw XUnit related to .Net and not Java. Sorry for that. Mistakes happen the same as developers make mistakes with the XML design regarding elements /flaky and rerun. This is the chance to improve the s/w. Btw we plan to release several release candidates for version 3.0.0 and we will break backwards compatibility in API (not in XML) this time and it is because we have no choice after 15 years. There is time and milestone where we have to say that we have to break something but hopefully not everything. We are not going to create a new plugin but after 15 years it is reasonable. Nikolas, the XML and old XSD was broken. Similar changes happened in Surefire but it was not this schema. It was also with standard output stream which was broken by user's libraries and the error was uncovered in logs however the users do not like it but they had to accept that we also do not want to be responsible for "their" mistakes in their project or used external libraries. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace Michael Neale the summary was edited after the fact. 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-27413) Handle file parameters
Title: Message Title Bauyrzhan Makhambetov commented on JENKINS-27413 Re: Handle file parameters Thank you for pointing that out. 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-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title
Erez Arbell commented on JENKINS-54222
Re: p4-plugin keeps opening connection during the build. Causing long delays
Thank you Paul Allen for the quick reply. I tried "autoClean", "forceClean" and "syncOnly". The behavior is he same. How can I use the new logging feature you added? The issue here is that the p4-pluging continue to do a loop of open and close p4 connections long after it finished its task. Can you please explain the need for this? I fail to see the need for it. If there will be need to do another use of p4, then it can open the connection then. I have jobs with duration of hours and days, and I keep see this slowness. You can see it yourself, in the pipeline code in steps to reproduce above, add long sleep between the p4 command and the "stage('run')". You will see that the plugin keep connecting to the p4 server and add long time to the build duration. This is not some overhead but a big issue. I apologize. I am not familiar with the internals of Jenkins so I do not understand the last paragraph you wrote. Anyway, as you can see be the simple steps to reproduce above, when using the p4-plugin, it makes the whole run of the build to be much slower. I am talking about a constant delay of 1-10 seconds between each two command in the Jenkinsfile. We had this slowness for long time but did not know why. Now that we discovered the reason we discussed it today in the team and due to this we consider moving to git.
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-53764) Bitbucket hook registration fails with response code 400
Title: Message Title Jason Sievert commented on JENKINS-53764 Re: Bitbucket hook registration fails with response code 400 Same for me Jenkins ver. 2.138.2 BitBucket Branch Source plugin 2.2.12 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-54219) dashboard-view plugin rendering broken with 2.146
Title: Message Title Tobias Gruetzmacher commented on JENKINS-54219 Re: dashboard-view plugin rendering broken with 2.146 This is due to https://jenkins.io/blog/2018/10/10/security-updates/ - I really need to check if we can sanitize the content somehow... 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-53327) Simple Theme Plugin v0.5 - CSS rule omitted by Jelly
Title: Message Title Tobias Gruetzmacher closed an issue as Fixed Jenkins / JENKINS-53327 Simple Theme Plugin v0.5 - CSS rule omitted by Jelly Change By: Tobias Gruetzmacher Status: Resolved 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Michael Neale commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace nice to see this happening! Also what is up with the date on this ticket: create in 2008? It foretold Pipeline-as-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-54229) Vsphere plugin job fails after snapshot
Title: Message Title roberto silva created an issue Jenkins / JENKINS-54229 Vsphere plugin job fails after snapshot Issue Type: Bug Assignee: Unassigned Components: core, vsphere-cloud-plugin Created: 2018-10-24 19:11 Environment: Jenkins 2.138.2, Vsphere plug in 2.18, agent via java web start Labels: vsphere slave-agent stash Priority: Minor Reporter: roberto silva I have a Jenkins on Windows Server 2016 in a pipeline declarative i first snapshot the VM slave and it connects successfully but after i tried to run a script on the VM i get an error. This error i get // java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) Caused: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from win-7ak7b4mfh74.cfnp.local/10.160.18.202:49177 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at hudson.FilePath.act(FilePath.java:1071) at
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's{{ ModelBuilder }} to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output: {code:json}[{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }]{code}The JSON objects in the resulting array can be used directly in a pipeline:{code:json}assert currentBuild.getBuildCauses().size() == 1assert currentBuild.getBuildCauses()[0].userId == 'tester'echo currentBuild.getBuildCauses()[0].shortDescription{code}Additionally, you can filter the result of {{currentBuild.getBuildCauses()}} by passing a class (or superclass) of the type you would like to filter by. For example, to get a list of build {{Cause}}s that only contains {{Cause}}s of type {{hudson.model.Cause$UserIdCause}}, call the method like this:{code:json}echo currentBuild.getBuildCauses(hudson.model.Cause$UserIdCause).size(){code}
Add Comment
[JIRA] (JENKINS-33455) Option to disable echo of executed commands
Title: Message Title david ducker commented on JENKINS-33455 Re: Option to disable echo of executed commands I agree this makes logs so much harder to read with no added value. Unless I'm mistaken you would have to set +x for every single shell, some of my scripts have 100's. This is not an adequate workaround. 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace If anyone is interested in trying my fix for this (and other) issues, you can install this experimental build. 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-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Jesse Glick commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build My proposed patch in JENKINS-2111 fixes or at least greatly improves these issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output:{code:json}[{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }] {code} The JSON objects in the resulting array can be used directly in a pipeline:{code:json}assert currentBuild.getBuildCauses().size() == 1assert currentBuild.getBuildCauses()[0].userId == 'tester'echo currentBuild.getBuildCauses()[0].shortDescription{code}Additionally, you can filter the result of {{currentBuild.getBuildCauses()}} by passing a class (or superclass) of the type you would like to filter by. For example, to get a list of build {{Cause}}s that only contains {{Cause}}s of type {{hudson.model.Cause$UserIdCause}}, call the method like this:{code:json}echo currentBuild.getBuildCauses(hudson.model.Cause$UserIdCause).size(){code}
Add Comment
[JIRA] (JENKINS-30148) Allocate shorter workspace if it will be too long for reasonable use inside build
Title: Message Title Sander Flobbe commented on JENKINS-30148 Re: Allocate shorter workspace if it will be too long for reasonable use inside build The description assumes "4096 is the maximal path allowed on linux". However the actual limit in some cases is much (!!) smaller. As mentioned in an earlier post by Sorin Sbarnea, with a python virtualenv command you will get shebang lines that include the full path. For example my bin/pip script created by virtualenv has this shebang line: #!/usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3ODEQZACDRSHT3HA6N5UIRQXOCQQIQ/virtualenv/bin/python This results in an error in my Multibranch Pipeline job: /usr/share/tomcat/.jenkins/workspace/Waterworks_master-IAYUAOZ7D4F2MCG5DIMHAV3: bad interpreter: No such file or directory The actual cut-off point appears to be at character 80. This is on a Centos 7.5 system. Although external documentation suggests 127 as the limit with linux (and I don't understand why I am hitting a barrier at 80), both these numbers are way smaller than the implied and assumed 4096 limit in the description of this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the {{Cause}}s of a build without using the non-whitelisted {{currentBuild.getRawBuild().getCauses()}} function. An additional drawback to that approach is that is allows direct access to the actual {{Cause}} objects, which could potentially allow a malicious pipeline script to manipulate the {{Cause}} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a {{Cause}}s {{@Exported}} fields:For example, a build with a {{hudson.model.Cause$UserId}} cause produce the following output: {code:json}[ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ] {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-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the{{ Cause }} s of a build without using the non-whitelisted \ { code} { currentBuild.getRawBuild().getCauses() \{/code } } function. An additional drawback to that approach is that is allows direct access to the actual{{ Cause }} objects, which could potentially allow a malicious pipeline script to manipulate the{{ Cause }} associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a{{ Cause }} s{{ @Exported }} fields:For example, a build with a{{ hudson.model.Cause$UserId }} cause produce the following output: < { code:json > } [{ "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" }] { 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
[JIRA] (JENKINS-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-54228 xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Change By: Nikolas Falco Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54228) xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-54228 xunit fails to validate XML surefire report of Maven Surefire Plugin since version 2.22.1 Issue Type: New Feature Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-10-24 18:42 Priority: Major Reporter: Nikolas Falco During a maven build upgrading the maven-surefire-plugin to version 2.22.1 xunit is not able to validate the report if the rerun feature is enabled. Add Comment This message was sent by
[JIRA] (JENKINS-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli updated an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Change By:
mike cirioli
It is currently not possible to access the Causes of a build without using the non-whitelisted < \{ code > } currentBuild.getRawBuild().getCauses() < \{ /code > } function. An additional drawback to that approach is that is allows direct access to the actual Cause objects, which could potentially allow a malicious pipeline script to manipulate the Cause associated with an upstream build.This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a Causes @Exported fields:For example, a build with a hudson.model.Cause$UserId cause produce the following output:[ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ]
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-54227) Safely expose the Cause(s) associated with the current build
Title: Message Title
mike cirioli created an issue
Jenkins / JENKINS-54227
Safely expose the Cause(s) associated with the current build
Issue Type:
New Feature
Assignee:
mike cirioli
Components:
workflow-support-plugin
Created:
2018-10-24 18:41
Labels:
pipeline plugin
Priority:
Minor
Reporter:
mike cirioli
It is currently not possible to access the Causes of a build without using the non-whitelisted currentBuild.getRawBuild().getCauses() function. An additional drawback to that approach is that is allows direct access to the actual Cause objects, which could potentially allow a malicious pipeline script to manipulate the Cause associated with an upstream build. This jira and its associated PR propose a different approach based on the use of stapler's ModelBuilder to create a JSON representation of a Causes @Exported fields: For example, a build with a hudson.model.Cause$UserId cause produce the following output: [ { "_class":"hudson.model.Cause$UserIdCause", "shortDescription":"Started by user anonymous", "userId":"tester", "userName":"anonymous" } ]
[JIRA] (JENKINS-53927) Jenkins Build opens up multiple Chrome instances
Title: Message Title Nikolas Falco commented on JENKINS-53927 Re: Jenkins Build opens up multiple Chrome instances I do not understand steps to reproduce this bug. > chrome instances that get opened by a Jenkins build the xunit plugin does not open external programs (the same I think also the other plugins you list). Please attach the entire console log (no doc, no images just a txt file with the copy/paste of console log output) and also a little example of your jenkins job 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-53927) Jenkins Build opens up multiple Chrome instances
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53927 Jenkins Build opens up multiple Chrome instances Change By: Nikolas Falco Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco assigned an issue to Damian Szczepanik Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Assignee: Tibor Digana Damian Szczepanik 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco edited a comment on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix > [~tibor17]The fact that Jenkins plugins are parsing this XML without any problem means that they do not mind in the elements of (rerunError, rerunFailure, flakyFailure, flakyError)Not true at all, plugins like xunit use the XSD to validate the XML (and with 2.22.1 is broken, files are skipped). It's not clear for me what is the gain of the stacktrace element and make rerun elements different from failure and error. EDIT: you missed to list the component that supports flaky elements... xunit and flaky-test-handler and for this reason you did get a response in time because no one of major interested people was informed. I'm here now because the new version had broken our organisation pipelines and I got this link from SUREFIRE-1559. 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco updated an issue Jenkins / JENKINS-53237 Maven Surefire Report XSD requires a fix Change By: Nikolas Falco Component/s: flaky-test-handler-plugin Component/s: xunit-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix > Tibor DiganaThe fact that Jenkins plugins are parsing this XML without any problem means that they do not mind in the elements of (rerunError, rerunFailure, flakyFailure, flakyError) Not true at all, plugins like xunit use the XSD to validate the XML (and with 2.22.1 is broken, files are skipped). It's not clear for me what is the gain of the stacktrace element and make rerun elements different from failure and error. 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-54226) Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts
Title: Message Title Jason Axley created an issue Jenkins / JENKINS-54226 Script not approved for use exception at the end of every build log - even for jobs with no groovy scripts Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2018-10-24 18:07 Priority: Minor Reporter: Jason Axley org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use*10:39:55* at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:466)10:39:55 at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval$using$0.call(Unknown Source)10:39:55 at com.splunk.splunkjenkins.UserActionDSL.perform(UserActionDSL.groovy:41)10:39:55 at com.splunk.splunkjenkins.listeners.LoggingRunListener.onCompleted(LoggingRunListener.java:85)10:39:55 at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)10:39:55 at hudson.model.Run.execute(Run.java:1864)10:39:55 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)10:39:55 at hudson.model.ResourceController.execute(ResourceController.java:97)10:39:55 at hudson.model.Executor.run(Executor.java:429) This exception is being thrown and logged at the end of every jenkins job invocation on our server, even jobs that have 0 groovy scripts in them. Because the exception is thrown at the end of the job and appears as the last thing in the log, save for perhaps the line saying it has FAILED, this causes developers to assume that the exception is the cause of the build failure when it actually doesn't cause anything to break. There are no unapproved script or method invocations in the script approval page.
[JIRA] (JENKINS-26657) File context menu missing when installing Slave under windows with jnlp
Title: Message Title Donald Horn commented on JENKINS-26657 Re: File context menu missing when installing Slave under windows with jnlp I have the same issue with the latest version of Jenkins, this took a while to figure out for me, but I found a work around. you'll need the Jenkins Slave Configuration XML and the Agent.jar file from your Jenkins webserver, as well as the secret keys. Logon to the server with the configured slave, and navigate to the Slave Directory. Back this directory up Copy the Agent.jar to the root of this directory. this can be found by clicking the offline slave and looking at it's configuration, then you can just right click and download. Edit the Jenkins-Slave.xml Edit the below line, note that %BASE%\Slave.jar should be changed to agent.jar, and the URL should match what the Jenkins Master node is looking for if you don't know this value click on the offline slave it'll display it. ( Jenkins is case sensitive ). make sure the secret key matches the master. -Xrs -jar "%BASE%\agent.jar" -jnlpUrl http://Jenkins:port/computer/Computername/slave-agent.jnlp -secret XX Save Jenkins-Slave.xml Start the Jenkins service, it will take a couple mins to check in but should work. Please let me know if this helps. Add Comment
[JIRA] (JENKINS-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title Johnny Willemsen updated an issue Jenkins / JENKINS-54225 Using disableDeferredWipeout within pipeline job results in no deleted workspace Change By: Johnny Willemsen Environment: wsCleanup 0.36 and Jenkins ver. 2.138.2Jenkins node is Fedora 28 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-54225) Using disableDeferredWipeout within pipeline job results in no deleted workspace
Title: Message Title
Johnny Willemsen created an issue
Jenkins / JENKINS-54225
Using disableDeferredWipeout within pipeline job results in no deleted workspace
Issue Type:
Bug
Assignee:
Oliver Gondža
Components:
ws-cleanup-plugin
Created:
2018-10-24 17:34
Priority:
Minor
Reporter:
Johnny Willemsen
We are using pipeline and at the end of the pipeline we have a stage as below. We added the disableDeferredWipeout recently to make sure that all disk space of the workspace is reclaimed before the job ends. We now notice that the workspace is not deleted anymore, when we remove the disableDeferredWipeout the workspace directory is gone again. Have tried to find some logs but can't find anything. stage('Post cleanup') { step([$class: 'WsCleanup', disableDeferredWipeout: true]) } In the log we only get the message below but at the end the workspace is still there [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... [WS-CLEANUP] done
Add Comment
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Lars Bilke your issue, at least, seems related to use of the timestamps step. See the proposed patch in JENKINS-48344. I will dig into why that would cause a regression (performance was always bad). 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-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Jesse Glick commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Can this problem also result in a huge spike of the "Computer.threadPoolForRemoting" threads (like thousands of them)? I have not seen that and do not know offhand of a reason why there would be such a spike. If true, that would certainly explain other symptoms. 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-48778) JNLP not considering plain hostnames when evaluating NO_PROXY
Title: Message Title Jeff Thompson commented on JENKINS-48778 Re: JNLP not considering plain hostnames when evaluating NO_PROXY Here's a PR to re-work the no_proxy implementation: https://github.com/jenkinsci/remoting/pull/293 It should deal with this report and provide additional, new capabilities. 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-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title
Florian Ramillien edited a comment on JENKINS-54081
Re: Timestamps missing for agent-based steps in Pipeline Job 2.26
Our tests results are: * Standard JOB + Timestamper 1.8.10 => *{color:#00875a}Build OK{color}* in less than 10 mn with expected timestamp on each line * Pipeline Job without Timestamper => *{color:#00875a}Build OK{color}* in less than 10 mn * Pipeline Job + Timestamper RC 1.8.11 => *{color:#de350b}Build Reported Fail{color}* in 19 mn with expected timestamp on each line. * Pipeline Job + Timestamper RC 1.8.11 + USE_WATCHING=false => *{color:#00875a}Build OK{color}* in less than 10 mn with expected timestampI say "Reported fail" because if we look on slave, build is correct and in "durable-" directory we could see that : * job result is OK (jenkins-result.txt) * delta time between "jenkins-main.bat" and "jenkins-result.txt" is less than 10mn (expected build time). * Log file (jenkins-logs.txt) size for this step is 3.5 MoLooking further on log on Jenkins UI, I could see that pipeline end in the middle of the log and 9 mn later some more logs are displayed (but not the full logs) and job fail: **{code:java}2018-10-24 10:18:24 Some CPP compiler outputs2018-10-24 10:18:24 [Pipeline] }[Pipeline] // timestamps[Pipeline] }2018-10-24 10:27:34 Some CPP compiler outputs2018-10-24 10:27:34 [Pipeline] // sshagent Some CPP compiler outputs2018-10-24 10:27:34 Some CPP compiler outputs... many outputs lines with time stamp ...2018-10-24 10:27:34 Some CPP compiler outputsERROR: script apparently exited with code 0 but asynchronous notification was lost[ 2018-10-24T10:27:34.892ZFinished: FAILURE{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-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title
Florian Ramillien edited a comment on JENKINS-54081
Re: Timestamps missing for agent-based steps in Pipeline Job 2.26
Our tests results are: * Standard JOB + Timestamper 1.8.10 => *{color:#00875a}Build OK{color}* in less than 10 mn with expected timestamp on each line * Pipeline Job without Timestamper => *{color:#00875a}Build OK{color}* in less than 10 mn * Pipeline Job + Timestamper RC 1.8.11 => *{color:#de350b}Build Reported Fail{color}* in 19 mn with expected timestamp on each line. * Pipeline Job + Timestamper RC 1.8.11 + USE_WATCHING=false => *{color:#00875a}Build OK{color}* in less than 10 mn with expected timestampI say "Reported fail" because if we look on slave, build is correct and in "durable-" directory we could see that : * job result is OK (jenkins-result.txt) * delta time between "jenkins-main.bat" and "jenkins-result.txt" is less than 10mn (expected build time). * Log file (jenkins-logs.txt) size for this step is 3.5 MoLooking further on log on Jenkins UI, I could see that pipeline end in the middle of the log and 9 mn later some more logs are displayed (but not the full logs) and job fail: * *{code:java} 2018-10-24 10:18:24 * Some CPP compiler outputs * 2018-10-24 10:18:24 * [Pipeline] }[Pipeline] // timestamps[Pipeline] } * 2018-10-24 10:27:34 * Some CPP compiler outputs * 2018-10-24 10:27:34 * [Pipeline] // sshagent Some CPP compiler outputs * 2018-10-24 10:27:34 * Some CPP compiler outputs... many outputs lines with time stamp ... * 2018-10-24 10:27:34 * Some CPP compiler outputs ERROR: script apparently exited with code 0 but asynchronous notification was lost[ 2018-10-24T10:27:34. 892ZFinished 892ZFinished : FAILURE {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
[JIRA] (JENKINS-54081) Timestamps missing for agent-based steps in Pipeline Job 2.26
Title: Message Title Florian Ramillien commented on JENKINS-54081 Re: Timestamps missing for agent-based steps in Pipeline Job 2.26 The result is the same, yes. But I don't think the cause was the same, in our case connection with agent is working unless some specific combinaison of components: A long build with a simple task (ping during 20mn) is working A shorter build (10mn) with hudge log generated by "bat" step, fail (see previous comment). Removing "timestamps" step from pipeline fix this issue Reverting from "push" to "pull" logs in "durable-task" fix this issue too. In our case, something occurs at the end of the job between master and slave, and master never receive the "OK" result from slave (nor the full logs). And after 9mn of inactivity build fail and agent is disconnected. It's always reproduced with hudge logs, but maybe logs size is just a factor triggering another hidden synchro/lock problem. For now "USE_WATCHING=false" is set in our Jenkins master and is an acceptable solution 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-54207) Update delete plugin flow to error out for anything other than file not found
Title: Message Title Elton Alves commented on JENKINS-54207 Re: Update delete plugin flow to error out for anything other than file not found i would like to work on this issue, anyone can guide me ? im a little bit new with java, and i have only 1 PR on jenkins repo thanks 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-52165) Use push rather than pull for durable task logging
Title: Message Title Jesse Glick reopened an issue Disabling this mode in workflow-durable-task-step 2.25 until some reported issues can be tracked down and fixed. Jenkins / JENKINS-52165 Use push rather than pull for durable task logging Change By: Jesse Glick Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Swathi Gangisetty closed an issue as Not A Defect Closing issue due to inactivity. Can be reopened if the user responds back to the last comment Jenkins / JENKINS-52969 java.lang.InterruptedException: sleep interrupted Change By: Swathi Gangisetty Status: In Progress 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-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Swathi Gangisetty started work on JENKINS-52969 Change By: Swathi Gangisetty Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52969) java.lang.InterruptedException: sleep interrupted
Title: Message Title Swathi Gangisetty assigned an issue to Swathi Gangisetty Jenkins / JENKINS-52969 java.lang.InterruptedException: sleep interrupted Change By: Swathi Gangisetty Assignee: Daniel Nurmi Swathi Gangisetty 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-50586) SSH support
Title: Message Title Alon Bar-Lev commented on JENKINS-50586 Re: SSH support This is important for proper authentication, the http is weak and problematic. Thanks! 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-53946) Bitbucket plugin unable to parse a Pull Request JSON Object
Title: Message Title Roxana Muresan commented on JENKINS-53946 Re: Bitbucket plugin unable to parse a Pull Request JSON Object I have the same issue when using a Post Webhook on push with Bitbucket Server 5.13.1. I am using Bitbucket Plugin 1.1.8. (on Jenkins 2.138.2). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. 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 Sounds good. When you abort the build, it can change the stored info, so I would collect an archive of the build files prior to aborting 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-46507) Parallel Pipeline random java.lang.InterruptedException
Title: Message Title Andrew a commented on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Thanks for looking into it. Yes, I have been manually aborting the build, but already when they were stuck with the exception. I'll clean up all logs and fire up a fresh regression run this weekend with fine logging you've mentioned. Let's see if that gives us any better results. 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 Andrew a edited a comment on JENKINS-46507 Re: Parallel Pipeline random java.lang.InterruptedException Thanks for looking into it. Yes, I have been manually aborting the build, but already when they were stuck with the exception. I'll clean up all logs and fire up a fresh regression run this weekend with fine logging you've mentioned. Let's see if that gives us any better results. 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-54135) Thread unsafe behavior in UserLanguages telemetry
Title: Message Title Daniel Beck started work on JENKINS-54135 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44869) Activity tabs Run id column should expand to fit value
Title: Message Title Thorsten Scherler commented on JENKINS-44869 Re: Activity tabs Run id column should expand to fit value Reinhold Füreder are you using https://wiki.jenkins.io/display/JENKINS/Version+Number+Plugin or https://wiki.jenkins.io/display/JENKINS/Build+Name+Setter+Plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25443) Show code coverage by source file
Title: Message Title Matej Dro commented on JENKINS-25443 Re: Show code coverage by source file This would also be useful for Kotlin files containing coroutines - these usually contain lots of subclasses, similarly to groovy example from above. 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-54136) Use per-trial correlator IDs
Title: Message Title Daniel Beck updated JENKINS-54136 Jenkins / JENKINS-54136 Use per-trial correlator IDs Change By: Daniel Beck 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-54137) Do not submit empty telemetry data
Title: Message Title Daniel Beck updated JENKINS-54137 Jenkins / JENKINS-54137 Do not submit empty telemetry data Change By: Daniel Beck 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Thorsten Scherler commented on JENKINS-46715 Re: Error steps may change to show up as errors in pipeline view Reinhold Füreder to track down the root cause I would need to know what the classic UI is showing. I mean if the classic UI is showing the error but BO not then we know that it is specific to BO but if the classic UI shows the same problems then there is a general 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-54136) Use per-trial correlator IDs
Title: Message Title Daniel Beck started work on JENKINS-54136 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Oliver Pereira commented on JENKINS-54187 Re: EC2 Plugin deadlock leaving Jenkins unresponsive Oct 24, 2018 4:15:51 PM jenkins.metrics.api.Metrics$HealthChecker executeOct 24, 2018 4:15:51 PM jenkins.metrics.api.Metrics$HealthChecker executeWARNING: Some health checks are reporting as unhealthy: [thread-deadlock : [jenkins.util.Timer [#8] locked on java.util.concurrent.locks.ReentrantLock$NonfairSync@594db2a0 (owned by jenkins.util.Timer [#9]): at sun.misc.Unsafe.park(Native Method) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285) at hudson.model.Queue._withLock(Queue.java:1437) at hudson.model.Queue.withLock(Queue.java:1300) at jenkins.model.Nodes.updateNode(Nodes.java:193) at jenkins.model.Jenkins.updateNode(Jenkins.java:2080) at hudson.model.Node.save(Node.java:140) at hudson.util.PersistedList.onModified(PersistedList.java:173) at hudson.util.PersistedList.replaceBy(PersistedList.java:85) at hudson.model.Slave.(Slave.java:198) at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:138) at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:49) at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:42) at hudson.plugins.ec2.SlaveTemplate.newOndemandSlave(SlaveTemplate.java:963) at hudson.plugins.ec2.SlaveTemplate.toSlaves(SlaveTemplate.java:660) at hudson.plugins.ec2.SlaveTemplate.provisionOndemand(SlaveTemplate.java:632) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:463) at hudson.plugins.ec2.EC2Cloud.getNewOrExistingAvailableSlave(EC2Cloud.java:587) at hudson.plugins.ec2.EC2Cloud.provision(EC2Cloud.java:602) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748), jenkins.util.Timer [#9] locked on hudson.plugins.ec2.AmazonEC2Cloud@755cde3d (owned by jenkins.util.Timer [#8]): at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(CloudHelper.java:47) at
[JIRA] (JENKINS-54224) Rework all json construction
Title: Message Title
Alon Bar-Lev created an issue
Jenkins / JENKINS-54224
Rework all json construction
Issue Type:
Bug
Assignee:
lucamilanesio
Components:
gerrit-code-review-plugin
Created:
2018-10-24 15:01
Priority:
Major
Reporter:
Alon Bar-Lev
Hi, While going over the code I noticed that you use string construction for json requests to gerrit. This is highly risky as users may put special characters within the variables and alter the request to gain access to other functionality the user is authorized. For example message="\", something=\"xxx" will add 'something' to the json as own field. The code must be refactored to use jackson or any json serialization that handles proper escaping. Jackson support pojos and serialize into json, the pojo can be a simple map of Map if you do not want to have pojo per use case. Then use mapper.writeValueAsString(pojo) to construct json.
@JsonInclude(JsonInclude.Include.NON_NULL)
class C {
@JsonProperty
String property1;
@JsonProperty
String property2;
};
ObjectMapper mapper = new ObjectMapper();
C c1 = new C();
c1.property1 = "value1";
String json = mapper.writeValueasString(c1); // request
C c2 = mapper.readValue(json, C.class) // response
[JIRA] (JENKINS-54222) p4-plugin keeps opening connection during the build. Causing long delays
Title: Message Title Paul Allen commented on JENKINS-54222 Re: p4-plugin keeps opening connection during the build. Causing long delays The 'p4-plugin' runs extra commands 'p4 reconcile', 'p4 revert', etc... to cleanup and prep the workspace. This was designed to help larger code bases, but does add an overhead. Which mode are you using with 'p4sync' - 'autoClean', 'forceClean', etc... I have added some additional logging to P4Logging.java, so I can see each command and its compute time. It probably makes sense to add this to aid with debugging. Unfortunately I can't share the P4 connection across Jenkins as it spawns multiple threads. In addition the plugin requires connections for the master and slave nodes. There are a few extra 'p4 info' and 'p4 login -s' commands that are used to test long running commands; they could be optimised, but with great care. 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jakub Bochenski commented on JENKINS-54223 Re: Job configurations displayed incorrectly (raw) Jochen A. Fürbacher OK, I'll be watching the ticket, please close it when the version is released 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-54137) Do not submit empty telemetry data
Title: Message Title Daniel Beck started work on JENKINS-54137 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33003) Copy Artifacts from Another Projects Strange Behavior
Title: Message Title Sam Liddicott commented on JENKINS-33003 Re: Copy Artifacts from Another Projects Strange Behavior Not only must you specify the upstream job, you must specify it as a literal you you can't even prepare a groovy environment that computes the value. If a variable is used, the copy fails with a message indicating the actual name that it ought to have been able to copy and can copy if specified literally 07:10:26 ERROR: Unable to find project for artifact copy: blah/thingy-project 07:10:26 This may be due to incorrect project name or permission settings; see help for project name in job configuration. 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-53201) Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
Title: Message Title Alberto Morando edited a comment on JENKINS-53201 Re: Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. HiSame issue hereAny update on when the issue is solved? Configuration:Jenkins version 2.138.1 on Windows 10 Plugins listsPLUGIN VERSION -- --- _javascript_ GUI Lib: ACE Editor bundle plugin 1.1 Static Analysis Utilities 1.95 Ant Plugin 1.8 OWASP Markup Formatter Plugin 1.5 Jenkins Apache HttpComponents Client 4.x API Plugin 4.5.5-3.0 Authentication Tokens API Plugin 1.3 Autofavorite for Blue Ocean 1.2.2 Bitbucket Pipeline for Blue Ocean 1.8.4 Common API for Blue Ocean 1.8.4 Config API for Blue Ocean 1.8.4 Blue Ocean Core JS 1.8.4 Dashboard for Blue Ocean 1.8.4 Display URL for Blue Ocean 2.2.0 Events API for Blue Ocean 1.8.4 Git Pipeline for Blue Ocean 1.8.4 GitHub Pipeline for Blue Ocean 1.8.4 i18n for Blue Ocean 1.8.4 JIRA Integration for Blue Ocean 1.8.4 JWT for Blue Ocean 1.8.4 Personalization for Blue Ocean 1.8.4 Pipeline implementation for Blue Ocean 1.8.4 Blue Ocean Pipeline Editor 1.8.4 Pipeline SCM API for Blue Ocean 1.8.4 REST Implementation for Blue Ocean 1.8.4 REST API for Blue Ocean 1.8.4 Web for Blue Ocean 1.8.4 Blue Ocean 1.8.4 bouncycastle API Plugin 2.17 Branch API Plugin 2.0.20 Build Monitor View 1.12+build.201809061734Build Timeout 1.19 Bitbucket Branch Source Plugin 2.2.12 Folders Plugin 6.6 Jenkins Cobertura Plugin 1.13 Code Coverage API Plugin 1.0.5 Command Agent Launcher Plugin 1.2 Credentials Binding Plugin 1.16 Credentials Plugin 2.1.18 Display URL API 2.2.0 Docker Commons Plugin 1.13 Docker Pipeline 1.17 Durable Task Plugin 1.26 Email Extension Plugin 2.63 External Monitor Job Type Plugin 1.7 Favorite 2.3.2 Jenkins Git client plugin 2.7.3 Jenkins GIT server Plugin 1.7 Jenkins Git plugin 3.9.1 GitHub API Plugin 1.92 GitHub Branch Source Plugin 2.3.6 GitHub plugin 1.29.2 Gradle Plugin 1.29 Green Balls 1.15 _javascript_ GUI Lib: Handlebars bundle plugin 1.1.1 Handy Uri Templates 2.x API Plugin 2.1.6-1.0 HTML Publisher plugin 1.16 Jackson 2 API Plugin 2.8.11.3 Javadoc Plugin 1.4 JDK Tool Plugin 1.1 Jenkins Design Language 1.8.4 Jenkins JIRA plugin 3.0.2 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin 1.2.1 Jenkins JSch dependency plugin 0.1.54.2 JUnit Plugin 1.26.1 LDAP Plugin 1.20 Locale plugin 1.3 Lockable Resources plugin 2.3 Jenkins Mailer Plugin 1.21 MapDB API Plugin 1.0.9.0 Matrix Authorization Strategy Plugin 2.3 Matrix Project Plugin 1.13 Maven Integration plugin 3.1.2 Jenkins Mercurial plugin 2.4 _javascript_ GUI Lib: Moment.js bundle plugin 1.1.1 Monitoring 1.74.0 PAM Authentication plugin 1.4 Pipeline: Build Step 2.7 Pipeline: GitHub Groovy Libraries 1.0 Pipeline Graph Analysis Plugin 1.7 Pipeline: Input Step 2.8 Pipeline: Milestone Step 1.3.1 Pipeline: Model API 1.3.2 Pipeline: Declarative Agent API 1.1.1 Pipeline: Declarative 1.3.2 Pipeline: Declarative Extension Points API 1.3.2 Pipeline: REST API Plugin 2.10 Pipeline: Stage Step 2.3 Pipeline: Stage Tags Metadata 1.3.2 Pipeline: Stage View Plugin 2.10 Plain Credentials Plugin 1.4 Jenkins Pub-Sub "light" Bus 1.12 Resource Disposer Plugin 0.12 Role-based Authorization Strategy 2.9.0 SCM API Plugin 2.2.8 Script Security Plugin 1.46 Simple Theme Plugin 0.5.1 Server Sent Events (SSE) Gateway Plugin 1.16 SSH Credentials Plugin 1.14 Jenkins SSH Slaves plugin 1.28.1 Structs Plugin 1.15 Jenkins Subversion Plug-in 2.12.1 ThinBackup 1.9 Timestamper 1.8.10 Token Macro Plugin 2.5 Variant Plugin 1.1 Warnings Plug-in 4.68 Windows Slaves Plugin 1.3.1 Pipeline 2.5 Pipeline: API 2.29 Pipeline: Basic Steps 2.11
[JIRA] (JENKINS-53201) Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled.
Title: Message Title Alberto Morando commented on JENKINS-53201 Re: Poll SCM not triggering on any externals: svn: E200015: ISVNAuthentication provider did not provide credentials; HTTP authorization cancelled. Hi Same issue here Any update on when the issue is solved? Configuration: Jenkins version 2.138.1 Plugins lists PLUGIN VERSION -- --- _javascript_ GUI Lib: ACE Editor bundle plugin 1.1 Static Analysis Utilities 1.95 Ant Plugin 1.8 OWASP Markup Formatter Plugin 1.5 Jenkins Apache HttpComponents Client 4.x API Plugin 4.5.5-3.0 Authentication Tokens API Plugin 1.3 Autofavorite for Blue Ocean 1.2.2 Bitbucket Pipeline for Blue Ocean 1.8.4 Common API for Blue Ocean 1.8.4 Config API for Blue Ocean 1.8.4 Blue Ocean Core JS 1.8.4 Dashboard for Blue Ocean 1.8.4 Display URL for Blue Ocean 2.2.0 Events API for Blue Ocean 1.8.4 Git Pipeline for Blue Ocean 1.8.4 GitHub Pipeline for Blue Ocean 1.8.4 i18n for Blue Ocean 1.8.4 JIRA Integration for Blue Ocean 1.8.4 JWT for Blue Ocean 1.8.4 Personalization for Blue Ocean 1.8.4 Pipeline implementation for Blue Ocean 1.8.4 Blue Ocean Pipeline Editor 1.8.4 Pipeline SCM API for Blue Ocean 1.8.4 REST Implementation for Blue Ocean 1.8.4 REST API for Blue Ocean 1.8.4 Web for Blue Ocean 1.8.4 Blue Ocean 1.8.4 bouncycastle API Plugin 2.17 Branch API Plugin 2.0.20 Build Monitor View 1.12+build.201809061734 Build Timeout 1.19 Bitbucket Branch Source Plugin 2.2.12 Folders Plugin 6.6 Jenkins Cobertura Plugin 1.13 Code Coverage API Plugin 1.0.5 Command Agent Launcher Plugin 1.2 Credentials Binding Plugin 1.16 Credentials Plugin 2.1.18 Display URL API 2.2.0 Docker Commons Plugin 1.13 Docker Pipeline 1.17 Durable Task Plugin 1.26 Email Extension Plugin 2.63 External Monitor Job Type Plugin 1.7 Favorite 2.3.2 Jenkins Git client plugin 2.7.3 Jenkins GIT server Plugin 1.7 Jenkins Git plugin 3.9.1 GitHub API Plugin 1.92 GitHub Branch Source Plugin 2.3.6 GitHub plugin 1.29.2 Gradle Plugin 1.29 Green Balls 1.15 _javascript_ GUI Lib: Handlebars bundle plugin 1.1.1 Handy Uri Templates 2.x API Plugin 2.1.6-1.0 HTML Publisher plugin 1.16 Jackson 2 API Plugin 2.8.11.3 Javadoc Plugin 1.4 JDK Tool Plugin 1.1 Jenkins Design Language 1.8.4 Jenkins JIRA plugin 3.0.2 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin 1.2.1 Jenkins JSch dependency plugin 0.1.54.2 JUnit Plugin 1.26.1 LDAP Plugin 1.20 Locale plugin 1.3 Lockable Resources plugin 2.3 Jenkins Mailer Plugin 1.21 MapDB API Plugin 1.0.9.0 Matrix Authorization Strategy Plugin 2.3 Matrix Project Plugin 1.13 Maven Integration plugin 3.1.2 Jenkins Mercurial plugin 2.4 _javascript_ GUI Lib: Moment.js bundle plugin 1.1.1 Monitoring 1.74.0 PAM Authentication plugin 1.4 Pipeline: Build Step 2.7 Pipeline: GitHub Groovy Libraries 1.0 Pipeline Graph Analysis Plugin 1.7 Pipeline: Input Step 2.8 Pipeline: Milestone Step 1.3.1 Pipeline: Model API 1.3.2 Pipeline: Declarative Agent API 1.1.1 Pipeline: Declarative 1.3.2 Pipeline: Declarative Extension Points API 1.3.2 Pipeline: REST API Plugin 2.10 Pipeline: Stage Step 2.3 Pipeline: Stage Tags Metadata 1.3.2 Pipeline: Stage View Plugin 2.10 Plain Credentials Plugin 1.4 Jenkins Pub-Sub "light" Bus 1.12 Resource Disposer Plugin 0.12 Role-based Authorization Strategy 2.9.0 SCM API Plugin 2.2.8 Script Security Plugin 1.46 Simple Theme Plugin 0.5.1 Server Sent Events (SSE) Gateway Plugin 1.16 SSH Credentials Plugin 1.14 Jenkins SSH Slaves plugin 1.28.1 Structs Plugin 1.15 Jenkins Subversion Plug-in 2.12.1 ThinBackup 1.9 Timestamper 1.8.10 Token Macro Plugin 2.5 Variant Plugin 1.1 Warnings Plug-in
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Holger Sunke commented on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Although marked as duplicate of a fixed issue, this is still not fixed in enviniject 2.1.6, jenkins 2.148 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-50429) Shell command are really slower than before
Title: Message Title Carlos Sanchez commented on JENKINS-50429 Re: Shell command are really slower than before can't you just collapse your shell commands? sh """ cmd1 cmd2 """ 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-53888) Batch step running on a node other than the master fails
Title: Message Title Jesse Glick commented on JENKINS-53888 Re: Batch step running on a node other than the master fails For what it is worth, I am unable to reproduce any such issue with a Windows 10 agent running a simple bat script. Possibly there are special conditions triggering 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-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 What information do you need, logs etc.? Jenkins system log, HTTP access log, client side HTTP log (e.g. har) 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jochen A. Fürbacher commented on JENKINS-54223 Re: Job configurations displayed incorrectly (raw) Jakub Bochenski: Thanks for reporting this issue. We already fixed this and looking forward to release a fixed version soon. 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jakub Bochenski Related to JENKINS-53819The diff displays correctly in 2.18.2 but using XML/raw output still shows escaped entities instead !Screenshot_20181024_150825.png |thumbnail ! 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jakub Bochenski Environment: Jenkins 2.138. 1 2 , Job Configuration History Plugin 2.18.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jakub Bochenski Related to JENKINS-53819The diff displays correctly in 2.18.2 but using XML/raw output still shows escaped entities instead !Screenshot_20181024_150825.png|thumbnail! 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-54223) Job configurations displayed incorrectly (raw)
Title: Message Title Jakub Bochenski updated an issue Jenkins / JENKINS-54223 Job configurations displayed incorrectly (raw) Change By: Jakub Bochenski Attachment: Screenshot_20181024_150825.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-53819) Job configurations displayed incorrectly
Title: Message Title Jakub Bochenski commented on JENKINS-53819 Re: Job configurations displayed incorrectly Created JENKINS-54223 about 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.
