Hi Lukasz,
thanks for your reply!
Our full builds have a duration of 2 ('quick') - 5+ hours ('quick + it
+ tcks') on the Jenkins CI infrastructure (depending on the saturation
of the available node) and are a result of the ancient hardware (there
is a separate discussion regarding AWS) used on the nodes.
Currently, we have GitHub actions available to conduct some basic
checks (style, compile) for pull requests but it doesn't execute our
long running test suites [1,2] - and yes: That also works for
contributors from their own forks.
Our last experiments with GH actions are already some time ago, but I
remember, that Jenkins was more "stable" for our test suites. Perhaps
the world has changed and we need to re-investigate. (And probably look
into the - often discussed - topic of GH self hosted runners + security
hardening).
Gruß
Richard
[1]
https://github.com/apache/tomee/blob/main/.github/workflows/main-pull-request-build.yml
[2]
https://github.com/apache/tomee/blob/main/.github/workflows/tomee-8.x-pull-request-build.yml
Am Freitag, dem 11.11.2022 um 07:18 +0100 schrieb Lukasz Lenart:
> czw., 10 lis 2022 o 20:31 Richard Zowalla <r...@apache.org>
> napisał(a):
> > We have a Jenkins pull request job in TomEE. We noticed, that this
> > job
> > only builds PRs, which originate from the ASF repo (and not from
> > (user)
> > forks).
> >
> > I guess, that this is intended due to some security concerns? Is
> > there
> > a possibility to run such pull request builds for forks after some
> > sort
> > of manual approval?
> >
> > I think of something like "Jenkins, test this please" (from a
> > committer
> > / pmc) and a job is triggered?
> >
> > I assume, that other projects might have the same problems or
> > already a
> > solutions for that kind of problem?
> >
> > Any hint / pointer is appreciated.
>
> I'm not sure if this is possible with Jenkins, maybe you should use
> Github Actions for that?
> https://github.com/apache/struts/blob/master/.github/workflows/maven.yml
>
>
> Regards
