-
Notifications
You must be signed in to change notification settings - Fork 161
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
[build] Master/PR/Release workflows #181
Conversation
.github/workflows/maven.yml
Outdated
- name: Run tests | ||
run: ./mvnw -V -B -ntp -ff verify | ||
run: ./mvnw -V -B -ntp -ff clean verify |
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.
Since we're running from scratch every time the workflow is being executed, the clean
phase can be skipped.
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.
I'm not familiar enough with the project to comment on this. However, it's usually best practice to ensure outputs are cleaned through the build tool before running a build in case there are any stale build outputs inadvertently committed to source.
.github/workflows/pr.yml
Outdated
restore-keys: | | ||
${{ runner.os }}-maven- | ||
- name: Run tests | ||
run: ./mvnw -V -B -ntp -ff clean verify |
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.
Since we're running from scratch every time the workflow is being executed, the clean
phase can be skipped.
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.
LGTM.
Relies on #172 before merging this.
This breaks master build from pull request builds, which will have different use cases.
Creates a release workflow which can be triggered manually from the actions tab in GitHub. This will tag/release automatically, and rollback if necessary. I haven't tested it, but it should work as-is.