Hi Robert,
On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote:
> 2020-07-09_20-33-20
>
>
> 2020-07-21_11-38-13
>
>
Ok so that implies someone on your end made a config change?
>
>
> This caused new configuration for *all* our branches and triggered new
> builds.
> The Ubuntu builds were o
On 22-7-2020 09:56:16, Gavin McDonald wrote:
Hi Robert,
On Tue, Jul 21, 2020 at 8:26 PM Robert Scholte wrote:
> 2020-07-09_20-33-20
>
>
> 2020-07-21_11-38-13
>
>
Ok so that implies someone on your end made a config change?
Robert Scholte:
That's very unlikely. I expect that Jenkins itself got
Hi!
On Wed, Jul 22, 2020 at 10:29 AM Robert Scholte
wrote:
>
>
> *Robert Scholte:*
> That's very unlikely. I expect that Jenkins itself got an update of that
> plugin and that our MultiBranch setup picked up that change.
>
hm, we don't normally do out of band plugin upgrades unless its' necessa
Hi,
As there is a folder per TLP project, can we use view feature ? Or we should
still avoid that.
Best Regards
Eric
-Message d'origine-
De : Roy Lenferink
Envoyé : mardi 21 juillet 2020 22:17
À : builds@apache.org
Objet : Re: [IMPORTANT] - Migration to ci-builds.a.o
The new build e
Hi Eric.
On Wed, Jul 22, 2020 at 1:17 PM Eric Barboni wrote:
> Hi,
> As there is a folder per TLP project, can we use view feature ? Or we
> should still avoid that.
>
If you want to use Views 'within' your folder, that's fine , just don't
want cluttered up views outside of those
HTH
Gav...
Hi,
for Apache CXF we currently have multiple build jobs per branch and JDK
version, e.g.
- Master-JDK8
- Master-JDK11
- Master-JDK-latest
- 3.3-JDK8
- 3.3-JDK11
- 3.3-JDK-latest
As we have an increasing number of Java versions that we support, I thought
about simplying this with the move to t
I just tried the 'git-websites' label for Groovy. Worked without a glitch:
https://ci-builds.apache.org/job/Groovy/job/Groovy%20dev%20website/1/
but about half the speed of before:
https://builds.apache.org/view/E-G/view/Groovy/job/Groovy%20dev%20website/130/
Is that to be expected?
It's not impa
śr., 22 lip 2020 o 13:49 Dennis Kieselhorst napisał(a):
> Has somebody already done it so that I can adapt that or experiences to share
> before I start building that?
At Struts project I developed something like this, this runs
sequentially (not sure why but there was a reason) and also support
At Brooklyn, we don't do multiple builds with different Java versions yet.
But that's something and wanted to implement to test compatibility.
Our build is a multibranch project using a combination of pipelines and
docker containers. With this setup, it would be very easy to add a parallel
step to
> At Struts project I developed something like this, this runs
> sequentially (not sure why but there was a reason) and also supports
> PRs (but that needs a dedicated Github user with access to ASF)
>
> https://github.com/apache/struts/blob/master/Jenkinsfile
Thanks Łukasz, that's what I was loo
https://www.jenkins.io/doc/book/pipeline/syntax/#declarative-matrix
This is a fairly recent feature (like within the past year) which
makes it super easy to write a pipeline across multiple testing axes.
On Wed, 22 Jul 2020 at 07:40, Dennis Kieselhorst wrote:
>
> > At Struts project I developed
The JIRA_PASSWORD is no longer required.
Created a new JIRA account (username: hadoopci) and registered the
credentials to the new Jenkins servers.
-Akira
On Mon, Jul 20, 2020 at 10:52 AM Akira Ajisaka wrote:
> HI Gavin,
>
> I would need JIRA_PASSWORD in the precommit job (
> https://builds.apa
12 matches
Mail list logo
