• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: elasticbox-plugin
• Labels:

  • pipeline

[JENKINS-25978] Workflow integration

Collapse comment: Jesse Glick added a comment - 2014-12-12 19:26

Jesse Glick added a comment - 2014-12-12 19:26

Cf.: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md

Expand comment: Jesse Glick added a comment - 2014-12-12 19:26

Jesse Glick added a comment - 2014-12-12 19:26 Cf.: https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md

Collapse comment: Phong Le added a comment - 2014-12-12 20:20

Phong Le added a comment - 2014-12-12 20:20

We will consider making ElasticBox build steps and post build actions available in the workflow job. This is not only to enable workflow to utilize temporary servers for testing purpose but also to deploy and manage application running on any clouds as well.

Expand comment: Phong Le added a comment - 2014-12-12 20:20

Phong Le added a comment - 2014-12-12 20:20 We will consider making ElasticBox build steps and post build actions available in the workflow job. This is not only to enable workflow to utilize temporary servers for testing purpose but also to deploy and manage application running on any clouds as well.

Collapse comment: Jesse Glick added a comment - 2014-12-12 21:26

Jesse Glick added a comment - 2014-12-12 21:26

So for build steps (including post-build actions) you just need to implement SimpleBuildStep. To allow workflow node blocks to run on ElasticBox clouds, possibly nothing is required, but you should not implement EphemeralNode (so the flow can survive a restart of Jenkins), and you may need to use the APIs in the executions package of the durable-task plugin to prevent a slave from being disposed of too early.

Expand comment: Jesse Glick added a comment - 2014-12-12 21:26

Jesse Glick added a comment - 2014-12-12 21:26 So for build steps (including post-build actions) you just need to implement SimpleBuildStep . To allow workflow node blocks to run on ElasticBox clouds, possibly nothing is required, but you should not implement EphemeralNode (so the flow can survive a restart of Jenkins), and you may need to use the APIs in the executions package of the durable-task plugin to prevent a slave from being disposed of too early.