UrbanCode Deploy

Deployment Triggers in UrbanCode Deploy

One of our goals with UrbanCode Deploy has been to address a number of high priority RFEs. In this post, I’ll go over our rework and enhancement of the feature formerly known as “Run Process after a Version is Created” and now called “Deployment Triggers.”

Deployment Triggers play a major role in helping to automate tasks that need to happen after a version is imported. The key feature we’ve added here is the ability to specify the user to run the process. In the earlier feature all processes would be run as admin and be configured on the component level. This was causing security concerns for our users and it was impossible to have more than one process run after a version was created. Now, you can find Deployment Triggers at an environment’s configuration pane, which drastically lowers configuration time when leveraging this feature. With the new Deployment triggers there’s no limit to the amount of triggers that can be created (per component) making this feature much more useful! 

deployment triggers

To run a process as a specific user, we’ve added a new security permission. A best practice would be setting up a single user to act as your “version import processes” user. You would then specify that user for all of your deployment triggers.

Any “triggers” you have from before this feature was updated will me migrated over and set to run as admin user by default.

Should the trigger be executed on an environment that requires approvals, we will still wait to execute the deployment until all relevant approvals have been given. The UI will display a helpful link to the deployment trigger in the description of that deployment request.

deployment triggers

Stay tuned for more exciting updates as we approach our release!