---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Publish an app from AES when linked to source control

# Publish an app from App Engine Studio when linked to source control {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 min. de leitura

You can publish a custom application from App Engine Studio (AES) when linked to source control.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

When you publish an application from App Engine Studio that is linked
to source control, there is a different outcome than when you publish via the
sys_app or sys_store_app Publish related link.

## Procedimento

1. Navigate to AllApp EngineApp Engine Studio.
2. From the My Apps page, open your application.
3. From the app home, select Publish.  
   App Engine Studio displays the publish app fields.
4. Enter the following field values.  
   {#publish-application__table_skj_zxl_s5__entry__2}

   | Field | Description |
   |-|-|
   | Version | View your current app version and provide a new version number for your application. Nota: To change the version number, you must have one of the following deployment permissions: Submit for deployment, Publish to app repo, or Publish to app store |
   | Release notes | Provide a brief description of the changes made to your application. |
   | Publish options | Select if you want the application to be published to your application repository or the ServiceNow Store. |
   [Tabela 1. Provide a version number and release notes]

   {#publish-application__table_skj_zxl_s5}  
   Nota:  
   All application developers on the instance share the credential used to link a Git repository to an application.
5. Select Continue.
6. The current state of the application is committed to source control, including any untracked or uncommitted changes.  
   The value of the glide.sourcecontrol.default_commit_mode property is ignored.  
   This occurs because when the application is published, all the untracked and uncommitted changes are also published. Therefore, the state of the application in the Git repository matches what is published. See the [Commit changes to a repository](https://servicenow-prod.fluidtopics.net/9JQVTvzj9dmgZlBPuZgt1w "Commit changes made in your application in App Engine Studio (AES) to a linked Git repository. You can either select a few changes to commit, or commit all changes on the instance at once.") topic for more information about the glide.sourcecontrol.default_commit_mode property.
7. A source control tag is created for the new version and the application is published.  
   If needed, the sys_app record is updated with the new store correlation ID.  
   Nota:  
   If your application is linked to source control and you publish a new version outside of App Engine Studio, a source control commit and tag are not created.
{#publish-application__steps_ldh_g1l_qqb}