![]() ![]() The following video will show you how to create an app, link it to a GitHub repo, setup your pipeline using GitHub Actions, and then test your pipeline. Now that you know about GitHub Actions and which actions are available to manage Now Platform development, let’s take a look at setting up and testing a CI/CD pipeline. How to Setup a CI/CD Pipeline using Github Actions More information on that can be found in the repo. We have links to the specific repos because they will rely on the open-source community to help drive fixes and feature enhancements via Issues. You can find links to the seven actions and links to their respective repos in the ServiceNow/sncicd_githubworkflow repo. Rollback Plugin - Rollback a desired plugin on ServiceNow instance.Activate Plugin - Activate a desired plugin on your ServiceNow instance.Run ATF Test Suite - Start a specified automated test suite.Rollback App - Initiate a rollback of a specified application to a specified version if installation fails.Publish App - Publishes the specified application and all of its artifacts to the application repository.Install App - Installs the specified application from the application repository onto the local instance.Apply Changes - Applies changes from a remote source control to a specified local application.To start with, we’ve published seven actions to the GitHub Marketplace. GitHub Actions allow you to automate nearly any part of your software development process, including tasks within your CI/CD process, all directly from GitHub. If that seems confusing I recommend going through the above linked doc that breaks everything down with some diagrams. A job contains one or more steps which control the order in which actions run. A workflow is a YAML file that contains jobs. In GitHub, an event can automatically triggers a workflow. This is explained very well in the Introduction to GitHub Actions documentation, but I’ll pull out a couple of things here. About GitHub Actionsīefore jumping into the ServiceNow specific actions it is helpful to understand the core concepts. In this Developer blog post we’ll introduce the newly released ServiceNow CI/CD GitHub Actions and look at how to use them with your instance stack. Because of that ask we have announced four new integrations with market-leading CI/CD toolsets in a blog post on the ServiceNow Blog. In addition to automating deployment pipelines inside ServiceNow, one of the things we’ve heard from developers is that many of them want to use their preferred DevOps tools to manage their ServiceNow CI/CD processes. Those include selective commits, editing outside of Studio, MID server support for the Source Control integration, global app support for Source Control, and APIs and IntegrationHub Spoke subflows and actions that allow developers to automate testing and deployment. The Orlando and Paris releases have brought many new capabilities to the Now Platform allowing developers to implement their own Continuous Improvement and Continuous Delivery (CI/CD) pipelines to accelerate Now Platform development.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |