You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "slawekjaranowski (via GitHub)" <gi...@apache.org> on 2023/02/24 19:32:21 UTC
[GitHub] [maven-javadoc-plugin] slawekjaranowski opened a new pull request, #187: Don't fail fast jobs in build matrix
slawekjaranowski opened a new pull request, #187:
URL: https://github.com/apache/maven-javadoc-plugin/pull/187
If one build for specific jdk fail we want to see result from others
---
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MJAVADOC) filed
for the change (usually before you start working on it). Trivial changes like typos do not
require a JIRA issue. Your pull request should address just this issue, without
pulling in other changes.
- [ ] Each commit in the pull request should have a meaningful subject line and body.
- [ ] Format the pull request title like `[MJAVADOC-XXX] - Fixes bug in ApproximateQuantiles`,
where you replace `MJAVADOC-XXX` with the appropriate JIRA issue. Best practice
is to use the JIRA issue title in the pull request title and in the first line of the
commit message.
- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [ ] Run `mvn clean verify -Prun-its` to make sure basic checks pass. A more thorough check will
be performed on your pull request automatically.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [ ] I hereby declare this contribution to be licensed under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-javadoc-plugin] slawekjaranowski closed pull request #187: Don't fail fast jobs in build matrix
Posted by "slawekjaranowski (via GitHub)" <gi...@apache.org>.
slawekjaranowski closed pull request #187: Don't fail fast jobs in build matrix
URL: https://github.com/apache/maven-javadoc-plugin/pull/187
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [maven-javadoc-plugin] olamy commented on pull request #187: Don't fail fast jobs in build matrix
Posted by "olamy (via GitHub)" <gi...@apache.org>.
olamy commented on PR #187:
URL: https://github.com/apache/maven-javadoc-plugin/pull/187#issuecomment-1444833318
I'm -0 for this. This will eventually lock a lot of shared resources whereas it's failing and no need to hold up resources.
Remember the github runners are shared with the community of Maven developers and even the Apache org.
If you really need this just push to your fork until its fixed and then make a PR.
At least you will use only your quota.
We just have the bad habits to push here whereas it's possible to push in a fork then make a PR..
Definitely possible look here https://github.com/olamy/maven-javadoc-plugin/actions
You just need to manually activate actions to run for your fork
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@maven.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org