From c03cc7f6f435fe638f39ce1a3e9780c4e542dcf3 Mon Sep 17 00:00:00 2001 From: Karthik Date: Tue, 6 Apr 2021 15:37:41 +0200 Subject: [PATCH] Update .travis.yml with new main branch tag --- .travis.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.travis.yml b/.travis.yml index 424ccda..b4f0cf7 100644 --- a/.travis.yml +++ b/.travis.yml @@ -8,18 +8,18 @@ cache: # For the conditionals below: the `branch` corresponds to the base branches: # for PRs. See https://docs.travis-ci.com/user/conditions-v1 for details. -# Only build on master OR for PRs. Otherwise, we will run the same tests twice: once +# Only build on main OR for PRs. Otherwise, we will run the same tests twice: once # for the PR, once for the branch. # If your builds do not start when you expect them to start, go here to understand why: # https://travis-ci.com/github/SAP/data-attribute-recommendation-python-sdk/requests -if: branch = master OR tag =~ ^rel/.*$ OR type != push +if: branch = main OR tag =~ ^rel/.*$ OR type != push os: linux dist: xenial notifications: email: - if: branch = master AND type != pull_request + if: branch = main AND type != pull_request on_failure: always recipients: # Michael @@ -36,7 +36,7 @@ stages: - name: linting - name: test - name: "system tests" - if: type != pull_request AND (branch = master OR tag =~ ^rel/.*$) + if: type != pull_request AND (branch = main OR tag =~ ^rel/.*$) # Note that deployment of the traceability report to github happens in the system # tests stage above, with an additional condition to only execute on tag =~ ^rel/.*$. # For technical reasons, the upload to pypi is a separate stage: the pypi upload does @@ -145,4 +145,4 @@ jobs: on: # Limitation on branches is done in the "stages" section, so if # the stage is executed, we always want to deploy - all_branches: true \ No newline at end of file + all_branches: true