Jenkins UI is a deprecated feature. We highly recommend starting to use the new Deployments after it is enabled in your ADE environment.
Deployment Management is a user interface used to control the deployment process after changes have been committed from the Designer.
This is an overview of the deployment process.
Automatic promotion and deployment
Automatic promotion and deployment is done by committing a package in Designer. This is possible when the deployment settings AUTOMATIC PROMOTION and AUTOMATIC DEPLOY of the Runtime environment are set to true.
A package is committed in Designer in the Commit tab. By committing a package changes made into it are stored into a commit repository.
Deployment Management takes over and proceeds with automatic package promotion and deployment.
Manual promotion is done inside the package job in Status tab. Package jobs have the same names as the committed packages.
Go to the desired package job.
Promote the package with Proceed:
If the package job has been aborted and is no longer waiting for promotion, it can be promoted by building it again:
Press Build with Parameters.
Select the target environment with promoteToEnvironment, leave other parameters to default and press Build.
Manual deployment is done by starting the deployment job with Build with Parameters. Deployment jobs are named like:
Go to the desired deployment job.
Select Build with Parameters.
Start the deployment job with Build.
If there are errors in a deployment, find the failed build from the deployment job:
Go to the deployment job (e.g. Deploy_dev_instance_default).
Move the mouse cursor over the latest deployment in the Build history and press the appearing arrow.
Select Console Output.
Press Full Log if needed and look for the failed package job.