I am wondering if it's possible to create a parent workflow that contains multiple concurrent nested child workflows, all active at the same time. I'm not talking about multiple levels of nesting. This nesting would be one level deep, but more than one child would be active at the same time. Here's the requirement:
We have a new, rather large, initiative that calls for a 3rd party vendor to develop a site or a modification to an existing site on our extranet. The vendor will drop assets (we are calling a set of assets that are encased in a job a
package) into TeamSite and kick off a job. That job may contain application code assets, web content assets, database assets, config assets, etc. Each type of asset needs to progress down its own development cycle path (child job) and eventually (it's not clear yet when) all of the separate development paths converge again for integration testing in the parent job. As an added "feature" they may want dependency functionality as well. In other words, don't push the code assets to the QA environment until the database assets are pushed to the QA environment. So that means one child job may need to know the state of another child job. It can get even more complex, but I need to know if this pattern is even possible. I can provide more detail if needed.
My main questions are:
o
Is it possible to have 1 to n nested child jobs active in a parent job?o
If so, can a parent job maintain the state of all its child jobs (in variables) so that each child job can know the state of any other child job?Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
