Adding new components to an application via Jenkins does not order them

[bglee]

When adding multiple new components to an application the components do not end up in the correct deployment order. Instead they are all under the base:

This means when I do deployment it freezes and never completes the deployment. (I am not sure why it does this)

If I rearrange them manually they deploy correctly:

This works for now but it would be desirable to have the components arranged correctly for sequential deployment when starting a new application from scratch via Jenkins. I would also like to understand why the parallel component deployment freezes.

CC: @piyush94 , @svisagan83

[sbtaylor15]

@bglee we double checked that the new component will be added to the end of the list, but you need to start with an ordered list. Try running the Jenkins Job with the list already ordered and let us know the results. A new component should be added to the end and an existing component with new version should be updated in place.

CC: @piyush94 , @svisagan83

[bglee]

The following were my experiments. Each time in between I order the components manually. The process creates a new application version before adding the new components to it. It adds multiple components before doing a deploy.

Script: new application version and add 1 component

Script: new application version and add 5 components (Moved components for visibility)

Manual: Reorder

Script: new application version and add 2 components (Moved components for visibility)

Manual: Reorder

Script: new application version and add 3 components (Moved components for visibility)

It looks like each time the new components are assigned to the application parallel to the last assigned component.

Is there another way I should order the components?

CC: @piyush94 , @svisagan83

[sbtaylor15]

@bglee it looks like the last component version in the list is not being found correctly. Let us double check the logic for finding it. We may need to do a web meeting. We will let you know.

The other way is to find the new component's parent and then do the assignment. This is a bit of work since you need to loop through the version array.

CC: @piyush94 , @svisagan83

[sbtaylor15]

@bglee we changed the recursive search to find the last component in the list. Please reorder back to the serial list and try again with the latest DeployHub image. The new component should be added to the end of the list.

CC: @piyush94 , @svisagan83

[bglee]

@sbtaylor15 - I have confirmed the fix works by running a Jenkins job that adds multiple components. The resulting application has the components ordered sequentially.

CC: @piyush94 , @svisagan83