Triggering multiple

Hi

What we are trying to do is kick off two other application , a web service app and then a web app.
If we run the two apps individual , ie create release, build ext and promote .. All works fine.
If we create a new app with the same workflow steps (internal, stage, prod)
• In app for Internal we have two new “Create new build actions” for the web service and web app ..
• On the second stage we have two promote build actions for the web service / web site . ie from internal to stage

When we run the new app , ie create release/ build.. the first stage passes ie build to internal, then if we promote we see the web service build and then get a strange error

Build 1 for Nebula And Members 4.4 (27/07/2012 1:51:06 AM)
Action Group 1: Deploy To Stage
Action 1: Force Build in Nebula from Internal to Staging.
Preparing remote servers for execution...
Preparation complete.
Initializing Action...
Initialization Complete. Executing...
Build #52 of Nebula (4.24) is currently in Staging; expected Internal
Execution Complete. Finalizing...
Finalization Complete.

Are we doing something wrong , is this supported ?

That sounds like it should work based on your setup. What do your settings look like for the two promote build actions?

Hi

We are not doing anythign fancy...
have teh app to promote set to teh app type (webservice or web) , release set to all. Promotion details Form internatal , to enviroment staging. Have tried with "force promotion , on and off with no dif.

At a bit of a loss on this one

Andrei

After reviewing the code within the action I believe I have discovered the bug that would cause the behavior you're seeing provided you have builds in both Internal and Staging at the time of the promotion.

I will enter this issue into our issue tracker and expect a fix to be included in the BuildMasterBeta extension by the end of the day.

Thanks look forward to it