Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/certbot/certbot.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBrad Warren <bmw@users.noreply.github.com>2020-02-28 02:07:33 +0300
committerGitHub <noreply@github.com>2020-02-28 02:07:33 +0300
commit50ea6085537dfec3bceaa4f9f4e4065de84d1407 (patch)
treee67013f6f3ae2a0560b479e406bd4de531e72a25
parentfa67b7ba0fb03453fc8d03e3631d6782a54a233b (diff)
Don't run advanced tests on PRs. (#7820)
When I wrote https://github.com/certbot/certbot/pull/7813, I didn't understand the default behavior for pull requests if you don't specify `pr` in the yaml file. According to https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=azure-devops&tabs=yaml#pr-triggers: > If no pr triggers appear in your YAML file, pull request builds are automatically enabled for all branches... This is not the behavior we want. This PR fixes the problem by disabling builds on PRs. You should be able to see this working because the advanced tests should not run on this PR but they did run on https://github.com/certbot/certbot/pull/7811.
-rw-r--r--.azure-pipelines/advanced-test.yml1
-rw-r--r--.azure-pipelines/advanced.yml1
2 files changed, 2 insertions, 0 deletions
diff --git a/.azure-pipelines/advanced-test.yml b/.azure-pipelines/advanced-test.yml
index b9ac9c38a..5be29ba79 100644
--- a/.azure-pipelines/advanced-test.yml
+++ b/.azure-pipelines/advanced-test.yml
@@ -4,6 +4,7 @@ trigger:
# "Running tests in CI" is still correct.
- azure-test-*
- test-*
+pr: none
jobs:
# Any addition here should be reflected in the advanced and release pipelines.
diff --git a/.azure-pipelines/advanced.yml b/.azure-pipelines/advanced.yml
index 7f0f5de50..d950e6524 100644
--- a/.azure-pipelines/advanced.yml
+++ b/.azure-pipelines/advanced.yml
@@ -1,6 +1,7 @@
# Advanced pipeline for running our full test suite on protected branches.
trigger:
- '*.x'
+pr: none
# This pipeline is also nightly run on master
schedules:
- cron: "0 4 * * *"