Hi, The INFRA docs [1] do not mention any constraint that the PR needs to come from the same repository.
It is also a problem, that we need to rely on different versions of Java based on a given branch, i.e. Java 8 for 8.x and Java 11 for 9.x, etc - there is no easy way to decide which one to use for the naive PR builder job. It might be possible, that there is a restriction regarding the GitHub Apache org members due to security concerns? For example: https://github.com/apache/tomee/pull/782 did build on the PR builder but the branch did not reside inside the ASF repo but was located in my fork. Sadly our full build takes too long for GH actions... Gruß Richard [1] https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+Jenkins+build+with+a+GitHub+PR Am Montag, dem 10.10.2022 um 09:57 -0500 schrieb David Blevins: > Was putting some thoughts into how we can maybe keep the build more > stable. > > One obstacle seems to be that the PR builder doesn't build PRs unless > they're coming from branches inside the apache/tomee.git repo, not > branches from a fork. Is anyone else seeing the same thing or have > any information there? > > If there is some kind of limitation for that plugin, maybe we need to > setup a git branch for each person who regularly submits PRs? > > Brainstorming at this point. Any thoughts? > > > -David >
smime.p7s
Description: S/MIME cryptographic signature
