I have the following deploy process (not sure if I understood everything right as I still try to figure out some relations [e.g. environment <> target]).
app process is performing the overall choreography of the deploy. When the environment is
PlayStore Dev Testing the actual deploy will be handled by thy
app-creation process and for all other environments it will be handled by the
app-promotion process. From my point of view this “split” is quite handy as I don’t need to place a lot of conditions into one process depending on the environment but just start a sub-process.
I have one deployment target (
PlayStore Target) to manage the deploy.
The problem is, that
app-promotion is long-running because it’s a rolling deploy taking up around 2 days for a complete roll-out for
PlayStore Alpha Testing (1 week for
PlayStore Beta Testing and 2 weeks for
PlayStore Production). The process themself contains multiple
Which are simply derived from the pre-existing
Wait task to accept an environment variable as wait time.
The main problem that will occur, is that while a deploy is still “waiting” in the
app-promotion process, no other deploy can be done in the
app-creation process because the target is still in use (even if it’s only waiting).
I tried to add another deploy target (for example
PlayStore Creation Target (env. alpha only) and
PlayStore Promotion Target (other three envs.) only for the given environments) but this will cause errors in the main process. I also tried to add more targets which are the same as the main target but this caused the process to run multiple times causing other errors. Finally, adding more target just blows up my target “budget” and it’s looking unnecessary to me because the Tentacles are 99% of the time in
Wait tasks anyway.
My question is: Is there a non-blocking Wait-Task which allows a tentacle to perform other tasks while waiting?
Are there any problem / mind-traps which I might not notice?
Any help would be welcome