-
Notifications
You must be signed in to change notification settings - Fork 92
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
No longer use scalaVersionsByJvm
#223
Conversation
@@ -1,8 +1,20 @@ | |||
# opt-in to Travis's newer/faster container-based infrastructure | |||
sudo: false | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we should switch to Travis's newer Ubuntu precise infrastructure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd stick with the defaults unless there's a good reason not to, but I also don't have a strong opinion. Either way is fine with me.
67f919a
to
74f3427
Compare
84f6ddb
to
f081fc6
Compare
Rebased on master, this PR is now independent of #222. |
Review by @SethTisue, @ashawley |
So now close in favor of #222? |
We can merge this first, independently of #222 |
@@ -11,18 +23,23 @@ env: | |||
- secure: "OpBwPc1GNvauageYOH3RscAa7wpZxgpmqDz15aigIKLNWzAhAtVUx0MleZ8rQeoqml6nrAvlnzuVHjKL2lVcjMPpjUis7bcQ5UAGK7tZK8x+qZNQxXmpXu8+pENwQA2yFaqt/xy7K5jFOrHJHTRxcPnyVG1yKakPWz53PPYUwbc=" | |||
# SONA_PASS | |||
- secure: "Xw7rI/qlML1nD2e2XwlakkhKAWNGZKqqE+Q3ntTvFpfHryl7KLCvVzJ4LIavnL6kGJaWOgy9vlSoEWn5g9nqHSfE31C/k5pY5nTMAKiwiJzfAS+r0asKXW2gmKhwtcTBkqyLVOZLCJSPVlFRQyfBJHY+Fs0L3KWcnMQgtBlyDhU=" | |||
matrix: | |||
- SCALAJS_VERSION= |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the significance of an empty SCALAJS_VERSION
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this case it builds for the JVM. If SCALAJS_VERSION
is non-empty, the build only builds for JS. See https://github.com/scala/scala-xml/pull/223/files#diff-3acefdae08499733e855dd23e1af933dR19.
On travis, every combination of the biuld matrix has its own "job", see https://travis-ci.org/scala/scala-xml/builds/381095011 for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tricky.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is where the idea comes from: https://github.com/scala/scala-collection-compat/pull/20/files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, we'll blame the code smell on @SethTisue, then. :-)
.travis.yml
Outdated
- oraclejdk8 | ||
- oraclejdk9 | ||
script: | ||
- if [[ "$TRAVIS_JDK_VERSION" == "openjdk6" && "$TRAVIS_SCALA_VERSION" =~ 2\.11\..* || "$TRAVIS_JDK_VERSION" == "oraclejdk8" && "$TRAVIS_SCALA_VERSION" =~ 2\.1[23]\..* ]]; then export RELEASE_COMBO=true; fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason this line is outside build.sh
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess my idea was to keep things that affect the build matrix in the travis file. But looking at it, I agree it's nicer to move it over to the bash script. Will do.
.travis.yml
Outdated
|
||
scala: | ||
- 2.11.12 | ||
- 2.12.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2.12.6???
.travis.yml
Outdated
exclude: | ||
- scala: 2.13.0-M3 | ||
env: SCALAJS_VERSION=1.0.0-M3 | ||
- scala: 2.12.4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2.12.6, again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, sorry I missed these..
Option(System.getenv("SCALAJS_VERSION")).filter(_.nonEmpty).getOrElse("0.6.23") | ||
|
||
addSbtPlugin("org.scala-js" % "sbt-scalajs" % scalaJSVersion) | ||
addSbtPlugin("org.portable-scala" % "sbt-scalajs-crossproject" % "0.4.0") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's this about?
[warn] Found version conflict(s) in library dependencies; some are suspected to be binary incompatible:
[warn]
[warn] * org.scala-js:sbt-scalajs:0.6.23 is selected over 0.6.22
[warn] +- default:scala-xml-build:0.1-SNAPSHOT (scalaVersion=2.10, sbtVersion=0.13) (depends on 0.6.23)
[warn] +- org.portable-scala:sbt-scalajs-crossproject:0.4.0 (scalaVersion=2.10, sbtVersion=0.13) (depends on 0.6.22)
[warn]
[warn] * org.portable-scala:sbt-platform-deps:1.0.0 is selected over 1.0.0-M2
[warn] +- org.scala-js:sbt-scalajs:0.6.23 (scalaVersion=2.10, sbtVersion=0.13) (depends on 1.0.0)
[warn] +- org.portable-scala:sbt-crossproject:0.4.0 (scalaVersion=2.10, sbtVersion=0.13) (depends on 1.0.0-M2)
[warn] +- org.portable-scala:sbt-scalajs-crossproject:0.4.0 (scalaVersion=2.10, sbtVersion=0.13) (depends on 1.0.0-M2)
[warn]
[warn] Run 'evicted' to see detailed eviction warnings
Why doesn't the sbt-scalajs-crossproject
plugin just bring in the corresponding sbt-scalajs
core plugin?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sbt-scalajs-crossproject
is not only about scala-js, but also native. I don't know it very well, but the docs say that the js plugin should be added (https://github.com/portable-scala/sbt-crossproject). It would be nice if this warning didn't show up though..
- scala: 2.12.6 | ||
jdk: openjdk6 | ||
- scala: 2.13.0-M3 | ||
jdk: openjdk6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are 19 builds at the moment. Do we really need all of them?
Trimming down would be nice, because the wall time used to be 10 minutes for 3 concurrent builds. The individuals builds are shorter, but now it looks like it takes over 20 minutes because Travis throttles only to 4 or 5 concurrent builds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's not wrong to test them. Maybe we could skip combinations that contain two preview versions: Scala-js 1.0.0-M3 & openjdk9.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, sounds like a good start.
I'm thinking ahead to #110 when things will really go downhill.
Looks like the project list is changed:
Used to be:
We'll need to update the wiki when this is merged: https://github.com/scala/scala-xml/wiki/Contributor-guide |
Looks like a spurious Travis error for Scala 2.11.12, oraclejdk8 and scala-js 0.6.23.
|
I clicked "rebuild" on travis, it went green. |
fi | ||
|
||
sbt "$publishVersion" "$publishScalaVersion" clean update +test +publishLocal $extraTarget | ||
sbt "++$TRAVIS_SCALA_VERSION" "$publishVersion" "$projectPrefix/clean" "$projectPrefix/test" "$projectPrefix/publishLocal" "$publishTask" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry to see the update
task go.
I don't know if "$projectPrefix/clean"
is a worthwhile distinction.
But these are nits.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
update
runs anways as part of test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I like the timestamp and success of each task I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Yay! Thanks @ashawley for the review. |
It was unnecessarily magic.