cancel
Showing results for 
Search instead for 
Did you mean: 

Auto Deploy to ASR

colindstephenso
Champ in-the-making
Champ in-the-making
Hey All,

I am testing an upgrade of a 3.1.0 project in 4.0.1.  So far this is all working pretty well after correcting some API invocations.  As part of the customisation the user can modify content, then submit it using the submitdirect workflow and have it auto delpoy to the live servers.

The customisation is invoking

submitListAssets(java.lang.String sbStoreId, java.util.List relativePaths, java.lang.String workflowName, java.util.Map workflowParams, java.lang.String submitLabel, java.lang.String submitDescription, java.util.Map expirationDates, java.util.Date launchDate, boolean autoDeploy)

(yip, the deprecated API) and content is being successfully pushed out to the ASRs and FSRs.  Unfortunately this is all going too well in that the content is being deployed to all live servers even if they have the "include in auto deploy" unchecked.

Does submitListAssets() respect the autoDeploy flag on the live serves, or indeed does the submitdirect workflow respect this flag?  Do I have to some additional work to prevent this from happening?

Thanks
Colin.
2 REPLIES 2

mrogers
Star Contributor
Star Contributor
Auto deploy is only implemented for the "submit" workflow.   It is not implemented for the "submitDirect" workflow.

It's just JBPM workflow configuration so would be a fairly simple change to cut and paste the extra functionality.

colindstephenso
Champ in-the-making
Champ in-the-making
@mrogers, thanks for the information.  I compared the submitdirect workflow from 3.1.0 to 4.0.1 and they are the same.  Interestingly the same custom code only pushes to the Live Servers which have the "Include In Auto Deploy" flag checked.

// note: always submit via workflow (if no workflow selected, then defaults to direct submit workflow)
getSandboxService().submitListAssets(sbStoreId, relativePaths, workflowName, workflowParams, submitLabel, submitComment, expirationDates, launchDate, validateLinks, autoDeploy);

The only change to this call for 4.x was to remove the validateLinks parameter, so it looks like there is something else I need to take care of to make sure I only autodeploy to enabled live servers.

Can you direct me to what I might need to update in the submitdirect workflow?

Thanks,
Colin.