Yes. Setting up an entire job is cumbersome.
I think, that it would be possible to have interactive user input (i.e.
the branch) for a Jenkins job using Jenkins pipelines without
additional plugins. Some solutions seem to require additional plugins.
So we need to check, which plugins are
> On Nov 10, 2022, at 10:34 PM, Richard Zowalla wrote:
>
> Currently, it is not possible with Jenkins to run jobs from forked
> repositories or for contributors, who do not have committer access to
> the TomEE repositories.
Thanks for getting that confirmed.
> However, they are discussing the
Hi,
I got some updates from builds@
Currently, it is not possible with Jenkins to run jobs from forked
repositories or for contributors, who do not have committer access to
the TomEE repositories.
The workaround is to push the branch to the asf repo and let it build
(as we are doing it).
Hi,
I dropped a message in the builds slack channel to get some thoughts on
our PR issue. Maybe they can give us some hints to docs.
If the topic is to broad / wide for a quick slack chat, I will sent a
mail to builds@ to get some thoughts / ideas.
I agree with David, that we cannot be the
It only works if you push the PR straight to Apache repo I think Richard
mentioned.
So every non committer submitting a PR is out of the builder. We need to
ask Infra maybe. I'd be surprised if we would be the first project to face
it.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
> On Oct 26, 2022, at 2:13 PM, David Blevins wrote:
>
> I wonder if there's some way this can be improved so Richard doesn't have to
> create CI jobs for individual PRs. At minimum, maybe we can have a PR
> builder job that takes the PR number as a parameter?
I wonder also if there's some
> On Oct 10, 2022, at 12:57 PM, David Blevins wrote:
>
>> On Oct 10, 2022, at 12:50 PM, Zowalla, Richard
>> wrote:
>>
>> It might be possible, that there is a restriction regarding the GitHub
>> Apache org members due to security concerns?
>>
>> For example:
Perhaps worth a mail to build@ ?
I can't imagine that others do not run into same issues related to
random number generations / entropy issues.
Gruß
Richard
Am Dienstag, dem 11.10.2022 um 17:50 +0200 schrieb Jean-Louis Monteiro:
> Yes you are correct. This is a possible problem.
>
> Digging
Yes you are correct. This is a possible problem.
Digging down a bit
TomEE :: TCK :: MicroProfile Config TCK 1 mn 38 s
TomEE :: TCK :: MicroProfile Fault Tolerance TCK 1 h 11 mn
TomEE :: TCK :: MicroProfile Health TCK 5 mn 6 s
TomEE :: iTests ::
> On Oct 11, 2022, at 2:33 AM, Jean-Louis Monteiro
> wrote:
>
> I can't measure without investing a lot of time, but looking at what Maven
> reports
> CDI + BVal TCK around 25 min
> MicroProfile TCK 2 hours and a half
There's definitely something going on with the build machines as the
We have a couple of other challenges in my opinion.
Deps - all the shading is a pain but also takes a significant amount of time
Examples - they are somehow also some testing code for our server, but they
take time
TCK - more and more TCK are now standalone and we can run them easily. As a
result
> On Oct 10, 2022, at 12:50 PM, Zowalla, Richard
> wrote:
>
> 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
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
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
14 matches
Mail list logo
