servicenowdevx/sncicd-gitlab-docker repository overview

⁠ServiceNow CI/CD Docker Image for GitLab CI/CD

⁠Contents

• Intro⁠
• Usage⁠

---

⁠Intro

This Docker image provides build steps for configuring CI/CD pipelines with Now Platform application development.

The build steps are API wrappers for the CI/CD APIs⁠ first released with Orlando. They will currently work from Orlando through Rome releases.

The source for the Docker image is provided via a GitHub repo⁠, where further information can be found for building the image locally.

⁠Usage

1. Link to Source Control⁠ for an application that has been created on your instance.
2. Add a new file named .gitlab-ci.yml in the root directory of the Git repo. This will be your pipeline in GitLab.
3. Copy and paste the contents of a pipeline template. We provide examples at this GitLab repo⁠.
4. Alternatively, you can include as image: servicenowdevx/sncicd-gitlab-docker:latest line in your pipeline.
5. Configure your CICD variables by defining keys such as SN_AUTH_DEV and values in the format username:password.
6. Depending on how you have your triggers for the pipeline setup, you can now run a build on every commit, PR, etc.

⁠Support Model

ServiceNow built this integration with the intent to help customers get started faster in adopting CI/CD APIs for DevOps workflows, but will not be providing formal support. This integration is therefore considered "use at your own risk", and will rely on the open-source community to help drive fixes and feature enhancements via Issues. Occasionally, ServiceNow may choose to contribute to the open-source project to help address the highest priority Issues, and will do our best to keep the integrations updated with the latest API changes shipped with family releases. This is a good opportunity for our customers and community developers to step up and help drive iteration and improvement on these open-source integrations for everyone's benefit.

⁠Governance Model

Initially, ServiceNow product management and engineering representatives will own governance of these integrations to ensure consistency with roadmap direction. In the longer term, we hope that contributors from customers and our community developers will help to guide prioritization and maintenance of these integrations. At that point, this governance model can be updated to reflect a broader pool of contributors and maintainers.