[JIRA] (JENKINS-61021) Performance issue in active-choices plugin at commit 372d91b
Title: Message Title Bruno P. Kinoshita created an issue Jenkins / JENKINS-61021 Performance issue in active-choices plugin at commit 372d91b Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-02-08 07:51 Priority: Major Reporter: Bruno P. Kinoshita Reported via the mailing list in Google (though I think it was a direct e-mail to list owners) The change to the active choices plugin at commit 372d91b is causing problems and we cannot use the latest versions of the plugin without reverting this commit and building on our own. The problem is strange. But, is appears to be mostly a performance issue. With this change, we are seeing '504 gateway error' failures because of connection timeouts. It is somehow related to the artifactory plugin, because the jenkins log file contains multiple occurrences per second of the following log message. (omitting message as it's not related to the performance issue) Add Comment
[JIRA] (JENKINS-60943) Add JCasC support for remote retrieval of plugins
Title: Message Title Ian Williams commented on JENKINS-60943 Re: Add JCasC support for remote retrieval of plugins This is something nof a catch-22. In order to leverage the JCasC plugin, to install plug-ins, you need the JCasC plugin! Have you reviewed tje history behind [Plugin Installation Manager CLI Tool / Library](https://jenkins.io/projects/gsoc/2019/plugin-installation-manager-tool-cli) and [Plugin Installation Manager Tool](https://github.com/jenkinsci/plugin-installation-manager-tool)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204344.1580670886000.4649.1581146820245%40Atlassian.JIRA.
[JIRA] (JENKINS-60962) credential plugin security issue
Title: Message Title Ian Williams edited a comment on JENKINS-60962 Re: credential plugin security issue You should probably be filing this as a [Jenkins SECURITY Issue|https://jenkins.io/security/ ] , along with the details to reproduce. Only you, tne Security Admin and the plugin maintainers will see the details. ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204422.1580820605000.4647.1581146040164%40Atlassian.JIRA.
[JIRA] (JENKINS-60962) credential plugin security issue
Title: Message Title Ian Williams commented on JENKINS-60962 Re: credential plugin security issue You should probably be filing this as a Jenkins SECURITY Issue Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204422.1580820605000.4645.1581145980171%40Atlassian.JIRA.
[JIRA] (JENKINS-60249) Pod retention policy onFailure is not applied
Title: Message Title Ignacio Pascual commented on JENKINS-60249 Re: Pod retention policy onFailure is not applied Thanks for your response. I see. In that case, Jenkins does not keep the pods when there are pipeline execution failures, but when there is some failure with the pod itself. According to the documentation, it should take the status of the build. Right? https://jenkins.io/doc/pipeline/steps/kubernetes/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203239.1574438028000.4639.1581118560150%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Michael Musenbrock commented on JENKINS-61020 Re: Allow custom context for commit status A proposal is added as a PR: https://github.com/jenkinsci/gitlab-branch-source-plugin/pull/75 I would be really happy about any feedback and maybe some hints for a proper name of the feature. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204491.1581115267000.4637.1581116100282%40Atlassian.JIRA.
[JIRA] (JENKINS-61020) Allow custom context for commit status
Title: Message Title Michael Musenbrock created an issue Jenkins / JENKINS-61020 Allow custom context for commit status Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-02-07 22:41 Labels: pipeline multi-branch gitlab Priority: Major Reporter: Michael Musenbrock Currently it is only possible to have a single job using the gitlab-branch-source-plugin for a repository due to the fact, that the context of the status updates is always 'jenkinsci/(branch|mr-head|mr-merge|tag)'. I see the reason in an ideal world, to have one job per project, but in real-life I stumbled to often over exactly that issue (previously on github projects). We have currently two use-cases for multiple jobs per repo. First: Large project which has troubles with flaky UI-Tests. So UI-Tests are done in a separate Job to see clearly, that at least the build, code analysis, and the deployment works fine, regardless of the flakiness of the tests. So it would be great to have a 'jenkinsci/ui/branch' and a 'jenkinsci/build-and-deploy/branch' context. Second: A project which consists of different modules in one repo, where every module has it's own multibranch-pipeline. Here a 'jenkinsci/server/branch' and a 'jenkinsci/client/branch' would be of use.
[JIRA] (JENKINS-52430) Connect slave to master through HTTPS REST API
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-52430 Connect slave to master through HTTPS REST API Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192253.1531135306000.4622.1581115080450%40Atlassian.JIRA.
[JIRA] (JENKINS-22877) jenkins remoting (slave node cmd processing) via http/websocket
Title: Message Title Jesse Glick resolved as Fixed Indeed. Jenkins / JENKINS-22877 jenkins remoting (slave node cmd processing) via http/websocket Change By: Jesse Glick Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-22877) jenkins remoting (slave node cmd processing) via http/websocket
Title: Message Title Oleg Nenashev commented on JENKINS-22877 Re: jenkins remoting (slave node cmd processing) via http/websocket Jesse Glick hi. Could you please update statuses here. Looks like https://github.com/jenkinsci/jep/tree/master/jep/222 addresses it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154722.1399328293000.4608.1581114600288%40Atlassian.JIRA.
[JIRA] (JENKINS-22877) jenkins remoting (slave node cmd processing) via http/websocket
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-22877 jenkins remoting (slave node cmd processing) via http/websocket Change By: Oleg Nenashev Assignee: Kohsuke Kawaguchi Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154722.1399328293000.4601.1581114540351%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title Nikolas Falco edited a comment on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Which step is at fooTool.groovy:597?I have no idea what to do, and the reason is that not only do I not know the exact point where it is blocked but also the reason. The only thing I can assume is that the CPU is busy by the JVM by the XSLT. The only test I can do is add a sort of thread sleep after 50 transformations. Obviously this change may have no effect if the ping thread only monitors before and after the execution of a callable (means the whole step) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192770.1533150138000.4587.1581110880175%40Atlassian.JIRA.
[JIRA] (JENKINS-52842) xUnit plugin blocks PingThread responses
Title: Message Title Nikolas Falco commented on JENKINS-52842 Re: xUnit plugin blocks PingThread responses Which step is at fooTool.groovy:597? I have no idea what to do, and the reason is that not only do I not know the exact point where it is blocked but also the reason. The only thing I can assume is that the CPU is busy by the JVM by the XSLT. The only test I can do is add a sort of thread sleep after 50 transformations. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192770.1533150138000.4583.1581110700212%40Atlassian.JIRA.
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Change By: Josh Soref Assignee: Josh Soref Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204490.1581107937000.4581.1581109560071%40Atlassian.JIRA.
[JIRA] (JENKINS-61019) java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-61019 java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel Issue Type: Bug Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2020-02-07 20:38 Priority: Minor Reporter: Josh Soref Feb 07, 2020 3:35:37 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1 onFailureFeb 07, 2020 3:35:37 PM org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1 onFailureWARNING: Failed to load CpsFlowExecution[Owner[retry-timeout/7:retry-timeout #7]]java.lang.NullPointerException at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.cancel(TimeoutStepExecution.java:154) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.setupTimer(TimeoutStepExecution.java:142) at org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.onResume(TimeoutStepExecution.java:93) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:185) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl$1.onSuccess(FlowExecutionList.java:180) at com.google.common.util.concurrent.Futures$6.run(Futures.java:975) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134) at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170) at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$5.onSuccess(CpsFlowExecution.java:1011) at
[JIRA] (JENKINS-59839) java.lang.NullPointerException at hudson.util.Secret$1.convert
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59839 java.lang.NullPointerException at hudson.util.Secret$1.convert Change By: Josh Soref Summary: java.lang.NullPointerException at hudson.util.Secret$1.convert Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202574.1571388185000.4575.1581107940242%40Atlassian.JIRA.
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Daniel Beck commented on JENKINS-61005 Re: Builds failing because Run defining the context within which to find P4 credential is null nor has anything been changed on Jenkins except for the version upgrade What other components besides Jenkins (core) and P4 plugin were updated? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204475.1581024719000.4564.1581104160290%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60630 Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.4559.1581102840139%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Jarred Parrett assigned an issue to Mark Waite Jenkins / JENKINS-60630 Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is Change By: Jarred Parrett Assignee: Jarred Parrett Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.4557.1581102720224%40Atlassian.JIRA.
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Dario Sindicic commented on JENKINS-57980 Re: Incorrect links in /manage Open a "Inspect element" and then go under tab Network and then make refresh and you will see 302 error and then 200 afterwards. I tried to fix it, but the thing is that pages that have 302 error are implemented on very different way compared to the ones that don't have 302 error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.4552.1581100740149%40Atlassian.JIRA.
[JIRA] (JENKINS-60915) Gitlab-branch-source Merge Request build failed with Templating Engine
Title: Message Title Joseph Petersen resolved as Fixed Released in https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.4 Jenkins / JENKINS-60915 Gitlab-branch-source Merge Request build failed with Templating Engine Change By: Joseph Petersen Status: Open Resolved Assignee: Parichay Barpanda Steven Terrana Resolution: Fixed Released As: https://github.com/jenkinsci/gitlab-branch-source-plugin/releases/tag/gitlab-branch-source-1.4.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61018) Cannot use plugin with existing storage account and secure transfer policy
Title: Message Title
Valentin Delaye updated an issue
Jenkins / JENKINS-61018
Cannot use plugin with existing storage account and secure transfer policy
Change By:
Valentin Delaye
Hi!We are trying to use the plugin with an existing resource group and storage account but this is not working with one of our subscription because of a policy that force "secure transfer" enabled.The storage account is already configured with secure transfer, but it seems that the plugin is trying to "change" the configuration of the storage account. Which fail with following error.Same issue if trying to use a new storage accountThis prevent us using the plugin :(Is if it possible for example to have an option on the config to force the use of secure transfer and avoid issue with policies ?{code}AzureVMManagementServiceDelegate: deployment: Unable to deploycom.microsoft.azure.CloudException: Status code 400, {"error":{"code":"InvalidTemplateDeployment","message":"The template deployment failed because of policy violation. Please see details for more information.","details":[{"code":"RequestDisallowedByPolicy","target":"*","message":"Resource '*devop*jenkins**' was disallowed by policy. Policy identifiers: '[{\"policyAssignment\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/subscriptions/*/providers/Microsoft.Authorization/policyAssignments/***\"},\"policyDefinition\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Authorization/policyDefinitions/\"}},{\"policyAssignment\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Management/managementGroups/-***-mg/providers/Microsoft.Authorization/policyAssignments/\"},\"policyDefinition\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Authorization/policyDefinitions/*\"}}]'.","additionalInfo":[{"type":"PolicyViolation","info":{"policyDefinitionDisplayName":"Secure transfer to storage accounts should be enabled","evaluationDetails":{"evaluatedExpressions":[{"result":"True","expressionKind":"Field","_expression_":"type","path":"type","expressionValue":"Microsoft.Storage/storageAccounts","targetValue":"Microsoft.Storage/storageAccounts","operator":"Equals"},{code}Thanks in advance for the help!Valentin
[JIRA] (JENKINS-61018) Cannot use plugin with existing storage account and secure transfer policy
Title: Message Title
Valentin Delaye created an issue
Jenkins / JENKINS-61018
Cannot use plugin with existing storage account and secure transfer policy
Issue Type:
Bug
Assignee:
Azure DevOps
Attachments:
Screenshot from 2020-02-07 18-39-55.png
Components:
azure-vm-agents-plugin
Created:
2020-02-07 17:46
Environment:
Jenkins ver. 2.204.2 Azure VM Agents 1.4.0
Priority:
Major
Reporter:
Valentin Delaye
Hi! We are trying to use the plugin with an existing resource group and storage account but this is not working with one of our subscription because of a policy that force "secure transfer" enabled. The storage account is already configured with secure transfer, but it seems that the plugin is trying to "change" the configuration of the storage account. Which fail with following error. Same issue if trying to use a new storage account This prevent us using the plugin Is if possible for example to have an option on the config to force the use of secure transfer and avoid issue with policies ?
AzureVMManagementServiceDelegate: deployment: Unable to deploy
com.microsoft.azure.CloudException: Status code 400, {"error":{"code":"InvalidTemplateDeployment","message":"The template deployment failed because of policy violation. Please see details for more information.","details":[{"code":"RequestDisallowedByPolicy","target":"*","message":"Resource '*devop*jenkins**' was
[JIRA] (JENKINS-61018) Cannot use plugin with existing storage account and secure transfer policy
Title: Message Title
Valentin Delaye updated an issue
Jenkins / JENKINS-61018
Cannot use plugin with existing storage account and secure transfer policy
Change By:
Valentin Delaye
Hi!We are trying to use the plugin with an existing resource group and storage account but this is not working with one of our subscription because of a policy that force "secure transfer" enabled.The storage account is already configured with secure transfer, but it seems that the plugin is trying to "change" the configuration of the storage account. Which fail with following error.Same issue if trying to use a new storage accountThis prevent us using the plugin :(Is if possible for example to have an option on the config to force the use of secure transfer and avoid issue with policies ?{code}AzureVMManagementServiceDelegate: deployment: Unable to deploycom.microsoft.azure.CloudException: Status code 400, {"error":{"code":"InvalidTemplateDeployment","message":"The template deployment failed because of policy violation. Please see details for more information.","details":[{"code":"RequestDisallowedByPolicy","target":"*","message":"Resource '*devop*jenkins**' was disallowed by policy. Policy identifiers: '[{\"policyAssignment\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/subscriptions/*/providers/Microsoft.Authorization/policyAssignments/***\"},\"policyDefinition\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Authorization/policyDefinitions/\"}},{\"policyAssignment\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Management/managementGroups/-***-mg/providers/Microsoft.Authorization/policyAssignments/\"},\"policyDefinition\":{\"name\":\"Secure transfer to storage accounts should be enabled\",\"id\":\"/providers/Microsoft.Authorization/policyDefinitions/*\"}}]'.","additionalInfo":[{"type":"PolicyViolation","info":{"policyDefinitionDisplayName":"Secure transfer to storage accounts should be enabled","evaluationDetails":{"evaluatedExpressions":[{"result":"True","expressionKind":"Field","_expression_":"type","path":"type","expressionValue":"Microsoft.Storage/storageAccounts","targetValue":"Microsoft.Storage/storageAccounts","operator":"Equals"},{code} Thanks in advance for the help!Valentin
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton edited a comment on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fixed in the next release.In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ (and if that _doesn't_ fix it, please do let me know) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4526.1581096360169%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton commented on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fix in the next release. In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4520.1581096300283%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title pjdarton edited a comment on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails It should be fix fixed in the next release.In the meantime, grab the as-yet-unreleased version from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/artifact/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4522.1581096300503%40Atlassian.JIRA.
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title Colin Newell closed an issue as Not A Defect Sorry, this appears to be an issue in an older version of Jenkins. Testing with 2.219 suggests this isn't currently a problem. Jenkins / JENKINS-61016 Git LFS clone failing when using credentials via GIT_SSH Change By: Colin Newell Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title Colin Newell commented on JENKINS-61016 Re: Git LFS clone failing when using credentials via GIT_SSH Thinking about this some more, I haven't tried downloading the latest Jenkins to verify that it's not something that hasn't already been fixed. I should try to replicate with a fresh (new) Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204487.1581093033000.4511.1581094800139%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title Ben Ptacek commented on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails The only workaround to not break Jenkins is to remove the retention strategy block. Unfortunately, it requires you to go in and change the values after JCasC deployment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.4508.1581094380142%40Atlassian.JIRA.
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title Colin Newell commented on JENKINS-61016 Re: Git LFS clone failing when using credentials via GIT_SSH We have an ssh username with private key setup in the Jenkins Credentials. In our checkout stage of our pipeline build we are calling checkout providing it with which set of credentials to use. The GIT_LFS env var is something I noticed from the logs. The git fetch does indeed work as you'd expect, and before each of those lines you'll notice the log says 'using GIT_SSH to set credentials'. I assume it uses that env var to setup the ssh command to point to the key it must manage on the worker box. The checkout however chokes because it tries to ssh over to grab the lfs files and that env var isn't set, and there aren't credentials that will work available by other means. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204487.1581093033000.4506.1581094320175%40Atlassian.JIRA.
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title
Mark Waite edited a comment on JENKINS-61016
Re: Git LFS clone failing when using credentials via GIT_SSH
Please explain further what you mean by bq. uses a set of credentials that are hooked up via the GIT_SSH environment variableAre you defining a {{GIT_SSH}} environment variable without using a Jenkins credential? If so, then why are you providing the credential ID in the userRemoteConfigs portion of the Jenkinsfile? If not, then please describe in more detail how you are performing the checkout and how others can duplicate the issue you are seeing. The plugin definitely clones repositories using both the SSH protocol and the HTTPS protocol when Git LFS is enabled.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204487.1581093033000.4504.1581093840106%40Atlassian.JIRA.
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title Mark Waite commented on JENKINS-61016 Re: Git LFS clone failing when using credentials via GIT_SSH Please explain further what you mean by uses a set of credentials that are hooked up via the GIT_SSH environment variable Are you defining a GIT_SSH environment variable without using a Jenkins credential? If so, then why are you providing the credential ID in the userRemoteConfigs portion of the Jenkinsfile? The plugin definitely clones repositories using both the SSH protocol and the HTTPS protocol when Git LFS is enabled. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204487.1581093033000.4500.1581093780281%40Atlassian.JIRA.
[JIRA] (JENKINS-60998) Azure VM Agents is using incorrect subscription id
Title: Message Title Ali Allomani updated an issue Jenkins / JENKINS-60998 Azure VM Agents is using incorrect subscription id Change By: Ali Allomani Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204466.1580995914000.4502.1581093780315%40Atlassian.JIRA.
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61016 Git LFS clone failing when using credentials via GIT_SSH Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204487.1581093033000.4498.1581093480139%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title
Mark Waite edited a comment on JENKINS-26100
Re: SCM steps should return revision state
> bq. I managed to get the variables with a script block, but I expected that there would be a way to get to this without breaking into scripting mode.The variables are available if you don't use the {{checkout}} step in the declarative pipeline. The declarative pipeline has an implicit checkout step that happens before the Pipeline executes. > bq. What is a default checkout: where would the pipeline know the url from?When the Jenkinsfile for the Pipeline is read from SCM, the declarative pipeline uses that URL. > bq. Does *withCheckout* exist? its referenced in this thread.No, withCheckout does not exist. It was added to the scm step plugin [May 5, 2017|https://github.com/jenkinsci/workflow-scm-step-plugin/commit/bec924c64a8f19efbd7f6f08af9d879636dcf4e4] and then removed on [May 16, 2017|https://github.com/jenkinsci/workflow-scm-step-plugin/commit/dbcfe52ad81d16fe3dfdc5ce642f49720aff36e3]. > bq. Docs send you completely in the wrong direction unfortunately.Which docs send you in the wrong direction?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.4398.1581093302326%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Mark Waite commented on JENKINS-26100 Re: SCM steps should return revision state > I managed to get the variables with a script block, but I expected that there would be a way to get to this without breaking into scripting mode. The variables are available if you don't use the checkout step in the declarative pipeline. The declarative pipeline has an implicit checkout step that happens before the Pipeline executes. > What is a default checkout: where would the pipeline know the url from? When the Jenkinsfile for the Pipeline is read from SCM, the declarative pipeline uses that URL. > Does withCheckout exist? its referenced in this thread. No, withCheckout does not exist. It was added to the scm step plugin May 5, 2017 and then removed on May 16, 2017. > Docs send you completely in the wrong direction unfortunately. Which docs send you in the wrong direction? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.4297.1581093242266%40Atlassian.JIRA.
[JIRA] (JENKINS-61017) Pipeline: SCM Step : Checkout extensions [Excluded Regions]
Title: Message Title
aiun rluk created an issue
Jenkins / JENKINS-61017
Pipeline: SCM Step : Checkout extensions [Excluded Regions]
Issue Type:
Bug
Assignee:
Unassigned
Components:
extension-filter-plugin, pipeline, scm-api-plugin
Created:
2020-02-07 16:31
Environment:
Jenkins Pipeline with Git
Labels:
jenkins-plugin Pipeline-scm-step checkout
Priority:
Major
Reporter:
aiun rluk
Hi folks, I am seeing an issue with using the Excluded Regions / Included Regions in the Pipeline:SCM step Checkout plugin. My pipeline script clones code from multiple Repos. However, I do not want the job to be triggered for changes in all these Repos. So to suppress builds form changes in one of the Repo, I tried using the extensions. But it seems this feature is not working as expected. I have the following code in my pipeline script: triggers { pollSCM('H/5 * * * *') } dir ('script') {dir ('script') { checkout([ $class : 'GitSCM', branches : [[name: '*/master']], extensions : [ [$class: 'PathRestriction', excludedRegions: ''], [$class: 'CleanBeforeCheckout'], [$class: 'DisableRemotePoll'] ], userRemoteConfigs: [[ credentialsId: '12345-x', name : 'origin', refspec : '+refs/heads/:refs/remotes/origin/+refs/pull/*:refs/remotes/origin/pr/ *', url :
[JIRA] (JENKINS-61016) Git LFS clone failing when using credentials via GIT_SSH
Title: Message Title
Colin Newell created an issue
Jenkins / JENKINS-61016
Git LFS clone failing when using credentials via GIT_SSH
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2020-02-07 16:30
Priority:
Minor
Reporter:
Colin Newell
When using git lfs and cloning a repo that uses a set of credentials that are hooked up via the GIT_SSH environment variable the 'pull' fails.
using credential ----
Cloning the remote Git repository
Cloning repository g...@bitbucket.org:someorg/ourrepo.git
> git init /home/jenkins2/workspace/ourrepo # timeout=10
Fetching upstream changes from g...@bitbucket.org:someorg/ourrepo.git
> git --version # timeout=10
using GIT_SSH to set credentials Our Bitbucket PR Builder
> git fetch --tags --progress g...@bitbucket.org:someorg/ourrepo.git +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@bitbucket.org:someorg/ourrepo.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@bitbucket.org:someorg/ourrepo.git # timeout=10
Fetching upstream changes from g...@bitbucket.org:someorg/ourrepo.git
using GIT_SSH to set credentials Our Bitbucket PR Builder
> git fetch --tags --progress g...@bitbucket.org:someorg/ourrepo.git +refs/heads/*:refs/remotes/origin/* # timeout=10
Checking out Revision fff2883fd545b3723b59dccd234c90e5 (refs/remotes/origin/master)
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> git config core.sparsecheckout # timeout=10
> git checkout -f 883fd545b3723b59dccd234c90e5 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline]
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Allan C commented on JENKINS-57980 Re: Incorrect links in /manage Dario Sindicic Štefan Kušnír Hi. I am having trouble replicating this issue. Do I need to have a remote Jenkins Server for this issue to come up? Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.4290.1581092940381%40Atlassian.JIRA.
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Allan C updated an issue Jenkins / JENKINS-57980 Incorrect links in /manage Change By: Allan C Attachment: Screen Shot 2020-02-07 at 11.27.30 AM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.4281.1581092880244%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Norbert Lange edited a comment on JENKINS-26100 Re: SCM steps should return revision state Yeah, I posted the entire declarative pipeline couple posts before.I managed to get the variables with a script block, but I expected that there would be a way to get to this without breaking into scripting mode.What is a default checkout: where would the pipeline know the url from?Does *withCheckout* exist? its referenced in this thread.Would be nice to get *withEnv* working like I illustrated above.Docs send you completely in the wrong direction unfortunately. Edit: I replied here because this is often referenced as "answer" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.4175.1581092403085%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Norbert Lange commented on JENKINS-26100 Re: SCM steps should return revision state Yeah, I posted the entire declarative pipeline couple posts before. I managed to get the variables with a script block, but I expected that there would be a way to get to this without breaking into scripting mode. What is a default checkout: where would the pipeline know the url from? Does withCheckout exist? its referenced in this thread. Would be nice to get withEnv working like I illustrated above. Docs send you completely in the wrong direction unfortunately. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.4073.1581092341720%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Mark Waite commented on JENKINS-26100 Re: SCM steps should return revision state Norbert Lange also, since this bug report is about the git step and not the checkout step, it would be better to use a different location for your question and for the answer to your question. When you ask a question in an issue, you limit the number of people that will answer the question to only those that are monitoring that bug. A question asked in the Jenkins mailing lists or the Jenkins chat channels can be seen by a much larger group. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.3971.1581092282107%40Atlassian.JIRA.
[JIRA] (JENKINS-59670) Support retrieval of secrets from multiple AWS accounts
Title: Message Title Chris Kilding commented on JENKINS-59670 Re: Support retrieval of secrets from multiple AWS accounts Started work in GitHub PR #25 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202362.1570220885000.3966.1581091920051%40Atlassian.JIRA.
[JIRA] (JENKINS-59670) Support retrieval of secrets from multiple AWS accounts
Title: Message Title Chris Kilding started work on JENKINS-59670 Change By: Chris Kilding Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202362.1570220885000.3965.1581091860213%40Atlassian.JIRA.
[JIRA] (JENKINS-61015) Test story for new component veracode-scan-plugin
Title: Message Title Dennis Gu created an issue Jenkins / JENKINS-61015 Test story for new component veracode-scan-plugin Issue Type: Story Assignee: Dennis Gu Components: veracode-scan-plugin Created: 2020-02-07 16:05 Priority: Minor Reporter: Dennis Gu This is a test story. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title
Mark Waite commented on JENKINS-26100
Re: SCM steps should return revision state
Norbert Lange it looks to me like you're using declarative pipeline but then ignoring the default checkout which declarative pipeline provides for you, without explicitly stating that you intend to skip the default checkout. If you intend to skip the default checkout then you should extend your declarative pipeline with
options {
skipDefaultCheckout()
}
If you don't intend to skip the default checkout, then the techniques described in that video will work. If you intend to skip the default checkout, specify your own checkout, and use the return value from the checkout step to collect the settings used in the checkout, then it appears you'll need to use a script block in your declarative Pipeline. Refer to this example that I created while experimenting with the question. The example skips the default checkout, performs its own checkout, and assigns the return value of checkout() to the variable results. It then displays values from results.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61013) plagin
Title: Message Title Karl Wirth closed an issue as Fixed Jenkins / JENKINS-61013 plagin Change By: Karl Wirth Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204483.158108912.3856.1581091260232%40Atlassian.JIRA.
[JIRA] (JENKINS-60029) vSphere cloud: Configuration-as-Code compatibility Export/Import fails
Title: Message Title Ben Ptacek commented on JENKINS-60029 Re: vSphere cloud: Configuration-as-Code compatibility Export/Import fails I am seeing this issue as well. Any solution to fix? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202854.1572774593000.3850.1581090900387%40Atlassian.JIRA.
[JIRA] (JENKINS-61014) Anchore plugin overwrittes pipeline reports
Title: Message Title Juan Caldas updated an issue Jenkins / JENKINS-61014 Anchore plugin overwrittes pipeline reports Change By: Juan Caldas Hi,My pipeline has multiple stages and each stage creates a docker image.there are two issues, first at the end of the pipeline I end up having 3 separate 'Achore reports' but they all have the same data (the Achore Policy Evaluation Report has the results for the 3 scans). Second, the 'Anchore Policy Evaluation Summary' shows the same image for the 3 different 'Anchore reports'The pipeline process is something like * Create base image * Create Builder image * Create Runner image I check each image after each stage (so that it fails if one of them had issues)I runanchore(name: IMAGES_FILE_PATH, engineRetries: '1000', forceAnalyze: true, policyBundleId: 'policyName')I tried using different names for the IMAGES_FILE_PATH but it yields the same problems it would be nice if each report only had the information about that one image Sorry if I didnt provided enough details, I would be happy to add more info Thanks! Edit:Kind of related stack overflow issue[https://stackoverflow.com/questions/57367074/adding-multiple-docker-images-in-jenkins-pipeline-to-scan-security-vulnerabiliti]with the exception that I cant wait until the end to scan the images Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61014) Anchore plugin overwrittes pipeline reports
Title: Message Title Juan Caldas created an issue Jenkins / JENKINS-61014 Anchore plugin overwrittes pipeline reports Issue Type: Bug Assignee: Daniel Nurmi Components: anchore-container-scanner-plugin Created: 2020-02-07 15:46 Priority: Minor Reporter: Juan Caldas Hi, My pipeline has multiple stages and each stage creates a docker image. there are two issues, first at the end of the pipeline I end up having 3 separate 'Achore reports' but they all have the same data (the Achore Policy Evaluation Report has the results for the 3 scans). Second, the 'Anchore Policy Evaluation Summary' shows the same image for the 3 different 'Anchore reports' The pipeline process is something like Create base image Create Builder image Create Runner image I check each image after each stage (so that it fails if one of them had issues) I run anchore(name: IMAGES_FILE_PATH, engineRetries: '1000', forceAnalyze: true, policyBundleId: 'policyName') I tried using different names for the IMAGES_FILE_PATH but it yields the same problems it would be nice if each report only had the information about that one image Sorry if I didnt provided enough details, I would be happy to add more info Thanks!
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Kristy ashton commented on JENKINS-26100 Re: SCM steps should return revision state Inter Milan vs AC Milan Soccer Live Streaming Online 2020 https://fb5531.pb.online/ https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.3837.1581089284724%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Kristy ashton commented on JENKINS-61009 Re: How to use a reference repository in an organization folder? Inter Milan vs AC Milan Soccer Live Streaming Online 2020 https://fb5531.pb.online/ https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204479.1581041026000.3735.1581089282560%40Atlassian.JIRA.
[JIRA] (JENKINS-61013) plagin
Title: Message Title Kristy ashton created an issue Jenkins / JENKINS-61013 plagin Issue Type: Story Assignee: Unassigned Components: p4-plugin Created: 2020-02-07 15:25 Environment: Inter Milan vs AC Milan Soccer Live Streaming Online 2020 Labels: plugin Priority: Minor Reporter: Kristy ashton Inter Milan vs AC Milan Soccer Live Streaming Online 2020 *https://fb5531.pb.online/* *https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa* *https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa* *https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa* *https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa* *https://medium.com/@kristyk.ashton/inter-milan-vs-ac-milan-soccer-live-streaming-online-2020-d29a41ee1cfa*
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title
Norbert Lange commented on JENKINS-26100
Re: SCM steps should return revision state
Mark Waite: No, video is generally a bad idea, and that specific one is not helping at all. Here is the problem in a single paragraph:
checkout()
// returns ""
sh 'echo ${GIT_COMMIT}'
// returns "null"
echo "${env.GIT_COMMIT}"
No environment variables are set.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.3623.1581087902538%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) How to use a reference repository in an organization folder?
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61009 How to use a reference repository in an organization folder? Change By: Mark Waite Summary: Jenkins GIT Reference Repository blocker How to use a reference repository in GitHub Organization Pipeline, where I have multi repositories in one an organization folder . ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204479.1581041026000.3620.1581087902480%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61009 Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder. Change By: Mark Waite Component/s: _unsorted Component/s: git-client-plugin Component/s: github-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204479.1581041026000.3618.1581087300453%40Atlassian.JIRA.
[JIRA] (JENKINS-61009) Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder.
Title: Message Title Mark Waite commented on JENKINS-61009 Re: Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder. Thanks for a well described question. We generally prefer that questions be asked in the mailing list or in the chat systems, but this question will lead to a documentation improvement, so let's answer the question here. Once I'm confident that your question is addressed and you're seeing the results you want, then I'll convert this issue into a documentation issue for the git plugin. Organization folder users have several choices for reference repositories: Define the reference repository in each Jenkinsfile as in this example Define the reference repository in the organization folder and use a combined repository that includes the content from all the repositories in the organization Don't use reference repositories Can you confirm that the reference repository in each Jenkinsfile works for you? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title Mark Waite commented on JENKINS-26100 Re: SCM steps should return revision state Norbert Lange could you review the Jenkins Minute video "Using Git Environment Variables" and see if it resolves your issue? If it resolves your issue, then I'll add a git plugin documentation section on using the git plugin with Pipeline and will embed that video in the new section. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159680.1418774393000.3610.1581086703505%40Atlassian.JIRA.
[JIRA] (JENKINS-61012) GitLab Group Scan Incorrectly Reports Missing Jenkinsfile as a Directory
Title: Message Title Charles Bozarth created an issue Jenkins / JENKINS-61012 GitLab Group Scan Incorrectly Reports Missing Jenkinsfile as a Directory Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-02-07 14:36 Environment: Jenkins 2.204.2 Windows Server 2016 GitLab Branch Source Plugin 1.4.3 Priority: Minor Reporter: Charles Bozarth The Scan GitLab Group Log reports the following when the project does not have a Jenkinsfile. Checking project Test Proposing Test Unable to detect if it is a mirror or not still fetching MRs anyway... Checking branches.. Checking branch master ‘Jenkinsfile’ found but is a directory not a file Does not meet criteria The message, "Jenkinsfile found but is a directory not a file", is inaccurate because there is not a directory named Jenkinsfile. I'd like to see this changed so that it more clearly states that a Jenkinsfile was not found.
[JIRA] (JENKINS-39963) Upgrade this plugin to make it usable with pipelines
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39963 Upgrade this plugin to make it usable with pipelines Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176585.1479889322000.3503.1581083820758%40Atlassian.JIRA.
[JIRA] (JENKINS-45028) Implement build weight support
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-45028 Implement build weight support Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183117.1498045302000.3501.1581083760475%40Atlassian.JIRA.
[JIRA] (JENKINS-44846) Support allocating multiple executors with node()
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-44846 Support allocating multiple executors with node() Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182908.1497354032000.3499.1581083760443%40Atlassian.JIRA.
[JIRA] (JENKINS-57980) Incorrect links in /manage
Title: Message Title Allan C commented on JENKINS-57980 Re: Incorrect links in /manage Aman Bora Hi, have you started working on this? Are you able to replicate the problem? Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199965.1560329204000.3495.1581083520193%40Atlassian.JIRA.
[JIRA] (JENKINS-39975) Possibility to specify number of executors a node step will consume
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39975 Possibility to specify number of executors a node step will consume Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176599.1479912575000.3492.1581083400404%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Aytunc BEKEN updated JENKINS-60446 Jenkins / JENKINS-60446 Add option to pass custom paramters from multibranch to the trigger jobs Change By: Aytunc BEKEN Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203523.157608026.3456.1581079381173%40Atlassian.JIRA.
[JIRA] (JENKINS-60446) Add option to pass custom paramters from multibranch to the trigger jobs
Title: Message Title Aytunc BEKEN commented on JENKINS-60446 Re: Add option to pass custom paramters from multibranch to the trigger jobs Hi, Adding custom parameters feature is released with 1.8 version. Probably It will be available soon in the plugin site. Please let me know, then I will close the ticket. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203523.157608026.3451.1581079381095%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title Christian Häussler updated an issue Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Change By: Christian Häussler Released As: https://github.com/jenkinsci/requests-plugin/blob/requests-2.2.4/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204481.158106000.3445.1581077880298%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title Christian Häussler updated an issue Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Change By: Christian Häussler We are using no flat folder hierarchy which leads to pending requests deleting not the job itself but everything under the top two folders resulting in accidently deleting several subfolders New Feature "Delete / jobs at once.-> extend HttpResponse doCreateXXXRequest(StaplerRequest Rename request , StaplerResponse response) functions to support unlimited subfolder hierarchy for entired Folder" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title Christian Häussler updated an issue Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Change By: Christian Häussler Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204481.158106000.3439.1581077823070%40Atlassian.JIRA.
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title Christian Häussler created an issue Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Issue Type: Bug Assignee: John Flynn Components: requests-plugin Created: 2020-02-07 12:16 Environment: CloudBees Jenkins Enterprise 2.164.32.0.1-fixed Priority: Critical Reporter: Christian Häussler We are using no flat folder hierarchy which leads to pending requests deleting not the job itself but everything under the top two folders resulting in accidently deleting several subfolders/jobs at once. -> extend HttpResponse doCreateXXXRequest(StaplerRequest request, StaplerResponse response) functions to support unlimited subfolder hierarchy Add Comment
[JIRA] (JENKINS-61011) New Feature "Delete / Rename request for entired Folder"
Title: Message Title Christian Häussler updated an issue Jenkins / JENKINS-61011 New Feature "Delete / Rename request for entired Folder" Change By: Christian Häussler Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204481.158106000.3442.1581077823529%40Atlassian.JIRA.
[JIRA] (JENKINS-61010) [saml] Wrong AssertionConsumerServiceURL error
Title: Message Title Ivan Fernandez Calvo updated JENKINS-61010 Jenkins / JENKINS-61010 [saml] Wrong AssertionConsumerServiceURL error Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Closed Resolution: Fixed Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204480.158107000.3430.1581075000347%40Atlassian.JIRA.
[JIRA] (JENKINS-61010) [saml] Wrong AssertionConsumerServiceURL error
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61010 Re: [saml] Wrong AssertionConsumerServiceURL error it is in the troubleshooting guide https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md#no-valid-subject-assertion-found-in-response, the JENKINS_URL matters to validate the SAMLResponse Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204480.158107000.3428.1581075000320%40Atlassian.JIRA.
[JIRA] (JENKINS-26100) SCM steps should return revision state
Title: Message Title
Norbert Lange commented on JENKINS-26100
Re: SCM steps should return revision state
I might be dense, but I still dont understand how I would do this with a declarative pipeline (without script blocks). Any help here? withCheckout is nowhere to be found the env variables are not set by default:
pipeline {
agent none
stages {
stage('checkout') {
post { always { deleteDir() } }
agent any
steps {
checkout([$class: 'GitSCM',
userRemoteConfigs: [[url: 'https://github.com/docker/for-linux.git']]])
sh 'set'
}
}
}
}
trying to stuff into a withEnv block fails with `java.lang.UnsupportedOperationException: must specify $class with an implementation of interface java.util.List`
pipeline {
agent none
stages {
stage('checkout') {
post { always { deleteDir() } }
agent any
steps {
withEnv(checkout([$class: 'GitSCM',
userRemoteConfigs: [[url: 'https://github.com/docker/for-linux.git']]])) {
sh 'set'
}
}
}
}
}
Jenkins ver. 2.219 (docker alpine installation) git 4.1.1 true git-client 3.1.1 true workflow-scm-step 2.10 true
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60926) Agent Windows service installation broken
Title: Message Title Oleg Nenashev started work on JENKINS-60926 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204323.1580417035000.3296.1581071820597%40Atlassian.JIRA.
[JIRA] (JENKINS-60926) Agent Windows service installation broken
Title: Message Title Oleg Nenashev updated JENKINS-60926 Jenkins / JENKINS-60926 Agent Windows service installation broken Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204323.1580417035000.3298.1581071820631%40Atlassian.JIRA.
[JIRA] (JENKINS-61010) [saml] Wrong AssertionConsumerServiceURL error
Title: Message Title Adam P updated JENKINS-61010 Under Manage Jenkins / Configuration / Jenkins Location / Jenkins URL wasn't correctly set. Jenkins / JENKINS-61010 [saml] Wrong AssertionConsumerServiceURL error Change By: Adam P Status: Open Fixed but Unreleased Assignee: Ivan Fernandez Calvo Adam P Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-44681) JobDSL Folder Creation Destroys Credentials
Title: Message Title Naresh Rayapati commented on JENKINS-44681 Re: JobDSL Folder Creation Destroys Credentials I also vote for updating folder properties vs overwriting those. Please add this support. Thanks a bunch in advance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182545.149666436.3267.1581069061998%40Atlassian.JIRA.
[JIRA] (JENKINS-61002) User-based toggle for the new UI
Title: Message Title Francisco Fernández updated JENKINS-61002 For the moment it won't be done. I will re-open if plans change. Jenkins / JENKINS-61002 User-based toggle for the new UI Change By: Francisco Fernández Status: In Review Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the
[JIRA] (JENKINS-61010) [saml] Wrong AssertionConsumerServiceURL error
Title: Message Title Adam P created an issue Jenkins / JENKINS-61010 [saml] Wrong AssertionConsumerServiceURL error Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2020-02-07 09:11 Environment: Jenkins ver. 2.190.1 running as a container SAML ver 1.1.2 Labels: plugin jenkins SAML2 auth0 Priority: Minor Reporter: Adam P Followed this article: https://3dsim.github.io/securing-jenkins-with-auth0/ to configure Auth0 in Jenkins. When try to login, Auth0 displays below error: Type: Failed Login Description: The SAML Request AssertionConsumerServiceURL is invalid: 'http://jenkins:8080/securityRealm/finishLogin' When testing Auth0 using their own debug function everything appear to be working. Auth0 Allowed Callback URLs is configured with a correct URL. jenkins:8080 doesn't appear anywhere in Jenkins, not in XML file from Auth0, not in config.xml file.
[JIRA] (JENKINS-61005) Builds failing because Run defining the context within which to find P4 credential is null
Title: Message Title Karl Wirth commented on JENKINS-61005 Re: Builds failing because Run defining the context within which to find P4 credential is null Hi Annie Chen - Thanks for letting us know. Are you saying that you have 3 Perforce builds and only one is failing, or are you saying that all your Perforce builds are failing? Please try the following tests: Create a new Perforce job does that work? Try creating a new credential that uses the same userid and password. Switch a failing job to using the new credential does that work? Usually after an upgrade there is a cleanup old data option under Manage Jenkins. Did you run this already? Please also give me additional information. Is this a freestyle job? Please send me screenshots showing how the job is defined and any Jenkinsfiles it may be using. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-61009) Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder.
Title: Message Title jbq assigned an issue to Mark Waite Jenkins / JENKINS-61009 Jenkins GIT Reference Repository blocker in GitHub Organization Pipeline, where I have multi repositories in one folder. Change By: jbq Assignee: jbq Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204479.1581041026000.3220.1581063720269%40Atlassian.JIRA.
