Deploy Now vs. Deploy Later

Updated 4 months ago by Copado Solutions

Deploy Now

This option will start the deployment immediately. First of all, Copado will verify that there are enough credits in your account before starting the process, in order to prevent the deployment from being halted before the end due to insufficient credits. Credit validation is performed also during the deployment process.

Deploy Later

This option will start the deployment at a specified date and time. Copado will verify that there are enough credits in your account before starting the process, in order to prevent the deployment from being halted before the end due to insufficient credits. Credit validation is performed also during the deployment process.

To test that everything is set, schedule a deployment for later and then go to Setup -> Scheduled Jobs. You should see your scheduled job there.

Session Management

On April 19, 2016 we updated our backend, which affects all Copado users (and it is not related to your installed version). Previously, a deployment being run by a user other than the deployment owner would have used the owner's OAuth session to update the Deployment record. When using deployment history reports, the owner would still show up as the one having updated the deployment status (thus, it looked like the owner had executed the deployment).

With the new update, Copado will honor the running user's OAuth information, if available. If this information is not available, the deployment owner's Oauth information will be used to update the Deployment record. If neither OAuth information is available, the running user's browser session will be used instead. Remember that if the browser session expires during long-running deployments, Copado will not be able to update the deployment. We, therefore recommend that each Copado user creates an Org Credential for their own Copado user.


How did we do?