assembly status improvements

[Paul Czarkowski]

Each step of the assembly process should have a Starting status and a Finished status.

At the start of the build process the status is set to BUILDING and then when the deploy process is started it is set to DEPLOYING

If an error happens after the build completes but before the deploy starts ( or the deployer handler is set to NOOP ) then the status will never change from BUILDING.

If we change the status to BUILT on completion of the build process then we have finer granularity of the build process and where errors are caused.

[Angus Salkeld (asalkeld)]

I think we should make assembly fit on top of the pipeline code (if keep it at all). I am quickly getting weary of people working on assembly when we have moved on.

[Adrian Otto (aotto)]

I do agree with Angus' sentiment that the assembly status should mirror the status of the underlying pipeline once we implement each of the assembly related tasks as pipelines.

I view the refactoring of Assembly to use Pipeline resources for tasks as a prerequisite for solving this.

[Devdatta Kulkarni (devdatta-kulkarni)]

We have added 'BUILT' status to workflow (and assembly).