How to use ReleaseOps with an Update Set to deploy a new app scope

[Jon G Lind]

Today I'm going to show you how to use ReleaseOps to deploy a brand new applications scope.

00:01: Hello. This is Jon Lind and today, I'm going to show you how to use release Ops to deploy a brand new applications scope.

00:13: So we're going to publish an app.

00:17: With update sets and use deployment requests in the release Ops to push it through the environments.

00:25: To do this, you simply go to your newly created application and use the publish to update set related link.

00:34: And like anything else, you'll get a new update set.

00:37: the update set is already complete, so all you have to do is choose promote update said,

00:42: Create a new deployment request and then add that to your release.

00:55: This is a great way to initialize your application.

00:59: At it to release and then you can add other DRS to that same release.

01:04: So that you have an entire complete application or anything to go and deploy as a unit.

01:17: Thank you. Hope, will you see how easy that is? And don't forget to do this whenever you're initializing a new application scope and make sure that's your first deployment. Request added to your release, Ops release.

 

Publish App with Update Set

We are going to publish a new app with update sets and use deployment requests in ReleaseOps to push it through the environments. To do this, you simply go to your newly created application and use the publish to update set related link. And like anything else, you'll get a new update set. The update set is already complete, so all you have to do is choose "promote update set", create a new deployment request and then add that to your Release.

This is a great way to initialize your application before you start adding changes using Deployment Requests.

Thank you. Hopefully you see how easy that is and don't forget to do this whenever you're initializing a new application scope and need to deploy it with ReleaseOps.

[-O-]

Hello,
Thank you for the video.
I wonder, wouldn't the "Add app install to current update set" be a better option?
I mean in that case the application would remain in App. Repo. mode (vs. update set mode).

[Mikael Karlsson]

I would use the app repo and app engine management center pipeline to do the automatic deployment. I've always learnt that we should never ever mix update set and repo for scoped apps.

[Daniel Draes]

@Kilo Patron: No, if you want to use ReleaseOps, then updated sets is the way to go for now. You don't want or need the app to be in AppRepo mode. This is only relevant if you use the App Engine Pipelines.

@Mikael Karlsson If you use AEMC and that pipeline, yes. At this point customers have options.... App Repo or Update sets. Both can be automated - and yes, you should not mix/flip-flop between the two.

[-O-]

@Daniel Draes I know it needs to be in an update set, but when one uses the "Add app install to current update set" one will still get an update set that can be promoted via the ReleaseOps pipeline.

When using related link UI Action a sys_upgrade_plan_item record is added to the update set. And the application remains in (My Company) App. Repo. mode.

[Daniel Draes]

Ah.. I read you comment the other way round. This seems more reasonable. I'll run a test for myself. thanks.

[-O-]

No problem 🙂