aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFelix Lange <fjl@twurst.com>2016-11-19 02:55:19 +0800
committerFelix Lange <fjl@twurst.com>2016-11-19 02:55:19 +0800
commit8ed72a84703382b88fe8372f08a5dbed2e0c47cf (patch)
treef4983d96a06561303b23a051269b8050dd8b9a3a
parent04edbb0703142f792522e29a557069a3e52705f5 (diff)
downloadgo-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar.gz
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar.bz2
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar.lz
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar.xz
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.tar.zst
go-tangerine-8ed72a84703382b88fe8372f08a5dbed2e0c47cf.zip
build: simplify unstable build check
ci.go decides whether a build is unstable by looking at the branch and tag. This causes issues when a GitHub release is created on the master branch because the build is considered unstable (the CI environment reports the branch as "master"). Fix this by looking at the tag only. Any tagged build is stable.
-rw-r--r--build/ci.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/build/ci.go b/build/ci.go
index 0e1ed37ca..71609c727 100644
--- a/build/ci.go
+++ b/build/ci.go
@@ -459,7 +459,7 @@ func makeWorkdir(wdflag string) string {
}
func isUnstableBuild(env build.Environment) bool {
- if env.Branch != "master" && env.Tag != "" {
+ if env.Tag != "" {
return false
}
return true