Hi Olivier,
thanks for your reply, too!
Yeah - this is the workaround, we are currently using.
But now we have some clarity.
Thanks & Gruß
Richard
Am Freitag, dem 11.11.2022 um 16:24 +1000 schrieb Olivier Lamy:
> currently it's not possible with Jenkins.
> But maybe when we will have some te
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 th
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 th
currently it's not possible with Jenkins.
But maybe when we will have some temporary nodes running in a k8s
cluster such restriction will be not needed anymore.
A solution is to have a committer pushing the pr as a branch and so
this will be build.
just use the gh tool, gh pr checkout $PRID.
then
czw., 10 lis 2022 o 20:31 Richard Zowalla 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 possibil
Hi all.
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
