You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# $SCALA_VER_BASE$SCALA_VER_SUFFIX (if former variable is set)
41
-
# By parsing the tag (if HEAD is tagged as v$base$suffix)
42
-
# By parsing build.number for the base version, suffixing with -$sha-nightly
43
-
# Serialize these versions to jenkins.properties, which are passed downstream to scala-release-2.11.x-dist.
44
-
# This also removes the need to tag scala/scala-dist (not possible for nightlies, still encouraged for releases, but not a hard requirement).
45
-
#
46
-
# Determine Module Versions
47
-
#
48
-
# When running in "versions.properties" mode (the default), derive tags from these versions and build, publishing only those modules that are not available yet.
49
-
# Otherwise, build HEAD for all modules, derive a -nightly version for them.
50
-
# Bootstrap:
51
-
#
52
-
# Build minimal core of Scala as this version (aka locker), publish to private-repo
53
-
# Build modules required to bootstrap, publish to private-repo
54
-
# Build Scala using the previously built core and bootstrap modules, publish to private-repo This overwrites the minimal core on private-repo
55
-
# Stage to sonatype (unless building a -nightly release):
56
-
#
57
-
# Stage this Scala build on sonatype
58
-
# Rebuild modules with this Scala build, and stage them on sonatype as well
59
-
# This script can be run in multiple modes. It is design to work without any input,
60
-
# so that it could be run in Travis CI. In that mode, it'll build a release when
61
-
# the current HEAD of the checkout in $WORKSPACE is tagged, and stage to sonatype. Otherwise,
62
-
# it'll build a nightly.
63
-
#
64
-
# Since the nightlies are intended to be a drop in replacement, all modules are built with the
65
-
# full Scala version as their binary version, so that you can just set scalaVersion to the
66
-
# nightly's sha-derived version and be good to go.
67
-
#
68
-
# The other way to trigger a release is by setting the SCALA_VER_BASE env var.
69
-
#
70
-
# By default, we build the versions of the modules as specified by versions.properties
71
-
# (as specified in the HEAD commit). Set moduleVersioning to something random
72
-
# to trigger building HEAD of each module, generating a fresh -$(git describe)-nightly version for each.
73
-
#
74
-
# PS: set publishToSonatype to anything but "yes" to avoid publishing to sonatype
75
-
# (publishing only done when $WORKSPACE checkout's HEAD is tagged / SCALA_VER_BASE is set.)
76
-
77
-
78
-
sbtCmd=${sbtCmd-sbt}# TESTING (this is a marker for defaults to change when testing locally: should be sbtx on my mac)
79
-
80
-
# 0.13.5 does not respect "set every scalaVersion", see
(git fetch "https://github.com/$1/$2.git"$3&& git checkout -q FETCH_HEAD) #|| git checkout -q $3 # || fallback is for local testing on tag
121
-
git reset --hard
122
-
}
123
23
124
24
##### sonatype interface
125
25
@@ -146,28 +46,6 @@ function st_stagingRepoClose() {
146
46
}
147
47
148
48
149
-
# ARGH trying to get this to work on multiple versions of sbt-extras...
150
-
# the old version (on jenkins, and I don't want to upgrade for risk of breaking other builds) honors -sbt-dir
151
-
# the new version of sbt-extras ignores sbt-dir, so we pass it in as -Dsbt.global.base
152
-
# need to set sbt-dir to one that has the gpg.sbt plugin config
0 commit comments