-
Notifications
You must be signed in to change notification settings - Fork 236
Build Site and fix 1288 #1289
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 Site and fix 1288 #1289
Conversation
.github/workflows/early-access.yaml
Outdated
|
|
||
| - name: 'Run default (non-native) build' | ||
| run: ./mvnw verify -Dmrm=false -V -B -ntp -e -s .mvn/release-settings.xml | ||
| run: ./mvnw verify site -Dmrm=false -V -B -ntp -e -s .mvn/release-settings.xml |
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'd not interleave site into this one... @gnodet ?
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.
Yes, maybe another job would be better specifically for the site.
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.
Moved it to another Job
044be95 to
3ea19ee
Compare
as the purpose of CI is to reveal errors early (in particular on forks). This contributes to fix apache#1288 but might be helpful for other changes as well. Otherwise this commit should be stripped from the build before merging
by switching to the latest Maven Fluido Skin which is compatible with the currently used M-Site-P (3.21.0).
10f45af to
e435124
Compare
gnodet
left a comment
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
Besides a fix for #1288 the change also contains
mvn ... site) to detect such problems early in the futureThe latter leads to CI builds for each development change (which is a major purpose of an automatic build and helps in particular for forks/new contributors who cannot issue a automatic build by creating a PR). Having said that, the respective commit could be dropped if there is a good reason not to follow this practice.