如何在Travis CI中设置匹配正则表达式的分支部署？

I’ve run into this exact issue before when setting up release branch deployments with Travis CI—often the problem boils down to an incorrect regex pattern or misplacing the branch filtering logic in your .travis.yml file. Let’s break down the fix step by step.

First, Get the Regex Right #

Your target branch format is release/x.x.x where x are numbers. The correct regex to match this pattern is:

^release/\d+\.\d+\.\d+$

Let’s break that down:

• ^ : Anchors the match to the start of the branch name
• release/ : Exact match for the prefix
• \d+ : Matches one or more digits (covers each version number segment)
• \. : Escaped dot (since dots in regex match any character, we need to escape it to match a literal dot)
• $ : Anchors the match to the end of the branch name (prevents partial matches like release/1.0.0-beta)

Option 1: Filter All Builds to Run Only on Release Branches #

If you want Travis to only run builds (and deployments) for release/x.x.x branches, add this branches section to your .travis.yml:

branches:
  only:
    - '^release/\d+\.\d+\.\d+$'

Using single quotes avoids having to escape slashes in YAML, which is a common source of syntax errors.

Option 2: Trigger Deploy Only for Release Branches (Allow Other Branches to Build) #

If you want other branches to run builds but only deploy when on a release/x.x.x branch, add an if condition to your deploy section:

deploy:
  provider: your-provider-name # e.g., heroku, s3, etc.
  # ... add your provider-specific configuration here ...
  on:
    branch: /^release\/\d+\.\d+\.\d+$/

For more complex scenarios (like combining branch checks with tag conditions), use the condition field:

deploy:
  provider: your-provider-name
  # ... other deploy settings ...
  on:
    condition: "$TRAVIS_BRANCH =~ ^release/\\d+\\.\\d+\\.\\d+$"
    tags: false # Optional: exclude tag builds if needed

Troubleshooting Tips #

• Test Your Regex: Use a regex tester to confirm your branch names match the pattern. For example, release/1.2.3 should match, but release/1.2 or release/v1.2.3 should not.
• Check YAML Indentation: YAML is strict about spacing—make sure all lines under branches or deploy are properly indented (usually 2 spaces per level).
• Review Travis Logs: If deployments still don’t trigger, check the build logs for lines like "Skipping deploy". They’ll often explicitly state why the deploy was skipped (e.g., "Branch does not match").

内容的提问来源于stack exchange，提问作者RJ Mohammad