CI/CD Tools Integration
Features that help you use SnapLogic with your CI/CD process.
Overview
Continuous Integration / Continuous Delivery/Deployment (CI/CD) is a set of automated processes that enable frequent testing, delivery, and deployment of software to users.
- SnapLogic - Git Integration. Link your SnapLogic projects to your Git repositories and manage them.
- Workflows and pipelines. Start with Git workflow examples, Dev Ops pipeline examples, and GitHub Action examples. Then customize them for your own processes.
- Secrets Management. Secure your CI/CD processes by integrating with secrets management tools.
- SnapLogic Public APIs. Use the SnapLogic Public APIs to automate your CI/CD processes.
CI/CD Strategies
Each organization has its own requirements and methods for CI/CD; therefore, each organization's strategy is unique.
The following example CI/CD strategies illustrate different ways of deploying from your dev/test environment to your production environment.
Migration
The migration CI/CD strategy uses migration tools to deploy changes from the dev/test environment to the production environment.
- In the production Org, set up accounts.
- In the dev/test Org, create a project.
- In the dev/test Org, make the required changes.
- Migrate the project to the production Org.
Accounts must already be set up in the destination environment. Accounts with the same name across all Orgs are considered the same account.
Import/Export
The import/export CI/CD strategy uses import and export tools to deploy changes from the dev/test environment to the production environment.
- In the dev/test Org, create a project.
- In the dev/test Org, make the required changes.
- Export the project.
The export process creates a zip file.
- Import the zip file into your production environment, as well as the accounts (accounts.json) and expression libraries (expression.zip) specific to the environment.
To undo, import a previously exported .zip file.
Repository
The repository CI/CD strategy uses a repository between the dev/test environment and the production environment. Updated files are committed from the dev/test environment into the repository and then pulled from the repository into the production environment.
- In the production Org, set up accounts.
- In the dev/test Org, create a project.
- Create a new branch in your repository.
- In the dev/test Org, make the required changes.
- Commit the changes.
- Create a pull request to review and test the changes.
- Merge the pull request with the
main
branch. - Associate a tag with the latest files in the
main
branch. - In the production environment, perform a pull using the defined tag. Accounts with the same name across all Orgs are considered the same account.
To undo, perform a pull using a tag defined for an earlier version of the main
branch files.
Concurrent Editing
The concurrent editing CI/CD strategy allows changes from multiple branches to be merged into a single branch which is deployed to the production environment.
To set up the concurrent editing CI/CD strategy, set up a CI/CD workflow that is automatically triggered whenever the main
branch is updated.
The CI/CD workflow performs a pull of the updated files into the production environment.
- Create a new project in their own project space.
- Create a new branch in the repository for their own project.
- Make the required changes.
- Commit the changes.
- Create a pull request to review and test the changes.
An admin reviews the pull requests and merges them into the main
branch.
The merge triggers the automated CI/CD workflow which copies the changes from the main
branch to the production environment.