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

TravisCI gone into infinite loop if ghr --delete used in after_success #45

Closed
popstas opened this issue Aug 30, 2016 · 1 comment
Closed

Comments

@popstas
Copy link

popstas commented Aug 30, 2016

I want to upload binaries after each commit to pre-release tag latest. If I used this:

after_success:
  - gox -output "dist/{{.OS}}_{{.Arch}}_{{.Dir}}" -arch="amd64" -os="windows linux darwin"
  - ghr --username popstas --token $GITHUB_TOKEN --replace --delete --prerelease --debug latest dist/

then Travis will begin build latest tag recursively.

@reaandrew
Copy link

I don't think this is a ghr problem, I think this is actually correct/unwanted/wanted behaviour. I got around this by specifying the branches which I wanted TravisCI to build e.g.

branches:
  only:
  - master
  - hotfix
  - release
  - develop
  - /feature.*/

Without this, when the tag is deleted and a new one created, this change is sent to TravisCI and a build starts with the target being the tag name even though the commit hash is one which has already been built, hence the loop begins.

@Songmu Songmu closed this as completed Apr 5, 2018
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