We are using Travis Enterprise together with GitHub Enterprise.
I have a .travis.yml with two deploy providers configured.
- s3: to upload the JAR to S3
- releases: to create a GitHub Release with the JAR
I was really confused when I was looking at the build log because I could see in the log “Skipping a deployment with the releases provider because this is not a tagged commit”. I was sure the commit was tagged. And then I realized that in fact it was actually creating a github release. How that can be?
I then realized that there are two builds in the Build History for that commit one for “master” and one for “v0.0.7” (my tag) both are building commit 6916c2a.
It seems wasteful that the same thing is build twice and even I can imaging that can be a race condition with the s3 provider trying to upload the same jar to the same location at the same time.
Is there a way to prevent this and trigger just the build for the tag in this case? Or it’s always going to build “master” and the tag as seperate thing even if they point to the same commit?