Source control (Github) and Update sets

[Hamza EL JIRARI]

Hello,

We are exploring the use of custom apps, i am following the tutorials on how to use UI Builder and i am wondering how we are supposed to move the modifications done on dev environement to test / prod.

Normally this would be updat sets, when commiting my changes in git, i discovered on custom app a ui action "publish to update set". Is this the correct way of moving the modifications done and stocked on git to other environements ?

BR,

Hamza.

[Tom Sienkiewicz · Accepted solution]

Hi,

theres a few options to move scoped apps, all have their pros and cons.

The "Publish to application repository" allows you to move the entire app from DEV to TEST etc. It uses a SN-provided app repo and is similar to installing from store. Usually used for bigger releases but it can also be used for smaller increments, dependfing how you set up your testing.

"Publish to update set" will export the app and any demo data you've added to a single US, which is also quite convenient to move between instances. Similar to app repo really.

Then there's the regular way of moving multiple smaller US. This can be used if you prefer to move and test smaller chunks (closer to devops).

And the fourth option is to connect to source control / pull via Git. You can use this if it fits well in your devops stack and have multiple devs working on the app.

I personally alternate between using the app repo, which is very convenient, and traditional US, when I need to have more ocntrol over what/when is moved.

[Hamza EL JIRARI]

Hello,

Thx, i think we will use the classic way (via publish to update sets). We wont be having big apps to developp (more small to medium sized apps).

DEV will be the only environement with GIT, once a version is ready we will use update sets.

BR,

Hamza.