Well, as I said, it is not really a problem. It is just that Travis seems to do the very same thing twice, wasting some computation power on this. But maybe it is not really easy to e.g. automatically figure out from
.travis.yml if the second build can be safely skipped or not. I just noticed this — but if you feel it’s not worthwile or too hard to optimize here, I don’t mind.
on travis-ci.org it works the same way.
Indeed, I see from the history now. I guess I never noticed because of some timing differences and assumed the notifications I received about tags came from the “simple” build when Travis noticed that commit had a tag on it.
But I think it would be handy if there was a per-repo or global setting to switch off simple commit build if there is a tagged build from same commit.
I feel nobody would use it, because it wouldn’t give anything to users, only to Travis backend by saving some CPU. Unless you can do it automatically, it’s probably not worth it to bother at all.