Publishing an application from App Studio

Before you begin: Review the steps in Configuring App Studio for publishing to ensure proper configurations of your systems before making application changes in App Studio. To publish an application change using App Studio:

1. Log in to your application in a development environment.
   Note: Application changes can only be published from a development environment.
2. In the top-right corner of App Studio, click Development.
   • If there are pending updates staged for publication, the application version states Not published in orange text.
   • If there are no updates, the application version states No changes.
3. Click Manage versions.
4. Your deployment pipeline is now visible under the Publish section, broken out into the pre-configured stages.
5. From the Development stage, click Publish to [next stage].
   Note: Publishing a new application aborts all existing publishes in progress, queued, and pending-promotion versions, irrespective of phase or stage. Ensure there are no active publishes in your pipeline before starting a new one.
6. In the publish confirmation dialogue, enter a short description for the publish log. You can also add any associated user stories/bugs if you have Agile Workbench configured with App Studio.
7. Click Ok.
8. The publishing of your application now progresses through your deployment pipeline model.
   Note: If you have a manual transition configured, this is marked in the pipeline model by a dotted-line between stages. This requires you to take action from the Deployment Manager portal.
9. Click Approve for production to finalize the publish and stage for production. App studio only supports the approval of publishing. To cancel or abort your publishing, simply start a new publish to overwrite any existing publishes in the pipeline.

See below for a few examples of the App Studio publish guardrails:

• App Studio can only publish if there is one configured deployment pipeline in Deployment Manager. App Studio returns an error if you attempt to publish with more than one deployment pipeline configured.

• If you have no pipelines configured, App Studio returns the following error. To add a pipeline in Deployment Manager, see Creating pipelines.
  
  

• It is not recommended to have a manual transition configured in your deployment pipeline. If a manual transition is required, you can configure this at the stage level. Once the stage encounters the manual transition (after all tasks complete in the stage), the Action Required alert is displayed on App Studio. You must switch to Deployment Manager to manually promote to the next stage.
  
  
  • If there is any manual input or approval needed between tasks for the deployment to proceed, you can configure the Perform manual step task in the pipeline. If the deployment is waiting at Perform manual step, you can approve directly from App Studio through the Perform manual step link.
  • 
    

• If a publish is paused, the pipeline will reflect that status with a Publish paused warning on in the stage on which it paused. To resume publication from the paused state, contact your application administrator.
  
  

• If a task fails for any reason in the publish cycle, the application publish will stop. The pipeline model provides a error for the stage on which Publish failed, along with the list of failed tasks to remedy before attempting to publish your application again. Once the issue is resolved, contact your application administrator to access Deployment Manager and retry the failed task and resume publishing.