Le 26/07/2020 à 23:39, Gary Gregory a écrit :
> For mythical builds that require Java 6, we should really consider bumping
> those up to Java 7 or 8 because newer JDKs do not accept compiling to
> targets older than Java 7.
Technically it's possible to build with Java 11 and use the --release 6
If building on Jenkins, it looks like Infra still supports all the way
back to 1.4:
https://cwiki.apache.org/confluence/display/INFRA/JDK+Installation+Matrix
On Sun, 26 Jul 2020 at 16:46, Gary Gregory wrote:
>
> Hi All:
>
> As a guideline I think our CI builds should use the following Java
Hi All:
As a guideline I think our CI builds should use the following Java versions:
- Java 8 since it is LTS
- Java 11 since it is LTS
- Java 14 since it is the latest version
- Java 15-ea since it is upcoming, but should be allowed to fail a build
- Java 16-ea since it is
On Sat, 25 Jul 2020 at 03:49, Stefan Bodewig wrote:
> On 2020-07-23, Olivier Lamy wrote:
>
> > In the Maven project we have plenty of maven-* git repo so we have
> created
> > a dedicated Jenkins plugin (which is used by other TLP such netbeans)
> which
> > scan the gitbox server to get repo
On 2020-07-23, Olivier Lamy wrote:
> In the Maven project we have plenty of maven-* git repo so we have created
> a dedicated Jenkins plugin (which is used by other TLP such netbeans) which
> scan the gitbox server to get repo based on regular expression or name
> content and create the build
Pipelines are the text file method of Jenkins jobs. You can store them in
the repo you’re building similar to other CI systems, or you can make a
dedicated repo for holding pipelines, or you can even store the pipeline
script directly in Jenkins (not the best idea, but can be useful during
Hi.
2020-07-23 15:59 UTC+02:00, Matt Sicker :
> [...] make every Commons component
> easily buildable in Jenkins [...]
How to do it practically?
Can we create a text file and drop it somewhere, or has
the configuration to be done in GUI ?
Gilles
As Olivier mentioned, that GitBox plugin plus some relatively simple
pipelines would make it fairly simple to make every Commons component
easily buildable in Jenkins just like how Maven set up their projects.
Well, hopefully a little more optimized since their setup occasionally
figures out how
Hello.
Le jeu. 23 juil. 2020 à 13:21, Olivier Lamy a écrit :
>
> On Thu, 23 Jul 2020 at 20:57, Gilles Sadowski wrote:
>
> > Hi.
> >
> > 2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> > > Hi
> > > As you know the current Jenkins infra is migrating to another CI server.
> > > The current commons-*
https://github.com/apache/logging-pipelines
For more pipelines.
On Thu, Jul 23, 2020 at 06:21 Olivier Lamy wrote:
> On Thu, 23 Jul 2020 at 20:57, Gilles Sadowski
> wrote:
>
> > Hi.
> >
> > 2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> > > Hi
> > > As you know the current Jenkins infra is
On Thu, 23 Jul 2020 at 20:57, Gilles Sadowski wrote:
> Hi.
>
> 2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> > Hi
> > As you know the current Jenkins infra is migrating to another CI server.
> > The current commons-* builds in the old Jenkins infra have been created
> > manually and this will be
Hi.
2020-07-23 12:38 UTC+02:00, Olivier Lamy :
> Hi
> As you know the current Jenkins infra is migrating to another CI server.
> The current commons-* builds in the old Jenkins infra have been created
> manually and this will be a pain to transfer to the new one and to keep
> maintaining
Hi
As you know the current Jenkins infra is migrating to another CI server.
The current commons-* builds in the old Jenkins infra have been created
manually and this will be a pain to transfer to the new one and to keep
maintaining manually.
In the Maven project we have plenty of maven-* git repo
On 2020-07-23, Stefan Bodewig wrote:
> My preference would be for using less of github rather than more. But
> I'm probably alone with that.
Of course I'm not. Sorry Gilles. :-)
Stefan
-
To unsubscribe, e-mail:
On 2020-07-22, Gary Gregory wrote:
> My main driver is that we already use GitHub for source mirroring and PRs,
> so it feels better to me to have builds in the same place.
My preference would be for using less of github rather than more. But
I'm probably alone with that.
-0 on defaulting to
Hi.
2020-07-23 5:17 UTC+02:00, Matt Sicker :
> If we request the pipeline template plugin to be installed, that would help
> reduce the amount of boilerplate needed in the new Jenkins. I could help
> with that.
I don't know what part of this discussion this is a
follow-up to, but I for sure
If we request the pipeline template plugin to be installed, that would help
reduce the amount of boilerplate needed in the new Jenkins. I could help
with that.
On Wed, Jul 22, 2020 at 22:00 Gilles Sadowski wrote:
> 2020-07-23 3:35 UTC+02:00, Torsten Curdt :
> >>
> >> > I realize that a local
2020-07-23 3:35 UTC+02:00, Torsten Curdt :
>>
>> > I realize that a local build seems to be your gold standard.
>>
>> Not mine. "Commons".
>>
>
> You are arguing for it.
No I'm not. It (i.e "maven", "svn" then "git") was there
when I came here.
It could change but that's another discussion that
>
> > I realize that a local build seems to be your gold standard.
>
> Not mine. "Commons".
>
You are arguing for it. I would just call it a current policy or practice.
> > That's a very debatable point of view.
>
> There was no debate.
Yet it is a debatable point of view :)
> I don't see
@gilles
I don't have a apache gitbox account, and nearly cannot do anything on
gitbox.
So it seems a mirror question to yours.
Gilles Sadowski 于 2020年7月23日周四 上午8:46写道：
> 2020-07-23 1:22 UTC+02:00, Torsten Curdt :
> >>
> >> > It does not mean that a source distribution goes away.
> >>
> >> Nor
2020-07-23 1:22 UTC+02:00, Torsten Curdt :
>>
>> > It does not mean that a source distribution goes away.
>>
>> Nor did I mean that it would.
>> I commented on the remark that one's own computer
>> supposedly did not matter.
>>
>
> Ah, then it was only the "(that one does not really count.)" that
github ci is good when it green.
But when it red, and you need to see the log, it become disgusting.
It have a disgusting UI design, with an ugliest and slowest scrollbar.
Olivier Lamy 于 2020年7月23日周四 上午7:54写道：
> On Thu, 23 Jul 2020 at 09:30, Gary Gregory wrote:
>
> > On Wed, Jul 22, 2020 at
On Thu, 23 Jul 2020 at 09:30, Gary Gregory wrote:
> On Wed, Jul 22, 2020 at 4:59 PM Olivier Lamy wrote:
>
> > On Thu, 23 Jul 2020 at 06:45, Gary Gregory
> wrote:
> >
> > > On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
> > >
> > > > How do you deploy snapshots automatically?
> > > >
> >
On Wed, Jul 22, 2020 at 5:35 PM Gilles Sadowski
wrote:
> Hi.
>
> 2020-07-22 21:48 UTC+02:00, Gary Gregory :
> > Hi All:
> >
> > There are three build systems available to us:
> >
> > - Apache Jenkins
> > - GitHub Actions
> > - Travis CI
> > - Plus, *your *PC (that one does not really count.)
>
>
On Wed, Jul 22, 2020 at 4:59 PM Olivier Lamy wrote:
> On Thu, 23 Jul 2020 at 06:45, Gary Gregory wrote:
>
> > On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
> >
> > > How do you deploy snapshots automatically?
> > >
> >
> > I don't use snapshots. If I have to have one, I build it locally.
>
> > It does not mean that a source distribution goes away.
>
> Nor did I mean that it would.
> I commented on the remark that one's own computer
> supposedly did not matter.
>
Ah, then it was only the "(that one does not really count.)" that didn't
sit well with you. Misunderstood.
> > We
2020-07-23 0:07 UTC+02:00, Torsten Curdt :
>>
>> I don't agree: a source distribution assumes that one's own
>> computing resources is essential.
>> This project never discussed departing from the assumption
>> that a contributor should be able to build locally and primarily
>> check that the
>
> I don't agree: a source distribution assumes that one's own
> computing resources is essential.
> This project never discussed departing from the assumption
> that a contributor should be able to build locally and primarily
> check that the reports generated comply with the level of
> quality
2020-07-22 22:58 UTC+02:00, Olivier Lamy :
> On Thu, 23 Jul 2020 at 06:45, Gary Gregory wrote:
>
>> On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
>>
>> > How do you deploy snapshots automatically?
>> >
>>
>> I don't use snapshots. If I have to have one, I build it locally.
>>
>
> But what
Hi.
2020-07-22 21:48 UTC+02:00, Gary Gregory :
> Hi All:
>
> There are three build systems available to us:
>
> - Apache Jenkins
> - GitHub Actions
> - Travis CI
> - Plus, *your *PC (that one does not really count.)
I don't agree: a source distribution assumes that one's own
computing resources
On Thu, 23 Jul 2020 at 06:45, Gary Gregory wrote:
> On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
>
> > How do you deploy snapshots automatically?
> >
>
> I don't use snapshots. If I have to have one, I build it locally.
>
But what about the community who wants to try snapshots build?
Hi,
I've been using GitHub actions for a while now, and it works fine. It's really
handy to have CI and code in GitHub. I believe even users not using GitHub
(i.e. no GitHub account) are able to access the CI logs, just like Travis.
I never gave much thought to the Coveralls and JaCoCo issue.
On Wed, Jul 22, 2020 at 4:22 PM Olivier Lamy wrote:
> How do you deploy snapshots automatically?
>
I don't use snapshots. If I have to have one, I build it locally.
Gary
>
> On Thu, 23 Jul 2020 at 05:48, Gary Gregory wrote:
>
> > Hi All:
> >
> > There are three build systems available to
How do you deploy snapshots automatically?
On Thu, 23 Jul 2020 at 05:48, Gary Gregory wrote:
> Hi All:
>
> There are three build systems available to us:
>
> - Apache Jenkins
> - GitHub Actions
> - Travis CI
> - Plus, *your *PC (that one does not really count.)
>
> We have components building
Hi All:
There are three build systems available to us:
- Apache Jenkins
- GitHub Actions
- Travis CI
- Plus, *your *PC (that one does not really count.)
We have components building here and there, with multiple components
building on multiple systems.
My main driver is that we already use
35 matches
Mail list logo
