Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform App Engine
Table of Contents
Choose your release version
    Home Orlando Now Platform App Engine Now Platform App Engine Application tools ServiceNow Studio Source control integration

    Source control integration

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Source control integration

    Enable application developers to integrate with a GIT source control repository. Save and manage multiple versions of an application from a non-production instance.

    Linking an application to source control allows all application developers on a non-production instance to:
    • Import applications from a GIT repository.
    • Pull and apply remote changes from a GIT repository.
    • Commit all local changes on the instance to a GIT repository.
    • Create tags to permanently link to a given version of an application.
    • Create branches to maintain multiple versions of an application simultaneously.

    Integration requirements

    To link an application to source control:
    • The non-production instance must have network access to the GIT repository.
    • Each application must be within its own GIT repository.
    • The repository user credentials must grant read and write access.
    Note: All application developers on the instance share a single set of credentials per repository.

    Options available from Studio

    After linking an application to source control, application developers can use Studio to manage the repository. From Studio, developers can:
    • Edit the application repository credentials.
    • Commit all local changes on the instance.
    • Apply remote changes from the repository.
    • Create a branch.
    • Switch branches.
    • Import an application from a remote repository.

    Source control integration does not support managing applications on a production instance. Instead, manage applications on a production instance using the application repository, an update set, or the ServiceNow Store. For more information about managing applications on a production instance, see Application sharing.

    Options available from a GIT repository

    ServiceNow offers limited support for modifying linked application files outside of an instance. From GIT, developers can:
    • Move application files to a different GIT directory structure.
    • Edit application files outside of Studio.

    The system generates a properties text file called sn_source_control.properties at the root level of the repository. To move application files to a different GIT directory structure, application developers can set the path parameter to specify the subfolder path containing their application files. For example, if you moved your application to the src/app subfolder, set the path to path=src/app.

    The system generates a checksum.txt file in the GIT repository to determine if any application files have been changed outside of Studio. When the checksum value from the file matches the current checksum value, the integration skips the validation and sanitization process. When the checksum values do not match, the integration validates and sanitizes the application files as part of the source control operation. The sanitization process:
    • Creates upgrade log entries for each sanitization action taken.
    • Removes unsupported folders and files from the repository.
    • Aborts all source control operations when a system application file fails XML schema validation. For example, if a database dictionary record fails XML schema validation, the system aborts all operations.
    • Skips the current source control operation when a non-system application file fails XML schema validation.

    The source control integration only sanitizes content within the application path listed in the sn_source_control.properties file. Repository content outside the application path is ignored.

    MID Server support

    Use an existing MID Server to connect to a source control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall.

    • Available source control operations

      The source control integration primarily supports operations from Studio, but can also support some operations directly from the GIT repository.

    • Link an application to source control

      Linking an application to source control allows application developers to manage changes from a GIT repository.

    • Import application from source control

      Import an application from a source control repository to continue developing it on this instance.

    • Apply remote changes

      Application developers can pull changes from a linked GIT repository to apply remote changes to the local instance.

    • Commit changes

      Application developers can commit all current changes on the instance to the linked GIT repository.

    • Stash local changes

      Application developers can remove and save changes locally to apply them later.

    • Manage stashes

      Application developers can apply or delete stashed changes from Studio.

    • Resolve conflicts

      Application developers can choose which application file version to use when applying remote or stashed changes.

    • Set default branch

      Set a default branch when you want to use a branch other than master for new changes or for your main development repository.

    • Create branch

      Application developers can create a branch to work on a new version of an existing application.

    • Switch branch

      Application developers can switch to a different repository branch to work on another version of the application.

    • View commit history

      Application developers can view the commit history of applications linked to a source control repository.

    • Move application files in a GIT repository

      Move application files linked to source control to any folder of the repository. Allow application developers to store supporting content such as automated tests in the same repository as the applications they support.

    • Collision avoidance

      Avoid modifying an application file across different update sets to ensure seamless experience during the commit process.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Source control integration

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Source control integration

      Enable application developers to integrate with a GIT source control repository. Save and manage multiple versions of an application from a non-production instance.

      Linking an application to source control allows all application developers on a non-production instance to:
      • Import applications from a GIT repository.
      • Pull and apply remote changes from a GIT repository.
      • Commit all local changes on the instance to a GIT repository.
      • Create tags to permanently link to a given version of an application.
      • Create branches to maintain multiple versions of an application simultaneously.

      Integration requirements

      To link an application to source control:
      • The non-production instance must have network access to the GIT repository.
      • Each application must be within its own GIT repository.
      • The repository user credentials must grant read and write access.
      Note: All application developers on the instance share a single set of credentials per repository.

      Options available from Studio

      After linking an application to source control, application developers can use Studio to manage the repository. From Studio, developers can:
      • Edit the application repository credentials.
      • Commit all local changes on the instance.
      • Apply remote changes from the repository.
      • Create a branch.
      • Switch branches.
      • Import an application from a remote repository.

      Source control integration does not support managing applications on a production instance. Instead, manage applications on a production instance using the application repository, an update set, or the ServiceNow Store. For more information about managing applications on a production instance, see Application sharing.

      Options available from a GIT repository

      ServiceNow offers limited support for modifying linked application files outside of an instance. From GIT, developers can:
      • Move application files to a different GIT directory structure.
      • Edit application files outside of Studio.

      The system generates a properties text file called sn_source_control.properties at the root level of the repository. To move application files to a different GIT directory structure, application developers can set the path parameter to specify the subfolder path containing their application files. For example, if you moved your application to the src/app subfolder, set the path to path=src/app.

      The system generates a checksum.txt file in the GIT repository to determine if any application files have been changed outside of Studio. When the checksum value from the file matches the current checksum value, the integration skips the validation and sanitization process. When the checksum values do not match, the integration validates and sanitizes the application files as part of the source control operation. The sanitization process:
      • Creates upgrade log entries for each sanitization action taken.
      • Removes unsupported folders and files from the repository.
      • Aborts all source control operations when a system application file fails XML schema validation. For example, if a database dictionary record fails XML schema validation, the system aborts all operations.
      • Skips the current source control operation when a non-system application file fails XML schema validation.

      The source control integration only sanitizes content within the application path listed in the sn_source_control.properties file. Repository content outside the application path is ignored.

      MID Server support

      Use an existing MID Server to connect to a source control repository. Linking or importing an application through a MID Server enables access to repositories behind a firewall.

      • Available source control operations

        The source control integration primarily supports operations from Studio, but can also support some operations directly from the GIT repository.

      • Link an application to source control

        Linking an application to source control allows application developers to manage changes from a GIT repository.

      • Import application from source control

        Import an application from a source control repository to continue developing it on this instance.

      • Apply remote changes

        Application developers can pull changes from a linked GIT repository to apply remote changes to the local instance.

      • Commit changes

        Application developers can commit all current changes on the instance to the linked GIT repository.

      • Stash local changes

        Application developers can remove and save changes locally to apply them later.

      • Manage stashes

        Application developers can apply or delete stashed changes from Studio.

      • Resolve conflicts

        Application developers can choose which application file version to use when applying remote or stashed changes.

      • Set default branch

        Set a default branch when you want to use a branch other than master for new changes or for your main development repository.

      • Create branch

        Application developers can create a branch to work on a new version of an existing application.

      • Switch branch

        Application developers can switch to a different repository branch to work on another version of the application.

      • View commit history

        Application developers can view the commit history of applications linked to a source control repository.

      • Move application files in a GIT repository

        Move application files linked to source control to any folder of the repository. Allow application developers to store supporting content such as automated tests in the same repository as the applications they support.

      • Collision avoidance

        Avoid modifying an application file across different update sets to ensure seamless experience during the commit process.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login