From 4e662a119547feddfc7ecdc37583c085e3f82395 Mon Sep 17 00:00:00 2001 From: Drew Bollinger Date: Tue, 12 Nov 2024 15:04:21 -0500 Subject: [PATCH] chore: don't run dev pipeline on release branch --- ci/pipeline.yml | 1 + docs/DEVELOPMENT.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/ci/pipeline.yml b/ci/pipeline.yml index 7366662de..eaf135ceb 100644 --- a/ci/pipeline.yml +++ b/ci/pipeline.yml @@ -466,6 +466,7 @@ resources: base_branch: main disable_forks: true ignore_drafts: false + ignore_paths: ["package.json", "CHANGELOG.md"] #@ if/end env == 'staging': - name: src diff --git a/docs/DEVELOPMENT.md b/docs/DEVELOPMENT.md index 9fc98813c..0d4ec0f6b 100644 --- a/docs/DEVELOPMENT.md +++ b/docs/DEVELOPMENT.md @@ -182,7 +182,7 @@ Our continuous integration pipeline is run on Concourse CI. To use Concourse, on This repository contains one deployment pipeline file which is used to deploy the application across three separate environments. This is acheived using the `boot` task from [`pages-pipeline-task`](https://github.com/cloud-gov/pages-pipeline-tasks/?tab=readme-ov-file#boot). Each pipeline deploys the Pages app/api, the admin app, and the queues app for a given environment. Notable differences between the per-environment pipelines: -- `dev`: This pipeline runs when a PR is created against the `main` branch. It will deploy the API without waiting for lint/tests to pass. It sends back information about various tasks as Github status checks. It runs integration testing post-deployment. +- `dev`: This pipeline runs when a PR is created against the `main` branch. It will deploy the API without waiting for lint/tests to pass. It sends back information about various tasks as Github status checks. It runs integration testing post-deployment. It will skip PRs which only change `package.json` or `CHANGELOG.md`, effectively skipping the `release` PRs. - `staging`: This pipeline runs when a new commit is added to the `main` branch. It updates a separate `release` branch which is used for automating releases and updating our changeleog. It runs integration testing post-deployment. - `production`: This pipeline runs when a new tag is added to the `main` branch. It will create a new Github release matching the tag and post the changelog to Slack.