[JIRA] (JENKINS-50410) Periods of high load cause "Invalid virtual machine image" exceptions
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50410 Periods of high load cause "Invalid virtual machine image" exceptions Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-03-26 16:34 Priority: Critical Reporter: R. Tyler Croy Periods of high usage (in this case on ci.jenkins.io) result in the ARM APIs apparently throttiling requests from the plugin, leading to these incorrect "invalid virtual machine image" exceptions. For the record, we're using 100% stock virtual machines, so these just appear to be poorly handled exceptions by the plugin Mar 26, 2018 2:45:42 PM SEVERE com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createStorageAccount The request is being throttled. Mar 26, 2018 2:45:42 PM SEVERE com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate createDeployment AzureVMManagementServiceDelegate: deployment: Unable to deploy com.microsoft.azure.vmagent.exceptions.AzureCloudException: Failed to create storage account with account name jnju95mbzq9arxtjl19kvjma, location eastus, resourceGroupName jenkinsinfra-agents: The request is being throttled. at com.microsoft.azure.vmagent.exceptions.AzureCloudException.create(AzureCloudException.java:49) at com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate.createStorageAccount(AzureVMManagementServiceDelegate.java:2254) at com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate.createDeployment(AzureVMManagementServiceDelegate.java:210) at com.microsoft.azure.vmagent.AzureVMManagementServiceDelegate.createDeployment(AzureVMManagementServiceDelegate.java:167) at com.microsoft.azure.vmagent.AzureVMAgentTemplate.provisionAgents(AzureVMAgentTemplate.java:807) at com.microsoft.azure.vmagent.AzureVMCloud$3.call(AzureVMCloud.java:790) at
[JIRA] (JENKINS-50409) Flexible Publish Plugin does not list 'Execute Shell' as an 'Action'
Title: Message Title
Eric Wallengren created an issue
Jenkins / JENKINS-50409
Flexible Publish Plugin does not list 'Execute Shell' as an 'Action'
Issue Type:
Bug
Assignee:
bap
Components:
flexible-publish-plugin
Created:
2018-03-26 16:31
Environment:
Ubuntu 16.04.3 Jenkins 2.107.1 Flexible Publish Plugin 0.15.2
Priority:
Minor
Reporter:
Eric Wallengren
When using the UI to create or edit a job, the flexible publish plugin does not list 'Execute Shell' as an action, however when creating a job using DSL, 'Execute Shell' (steps->shell) is a valid action, and the resulting output does show 'Execute Shell'. This DSL works: freeStyleJob('thisworks') { wrappers { timestamperBuildWrapper() } steps { shell("ps -ef") } publishers { flexiblePublish { conditionalAction { condition { alwaysRun() } runner('Run') steps { shell("ps -ef") } } } } }
Add Comment
[JIRA] (JENKINS-42623) PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view"
Title: Message Title Karl Wirth commented on JENKINS-42623 Re: PerforceScm(pipeline) checkout fails with "hudson.AbortException: P4: invalid client view" Hi boris avney. Can you please put the working text here please? I'd like to check if we have a bug. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Vivek Pandey commented on JENKINS-50406 Re: "Triggered Build" links broken with cloudbees-folder Joshua Hoblitt Thanks for reporting. Josh McDonald Looks like a bug in how run details url is constructed for downstream jobs. PTAL. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-50406 "Triggered Build" links broken with cloudbees-folder Change By: Vivek Pandey Sprint: Blue Ocean 1.5 - beta 3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49810) Define the evergreen-client -> status service API contract
Title: Message Title R. Tyler Croy stopped work on JENKINS-49810 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50385) Jenkins Cloud Foundry plugin error: Organization does not exist
Title: Message Title Muthuganesh Gnanasekar started work on JENKINS-50385 Change By: Muthuganesh Gnanasekar Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50385) Jenkins Cloud Foundry plugin error: Organization does not exist
Title: Message Title Muthuganesh Gnanasekar stopped work on JENKINS-50385 Change By: Muthuganesh Gnanasekar Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50408) Highlight difficult to see for grey pipelines
Title: Message Title Keith Zantow created an issue Jenkins / JENKINS-50408 Highlight difficult to see for grey pipelines Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-26 16:05 Priority: Minor Reporter: Keith Zantow Feedback from Gitter, Craig Rodrigues: for the circles displayed for each stage in the pipeline there are 4 colors 1. green = a stage has completed successfully 2. red = a stage has failed 3. blue = a stage is in progress 4 . dark grey highlighted circle = I clicked on the stage in UI for color 4., I would request that the visual clue that the stage has been selected be made more clear. When I have about 15 stages displayed on the screen, the dark grey highlight is difficult to see Add Comment
[JIRA] (JENKINS-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title Oleg Nenashev edited a comment on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Created a backporting PR: https:// issues github . com/jenkinsci/ jenkins -ci.org / browse pull / JENKINS-50237 3372 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title Oleg Nenashev commented on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Created a backporting PR: https://issues.jenkins-ci.org/browse/JENKINS-50237 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza started work on JENKINS-50405 Change By: Raul Arabaolaza Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza updated JENKINS-50405 Jenkins / JENKINS-50405 runATH leads to deadlock of resource consumption for core PR builds Change By: Raul Arabaolaza Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Vivek Pandey assigned an issue to Josh McDonald Jenkins / JENKINS-50406 "Triggered Build" links broken with cloudbees-folder Change By: Vivek Pandey Assignee: Josh McDonald Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Mark Waite resolved as Not A Defect Thanks for the investigation! Jenkins / JENKINS-50369 Missing git variables from the per-job "Environment Variables" page Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter edited a comment on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page I found that the the different is the build-step 'Inject environment variables' cause the git variables to show appear on the list. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter commented on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page I found the the different is the build-step 'Inject environment variables' cause the git variables to show appear on the list. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Paul Dragoonis Attachment: Screen Shot 2018-03-23 at 13.38.17.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50407) NPE from SandboxContinuable.run0 after restart
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50407 NPE from SandboxContinuable.run0 after restart Issue Type: Bug Assignee: Unassigned Components: workflow-cps-plugin Created: 2018-03-26 15:31 Priority: Minor Reporter: Jesse Glick In this build I observed ... Running in Durability level: PERFORMANCE_OPTIMIZED ... Resuming build at ... after Jenkins restart [Pipeline] End of Pipeline GitHub has been notified of this commit's build result java.lang.NullPointerException at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:43) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:331) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$200(CpsThreadGroup.java:82) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:243) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:231) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:64) at ... Finished: FAILURE The flow graph is also missing. Not sure what happened here.
[JIRA] (JENKINS-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Paul Dragoonis This functionality is said to be RESOLVED in the blue ocean 1.2 sprint: https://issues.jenkins-ci.org/browse/JENKINS-39628 I already have these plugins installed: Pipeline API - 2.26 Pipeline: Declarative - 1.2.7 Blue Ocean 1.4.2 Pipeline Graph Analysis Plugin 1.6 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Paul Dragoonis This functionality is said to be RESOLVED in the blue ocean 1.2 sprint: https://issues.jenkins-ci.org/browse/JENKINS-39628 I already have these plugins installed: Pipeline API - 2.26 Pipeline: Declarative - 1.2.7 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Joshua Hoblitt created an issue Jenkins / JENKINS-50406 "Triggered Build" links broken with cloudbees-folder Issue Type: Bug Assignee: Unassigned Attachments: Screenshot from 2018-03-26 08-24-02.png, Screenshot from 2018-03-26 08-24-12.png Components: blueocean-plugin Created: 2018-03-26 15:26 Environment: jenkins core 2.89.4 LTS blueocean 1.5.0-beta-2 Priority: Critical Reporter: Joshua Hoblitt The links to triggered builds are broken, at least when using cloudbees-folder (did not test with jobs at the "root"). It looks like the job portion of the URL path is not being escaped. Add Comment
[JIRA] (JENKINS-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-50405 runATH leads to deadlock of resource consumption for core PR builds Change By: R. Tyler Croy Component/s: essentials Sprint: Essentials - Milestone 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds So, after a talk with R. Tyler Croy we are not going to disable this yet, I am going to start to think in a better way to orchestrate nodes so I can minimize resource contention, seems like it has been properly running all week and the problem was triggered by a bunch of very quick merges into core Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50001) Global PTC settings not saved to JEP-200 changes
Title: Message Title Oleg Nenashev updated JENKINS-50001 It has been released in version 2.2 Jenkins / JENKINS-50001 Global PTC settings not saved to JEP-200 changes Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50376) New Item sidebar link is not working
Title: Message Title Daniel Beck commented on JENKINS-50376 Re: New Item sidebar link is not working If it's visible, it's not a permission issue. My first guess is a CSS/rendering problem. Check to see whether the link is overlapped by other elements. Do you use Simple Theme Plugin or similar? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-46255) Windows Slave Plugin to support SMB Version 2 or greater
Title: Message Title Stanislav Z commented on JENKINS-46255 Re: Windows Slave Plugin to support SMB Version 2 or greater I fixed issue by these commands in Windows Server 2012, start powershell as admin and run: Enable-WindowsOptionalFeature -Online -FeatureName smb1protocol Set-SmbServerConfiguration -EnableSMB1Protocol $true Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title Raul Arabaolaza commented on JENKINS-50405 Re: runATH leads to deadlock of resource consumption for core PR builds So, as a quick fix, I am going to create a quick PR to just do not run the ath for the moment. As a better solution, I have to find a way to liberate the "linux" node while is waiting for the docker ones if possible and if not just make sure the full runATH is executed on docker& Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title Maxfield Stewart commented on JENKINS-50393 Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable Confirmed this happens for us as well with 1.8.7 and we had to downgrade to 1.8.6. It would appear that folder paths, in particular, are not escaped properly in the workspace name (but still escape properly in the client spec). Workspace names are not properly converting the job_name of a folder, which will have a path style syntax with "/" for folder breaks, into "-" hyphen's which was the traditional behavior. It still works for the clientspec however. This effectively breaks anyone using jobs in folders. For us this occurred trying to load global libraries for a pipeline in the folder global library config, but we can repro it at the job level as well. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50291) Customize where AsyncPeriodicWork are logged
Title: Message Title Jesse Glick commented on JENKINS-50291 Re: Customize where AsyncPeriodicWork are logged Maybe better done via JENKINS-38313. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50403) Single agent limit allows for an inadvertent denial-of-services
Title: Message Title pjdarton commented on JENKINS-50403 Re: Single agent limit allows for an inadvertent denial-of-services FYI this kind of "per template limit" functionality is present on other cloud plugins, e.g. Docker, OpenStack, vSphere. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50405) runATH leads to deadlock of resource consumption for core PR builds
Title: Message Title
R. Tyler Croy created an issue
Jenkins / JENKINS-50405
runATH leads to deadlock of resource consumption for core PR builds
Issue Type:
Bug
Assignee:
Raul Arabaolaza
Components:
acceptance-test-harness
Created:
2018-03-26 14:28
Priority:
Major
Reporter:
R. Tyler Croy
This weekend we experienced a denial-of-service on ci.jenkins.io due to this resource contention caused by the runATH step in the core Jenkinsfile. Basically, an executor on the "linux" label was occupied while blocking and waiting for an executor on "docker&". When Jenkins couldn't provision "highmem" due to capacity issues, the runATH step blocks the "linux" executor indefinitely. At the bottom of the Jenkinsfile for core, is some code along these lines:
node('linux') {
/* some setup */
runAth()
}
In runATH(), the first ensureInNode statement ensure that the Pipeline only uses on node, since the execution is already in a "linux" NODE_LABEL. When the second ensureInNode executes, it's attempting to ensure that the execution is in docker&, which it is of course not. This causes Pipeline to block waiting for this node, while occupying the outer "linux" node declaration. This is kind of a big problem and will cause additional resource contention whenever more than one or two core PRs are merged in quick succession.
[JIRA] (JENKINS-50404) Local Client configuration does not work with projects that are not named project.pj
Title: Message Title Florian Bamberg created an issue Jenkins / JENKINS-50404 Local Client configuration does not work with projects that are not named project.pj Issue Type: Bug Assignee: PTC ALM Components: integrity-plugin Created: 2018-03-26 14:27 Environment: PTC Integrity Plugin V2.1 Jenkins 2.60.1 Priority: Blocker Reporter: Florian Bamberg When trying to run the local Client Integration with a PTC Integrity Project that is not named "project.pj" Jenkins always throws the following error: for : #p=/Test/Test.pj Preparing to execute si projectinfo for #p=/Test/Test.pj [LocalClient] Executing Sandbox Verification [LocalClient] Executing si sandboxes [LocalClient] si sandboxes response:0 [LocalClient] Searching Sandbox: : D:\workspace\TestPTCLocalClient, for Project Config: [/Test/Test.pj], Build Revision: [null] [LocalClient] Sandbox not found in : D:\workspace\TestPTCLocalClient, for Project Config: [/Test/Test.pj], Build Revision: [null] [LocalClient] Executing CreateSandbox D:\workspace\TestPTCLocalClient [LocalClient] CreateSandbox response:0 [LocalClient] Clean Copy Requested :true [LocalClient] Starting Resync Task.. [LocalClient] Executing IntegrityResyncSandboxTask D:\workspace\TestPTCLocalClient [LocalClient] Executing ResyncSandbox D:\workspace\TestPTCLocalClient [LocalClient] IntegrityResyncSandboxTask invoke Exception :MKS125216: The sandbox file d:\workspace\TestPTCLocalClient\project.pj is not registered with the system. hudson.AbortException: [Local Client] Failed to resync Workspace! When switching to Server Integration Point it works as designed. This way the local Client configuration is not usable.
[JIRA] (JENKINS-49151) Post FOSDEM 2018 Jenkins Hackfest
Title: Message Title Mark Waite commented on JENKINS-49151 Re: Post FOSDEM 2018 Jenkins Hackfest The git client plugin JGit improvements I made with Christian Halstrick need code review, but that doesn't need an epic to track it. Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/META-INF/hudson.remoting.ClassFilter http://jenkins-ci.org/commit/pipeline-utility-steps-plugin/de62daf08bbc43717ceac4c4c36f707b4fd48903 Log: JENKINS-50237 - Apply workaround while Jenkins Core is not fixed/backported Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50237) [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50237 Re: [JEP-200] java.lang.SecurityException: Rejected: org.apache.tools.ant.Location Code changed in jenkins User: Robert Sandell Path: src/main/resources/META-INF/hudson.remoting.ClassFilter http://jenkins-ci.org/commit/pipeline-utility-steps-plugin/1d30c48f88b28334ad84e929d23f15dbb2ef0198 Log: Merge pull request #44 from oleg-nenashev/JENKINS-50237 JENKINS-50237 - Apply workaround while Jenkins Core is not fixed/backported Compare: https://github.com/jenkinsci/pipeline-utility-steps-plugin/compare/2a9ba4b6632e...1d30c48f88b2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49151) Post FOSDEM 2018 Jenkins Hackfest
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-49151 Post FOSDEM 2018 Jenkins Hackfest Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49151) Post FOSDEM 2018 Jenkins Hackfest
Title: Message Title Oleg Nenashev commented on JENKINS-49151 Re: Post FOSDEM 2018 Jenkins Hackfest +1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50251) Rejected: org.apache.maven.model.Notifier
Title: Message Title Oleg Nenashev commented on JENKINS-50251 Re: Rejected: org.apache.maven.model.Notifier thanks for catching it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49151) Post FOSDEM 2018 Jenkins Hackfest
Title: Message Title Jesse Glick commented on JENKINS-49151 Re: Post FOSDEM 2018 Jenkins Hackfest Since there is nothing in this epic, can it be closed? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50251) Rejected: org.apache.maven.model.Notifier
Title: Message Title Rainer Frey commented on JENKINS-50251 Re: Rejected: org.apache.maven.model.Notifier This fix triggers a NullPointerException in certain circumstances. Please see https://github.com/jenkinsci/maven-plugin/pull/116 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50403) Single agent limit allows for an inadvertent denial-of-services
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50403 Single agent limit allows for an inadvertent denial-of-services Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-03-26 14:14 Priority: Minor Reporter: R. Tyler Croy We found ourselves in a very interesting position this morning on ci.jenkins.io! We have a "Max Jenkins Agents limit" set to 50, and it turns out that when an influx of one type of Pipeline comes in, and requests an Agent matching a specific label, a denial of service can occur for other Pipelines which require other labels. For example, if a pull request is merged on a repository which has 60 open pull requests, 60 new builds will (correctly) be queued. If those Pipelines are poorly configured, or run for an exceedingly long time, then a denial of service will occur for all other Pipelines on the system. I would propose a solution would be to include optional per-template limits which ensure that no more than X of a specific template can be provisioned in the system Add Comment
[JIRA] (JENKINS-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis updated an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Paul Dragoonis This functionality is said to be RESOLVED in the blue ocean 1.2 sprint: https://issues.jenkins-ci.org/browse/JENKINS-39628 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50241) Add Maven details tab to build result page
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50241 Re: Add Maven details tab to build result page Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/help-generatedArtifacts.html jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenReport/index.jelly http://jenkins-ci.org/commit/pipeline-maven-plugin/c099e026db3d4c6d31b0e0c926ae91d9565d15a3 Log: JENKINS-50241 Add "dependencies" on the Maven details screen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49227) Cannot configure findbugs reporter to mark build as unstable for findbugs failures
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49227 Re: Cannot configure findbugs reporter to mark build as unstable for findbugs failures Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/AbstractHealthAwarePublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher.java jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/AbstractHealthAwarePublisher/health.jelly jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/FindbugsAnalysisPublisher/config.jelly jenkins-plugin/src/main/webapp/images/16x16/health-00to19.gif jenkins-plugin/src/main/webapp/images/16x16/health-80plus.gif http://jenkins-ci.org/commit/pipeline-maven-plugin/c4a00f6a641c7378dd01a720126b2e1316d1a1c1 Log: JENKINS-49227 Add healthy/unhealthy thresholds to the FindBugs publisher Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50336) Optional extensions are not picked up after installing the optional dependency
Title: Message Title Vincent Latombe started work on JENKINS-50336 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50336) Optional extensions are not picked up after installing the optional dependency
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-50336 Optional extensions are not picked up after installing the optional dependency Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50336) Optional extensions are not picked up after installing the optional dependency
Title: Message Title Vincent Latombe updated JENKINS-50336 Jenkins / JENKINS-50336 Optional extensions are not picked up after installing the optional dependency Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor updated an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Change By: Alex Taylor Attachment: image001.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50402) When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-50402 When building a downstream job in Blue Ocean it would great to have a link in the image of the branch to the downstream job Issue Type: Bug Assignee: Unassigned Attachments: image001.png Components: blueocean-plugin Created: 2018-03-26 13:43 Priority: Minor Reporter: Alex Taylor Problem: When a pipeline builds a downstream job, there is not an easy way inside of blue ocean to navigate to that job(you have to go to the console log of the build and then click the downstream build link) Idea: It would be great if we could have a link in the pipeline flow UI(see attached) where the build link would either be clickable or there would be a new sub arrow which would give the downstream build links. Add Comment
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title
Rafael Pestano edited a comment on JENKINS-48379
Re: Input/parameters for Stages
Alright, got it working, the pipeline must run with agent 'none' and then each stage must declare it's agent:{noformat}pipeline { agent none //importanttools { maven 'Maven 3.3.9' jdk 'jdk1.8' }stages {stage("Build") { agent anysteps {sh 'mvn clean package'}} stage("Ir para produção?") {input {message "Aprovar o deploy?"ok "Sim"}agent any //must be declared after input directivesteps { deploy ambiente: 'DES-7.0', grupo: 'APM' }} }//end stages } {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-48379) Input/parameters for Stages
Title: Message Title
Rafael Pestano edited a comment on JENKINS-48379
Re: Input/parameters for Stages
Alright, got it working, the pipeline must run with agent 'none' and then each stage must declare it's agent: {noformat}pipeline { agent none //important tools { maven 'Maven 3.3.9' jdk 'jdk1.8' }stages {stage("Build") { agent { any label 'master'} steps {sh 'mvn clean package'}} stage("Ir para produção?") {input {message "Aprovar o deploy?"ok "Sim"}agent { any //must be declared after input directive label 'master'} steps { deploy ambiente: 'DES-7.0', grupo: 'APM' }} }// fim end stages } {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Mark Waite commented on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page Any idea when the last version was that showed those environment variables in that page? I'm not aware of any changes in the git plugin that would result in such a change in the environment variables page. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48379) Input/parameters for Stages
Title: Message Title
Rafael Pestano commented on JENKINS-48379
Re: Input/parameters for Stages
Alright, got it working, the pipeline must run with agent 'none' and then each stage must declare it's agent:
pipeline {
agent none
tools {
maven 'Maven 3.3.9'
jdk 'jdk1.8'
}
stages {
stage("Build") {
agent {
label 'master'
}
steps {
sh 'mvn clean package'
}
}
stage("Ir para produção?") {
input {
message "Aprovar o deploy?"
ok "Sim"
}
agent {
label 'master'
}
steps {
deploy ambiente: 'DES-7.0', grupo: 'APM'
}
}
}//fim stages
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter edited a comment on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page It was because my jobs didn't use job-sciprt shows that the variables were empty , so I was looking for the list to check if they where set, because in the past they where listed !envVars2.PNG!But in the now it shows that I access the variables wrong. Every thing works as expected, except of the view as you find out.If I change jobs and something went wrong with variables this is one of my first point to look at. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48379) Input/parameters for Stages
Title: Message Title
Rafael Pestano edited a comment on JENKINS-48379
Re: Input/parameters for Stages
Hi guys, I'm using pipeline decçarative (and pipeline model api) v1.2.7 and am using the input directive on a stage like below:{noformat}pipeline { agent anytools { maven 'Maven 3.3.9' jdk 'jdk1.8' }stages {stage("Build") {steps {sh 'mvn clean package'}} stage("Ir para produção?") {input {message "Aprovar o deploy?"ok "Sim"}agent {label 'master'}steps {deploy ambiente: 'DES-7.0', grupo: 'APM'}} }//fim stages } {noformat}but a Jenkins executor is being alocated. I thought this issue would fix this. IOn In image "agent-blocked.png" attached you can see a job queued (waiting for executor) and one executing the pipeline above (waiting for manual approval). !agent-blocked.png|thumbnail! Jenkins v2.89.3Pipeline declarative v1.2.7
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Tomas Bjerre assigned an issue to Unassigned Jenkins / JENKINS-45930 Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Change By: Tomas Bjerre Assignee: Tomas Bjerre Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-48379) Input/parameters for Stages
Title: Message Title
Rafael Pestano commented on JENKINS-48379
Re: Input/parameters for Stages
Hi guys, I'm using pipeline decçarative (and pipeline model api) v1.2.7 and am using the input directive on a stage like below:
pipeline {
agent any
tools {
maven 'Maven 3.3.9'
jdk 'jdk1.8'
}
stages {
stage("Build") {
steps {
sh 'mvn clean package'
}
}
stage("Ir para produção?") {
input {
message "Aprovar o deploy?"
ok "Sim"
}
agent {
label 'master'
}
steps {
deploy ambiente: 'DES-7.0', grupo: 'APM'
}
}
}//fim stages
}
but a Jenkins executor is being alocated. I thought this issue would fix this. IOn image "agent-blocked.png" attached you can see a job queued (waiting for executor) and one executing the pipeline above (waiting for manual approval). Jenkins v2.89.3 Pipeline declarative v1.2.7
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-48379) Input/parameters for Stages
Title: Message Title Rafael Pestano updated an issue Jenkins / JENKINS-48379 Input/parameters for Stages Change By: Rafael Pestano Attachment: agent-blocked.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter edited a comment on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page It was because my jobs didn't use the variables, so I was looking for the list to check if they where set, because in the past they where listed !envVars2.PNG!But in the now it shows that I access the variables wrong. Every thing works as expected, except of the view as you find out. If I change jobs and something went wrong with variables this is one of my first point to look at. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter updated an issue Jenkins / JENKINS-50369 Missing git variables from the per-job "Environment Variables" page Change By: Tim Schlüter Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter commented on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page It was because my jobs didn't use the variables, so I was looking for the list to check if they where set, because in the past they where listed But in the now it shows that I access the variables wrong. Every thing works as expected, except of the view as you find out. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Tim Schlüter updated an issue Jenkins / JENKINS-50369 Missing git variables from the per-job "Environment Variables" page Change By: Tim Schlüter Attachment: envVars2.PNG Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50371) JIRA PIPELINE jiraSearch() finds max 50 items
Title: Message Title Radek Antoniuk commented on JENKINS-50371 Re: JIRA PIPELINE jiraSearch() finds max 50 items Thanks Julian for noticing this, looks like an inconsistent oversight. Do you think you could provide a PR for this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Matej Kenda updated an issue Jenkins / JENKINS-45930 Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Change By: Matej Kenda Attachment: CodeNarc-Report.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50400) Build error for PRQA (build environment)
Title: Message Title Oleg Nenashev commented on JENKINS-50400 Re: Build error for PRQA (build environment) Please reach out to the plugin maintainers or to PRQA support. I won't be triaging issues for this plugin since mentors are not responsive in JIRA. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Mark Waite commented on JENKINS-50369 Re: Missing git variables from the per-job "Environment Variables" page The picture of the environment variables screen was the key item. I've never used that page to see the environment variables which were set during the job. The git plugin injects environment variables into the job but does not inject them in such a way that they are visible in that page. My example job shows that the environment variables are set by the plugin and are usable by "bat", "shell" and "cross-platform shell" steps. However, my "Environment Variables" page for each job does not show those variables. Since the URL to that environment variables page is called "injectedEnvVars", I assume the git plugin is adding environment variables to the job by a different technique than other plugins. Can you describe your use case more deeply? Are you reading the values of those environment variables from a program later? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50400) Build error for PRQA (build environment)
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-50400 Build error for PRQA (build environment) Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50401) Checkout resolution misbehaves with local branch and forward slashes
Title: Message Title
Stephan Hauser created an issue
Jenkins / JENKINS-50401
Checkout resolution misbehaves with local branch and forward slashes
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-03-26 12:59
Environment:
Jenkins 2.107.1, git-plugin 2.7.1
Priority:
Minor
Reporter:
Stephan Hauser
If the git plugin uses a local branch which is named the same as the remote and contains a forward slash, it will cause the checkout command to not update to the latest commit. Since using branches with / is common and local branch might be necessary, this should be fixed or at least produce a warning. To test: Create the following pipeline:
node {
stage ('hello') {
dir ('foo') {
checkout([$class: 'GitSCM', branches: [[name: "foo/bar"]], extensions: [[$class: 'LocalBranch', localBranch: 'foo/bar']], userRemoteConfigs: [[credentialsId: '...', url: "..."]]])
}
}
}
And follow these steps:
Push branch foo/bar
Run pipeline
Push branch foo/bar with new versions
Re-run pipeline in same folder
The output should have the following contents:
[JIRA] (JENKINS-50400) Build error for PRQA (build environment)
Title: Message Title Priyanga G created an issue Jenkins / JENKINS-50400 Build error for PRQA (build environment) Issue Type: Bug Assignee: Oleg Nenashev Components: prqa-plugin Created: 2018-03-26 12:57 Priority: Minor Reporter: Priyanga G While creating project for PRQA,I have create a build environment but in the build environment error showing Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50369) Missing git variables from the per-job "Environment Variables" page
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-50369 Missing git variables from the per-job "Environment Variables" page Change By: Mark Waite Summary: Missing git environment variable variables from the per-job "Environment Variables" page Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title
Matej Kenda edited a comment on JENKINS-45930
Re: Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
I get the same problem with Codenarc 1.1 and Jenkins 2.112.This is the piece of the code to publich publish CodeNarc results:{code:java}warnings( [canComputeNew: false,canResolveRelativePaths: false,parserConfigurations: [[parserName: 'Codenarc', pattern: 'target/CodeNarc-Report.xml']],useDeltaValues: true,useStableBuildAsReference: true] ){code}Shall a sample codenarc file also help?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google 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-45930) Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Matej Kenda updated an issue Jenkins / JENKINS-45930 Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Change By: Matej Kenda Summary: Pipeline: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50396) no Join Trigger can be added. org.apache.commons.jelly.JellyTagException
Title: Message Title Michael Ebi commented on JENKINS-50396 Re: no Join Trigger can be added. org.apache.commons.jelly.JellyTagException Oleg Neashev, The Mailer Plugin is installed in Version 1.20. That was the first i did check Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45385) currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven)
Title: Message Title carlspring commented on JENKINS-45385 Re: currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven) Hi! When could we get some response on this issue? Is anybody looking into it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Paul Dragoonis created an issue Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-26 12:23 Priority: Major Reporter: Paul Dragoonis Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-45930) Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException)
Title: Message Title Matej Kenda commented on JENKINS-45930 Re: Warnings Plugin fails with CodeNarc XML report (java.io.NotSerializableException) I get the same problem with Codenarc 1.1 and Jenkins 2.112. This is the piece of the code to publich CodeNarc results: warnings( [ canComputeNew: false, canResolveRelativePaths: false, parserConfigurations: [ [parserName: 'Codenarc', pattern: 'target/CodeNarc-Report.xml'] ], useDeltaValues: true, useStableBuildAsReference: true ] ) Shall a sample codenarc file also help? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50392) Use the right API to get process' exitcode
Title: Message Title Carlos Sanchez started work on JENKINS-50392 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-21499) what's the use of build->send files over ssh-> i'm not able to simulate it ..any best way to test.
Title: Message Title nur khan commented on JENKINS-21499 Re: what's the use of build->send files over ssh-> i'm not able to simulate it ..any best way to test. Having same issue, I tested with commands working fine but file transfer via ssh having above notified error. I like this pulgin and seem very useful. will much appriciated if this issue fixed in time. If anyone have workaround please share. Reagrds, Nur Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-45385) currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven)
Title: Message Title Steve Todorov assigned an issue to Alvaro Lobato Jenkins / JENKINS-45385 currentBuild.result is not properly set to ABORTED when a build is aborted (withMaven) Change By: Steve Todorov Assignee: Alvaro Lobato Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50396) no Join Trigger can be added. org.apache.commons.jelly.JellyTagException
Title: Message Title Oleg Nenashev commented on JENKINS-50396 Re: no Join Trigger can be added. org.apache.commons.jelly.JellyTagException Caused by: java.lang.NoClassDefFoundError: hudson/tasks/Mailer$DescriptorImpl at join.JoinTrigger$DescriptorImpl.getApplicableDescriptors(JoinTrigger.java:393) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Make sure that the plugin is installed. Likely JoinTrigger has issues with optional dependencies which are not actually optional Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50398) Error when running browserstack jobs in folders
Title: Message Title Graham Lyons commented on JENKINS-50398 Re: Error when running browserstack jobs in folders Pull request created to fix this: https://github.com/jenkinsci/browserstack-integration-plugin/pull/13 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50340) P4 Plugin : Changes / Recent Changes / changelogs empty in multi-node environment due to syncID calculation
Title: Message Title
Philip Arickx commented on JENKINS-50340
Re: P4 Plugin : Changes / Recent Changes / changelogs empty in multi-node environment due to syncID calculation
I forgot to add information on the workaround - which is simple enough : explicitly define the syncID yourself for each workspace in a p4 sync operation. Any static String will do as long as it is unique within the Jenkins instance, and doesn't depend on the node name, executor number or build number (in other words, it has to remain constant across builds). Generally speaking, $JOB_BASE_NAME should work quite well as basis for the value (provided you don't have jobs with the same name in different folders - which may be allowed by Jenkins), but when the job is renamed there may be a single build where the changes will be empty. Subsequent builds will have proper changelists again. $JOB_NAME might work too, but will produce a build with empty changes when the job is renamed or moved to a different folder. Also, since the String is a path, you might want to clean up special characters such as slashes to be safe, although I'm not running into any issues ATM. This translates into the checkout step as follows : (in this case, using only $JOB_BASE_NAME, there's only a single checkout in this script)
checkout perforce(
credential: 'myCreds',
populate: autoClean( ... ),
workspace: manualSpec(
charset: 'utf8',
name: "$env.P4CLIENT",
pinHost: false,
spec: clientSpec( ... ),
syncID: "${JOB_BASE_NAME}"
)
)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50324) User without READ cannot logout from CLI with remoting
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50324 User without READ cannot logout from CLI with remoting Change By: Oleg Nenashev Labels: lts-candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-47020) Change search result pagination from 20 to 100 jobs
Title: Message Title Oleg Nenashev updated JENKINS-47020 It has been released in 2.113 Jenkins / JENKINS-47020 Change search result pagination from 20 to 100 jobs Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50324) User without READ cannot logout from CLI with remoting
Title: Message Title Oleg Nenashev commented on JENKINS-50324 Re: User without READ cannot logout from CLI with remoting It has been released in 2.113. Looks like LTS candidate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-46386) Agent sometimes fails to launch in custom cloud provider
Title: Message Title Oleg Nenashev updated JENKINS-46386 The patch from Jesse Glick has been released in 2.113. I am closing this issue, because now the general use-case is addressed Jenkins / JENKINS-46386 Agent sometimes fails to launch in custom cloud provider Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-50398) Error when running browserstack jobs in folders
Title: Message Title Graham Lyons created an issue Jenkins / JENKINS-50398 Error when running browserstack jobs in folders Issue Type: Bug Assignee: BrowserStack Integrations Components: browserstack-integration-plugin Created: 2018-03-26 11:40 Environment: Jenkins ver. 2.107.1 Folders Plugin 6.4 BrowserStack 1.0.10 Priority: Major Reporter: Graham Lyons Jobs in folders get an invalid local identifier passed to the BrowserStack binary, resulting in this error message: [BrowserStack] Local: Starting BrowserStack Local... FATAL: For security reasons identifier can only have alphanumeric characthers with combination of hiphen(-), underscore(_) and dot(.). Please rename the identifier. It looks like the buildTag which is passed to the plugin to use as part of the identifier contains a » character.
[JIRA] (JENKINS-49573) Matrix Configuration Parameter Plugin is affected by JEP-200
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49573 Re: Matrix Configuration Parameter Plugin is affected by JEP-200 Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ParametersAction.java http://jenkins-ci.org/commit/jenkins/5d4a76d28423dea1aedbb7ee73e9444a834b2ff9 Log: JENKINS-49573 Fix bad serialization of ParametersAction.parameterDefinitionNames. (cherry picked part of commit fcae9bb59881a8878774e4ebbe563935ed1382b4) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50199) Failed pipeline jobs stuck running after incorrect resume
Title: Message Title Piotr Paczyński commented on JENKINS-50199 Re: Failed pipeline jobs stuck running after incorrect resume We're also affected by this issue and seeing similar NPE errors. I can provide more details if needed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-46402) Unable to open build log when combining user-defined axis with label expression
Title: Message Title Allan Lewis commented on JENKINS-46402 Re: Unable to open build log when combining user-defined axis with label _expression_ I've seen this with two user-defined axes and a "slaves" axis on Jenkins 2.89.2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50370) Return Ansible Tower STDERR only
Title: Message Title m t commented on JENKINS-50370 Re: Return Ansible Tower STDERR only Yes you are right, I would like to use the reason for failure in the "post build step" by adding it to gitlab as a comment. Ideally it would be greate if you can get something like $TowerFaildTask aviable to other plugins. BTW do you know where does the Tower stores the logs in the DB? I was trying to find that so I can parse it somehow, however without luck. How are you pulling the Tower Log? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50396) no Join Trigger can be added. org.apache.commons.jelly.JellyTagException
Title: Message Title Michael Ebi commented on JENKINS-50396 Re: no Join Trigger can be added. org.apache.commons.jelly.JellyTagException Last working Version of join plugin is 1.19. After downgrade to this version Trigger can be added again Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50396) no Join Trigger can be added. org.apache.commons.jelly.JellyTagException
Title: Message Title Michael Ebi commented on JENKINS-50396 Re: no Join Trigger can be added. org.apache.commons.jelly.JellyTagException Last working Version of join plugin is 1.19. After downgrade to this version Trigger can be added again Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50314) Using or not caches should be configurable in servers global configuration
Title: Message Title benoit guerin updated an issue Jenkins / JENKINS-50314 Using or not caches should be configurable in servers global configuration Change By: benoit guerin Attachment: jenkins_50314.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50314) Using or not caches should be configurable in servers global configuration
Title: Message Title benoit guerin commented on JENKINS-50314 Re: Using or not caches should be configurable in servers global configuration Features : enable / disable use of cache configure how long responses are kept in cache see cache contents clear cache contents Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50314) Using or not caches should be configurable in servers global configuration
Title: Message Title benoit guerin updated JENKINS-50314 Jenkins / JENKINS-50314 Using or not caches should be configurable in servers global configuration Change By: benoit guerin Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-50251) Rejected: org.apache.maven.model.Notifier
Title: Message Title Oleg Nenashev commented on JENKINS-50251 Re: Rejected: org.apache.maven.model.Notifier Thanks Arnaud Héritier and Jesse Glick I have also confirmed the fix manually on my instance Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-20321) Chaining Jobs via REST Callback
Title: Message Title suren pi commented on JENKINS-20321 Re: Chaining Jobs via REST Callback You can use pipeline step – build, this step can trigger another job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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.
