Roll Back a Published Extension

Sometimes after publishing your changes to an Oracle Cloud Applications instance, you might need to roll them back. When you "roll back" an extension, what you're actually doing is redeploying a previous extension version. To do this, you'll need to locate the previous version in VB Studio, and then move it to your extension's remote repository so that you can redeploy it.

It's always best to redeploy the previous version's actual build artifact that was originally packaged and deployed. If you have access to this build artifact in Advanced mode and you'd like to redeploy it, see this blog.

But, if you’re working in Express mode, it’s likely that the way you publish your extension means that build artifacts aren't available for future redeployment. Instead, here's a quick overview of the process you'll need to follow to roll back to a previous version.

In the Designer, switch your branch to the previous extension version.

Tip:
Look for the branches named <user name>-<timestamp>; these are the branches that are created each time you publish a release.

When switching, select the New branch from selected checkbox.
Push the new branch to your remote repository.
Switch to Advanced mode and, on VB Studio's Builds page, configure your extension's package job with a new "Branch" parameter.

Set the parameter's default value to main so that, when you use the Publish button in VB Studio, everything still functions as usual.
Run the package job manually, entering your newly created branch (instead of main) in the parameter you just added.
The package job will run and create a build artifact using the specified branch. Once the job finishes, it will automatically trigger the deploy job as usual.

For step-by-step instructions, see this blog.