-
Notifications
You must be signed in to change notification settings - Fork 101
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: include multiple versions of java and OS in test_pack_dock workflow #1093
Conversation
Thank you for this contribution! 🍰✨🦄 Information about source corruption0 out of 1248 sources are corrupted. Acceptance test detailsThe changes in this pull request did not trigger any new errors on known GTFS datasets from the MobilityDatabase. |
.github/workflows/test_pack_doc.yml
Outdated
@@ -110,11 +116,14 @@ jobs: | |||
- name: Persist cli app jar | |||
uses: actions/upload-artifact@v2 | |||
with: | |||
name: Application - cli executable .jar -- ${{ steps.prep.outputs.versionTag }} | |||
name: Application - cli executable - Java ${{ matrix.java_version }}.jar -- ${{ steps.prep.outputs.versionTag }} |
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.
IMHO this is difficult to read as a name, and it's already hard to find the right Action when looking at "checks" output (see #1095 for a more general discussion of this).
Here's an alternative that I think is easier to read:
name: Application - cli executable - Java ${{ matrix.java_version }}.jar -- ${{ steps.prep.outputs.versionTag }} | |
name: Application - CLI executable - Java ${{ matrix.java_version }} JAR file -- ${{ steps.prep.outputs.versionTag }} |
You bet, it's centos stream 8 (redhat workalike) here's the version from the server; uname redhat-release java packages
|
"Ubuntu 20.04" is probably the nearest. |
This reverts commit 9a068e8.
It seems that the generation of javadocs on As of now, |
Thank you for this contribution! 🍰✨🦄 Information about source corruption0 out of 1248 sources are corrupted. Acceptance test detailsThe changes in this pull request did not trigger any new errors on known GTFS datasets from the MobilityDatabase. |
Hopefully Windows Javadoc generation should work correctly after PR #1121 is merged, which should unblock this PR. |
Thank you for this contribution! 🍰✨🦄 Information about source corruption0 out of 1248 sources are corrupted. Acceptance test detailsThe changes in this pull request did not trigger any new errors on known GTFS datasets from the MobilityDatabase. |
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.
@maximearmstrong Do you have any objection to merging this? It seems to be working as intended to me - package/test/javadoc tasks are run across Linux and Windows on GitHub CI now, for both Java 11 and 17.
@barbeau All good on my side! Thank you! |
Summary:
This PR provides support to execute
test_pack_doc.yml
workflow on multiple versions of Java: 11 and 17, as well as different OS; in order to flag potential incompatibilities.Expected behavior:
Run the same jobs
test
,doc
, andpack
on different versions of the JDK: 11 and 17.All artifacts should be persisted and identified by the JDK's and OS version that was used to produce them.
Please make sure these boxes are checked before submitting your pull request - thanks!
gradle test
to make sure you didn't break anything