[JIRA] [core] (JENKINS-19728) Much needed dependency management between jobs

Tue, 11 Nov 2014 07:55:35 -0800

Jesse Glick commented on New Feature JENKINS-19728

Have you tried implementing these kinds of use cases using the Workflow system? It does nothing magical in terms of investigating dependencies; it just runs the things you told it to, in the order you told it, under the conditions you specified. Nonetheless it has some aspects which allow it to model the kinds of scenarios you discuss better than the Build Flow DSL plugin. In particular:

  • While there is a build step to call out to “legacy” jobs, you need not use this at all, and can have all steps defined in one flow. This means that there is no chance of some subsection of the script being invoked independently and out of context—unless you made the flow parameterized and wrote its script to expect to skip some stages sometimes.
  • You can have multiple SCM checkouts in one flow, with a single polling/changelog function.
  • archive and unarchive let you pass artifacts between workspaces without using the Copy Artifact plugin. Or, if different stages can all run in one workspace, you need not do any copying at all.

In common with Build Flow:

  • You can freely pass information from one part of the flow to another, as local variables.
  • You can use parallel to run some things concurrently, with an implicit join.
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to