-
Notifications
You must be signed in to change notification settings - Fork 12
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
chore(GHA): Run Java CI testing for MPL Latest Release #1605
base: main
Are you sure you want to change the base?
Conversation
uses: ./.github/workflows/dafny-interop.yml | ||
with: | ||
mpl-dafny: ${{needs.getLatestReleaseMplVersion.outputs.version}} | ||
mpl-commit: ${{needs.getMplDafnyVersion.outputs.dafnyVersion}} |
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.
this doesn't make sense, why for the mpl commit are we supplying the dafny version?
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.
Because the MPL version will be built with its own Dafny version, and we pick this up from the project properties file of the MPL.
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.
Look at the first input to dafny-interop.yml.
Issue #, if available:
Description of changes:
Adds a daily job to check that the HEAD of DB-ESDK is compatible with the latest release of the MPL (pulled from Maven).
An important part is that this should be independent of Daily CI / Push CI / Pull CI, because when the MPL is actually updated, we will see errors with testing the last release, and we don't want our current CI process to get affected because of this.
We also won't need to go through the pain of running the MCM step to run dafny-interop.yml manually for the latest released version of the MPL. This new workflow does it automatically, and the oncall just needs to verify that everything is green.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.