[JIRA] [lockable-resources-plugin] (JENKINS-34892) lock step in Pipeline should allow creation of implicit locks
Title: Message Title Nigel Harniman commented on JENKINS-34892 Re: lock step in Pipeline should allow creation of implicit locks Should this say: that prevents other builds of this job from entering Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [customtools-plugin] (JENKINS-30680) Make CustomToolInstallWrapper compatible with workflow
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-30680 Make CustomToolInstallWrapper compatible with workflow Issue Type: Bug Assignee: Oleg Nenashev Components: customtools-plugin Created: 28/Sep/15 5:26 PM Labels: workflow Priority: Minor Reporter: Nigel Harniman Add support for workflow Add Comment
[JIRA] [ansicolor-plugin] (JENKINS-30528) Add ANSI colour support to workflow log output
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-30528 Add ANSI colour support to workflow log output Issue Type: Improvement Assignee: Unassigned Components: ansicolor-plugin Created: 17/Sep/15 8:15 PM Labels: workflow Priority: Major Reporter: Nigel Harniman Add workflow log support to ansi-colour plugin Add Comment
[JIRA] [test-results-analyzer-plugin] (JENKINS-30522) Test results analyser should support workflow
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-30522 Test results analyser should support workflow Issue Type: Improvement Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 17/Sep/15 3:42 PM Labels: workflow Priority: Major Reporter: Nigel Harniman As a user I want to be able to analyse the test results for the various testing phases that exist in the workflow pipeline. Add Comment
[JIRA] [log-parser-plugin] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow
Title: Message Title Nigel Harniman commented on JENKINS-27208 Re: Make Log Parser Plugin compatible with Workflow Manuel Jesús Recena Soto What's the status of the PR? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title
Nigel Harniman updated an issue
Jenkins / JENKINS-30269
Add workflow support for resource locking
Change By:
Nigel Harniman
Add support to use this plugin from workflow to manage concurrent consumption of resources.Similar to how {{stage}} step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs.Continue to allow the resources to be set up in the Jenkins configuration.Consumption of resources should be controlled with a syntax along these lines:For a single resource:resource (name: db-a-1, reservedVariable: DB_RESOURCE) \ { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”} For a pool of resources sharing a label: resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) \ { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title
Nigel Harniman updated an issue
Jenkins / JENKINS-30269
Add workflow support for resource locking
Change By:
Nigel Harniman
Add support to use this plugin from workflow to manage concurrent consumption of resources.Similar to how {{stage}} step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs.Continue to allow the resources to be set up in the Jenkins configuration.Consumption of resources should be controlled with a syntax along these lines:For a single resource:resource (name: db-a-1, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE”}For a pool of resources sharing a label:resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) { // Do something here that uses the resourceecho “DB Resource(s) used = $DB_RESOURCE”}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [lockable-resources-plugin] (JENKINS-30269) Add workflow support for resource locking
Title: Message Title
Nigel Harniman created an issue
Jenkins / JENKINS-30269
Add workflow support for resource locking
Issue Type:
Improvement
Assignee:
Unassigned
Components:
lockable-resources-plugin
Created:
02/Sep/15 4:17 PM
Labels:
workflow
Priority:
Major
Reporter:
Nigel Harniman
Add support to use this plugin from workflow to manage concurrent consumption of resources.
Similar to how stage step works as blocked scoped to control concurrency of other builds for this job running this step at the same time, it would be useful to be able to do this for resources across jobs.
Continue to allow the resources to be set up in the Jenkins configuration.
Consumption of resources should be controlled with a syntax along these lines:
For a single resource:
resource (name: db-a-1, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE” } For a pool of resources sharing a label: resource (label: db-a, quantity: 2, reservedVariable: DB_RESOURCE) { // Do something here that uses the resource echo “DB Resource(s) used = $DB_RESOURCE” }
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman closed an issue as Won't Fix Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Change By: Nigel Harniman Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman resolved as Won't Fix Customer fixed permissions issue. Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Change By: Nigel Harniman Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert This fixed the customer's problem - was a permission issue. This can be closed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman commented on JENKINS-29763 Re: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Thanks for the info - we'll check these out. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing Issue Type: Bug Assignee: Unassigned Components: teamconcert-plugin Created: 03/Aug/15 7:12 PM Environment: Jenkins 1.609 teamconcert-plugin 1.1.9.3 Labels: workflow Priority: Major Reporter: Nigel Harniman When choosing to load the Workflow Groovy Script direct from the SCM (the Groovy CPS DSL from SCM definition option) the following error occurs: RTC : checkout... RTC Checkout : Source control setup RTC Checkout : Accepting changes into workspace "xxx-main-jenkins-pipeline" ... RTC Checkout : Fetching files to fetch destination "/mnt/workspace/XXX-Docker-Workflow@script" ... FATAL: RTC : checkout failure: Failed to create /mnt/workspace/XXX-Docker-Workflow@script/.jazz5 Failed to create /mnt/workspace/XXX-Docker-Workflow@script/.jazz5 com.ibm.team.build.internal.scm.SourceControlUtility$
[JIRA] [teamconcert-plugin] (JENKINS-29763) Load Workflow Groovy Script from SCM (RTC) is failing with team-concert
Title: Message Title Nigel Harniman updated an issue Jenkins / JENKINS-29763 Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Change By: Nigel Harniman Summary: Load Workflow Groovy Script from SCM (RTC) is failing with team-concert Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [teamconcert-plugin] (JENKINS-29076) Auto create job parameters on trigger from RTC
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-29076 Auto create job parameters on trigger from RTC Issue Type: New Feature Assignee: Unassigned Components: teamconcert-plugin Created: 25/Jun/15 7:26 AM Environment: 1.609 teamconcert 1.1.9.2 Labels: scm plugins Priority: Minor Reporter: Nigel Harniman RTC parameters other than buildResultUUID are not recognised unless we add a string parameter to the Job definition. Can the teamconcert-plugin detect them and auto modify the job.
[JIRA] [maven-plugin] (JENKINS-28761) Add maven site link when a workflow job produces a maven site
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-28761 Add maven site link when a workflow job produces a maven site Issue Type: New Feature Assignee: Unassigned Attachments: Screen Shot 2015-06-04 at 16.40.40.png Components: maven-plugin Created: 05/Jun/15 7:55 AM Environment: Jenkins 1.580.13.1 Workflow 1.4 Labels: workflow Priority: Minor Reporter: Nigel Harniman This may be best delivered via a new publisher plugin**
[JIRA] [seleniumhtmlreport-plugin] (JENKINS-28388) Make SeleniumHtmlReportPublisher a SimpleBuildStep
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-28388 Make SeleniumHtmlReportPublisher a SimpleBuildStep Issue Type: New Feature Assignee: m211 Components: seleniumhtmlreport-plugin Created: 13/May/15 9:22 PM Priority: Major Reporter: Nigel Harniman Would allow for use from workflows. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [veracode-scanner-plugin] (JENKINS-28387) Make VeracodeNotifier a SimpleBuildStep
Title: Message Title Nigel Harniman created an issue Jenkins / JENKINS-28387 Make VeracodeNotifier a SimpleBuildStep Issue Type: New Feature Assignee: Mike Bockus Components: veracode-scanner-plugin Created: 13/May/15 9:11 PM Labels: workflow Priority: Major Reporter: Nigel Harniman Would allow for use from workflows. Add Comment
[JIRA] [workflow-plugin] (JENKINS-27916) Unable to pass variable to file path element of unarchive map
Nigel Harniman created JENKINS-27916 Unable to pass variable to file path element of unarchive map Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 13/Apr/15 2:26 PM Description: I want to resolve the artifact to be unarchived at execution time. Therefore I want to be able to perform the following: requiredFile = 'target/' unarchive mapping: [requiredFile: .] Unfortunately this does not replace `requiredFile` with its value. trying to use the Groovy style like this: unarchive mapping: ["$requiredFile": .] results in java.lang.ClassCastException: org.codehaus.groovy.runtime.GStringImpl cannot be cast to java.lang.String Environment: 1.580.13.1 / Workflow 1.4 Project: Jenkins Priority: Minor Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [claim-plugin] (JENKINS-27206) Enable claim support from workflow
Nigel Harniman updated JENKINS-27206 Enable claim support from workflow Change By: Nigel Harniman (02/Mar/15 9:32 PM) Labels: workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Nigel Harniman created JENKINS-27209 Enable reporting of compiler warnings in workflow steps Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-plugin Created: 02/Mar/15 9:26 PM Description: Enable generation of trend report data on compiler warnings from workflow build steps. Handle multiple compiles in a workflow. Project: Jenkins Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [warnings-plugin] (JENKINS-27209) Enable reporting of compiler warnings in workflow steps
Nigel Harniman updated JENKINS-27209 Enable reporting of compiler warnings in workflow steps Change By: Nigel Harniman (02/Mar/15 9:26 PM) Labels: workflow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [log-parser-plugin] (JENKINS-27208) Add workflow compatibility to log-parser
Nigel Harniman created JENKINS-27208 Add workflow compatibility to log-parser Issue Type: New Feature Assignee: rgoren Components: log-parser-plugin Created: 02/Mar/15 9:19 PM Description: highlighting lines of interest in workflow logs (errors, warnings, information) dividing the log into sections based on stages and parallel executions displaying a summary of number of errors , warnings and information lines within the workflow log and its sections. linking the summary of errors and warnings into the context of the full workflow log, making it easy to find a line of interest in the log showing a summary of errors and warnings on the build page Project: Jenkins Labels: workflow Priority: Minor Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [timestamper-plugin] (JENKINS-27207) Add timestamps to workflow console output
Nigel Harniman created JENKINS-27207 Add timestamps to workflow console output Issue Type: New Feature Assignee: stevengbrown Components: timestamper-plugin Created: 02/Mar/15 9:12 PM Description: Add timestamps to workflow job output Project: Jenkins Labels: workflow Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [claim-plugin] (JENKINS-27206) Enable claim support from workflow
Nigel Harniman created JENKINS-27206 Enable claim support from workflow Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 02/Mar/15 9:02 PM Description: It should be possible to claim failed workflow builds. Project: Jenkins Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [hipchat-plugin] (JENKINS-27202) Implement SimpleBuildStep for Workflow Compatibility
Nigel Harniman created JENKINS-27202 Implement SimpleBuildStep for Workflow Compatibility Issue Type: New Feature Assignee: Unassigned Components: hipchat-plugin Created: 02/Mar/15 5:05 PM Description: hipchat-plugin should implement SimpleBuildStep to allow tighter workflow integration. This will enable workflow to trigger hipchat notifications after a build step rather than at the end of the workflow job. Project: Jenkins Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-27098) Support outputting deployments to environment-dashboard
Nigel Harniman commented on JENKINS-27098 Support outputting deployments to environment-dashboard Done. See https://github.com/vipinsthename/environment-dashboard/issues/20 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-27098) Support outputting deployments to environment-dashboard
Nigel Harniman created JENKINS-27098 Support outputting deployments to environment-dashboard Issue Type: New Feature Assignee: Jesse Glick Components: workflow-plugin Created: 24/Feb/15 8:48 AM Description: Linked to JENKINS-24673. It would be useful to support BuildWrappers in workflow so that plugins such as environment-dashboard could be used to provide visibility of deployments. NB- there is no component in Jira for environment-dashboard Project: Jenkins Labels: workflow Priority: Minor Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [svn-tag-plugin] (JENKINS-26949) Implement SimpleBuildStep for Workflow Compatibility
Nigel Harniman created JENKINS-26949 Implement SimpleBuildStep for Workflow Compatibility Issue Type: New Feature Assignee: k2nakamura Components: svn-tag-plugin Created: 12/Feb/15 10:47 PM Description: svn-tag should implement SimpleBuildStep to allow tighter workflow integration. Project: Jenkins Labels: workflow Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [msbuild-plugin] (JENKINS-26948) Implement SimpleBuildStep for Workflow Compatibility
Nigel Harniman created JENKINS-26948 Implement SimpleBuildStep for Workflow Compatibility Issue Type: New Feature Assignee: kdsweeney Components: msbuild-plugin Created: 12/Feb/15 10:44 PM Description: msbuild-plugin should implement SimpleBuildStep to allow tighter workflow integration. Project: Jenkins Labels: workflow Priority: Major Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-26635) Provide Groovy workflow build step
Nigel Harniman updated JENKINS-26635 Provide Groovy workflow build step Change By: Nigel Harniman (27/Jan/15 3:56 PM) Summary: Provide Groovy workflow build step Description: Provide a built in step in its own intepreter interpreter for running Groovy code to separate it out from the workflow DSL.Although its possible ti run a groovy script from within the sh task having a native capability would be better.NB this is blocked by https://issues.jenkins-ci.org/browse/JENKINS-26055 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-26513) Deserialization error of ExecutorStepExecution
Nigel Harniman
commented on JENKINS-26513
Deserialization error of ExecutorStepExecution
I have reproduced this using local linux slaves.
Having the following DSL
node('linux') {
echo "Now on slave"
def x=0
for ( i in 0..1000 ) {
echo "I'm waiting: $i"
sleep 1000
x += i
}
}
And restarting Jenkins Master causes the error to occur repeatedly.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [groovy-plugin] (JENKINS-26635) Provide Groovy workflow step
Nigel Harniman created JENKINS-26635 Provide Groovy workflow step Issue Type: Improvement Assignee: vjuranek Components: groovy-plugin Created: 27/Jan/15 3:56 PM Description: Provide a built in step in its own intepreter for running Groovy code to separate it out from the workflow DSL. Although its possible ti run a groovy script from within the sh task having a native capability would be better. NB this is blocked by https://issues.jenkins-ci.org/browse/JENKINS-26055 Environment: Jenkins 1.580.2.1 Workflow (all) 1.1 Project: Jenkins Labels: workflow Priority: Minor Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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] [workflow-plugin] (JENKINS-26143) Workflow Snippet Generator - Incorrect format for Input with Choice Parameter
Nigel Harniman created JENKINS-26143 Workflow Snippet Generator - Incorrect format for Input with Choice Parameter Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 17/Dec/14 8:07 PM Description: Snippet generator generates an array: input id: 'Cc2a7d4d888ad098e3ca0ed7599d887d', message: 'Which environment?', ok: 'Submit', parameters: [[$class: 'ChoiceParameterDefinition', choices: ['Red', 'Blue', 'Green'], description: '', name: 'env']] ChoiceParameterDefinition requires delimted string. Workaround by modifying the snippet code by converting array to string with "\n" separator. ie input id: 'Cc2a7d4d888ad098e3ca0ed7599d887d', message: 'Which environment?', ok: 'Submit', parameters: [[$class: 'ChoiceParameterDefinition', choices: 'Red\nBlue\nGreen', description: '', name: 'env']] Environment: Jenkins 1.580.1.1 Linux 18559e0ec842 3.16.7-tinycore64 #1 SMP Thu Nov 20 00:06:13 UTC 2014 x86_64 GNU/Linux java version "1.7.0_65" OpenJDK Runtime Environment (IcedTea 2.5.3) (7u71-2.5.3-2) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) Project: Jenkins Priority: Minor Reporter: Nigel Harniman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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.
