-
Notifications
You must be signed in to change notification settings - Fork 0
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
CI caching #50
CI caching #50
Conversation
.travis.yml
Outdated
- $HOME/.sbt | ||
|
||
before_cache: | ||
# Cleanup the cached directories to avoid unnecessary cache updates |
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.
Hmm maybe just delete all the contents of ~/.ivy2/cache
and ~/.sbt
... why just specifically these 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.
If not, then include the reason for only removing *.properties
/*.lock
in the comment
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.
It seems that it doesn't really matter.
The original comes from here: https://www.scala-sbt.org/0.13/docs/Travis-CI-with-sbt.html#Caching
There is no explanation though.
Here is an example of the way you suggested: typelevel/cats#2158
and I quote: seems marginally faster, or at least not slower, and it is also simpler.
So for the sake of simplicity lets remove before_cache
section
@@ -57,7 +68,7 @@ script: | |||
# -batch is necessary to make sure sbt doesn't stall waiting for user input in case of certain failures | |||
- echo '-batch' >> .sbtopts | |||
- sbt scalafmtCheck | |||
- sbt compile test | |||
- sbt compile |
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.
We've got no actual tests, right?
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.
No description provided.