Conversation
|
Also, do not copy it to |
|
Or just merge master, the mentioned PR is merged. But the |
| withEnv(["JAVA_HOME=${tool "$jdk"}", | ||
| "PATH+MAVEN=${ tool "$jdk" }/bin:${tool "maven_3_latest"}/bin", | ||
| "MAVEN_OPTS=-Xms4G -Xmx4G -Djava.awt.headless=true"]) { | ||
| sh "cp .github/ci-extensions.xml .mvn/extensions.xml" |
There was a problem hiding this comment.
| sh "cp .github/ci-extensions.xml .mvn/extensions.xml" | |
| sh "cp .github/ci-extensions.xml ~/.m2/extensions.xml" |
|
Oh, just spotted: with Mimir, the maven.repo.local/tail thing is not needed anymore, that was done ONLY to make sure GH cached local repo is not "polluted" with CI installed things (that needs to be installed for ITs) |
|
And another Mimir change for CI #2212 |
but it is user wide and Jenkins is sharing nodes. |
If shared, then yes, this place is good. GH does not share and always re-creates runners... |
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy <olamy@apache.org>
Signed-off-by: Olivier Lamy olamy@apache.org
Following this checklist to help us incorporate your
contribution quickly and easily:
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
[MNG-XXX] SUMMARY,where you replace
MNG-XXXandSUMMARYwith the appropriate JIRA issue.[MNG-XXX] SUMMARY.Best practice is to use the JIRA issue title in both the pull request title and in the first line of the commit message.
mvn clean verifyto make sure basic checks pass. A more thorough check willbe performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.