[JIRA] (JENKINS-53108) cloudbuild: specify the bucket to upload source
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-53108 cloudbuild: specify the bucket to upload source Change By: ikedam Assignee: Brad Kimmel ikedam Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53107) cloudbuild: HTTP proxy support
Title: Message Title ikedam updated JENKINS-53107 Jenkins / JENKINS-53107 cloudbuild: HTTP proxy support Change By: ikedam Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53107) cloudbuild: HTTP proxy support
Title: Message Title ikedam commented on JENKINS-53107 Re: cloudbuild: HTTP proxy support https://github.com/jenkinsci/google-cloudbuild-plugin/pull/11 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53107) cloudbuild: HTTP proxy support
Title: Message Title ikedam commented on JENKINS-53107 Re: cloudbuild: HTTP proxy support I verified that http.proxyHost / http.proxyPort doesn't work. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues commented on JENKINS-52944 Re: Test duration is always displayed as <1s Here is an example JUnit report.xml file. In classic UI, it displays the proper test duration. In Blue Ocean test UI, the test duration is wrong. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52944 Test duration is always displayed as <1s Change By: Craig Rodrigues Attachment: report.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52944 Test duration is always displayed as <1s Change By: Craig Rodrigues Attachment: Screen Shot 2018-08-18 at 7.47.02 PM.png Attachment: Screen Shot 2018-08-18 at 7.47.31 PM.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52944 Test duration is always displayed as <1s Change By: Craig Rodrigues Attachment: report.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52944) Test duration is always displayed as <1s
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52944 Test duration is always displayed as <1s Change By: Craig Rodrigues Attachment: report.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-50343) ComposedClosure not working with List.each
Title: Message Title
Steven Terrana commented on JENKINS-50343
Re: ComposedClosure not working with List.each
It seems that the ComposedClosure issue extends beyond iterating via .each. The following:
c = { println "my first closure" }
println c
c = c << { println "my second closure" }
println c
c()
results in:
Started by user unknown or anonymous
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] echo
org.jenkinsci.plugins.workflow.cps.CpsClosure2@753b4e4
[Pipeline] echo
org.codehaus.groovy.runtime.ComposedClosure@36c30d6
[Pipeline] echo
my second closure
[Pipeline] End of Pipeline
Finished: SUCCESS
Jenkins version: 2.121.2 workflow-cps version: 2.53 Happy to try to fix if I could be pointed in the general direction to look. Perhaps by creating a CpsComposedClosure similarly to https://github.com/cloudbees/groovy-cps/blob/master/lib/src/main/java/com/cloudbees/groovy/cps/impl/CpsClosure.java ? Thanks, Steven Terrana
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google 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-52058) Provide report filename as variable to Groovy parser
Title: Message Title Ulli Hafner commented on JENKINS-52058 Re: Provide report filename as variable to Groovy parser As a first step I added the file name to the parser API. This needs to be applied to the Groovy part in the Jenkins Plugin as well. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-50011) Reference all existing icons in static analysis tool definitions
Title: Message Title Ulli Hafner updated JENKINS-50011 Jenkins / JENKINS-50011 Reference all existing icons in static analysis tool definitions Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-51444) Maven Parser creates errors during affectedFilesResolving
Title: Message Title Ulli Hafner updated JENKINS-51444 Jenkins / JENKINS-51444 Maven Parser creates errors during affectedFilesResolving Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-50062) Add support for open task scanner
Title: Message Title Ulli Hafner stopped work on JENKINS-50062 Change By: Ulli Hafner Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-50062) Add support for open task scanner
Title: Message Title Ulli Hafner started work on JENKINS-50062 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-51466) Improve description of reference build
Title: Message Title Ulli Hafner started work on JENKINS-51466 Change By: Ulli Hafner Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53117) Gerrit Missed Events Playback is not supported. Verify if the connection has the REST API enabled and that the Gerrit Events-log plugin is installed and configured on the Gerrit
Title: Message Title Humberto Israel Perez Rodriguez created an issue Jenkins / JENKINS-53117 Gerrit Missed Events Playback is not supported. Verify if the connection has the REST API enabled and that the Gerrit Events-log plugin is installed and configured on the Gerrit Server. Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2018-08-18 19:08 Environment: Jenkins ver. 2.121.3 Gerrit Trigger Plugin Version: 2.27.5 Gerrit Code Review (2.14.8) events-log plugin version v2.13-15-g7d4a8be Priority: Critical Reporter: Humberto Israel Perez Rodriguez Hi: I am having issues with Gerrit Trigger Plugin in Jenkins, then plugins shows the following message: Gerrit Missed Events Playback is not supported. Verify if the connection has the REST API enabled and that the Gerrit Events-log plugin is installed and configured on the Gerrit Server. I have all in order and I can not figure out where could be the issue Document followed: = https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger#GerritTrigger-MissedEventsPlaybackFeature(Availablefromv.2.14.0) Comments: Jenkins: Gerrit Connection Setting is success REST API Connection is success Configurations: == Gerrit plugin events-log configuration: [plugin "events-log"][plugin "events-log"] maxAge = 30 returnLimit = 1 storeUrl = jdbc:h2:/home/gerrit/tree/events/db urlOptions = loglevel=INFO urlOptions = logUnclosedConnections=true copyLocal = true Any help here will be welcome. Thanks
[JIRA] (JENKINS-48562) Inline Environment Variables not replaced in config file
Title: Message Title
Michael Porter commented on JENKINS-48562
Re: Inline Environment Variables not replaced in config file
A bit of a hack, but I found a pipeline workaround. by using `envsubst`
node{
configFileProvider([configFile(fileId: 'drupal7-test',
replaceTokens: false, targetLocation: "web/settings.template.php")]) {
sh """cat web/settings.template.php
SITE_NAME=my-db-master DATABASE_NAME=my_db_master DATABASE_USER=my_db envsubst < web/settings.template.php > web/settings.local.php
cat web/settings.local.php
"""
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to the Google 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-52990) Allow setting priority per category
Title: Message Title Ulli Hafner commented on JENKINS-52990 Re: Allow setting priority per category I see. I wonder if it would make sense to introduce a kind of priority mapping file (local in the workspace) that would map a given warning property to a priority. This would be more powerful and should be simpler to implement than a Ui. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-48562) Inline Environment Variables not replaced in config file
Title: Message Title
Michael Porter commented on JENKINS-48562
Re: Inline Environment Variables not replaced in config file
I noticed your first example you are not calling `env.dbName` but `dbName` is that a type-o or does it not work still?
node{
withEnv(['dbName = "test-$\{env.BUILD_NUMBER}"', 'X_SITENAME = "HELLO"', 'X_DB_USER = "mp"', 'DOMAIN_NAME = "https://www.example.com"']) {
configFileProvider([configFile(fileId: 'settings_php', replaceTokens: true, targetLocation: "$\{dbName}/www/local.settings.php")]) {
sh "cat ${env.dbName}/www/local.settings.php"
}
}
}
I have been calling a Job to build the file, but it would be nice to get away from this and us full pipeline.
build job: 'global-builds/drupal-build-site-test',
parameters: [
string(name: 'SITE_NAME', value: "${siteName}"),
string(name: 'DATABASE_NAME', value: "${siteName.replaceAll('-','_')}"),
string(name: 'DATABASE_USER', value: "${dbUser}"),
string(name: 'DOMAIN_NAME', value: "${domain}"),
[$class: 'LabelParameterValue', name: 'node', label: "${buildLabel}"]]
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you 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-53111) List the created at information on the homepage
Title: Message Title R. Tyler Croy updated JENKINS-53111 Jenkins / JENKINS-53111 List the created at information on the homepage Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53111) List the created at information on the homepage
Title: Message Title R. Tyler Croy started work on JENKINS-53111 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-52990) Allow setting priority per category
Title: Message Title Simon Richter commented on JENKINS-52990 Re: Allow setting priority per category I'm using both gcc and MSBuild parsers for different projects. I think different teams would be using different settings here, as they may have different views on the severity of stylistic warnings. I think there is no need to make this parser specific. There is already a setting "Categories to ignore", this feature would add "High/Medium/Low Categories" and/or replace that by a mapping table where users can override default classifications with "High/Medium/Low/Ignore". It might also be useful to some people to have a similar mechanism for matches against file names or warning messages and/or combinations of these (e.g. demote certain warnings in third-party components without hiding them), but this would probably increase the complexity quite a bit. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-49260) this.binding.jenkinsProject not returning project of current build
Title: Message Title Sébastien COLLIN commented on JENKINS-49260 Re: this.binding.jenkinsProject not returning project of current build Just made a pull request to solve this issue : https://github.com/jenkinsci/active-choices-plugin/pull/19 Wasn't hard to solve (biggest part was the test...) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Title: Message Title
Jesús Benavente updated an issue
Jenkins / JENKINS-53116
Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Change By:
Jesús Benavente
Includes custom user fields from archived attachments results from a JenkinsfileAS a user that consumes the plugin through a jenkinsfile pipelineI NEED to be able to include custom user fields in said pipelineTO be loaded into the tool for the different entities, test and testcase Modify example JENKINS-52753 to include the fieldstestSetFields: [ 'user-01': 'VALUE', 'user-02': 'VALUE'], //List user-fields associate with testSet testCaseFields: [ 'user-3': 'VALUE', 'user-04': 'VALUE'] {code:java}// EXAMPLEpost {always {junit testResults: '**/target/*-reports/TEST-*.xml', allowEmptyResults: true step ([$class: 'TestResultToALMUploader', almServerName: 'HP ALM Isban', credentialsId: 'CREDENTIALS', almDomain: 'DOMAIN_ALM', almProject: 'ALM_PROJECT', testingFramework: 'JUnit', testingTool: '', //testingTool almTestFolder: 'Demo HP TEST ALM', almTestSetFolder: 'Demo HP TEST ALM', almTimeout: '-1', testingResultFile: "**/junitResult.xml", jenkinsServerUrl: '', testSetFields: [ 'user-01': 'VALUE', 'user-02': 'VALUE'], //List user-fields associate with testSet testCaseFields: [ 'user-3': 'VALUE', 'user-04': 'VALUE']//List user-fields associate with testcase) }}{code}
Add Comment
[JIRA] (JENKINS-53116) Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Title: Message Title
Jesús Benavente created an issue
Jenkins / JENKINS-53116
Include user-fields To Uploads archived junit results from Jenkinsfile (@see JENKINS-52753)
Issue Type:
Improvement
Assignee:
Daniel Gront
Components:
hp-application-automation-tools-plugin
Created:
2018-08-18 11:13
Priority:
Minor
Reporter:
Jesús Benavente
Includes custom user fields from archived attachments results from a Jenkinsfile AS a user that consumes the plugin through a jenkinsfile pipeline I NEED to be able to include custom user fields in said pipeline TO be loaded into the tool for the different entities, test and testcase Modify example JENKINS-52753 to include the fields testSetFields: [ 'user-01': 'VALUE', 'user-02': 'VALUE'], //List user-fields associate with testSet testCaseFields: [ 'user-3': 'VALUE', 'user-04': 'VALUE']
// EXAMPLE
post {
always {
junit testResults: '**/target/*-reports/TEST-*.xml', allowEmptyResults: true
step ([$class: 'TestResultToALMUploader',
almServerName: 'HP ALM Isban',
credentialsId: 'CREDENTIALS',
almDomain: 'DOMAIN_ALM',
almProject: 'ALM_PROJECT',
testingFramework: 'JUnit',
testingTool: '', //testingTool
almTestFolder: 'Demo HP TEST ALM',
almTestSetFolder: 'Demo HP TEST ALM',
almTimeout: '-1',
testingResultFile: "**/junitResult.xml",
jenkinsServerUrl: '',
testSetFields: [ 'user-01': 'VALUE', 'user-02': 'VALUE'], //List user-fields associate with testSet
testCaseFields: [ 'user-3': 'VALUE', 'user-04': 'VALUE']
[JIRA] (JENKINS-53115) Failure to parse JUnit after upgrading from 1.104 to 2.2.3
Title: Message Title Nikolas Falco commented on JENKINS-53115 Re: Failure to parse JUnit after upgrading from 1.104 to 2.2.3 Miss the required errors attribute on testsuite element. Refer to the wiki about changes in 2.x Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53115) Failure to parse JUnit after upgrading from 1.104 to 2.2.3
Title: Message Title Nikolas Falco closed an issue as Not A Defect Jenkins / JENKINS-53115 Failure to parse JUnit after upgrading from 1.104 to 2.2.3 Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google 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-53115) Failure to parse JUnit after upgrading from 1.104 to 2.2.3
Title: Message Title Nenad Miksa created an issue Jenkins / JENKINS-53115 Failure to parse JUnit after upgrading from 1.104 to 2.2.3 Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-08-18 08:12 Environment: Jenkins 2.136 Master node is on ArchLinux x64, installed from pacman repository Priority: Major Reporter: Nenad Miksa Here is the exception I get: org.jenkinsci.plugins.xunit.service.TransformerException: The result file '/opt/fast/jenkins/jenkinsData/Executor3/build/ios-jenkins-Release/junit/CoreUtils.xml' for the metric 'JUnit' is not valid. The result file has been skipped. at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:112) at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:39) at hudson.FilePath.act(FilePath.java:1076) at hudson.FilePath.act(FilePath.java:1059) at org.jenkinsci.plugins.xunit.XUnitProcessor.processTestsReport(XUnitProcessor.java:180) at org.jenkinsci.plugins.xunit.XUnitProcessor.process(XUnitProcessor.java:150) at org.jenkinsci.plugins.xunit.XUnitBuilder.perform(XUnitBuilder.java:114) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at
