You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ol...@apache.org on 2018/04/07 11:19:23 UTC
[maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
This is an automated email from the ASF dual-hosted git repository.
olamy pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
from 50410a9 Add JDK 10 to the jdk default
add 96afe26 auto deploy if we are currently on master branch
new bb8b8c8 Merge pull request #1 from olamy/master
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
--
To stop receiving notification emails like this one, please contact
olamy@apache.org.
[maven-jenkins-lib] 01/01: Merge pull request #1 from olamy/master
Posted by ol...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
olamy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git
commit bb8b8c8d82a1ad62e7e61d2893993feed6b0140c
Merge: 50410a9 96afe26
Author: Olivier Lamy <ol...@apache.org>
AuthorDate: Sat Apr 7 21:19:21 2018 +1000
Merge pull request #1 from olamy/master
auto deploy if we are currently on master branch
vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
1 file changed, 19 insertions(+), 11 deletions(-)
--
To stop receiving notification emails like this one, please contact
olamy@apache.org.
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Olivier Lamy <ol...@apache.org>.
On Sun, 8 Apr 2018 at 23:20, Robert Scholte <rf...@apache.org> wrote:
> On Sun, 08 Apr 2018 13:22:14 +0200, Olivier Lamy <ol...@apache.org> wrote:
>
> > On Sun, 8 Apr 2018 at 19:31, Karl Heinz Marbaise <kh...@gmx.de>
> > wrote:
> >
> >> Hi,
> >>
> >> On 08/04/18 02:04, Olivier Lamy wrote:
> >> > I have disabled it as there were some errors (not sure what) with
> >> using
> >> the
> >> > configfile provider plugin.
> >> > But yup good catch we definitely need to do it only for one jdk...
> >>
> >> would be better...
> >>
> >> > not sure how to do the deploy at end as it was done previously by the
> >> maven
> >> > plugin. (probably someone need to write a plugin for this :-) )
> >>
> >> did I miss something ? What do you mean by this?
> >>
> >
> > ideally I'd like to get the produced/attached artifacts of a maven build
> > and deploy them.
> > But I'm not sure if with withMaven we can know which artifacts has been
> > produced by a jdk....
> >
>
> The information is there: take a look at
> https://builds.apache.org/job/maven-box/job/maven-invoker/job/master/
> or https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/
> They contain a list of Last Successful Artifacts, exactly the files that
> should be deployed.
>
>
yup, I can definitely have a towards the end of the week or early next week
(a bit busy this week with school holidays :-) )
> > So looks better to activate deploy goal only jdk=jdk7.
> > I don't like the idea about being dependant of a label (and what about
> > the
> > future when some part will be build with only jdk8+)
> > if any better idea?
> >
> >
> >>
> >> Kind regards
> >> Karl Heinz Marbaise
> >>
> >> >
> >> > On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rf...@apache.org>
> >> wrote:
> >> >
> >> >> Hi Olivier,
> >> >>
> >> >> doesn't this mean that we get about 8 deployments (2 oses times 4
> >> jdks)
> >> of
> >> >> the same artifacts?
> >> >> This is a potential problem for the metadata files.
> >> >> Is it possible to do it really at the end by Jenkins?
> >> >>
> >> >> thanks,
> >> >> Robert
> >> >>
> >> >> On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
> >> >>
> >> >>> This is an automated email from the ASF dual-hosted git repository.
> >> >>>
> >> >>> olamy pushed a change to branch master
> >> >>> in repository
> >> https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
> >> >>>
> >> >>>
> >> >>> from 50410a9 Add JDK 10 to the jdk default
> >> >>> add 96afe26 auto deploy if we are currently on master branch
> >> >>> new bb8b8c8 Merge pull request #1 from olamy/master
> >> >>>
> >> >>> The 1 revisions listed above as "new" are entirely new to this
> >> >>> repository and will be described in separate emails. The revisions
> >> >>> listed as "add" were already present in the repository and have only
> >> >>> been added to this reference.
> >> >>>
> >> >>>
> >> >>> Summary of changes:
> >> >>> vars/asfMavenTlpStdBuild.groovy | 30
> >> +++++++++++++++++++-----------
> >> >>> 1 file changed, 19 insertions(+), 11 deletions(-)
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Robert Scholte <rf...@apache.org>.
On Sun, 08 Apr 2018 13:22:14 +0200, Olivier Lamy <ol...@apache.org> wrote:
> On Sun, 8 Apr 2018 at 19:31, Karl Heinz Marbaise <kh...@gmx.de>
> wrote:
>
>> Hi,
>>
>> On 08/04/18 02:04, Olivier Lamy wrote:
>> > I have disabled it as there were some errors (not sure what) with
>> using
>> the
>> > configfile provider plugin.
>> > But yup good catch we definitely need to do it only for one jdk...
>>
>> would be better...
>>
>> > not sure how to do the deploy at end as it was done previously by the
>> maven
>> > plugin. (probably someone need to write a plugin for this :-) )
>>
>> did I miss something ? What do you mean by this?
>>
>
> ideally I'd like to get the produced/attached artifacts of a maven build
> and deploy them.
> But I'm not sure if with withMaven we can know which artifacts has been
> produced by a jdk....
>
The information is there: take a look at
https://builds.apache.org/job/maven-box/job/maven-invoker/job/master/
or https://builds.apache.org/job/maven-box/job/maven-wagon/job/master/
They contain a list of Last Successful Artifacts, exactly the files that
should be deployed.
> So looks better to activate deploy goal only jdk=jdk7.
> I don't like the idea about being dependant of a label (and what about
> the
> future when some part will be build with only jdk8+)
> if any better idea?
>
>
>>
>> Kind regards
>> Karl Heinz Marbaise
>>
>> >
>> > On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rf...@apache.org>
>> wrote:
>> >
>> >> Hi Olivier,
>> >>
>> >> doesn't this mean that we get about 8 deployments (2 oses times 4
>> jdks)
>> of
>> >> the same artifacts?
>> >> This is a potential problem for the metadata files.
>> >> Is it possible to do it really at the end by Jenkins?
>> >>
>> >> thanks,
>> >> Robert
>> >>
>> >> On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
>> >>
>> >>> This is an automated email from the ASF dual-hosted git repository.
>> >>>
>> >>> olamy pushed a change to branch master
>> >>> in repository
>> https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
>> >>>
>> >>>
>> >>> from 50410a9 Add JDK 10 to the jdk default
>> >>> add 96afe26 auto deploy if we are currently on master branch
>> >>> new bb8b8c8 Merge pull request #1 from olamy/master
>> >>>
>> >>> The 1 revisions listed above as "new" are entirely new to this
>> >>> repository and will be described in separate emails. The revisions
>> >>> listed as "add" were already present in the repository and have only
>> >>> been added to this reference.
>> >>>
>> >>>
>> >>> Summary of changes:
>> >>> vars/asfMavenTlpStdBuild.groovy | 30
>> +++++++++++++++++++-----------
>> >>> 1 file changed, 19 insertions(+), 11 deletions(-)
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Olivier Lamy <ol...@apache.org>.
On Sun, 8 Apr 2018 at 19:31, Karl Heinz Marbaise <kh...@gmx.de> wrote:
> Hi,
>
> On 08/04/18 02:04, Olivier Lamy wrote:
> > I have disabled it as there were some errors (not sure what) with using
> the
> > configfile provider plugin.
> > But yup good catch we definitely need to do it only for one jdk...
>
> would be better...
>
> > not sure how to do the deploy at end as it was done previously by the
> maven
> > plugin. (probably someone need to write a plugin for this :-) )
>
> did I miss something ? What do you mean by this?
>
ideally I'd like to get the produced/attached artifacts of a maven build
and deploy them.
But I'm not sure if with withMaven we can know which artifacts has been
produced by a jdk....
So looks better to activate deploy goal only jdk=jdk7.
I don't like the idea about being dependant of a label (and what about the
future when some part will be build with only jdk8+)
if any better idea?
>
> Kind regards
> Karl Heinz Marbaise
>
> >
> > On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rf...@apache.org>
> wrote:
> >
> >> Hi Olivier,
> >>
> >> doesn't this mean that we get about 8 deployments (2 oses times 4 jdks)
> of
> >> the same artifacts?
> >> This is a potential problem for the metadata files.
> >> Is it possible to do it really at the end by Jenkins?
> >>
> >> thanks,
> >> Robert
> >>
> >> On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
> >>
> >>> This is an automated email from the ASF dual-hosted git repository.
> >>>
> >>> olamy pushed a change to branch master
> >>> in repository
> https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
> >>>
> >>>
> >>> from 50410a9 Add JDK 10 to the jdk default
> >>> add 96afe26 auto deploy if we are currently on master branch
> >>> new bb8b8c8 Merge pull request #1 from olamy/master
> >>>
> >>> The 1 revisions listed above as "new" are entirely new to this
> >>> repository and will be described in separate emails. The revisions
> >>> listed as "add" were already present in the repository and have only
> >>> been added to this reference.
> >>>
> >>>
> >>> Summary of changes:
> >>> vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
> >>> 1 file changed, 19 insertions(+), 11 deletions(-)
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,
On 08/04/18 02:04, Olivier Lamy wrote:
> I have disabled it as there were some errors (not sure what) with using the
> configfile provider plugin.
> But yup good catch we definitely need to do it only for one jdk...
would be better...
> not sure how to do the deploy at end as it was done previously by the maven
> plugin. (probably someone need to write a plugin for this :-) )
did I miss something ? What do you mean by this?
Kind regards
Karl Heinz Marbaise
>
> On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rf...@apache.org> wrote:
>
>> Hi Olivier,
>>
>> doesn't this mean that we get about 8 deployments (2 oses times 4 jdks) of
>> the same artifacts?
>> This is a potential problem for the metadata files.
>> Is it possible to do it really at the end by Jenkins?
>>
>> thanks,
>> Robert
>>
>> On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
>>
>>> This is an automated email from the ASF dual-hosted git repository.
>>>
>>> olamy pushed a change to branch master
>>> in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
>>>
>>>
>>> from 50410a9 Add JDK 10 to the jdk default
>>> add 96afe26 auto deploy if we are currently on master branch
>>> new bb8b8c8 Merge pull request #1 from olamy/master
>>>
>>> The 1 revisions listed above as "new" are entirely new to this
>>> repository and will be described in separate emails. The revisions
>>> listed as "add" were already present in the repository and have only
>>> been added to this reference.
>>>
>>>
>>> Summary of changes:
>>> vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
>>> 1 file changed, 19 insertions(+), 11 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Olivier Lamy <ol...@apache.org>.
I have disabled it as there were some errors (not sure what) with using the
configfile provider plugin.
But yup good catch we definitely need to do it only for one jdk...
not sure how to do the deploy at end as it was done previously by the maven
plugin. (probably someone need to write a plugin for this :-) )
On Sat, 7 Apr 2018 at 22:09, Robert Scholte <rf...@apache.org> wrote:
> Hi Olivier,
>
> doesn't this mean that we get about 8 deployments (2 oses times 4 jdks) of
> the same artifacts?
> This is a potential problem for the metadata files.
> Is it possible to do it really at the end by Jenkins?
>
> thanks,
> Robert
>
> On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > olamy pushed a change to branch master
> > in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
> >
> >
> > from 50410a9 Add JDK 10 to the jdk default
> > add 96afe26 auto deploy if we are currently on master branch
> > new bb8b8c8 Merge pull request #1 from olamy/master
> >
> > The 1 revisions listed above as "new" are entirely new to this
> > repository and will be described in separate emails. The revisions
> > listed as "add" were already present in the repository and have only
> > been added to this reference.
> >
> >
> > Summary of changes:
> > vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
> > 1 file changed, 19 insertions(+), 11 deletions(-)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: [maven-jenkins-lib] branch master updated (50410a9 -> bb8b8c8)
Posted by Robert Scholte <rf...@apache.org>.
Hi Olivier,
doesn't this mean that we get about 8 deployments (2 oses times 4 jdks) of
the same artifacts?
This is a potential problem for the metadata files.
Is it possible to do it really at the end by Jenkins?
thanks,
Robert
On Sat, 07 Apr 2018 13:19:23 +0200, <ol...@apache.org> wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> olamy pushed a change to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git.
>
>
> from 50410a9 Add JDK 10 to the jdk default
> add 96afe26 auto deploy if we are currently on master branch
> new bb8b8c8 Merge pull request #1 from olamy/master
>
> The 1 revisions listed above as "new" are entirely new to this
> repository and will be described in separate emails. The revisions
> listed as "add" were already present in the repository and have only
> been added to this reference.
>
>
> Summary of changes:
> vars/asfMavenTlpStdBuild.groovy | 30 +++++++++++++++++++-----------
> 1 file changed, 19 insertions(+), 11 deletions(-)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org