-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrade deployment to Maven Central to use new plugin from Sonatype #41
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,3 +6,4 @@ target | |
| *.iml | ||
| .idea | ||
| .sonatype | ||
| .vscode/settings.json | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Sånn det er satt opp nå, så vil det jo i praksis bli kjørt to (nesten) identiske Maven-bygg i sekvens, hvis man teller den første parallell-matrisen som ett bygg. Først kjøres et fullstendig Maven-bygg eksl. deploy til remote repository, deretter et fullstendig Maven-bygg til inkl. deploy til remote repository.
Kunne vi gjort dette litt mer effektivt? Har to forslag:
publish-jobben, tester peker seg jo ut her, både kompilering av testkode og kjøring av tester.buildogpublishtil en jobb. Problemet her er jo at vi gjerne vil kjøre 3 bygg-varianter med ulike Java-versjoner, så om vi tilpasser om vi kjørermvn deploypå én spesifikk Java-versjon, og ellersmvn verify. Jeg tror kanskje dette også vil gi minst duplisert GitHub actions jobb-oppsett.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.
Ref PR: #42 😇
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.
Enig. Den første jobben er egentlig bortkasta CPU og energi. Den andre vil jo feile på samme måte som den første i verify-steget, uansett. Vi kan hellere reintrodusere en eller annen form for delvis bygging uten publisering, om det skulle være bruk for det seinere. Ser nærmere på PR-en din om litt.