Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add commits filtering based on tag name #1493

Open
IlyaFinkelshteyn opened this issue Apr 13, 2017 · 2 comments
Open

Add commits filtering based on tag name #1493

IlyaFinkelshteyn opened this issue Apr 13, 2017 · 2 comments

Comments

@IlyaFinkelshteyn
Copy link
Contributor

Skip commits feature to extend
Discussion

@tsteven4
Copy link

tsteven4 commented May 2, 2019

This cost me several hours. I was mislead by https://www.appveyor.com/docs/branches/#white--and-blacklisting which states:

Despite the option name, only and except is applied to tag names too, so the above example using only would cause tags not trigger the build.

I just wanted the following in my appveyor.yml

branches:
  except:
    - continuous-windows
    - continuous

to cause builds to be skipped that might otherwise be initiated by tag pushes with tag names continuous or continuous-windows. This works for branches with these names, but not for tags.

Unfortunately I cannot predict the message associated with the tags, so commit message filtering won't work for me.

As an ugly workaround I have:

before_build:
  - ps: |
      if (($env:APPVEYOR_REPO_TAG -eq "true") -and ($env:APPVEYOR_REPO_TAG_NAME -match "^continuous"))
      {
        echo "tag: $env:APPVEYOR_REPO_TAG tag_name: $env:APPVEYOR_REPO_TAG_NAME"
        Write-Error "This job should have been filtered out."
      }

Which causes the jobs to fail fairly quickly, but it would be preferred if the whole build never was initiated.

@IlyaFinkelshteyn
Copy link
Contributor Author

Duplicate to #486

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants