-
Notifications
You must be signed in to change notification settings - Fork 4
update to jdk 11 [AS-594] #1372
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
Changes from all commits
df335dd
fd4f4a8
237ebe5
4eb13a8
b5befd2
7c9df33
66f3133
e96c5ec
46cee51
d70439b
3f3d4ad
2f04caf
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
1.8 | ||
11 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
sbt.version = 1.4.6 | ||
sbt.version = 1.4.7 |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,4 @@ | ||
import MinnieKenny.testSettings | ||
import sbt.Keys._ | ||
import sbt._ | ||
|
||
|
@@ -22,6 +23,9 @@ object Testing { | |
|
||
val commonTestSettings: Seq[Setting[_]] = List( | ||
|
||
testOptions in Test += Tests.Setup(() => | ||
sys.props += "mockserver.logLevel" -> "WARN" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The default log verbosity for mockserver logs every mock defined, for every test that defines it. Since this goes to the console for jenkins jobs, it makes the logs huge, to the point that the browser has trouble searching through them. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Awesome!! |
||
), | ||
// SLF4J initializes itself upon the first logging call. Because sbt | ||
// runs tests in parallel it is likely that a second thread will | ||
// invoke a second logging call before SLF4J has completed | ||
|
@@ -55,7 +59,7 @@ object Testing { | |
(testOnly in Test) := ((testOnly in Test) dependsOn validMySqlHost).evaluated, | ||
|
||
parallelExecution in Test := false | ||
) ++ MinnieKenny.testSettings | ||
) ++ (if (sys.props.getOrElse("secrets.skip", "false") != "true") MinnieKenny.testSettings else List()) | ||
|
||
implicit class ProjectTestSettings(val project: Project) extends AnyVal { | ||
def withTestSettings: Project = project | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
sbt.version=1.4.6 | ||
sbt.version=1.4.7 |
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.
Assuming container-based compilation is absolutely required, someday I hope this custom image gets pushed to a public GCR or anywhere else besides docker.io. We have so many tests in the terra multi-repo that are failing due to pull rate limits from docker.io these days. 😢
Or for easier patching of individual components, just use a more flexible base container like focal and then download java and the 0.016GB sbt package. While Java gets patches much slower, Scala and SBT get patches once a month. For example: sbt 1.4.8 is already out.
Uh oh!
There was an error while loading. Please reload this page.
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.
So:
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.
my take is that even though sbt will automatically download whatever it needs, the entire point of adding sbt to a baseimage is to preload as many dependencies as possible at docker-build time, and avoid re-downloading those dependencies on every build of every service that uses this image. So, counting on sbt to download what it needs defeats the purpose - if we're relying on that, I could see omitting it entirely and downloading it at runtime, avoiding the maintenance of the baseimage.