You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Enrico Olivelli <eo...@gmail.com> on 2017/04/21 14:06:27 UTC
Publish SNAPSHOT artifacts on Maven Central
I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
Maven Central.
This will help projects which want to try the upcoming version without
dealing with custom local Maven Repositories.
I see recently Apache Tomcat started doing so
http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
I you all agree I would like to work on this.
-- Enrico
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
I managed to configure the daily master build to publish snapshots.
I have configured the job to go ahead even in case of test failures.
Snapshots are not signed
Enrico
Il mar 30 mag 2017, 22:23 Sijie Guo <gu...@gmail.com> ha scritto:
> Cool, thank you Enrico!
>
> - Sijie
>
> On Tue, May 30, 2017 at 1:21 PM, Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > 2017-05-30 22:07 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > > Sorry for late response.
> > >
> > > I just added you. Please check and let me know if it works.
> >
> > Now I can edit the configuration.
> > Thank you!
> > I am going to do some trials
> >
> > -- Enrico
> >
> >
> > >
> > > - Sijie
> > >
> > > On Tue, May 30, 2017 at 12:52 PM, Enrico Olivelli <eolivelli@gmail.com
> >
> > > wrote:
> > >
> > >> I apologize, did you have time to check the wiki?
> > >> Thanks
> > >> Enrico
> > >>
> > >> Il mar 16 mag 2017, 16:16 Enrico Olivelli <eo...@gmail.com> ha
> > >> scritto:
> > >>
> > >> > 2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > >> > > Gotcha. Let me check the wiki. (I am currently traveling.) I will
> > try
> > >> to
> > >> > > get this ready for you when I have a better access to internet.
> > >> > >
> > >> >
> > >> > Did you have time to check this activity ?
> > >> >
> > >> > Thanks
> > >> >
> > >> > -- Enrico
> > >> >
> > >> > > - Sijie
> > >> > >
> > >> > > On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <
> > eolivelli@gmail.com>
> > >> > wrote:
> > >> > >
> > >> > >> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > >> > >> > Enrico,
> > >> > >> >
> > >> > >> > Let me check it out. But I think you can apply for permissions
> to
> > >> > access
> > >> > >> > apache jenkins. Probably an INFRA ticket?
> > >> > >> >
> > >> > >>
> > >> > >>
> > >> > >> I'm sorry I cannot edit the configuration.
> > >> > >>
> > >> > >> According to this guide
> > >> > >> https://wiki.apache.org/general/Jenkins
> > >> > >> you (only the PMC chair) can give me access to job administration
> > by
> > >> > >> adding my id to the "hudson-jobadmin" group.
> > >> > >> My Apache ID is 'eolivelli'.
> > >> > >>
> > >> > >>
> > >> > >> Thank you
> > >> > >> -- Enrico
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >>
> > >> > >> > - Sijie
> > >> > >> >
> > >> > >> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <
> > >> eolivelli@gmail.com>
> > >> > >> wrote:
> > >> > >> >
> > >> > >> >> The PR has been merged, so now any committer can publish all
> the
> > >> > >> >> artifacts to the Apache snapshots repo
> > >> > >> >> just issuing from the cmd line:
> > >> > >> >> mvn clean deploy -DskipTests -Pdeploy
> > >> > >> >>
> > >> > >> >> I would like to try to add the 'deploy' goal to our daily
> build
> > on
> > >> > >> jenkins
> > >> > >> >> On the users@infra list they told me that it would be enough
> to
> > >> add
> > >> > >> >> the deploy goal and all is already 'ready' (deploy credentials
> > and
> > >> > PGP
> > >> > >> >> I think)
> > >> > >> >> I think I do no have enough permissions to modify the
> > configuration
> > >> > of
> > >> > >> the
> > >> > >> >> Job
> > >> > >> >> so Sijie can you try ?
> > >> > >> >>
> > >> > >> >> note:
> > >> > >> >> the "official" guide (1) tells to use a special maven profile
> to
> > >> > >> >> deploy the artifacts (-Papache-release), but for us it is
> > failing
> > >> > >> >> because it tries to create the javadocs for the 'compat' deps.
> > >> > >> >> IMHO our custom 'deploy' profile will be enough
> > >> > >> >>
> > >> > >> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> > >> >>
> > >> > >> >> -- Enrico
> > >> > >> >>
> > >> > >> >>
> > >> > >> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <
> eolivelli@gmail.com
> > >:
> > >> > >> >> > I am currently discussing on the users@infra mailing list
> > about
> > >> > how
> > >> > >> to
> > >> > >> >> > achieve our goal.
> > >> > >> >> > While playing with the deploy goal I succeeded in publishing
> > the
> > >> > >> >> > -SNAPSHOT version to the official apache snapshots
> repository
> > >> > >> >> >
> > >> > >> >> > In order to achieve it manually it is enough to follow the
> > guide
> > >> > >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> > >> >> >
> > >> > >> >> > Actually the goal for us is
> > >> > >> >> > mvn clean install -Pdeploy
> > >> > >> >> > as we have a "-SNAPSHOT" version the deploy is targeted to
> the
> > >> > apache
> > >> > >> >> > snapshots repository automatically (as written in the Apache
> > >> Parent
> > >> > >> >> > pom)
> > >> > >> >> >
> > >> > >> >> > But currently we have an issue on the versioning scheme of
> the
> > >> > >> >> > "compats" subproject, so that the 'deploy' goal against the
> > >> > snapshots
> > >> > >> >> > repository cannot be performed.
> > >> > >> >> >
> > >> > >> >> > This is our JIRA ticket
> > >> > >> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> > >> > >> >> >
> > >> > >> >> > This is the PR
> > >> > >> >> > https://github.com/apache/bookkeeper/pull/134
> > >> > >> >> >
> > >> > >> >> > This is our first public SNAPSHOT
> > >> > >> >> > https://repository.apache.org/content/repositories/
> > >> > >> snapshots/org/apache/
> > >> > >> >> bookkeeper/
> > >> > >> >> >
> > >> > >> >> > I need any committer to check and merge the PR in order to
> > >> continue
> > >> > >> the
> > >> > >> >> work.
> > >> > >> >> >
> > >> > >> >> > Once we have a compliant versioning scheme a think we can
> > >> continue
> > >> > the
> > >> > >> >> > discussion with the infra team in order to add an automatic
> > >> > deployment
> > >> > >> >> > on our Jenkins builds
> > >> > >> >> >
> > >> > >> >> > Notes:
> > >> > >> >> > 1) It seems that only one snapshot is retained and this is
> OK
> > >> > >> >> > 2) We will need to update the docs and write somewhere how
> to
> > use
> > >> > the
> > >> > >> >> > snapshots repository (just an example and a simple
> > explanation).
> > >> > Maybe
> > >> > >> >> > just on Confluence (I will do)
> > >> > >> >> > 3) Currently I have published the snapshot of the current
> > master,
> > >> > but
> > >> > >> >> > I have used my Apache PGP key (eolivelli@apache.org) but it
> > is
> > >> not
> > >> > >> >> > signed by any other person on the Apache Web Of Trust (I
> need
> > to
> > >> > find
> > >> > >> >> > some Apache fellow to sign my key, and it is not so simple
> in
> > >> > Italy).
> > >> > >> >> > I think this is not good. Maybe once the pom is OK and the
> > >> > procedure
> > >> > >> >> > is OK it will be better that some other committer with a
> > signed
> > >> PGP
> > >> > >> >> > key will publish a new version of the snapshot (maybe Sijie
> or
> > >> > Matteo
> > >> > >> >> > which were the last release managers)
> > >> > >> >> >
> > >> > >> >> >
> > >> > >> >> > -- Enrico
> > >> > >> >> >
> > >> > >> >> >
> > >> > >> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <
> > eolivelli@gmail.com
> > >> >:
> > >> > >> >> >> I will start inspecting the possibilities with the INFRA
> team
> > >> > >> >> >>
> > >> > >> >> >> I will come back to the list with some proposal
> > >> > >> >> >>
> > >> > >> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans
> > >> > <evans@yahoo-inc.com.invalid
> > >> > >> >:
> > >> > >> >> >>> There is a special SNAPSHOTS repo that is already setup.
> I
> > >> know
> > >> > >> that
> > >> > >> >> hadoop has been using it for a while, so you should just need
> to
> > >> ask
> > >> > >> where
> > >> > >> >> the snapshot repo is. Maven also will only push a -SNAPSHOT
> > build
> > >> > to a
> > >> > >> >> repo that has been confiugred to accept snapshots.
> > >> > >> >> >>>
> > >> > >> >> >>>
> > >> > >> >> >>> - Bobby
> > >> > >> >> >>>
> > >> > >> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico
> > Olivelli <
> > >> > >> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie
> > Guo <
> > >> > >> >> guosijie@gmail.com>:
> > >> > >> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> > >> > >> >> eolivelli@gmail.com>
> > >> > >> >> >>>> wrote:
> > >> > >> >> >>>>
> > >> > >> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <guosijie@gmail.com
> >
> > ha
> > >> > >> scritto:
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> > I don't have any objections on doing this, if we can
> > figure
> > >> > out
> > >> > >> >> >>>>> following:
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > - does Apache infra allow doing this?
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can
> > ask
> > >> > Mark.
> > >> > >> >> >>>>>
> > >> > >> >> >>>>
> > >> > >> >> >>>> How does the SNAPSHOT version look like? is it just
> > SNAPSHOT
> > >> or
> > >> > >> >> SNAPSHOT
> > >> > >> >> >>>> with gitsha suffix.
> > >> > >> >> >>>>
> > >> > >> >> >>>> The reason I asked this -
> > >> > >> >> >>>>
> > >> > >> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the
> > >> > packages
> > >> > >> >> every
> > >> > >> >> >>>> time?
> > >> > >> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC
> > >> releases
> > >> > >> >> within a
> > >> > >> >> >>>> big release?
> > >> > >> >> >>>>
> > >> > >> >> >>>
> > >> > >> >> >>> I think we can ask infra help to setup an auto-clean up of
> > the
> > >> > >> >> >>> repository, usually -SNASHOT is deployed with a timestamp
> > >> suffix
> > >> > of
> > >> > >> >> >>> whatever
> > >> > >> >> >>>
> > >> > >> >> >>> If you are OK a can contact infra in order to ask for help
> > and
> > >> > ask
> > >> > >> if
> > >> > >> >> >>> is feasible
> > >> > >> >> >>>
> > >> > >> >> >>>
> > >> > >> >> >>>
> > >> > >> >> >>>
> > >> > >> >> >>>>
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you
> > want
> > >> to
> > >> > >> >> publish?
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> Only the last successful build on jenkins
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> - why not shorten the release scope and publish a
> release
> > >> > instead?
> > >> > >> >> >>>>>
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> I really would like to have a release ASAP but I think
> > this
> > >> is
> > >> > a
> > >> > >> >> different
> > >> > >> >> >>>>> problem.
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> The idea is to simplify testing of other downstream
> > project
> > >> > >> against
> > >> > >> >> the
> > >> > >> >> >>>>> current master without the need to publish local forks
> of
> > BK
> > >> to
> > >> > >> >> local maven
> > >> > >> >> >>>>> repositories.
> > >> > >> >> >>>>> For all downstream open source projects this will be
> very
> > >> > useful
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> I volunteer to setup the jenkins job and deal with infra
> > >> > >> >> >>>>>
> > >> > >> >> >>>>
> > >> > >> >> >>>> +1 on this.
> > >> > >> >> >>>>
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > Thoughts?
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> > >> > >> >> jujjuri@gmail.com>
> > >> > >> >> >>>>> > wrote:
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > +1
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> > >> > >> >> matteo.merli@gmail.com>
> > >> > >> >> >>>>> > wrote:
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > > +1
> > >> > >> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> > >> > >> >> eolivelli@gmail.com>
> > >> > >> >> >>>>> > > wrote:
> > >> > >> >> >>>>> > >
> > >> > >> >> >>>>> > > > I wonder if we can start publishing the
> > 4.5.0-SNAPSHOT
> > >> > >> >> binaries on
> > >> > >> >> >>>>> > > > Maven Central.
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > > This will help projects which want to try the
> > upcoming
> > >> > >> version
> > >> > >> >> >>>>> without
> > >> > >> >> >>>>> > > > dealing with custom local Maven Repositories.
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > > I see recently Apache Tomcat started doing so
> > >> > >> >> >>>>> > > > http://marc.info/?l=tomcat-
> > dev&m=149269803006113&w=2
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > > I you all agree I would like to work on this.
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > > > -- Enrico
> > >> > >> >> >>>>> > > >
> > >> > >> >> >>>>> > >
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> > --
> > >> > >> >> >>>>> > Jvrao
> > >> > >> >> >>>>> > ---
> > >> > >> >> >>>>> > First they ignore you, then they laugh at you, then
> they
> > >> > fight
> > >> > >> >> you, then
> > >> > >> >> >>>>> > you win. - Mahatma Gandhi
> > >> > >> >> >>>>> >
> > >> > >> >> >>>>> --
> > >> > >> >> >>>>>
> > >> > >> >> >>>>>
> > >> > >> >> >>>>> -- Enrico Olivelli
> > >> > >> >> >>>>>
> > >> > >> >>
> > >> > >>
> > >> >
> > >> --
> > >>
> > >>
> > >> -- Enrico Olivelli
> > >>
> >
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
Cool, thank you Enrico!
- Sijie
On Tue, May 30, 2017 at 1:21 PM, Enrico Olivelli <eo...@gmail.com>
wrote:
> 2017-05-30 22:07 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > Sorry for late response.
> >
> > I just added you. Please check and let me know if it works.
>
> Now I can edit the configuration.
> Thank you!
> I am going to do some trials
>
> -- Enrico
>
>
> >
> > - Sijie
> >
> > On Tue, May 30, 2017 at 12:52 PM, Enrico Olivelli <eo...@gmail.com>
> > wrote:
> >
> >> I apologize, did you have time to check the wiki?
> >> Thanks
> >> Enrico
> >>
> >> Il mar 16 mag 2017, 16:16 Enrico Olivelli <eo...@gmail.com> ha
> >> scritto:
> >>
> >> > 2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> >> > > Gotcha. Let me check the wiki. (I am currently traveling.) I will
> try
> >> to
> >> > > get this ready for you when I have a better access to internet.
> >> > >
> >> >
> >> > Did you have time to check this activity ?
> >> >
> >> > Thanks
> >> >
> >> > -- Enrico
> >> >
> >> > > - Sijie
> >> > >
> >> > > On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <
> eolivelli@gmail.com>
> >> > wrote:
> >> > >
> >> > >> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> >> > >> > Enrico,
> >> > >> >
> >> > >> > Let me check it out. But I think you can apply for permissions to
> >> > access
> >> > >> > apache jenkins. Probably an INFRA ticket?
> >> > >> >
> >> > >>
> >> > >>
> >> > >> I'm sorry I cannot edit the configuration.
> >> > >>
> >> > >> According to this guide
> >> > >> https://wiki.apache.org/general/Jenkins
> >> > >> you (only the PMC chair) can give me access to job administration
> by
> >> > >> adding my id to the "hudson-jobadmin" group.
> >> > >> My Apache ID is 'eolivelli'.
> >> > >>
> >> > >>
> >> > >> Thank you
> >> > >> -- Enrico
> >> > >>
> >> > >>
> >> > >>
> >> > >>
> >> > >> > - Sijie
> >> > >> >
> >> > >> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <
> >> eolivelli@gmail.com>
> >> > >> wrote:
> >> > >> >
> >> > >> >> The PR has been merged, so now any committer can publish all the
> >> > >> >> artifacts to the Apache snapshots repo
> >> > >> >> just issuing from the cmd line:
> >> > >> >> mvn clean deploy -DskipTests -Pdeploy
> >> > >> >>
> >> > >> >> I would like to try to add the 'deploy' goal to our daily build
> on
> >> > >> jenkins
> >> > >> >> On the users@infra list they told me that it would be enough to
> >> add
> >> > >> >> the deploy goal and all is already 'ready' (deploy credentials
> and
> >> > PGP
> >> > >> >> I think)
> >> > >> >> I think I do no have enough permissions to modify the
> configuration
> >> > of
> >> > >> the
> >> > >> >> Job
> >> > >> >> so Sijie can you try ?
> >> > >> >>
> >> > >> >> note:
> >> > >> >> the "official" guide (1) tells to use a special maven profile to
> >> > >> >> deploy the artifacts (-Papache-release), but for us it is
> failing
> >> > >> >> because it tries to create the javadocs for the 'compat' deps.
> >> > >> >> IMHO our custom 'deploy' profile will be enough
> >> > >> >>
> >> > >> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
> >> > >> >>
> >> > >> >> -- Enrico
> >> > >> >>
> >> > >> >>
> >> > >> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eolivelli@gmail.com
> >:
> >> > >> >> > I am currently discussing on the users@infra mailing list
> about
> >> > how
> >> > >> to
> >> > >> >> > achieve our goal.
> >> > >> >> > While playing with the deploy goal I succeeded in publishing
> the
> >> > >> >> > -SNAPSHOT version to the official apache snapshots repository
> >> > >> >> >
> >> > >> >> > In order to achieve it manually it is enough to follow the
> guide
> >> > >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
> >> > >> >> >
> >> > >> >> > Actually the goal for us is
> >> > >> >> > mvn clean install -Pdeploy
> >> > >> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the
> >> > apache
> >> > >> >> > snapshots repository automatically (as written in the Apache
> >> Parent
> >> > >> >> > pom)
> >> > >> >> >
> >> > >> >> > But currently we have an issue on the versioning scheme of the
> >> > >> >> > "compats" subproject, so that the 'deploy' goal against the
> >> > snapshots
> >> > >> >> > repository cannot be performed.
> >> > >> >> >
> >> > >> >> > This is our JIRA ticket
> >> > >> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> >> > >> >> >
> >> > >> >> > This is the PR
> >> > >> >> > https://github.com/apache/bookkeeper/pull/134
> >> > >> >> >
> >> > >> >> > This is our first public SNAPSHOT
> >> > >> >> > https://repository.apache.org/content/repositories/
> >> > >> snapshots/org/apache/
> >> > >> >> bookkeeper/
> >> > >> >> >
> >> > >> >> > I need any committer to check and merge the PR in order to
> >> continue
> >> > >> the
> >> > >> >> work.
> >> > >> >> >
> >> > >> >> > Once we have a compliant versioning scheme a think we can
> >> continue
> >> > the
> >> > >> >> > discussion with the infra team in order to add an automatic
> >> > deployment
> >> > >> >> > on our Jenkins builds
> >> > >> >> >
> >> > >> >> > Notes:
> >> > >> >> > 1) It seems that only one snapshot is retained and this is OK
> >> > >> >> > 2) We will need to update the docs and write somewhere how to
> use
> >> > the
> >> > >> >> > snapshots repository (just an example and a simple
> explanation).
> >> > Maybe
> >> > >> >> > just on Confluence (I will do)
> >> > >> >> > 3) Currently I have published the snapshot of the current
> master,
> >> > but
> >> > >> >> > I have used my Apache PGP key (eolivelli@apache.org) but it
> is
> >> not
> >> > >> >> > signed by any other person on the Apache Web Of Trust (I need
> to
> >> > find
> >> > >> >> > some Apache fellow to sign my key, and it is not so simple in
> >> > Italy).
> >> > >> >> > I think this is not good. Maybe once the pom is OK and the
> >> > procedure
> >> > >> >> > is OK it will be better that some other committer with a
> signed
> >> PGP
> >> > >> >> > key will publish a new version of the snapshot (maybe Sijie or
> >> > Matteo
> >> > >> >> > which were the last release managers)
> >> > >> >> >
> >> > >> >> >
> >> > >> >> > -- Enrico
> >> > >> >> >
> >> > >> >> >
> >> > >> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <
> eolivelli@gmail.com
> >> >:
> >> > >> >> >> I will start inspecting the possibilities with the INFRA team
> >> > >> >> >>
> >> > >> >> >> I will come back to the list with some proposal
> >> > >> >> >>
> >> > >> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans
> >> > <evans@yahoo-inc.com.invalid
> >> > >> >:
> >> > >> >> >>> There is a special SNAPSHOTS repo that is already setup. I
> >> know
> >> > >> that
> >> > >> >> hadoop has been using it for a while, so you should just need to
> >> ask
> >> > >> where
> >> > >> >> the snapshot repo is. Maven also will only push a -SNAPSHOT
> build
> >> > to a
> >> > >> >> repo that has been confiugred to accept snapshots.
> >> > >> >> >>>
> >> > >> >> >>>
> >> > >> >> >>> - Bobby
> >> > >> >> >>>
> >> > >> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico
> Olivelli <
> >> > >> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie
> Guo <
> >> > >> >> guosijie@gmail.com>:
> >> > >> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> >> > >> >> eolivelli@gmail.com>
> >> > >> >> >>>> wrote:
> >> > >> >> >>>>
> >> > >> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com>
> ha
> >> > >> scritto:
> >> > >> >> >>>>>
> >> > >> >> >>>>> > I don't have any objections on doing this, if we can
> figure
> >> > out
> >> > >> >> >>>>> following:
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > - does Apache infra allow doing this?
> >> > >> >> >>>>> >
> >> > >> >> >>>>>
> >> > >> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can
> ask
> >> > Mark.
> >> > >> >> >>>>>
> >> > >> >> >>>>
> >> > >> >> >>>> How does the SNAPSHOT version look like? is it just
> SNAPSHOT
> >> or
> >> > >> >> SNAPSHOT
> >> > >> >> >>>> with gitsha suffix.
> >> > >> >> >>>>
> >> > >> >> >>>> The reason I asked this -
> >> > >> >> >>>>
> >> > >> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the
> >> > packages
> >> > >> >> every
> >> > >> >> >>>> time?
> >> > >> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC
> >> releases
> >> > >> >> within a
> >> > >> >> >>>> big release?
> >> > >> >> >>>>
> >> > >> >> >>>
> >> > >> >> >>> I think we can ask infra help to setup an auto-clean up of
> the
> >> > >> >> >>> repository, usually -SNASHOT is deployed with a timestamp
> >> suffix
> >> > of
> >> > >> >> >>> whatever
> >> > >> >> >>>
> >> > >> >> >>> If you are OK a can contact infra in order to ask for help
> and
> >> > ask
> >> > >> if
> >> > >> >> >>> is feasible
> >> > >> >> >>>
> >> > >> >> >>>
> >> > >> >> >>>
> >> > >> >> >>>
> >> > >> >> >>>>
> >> > >> >> >>>>>
> >> > >> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you
> want
> >> to
> >> > >> >> publish?
> >> > >> >> >>>>> >
> >> > >> >> >>>>> Only the last successful build on jenkins
> >> > >> >> >>>>>
> >> > >> >> >>>>> - why not shorten the release scope and publish a release
> >> > instead?
> >> > >> >> >>>>>
> >> > >> >> >>>>>
> >> > >> >> >>>>> I really would like to have a release ASAP but I think
> this
> >> is
> >> > a
> >> > >> >> different
> >> > >> >> >>>>> problem.
> >> > >> >> >>>>>
> >> > >> >> >>>>> The idea is to simplify testing of other downstream
> project
> >> > >> against
> >> > >> >> the
> >> > >> >> >>>>> current master without the need to publish local forks of
> BK
> >> to
> >> > >> >> local maven
> >> > >> >> >>>>> repositories.
> >> > >> >> >>>>> For all downstream open source projects this will be very
> >> > useful
> >> > >> >> >>>>>
> >> > >> >> >>>>> I volunteer to setup the jenkins job and deal with infra
> >> > >> >> >>>>>
> >> > >> >> >>>>
> >> > >> >> >>>> +1 on this.
> >> > >> >> >>>>
> >> > >> >> >>>>>
> >> > >> >> >>>>> >
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > Thoughts?
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> >> > >> >> jujjuri@gmail.com>
> >> > >> >> >>>>> > wrote:
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > +1
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> >> > >> >> matteo.merli@gmail.com>
> >> > >> >> >>>>> > wrote:
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > > +1
> >> > >> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> >> > >> >> eolivelli@gmail.com>
> >> > >> >> >>>>> > > wrote:
> >> > >> >> >>>>> > >
> >> > >> >> >>>>> > > > I wonder if we can start publishing the
> 4.5.0-SNAPSHOT
> >> > >> >> binaries on
> >> > >> >> >>>>> > > > Maven Central.
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > > This will help projects which want to try the
> upcoming
> >> > >> version
> >> > >> >> >>>>> without
> >> > >> >> >>>>> > > > dealing with custom local Maven Repositories.
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > > I see recently Apache Tomcat started doing so
> >> > >> >> >>>>> > > > http://marc.info/?l=tomcat-
> dev&m=149269803006113&w=2
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > > I you all agree I would like to work on this.
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > > > -- Enrico
> >> > >> >> >>>>> > > >
> >> > >> >> >>>>> > >
> >> > >> >> >>>>> >
> >> > >> >> >>>>> >
> >> > >> >> >>>>> >
> >> > >> >> >>>>> > --
> >> > >> >> >>>>> > Jvrao
> >> > >> >> >>>>> > ---
> >> > >> >> >>>>> > First they ignore you, then they laugh at you, then they
> >> > fight
> >> > >> >> you, then
> >> > >> >> >>>>> > you win. - Mahatma Gandhi
> >> > >> >> >>>>> >
> >> > >> >> >>>>> --
> >> > >> >> >>>>>
> >> > >> >> >>>>>
> >> > >> >> >>>>> -- Enrico Olivelli
> >> > >> >> >>>>>
> >> > >> >>
> >> > >>
> >> >
> >> --
> >>
> >>
> >> -- Enrico Olivelli
> >>
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
2017-05-30 22:07 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> Sorry for late response.
>
> I just added you. Please check and let me know if it works.
Now I can edit the configuration.
Thank you!
I am going to do some trials
-- Enrico
>
> - Sijie
>
> On Tue, May 30, 2017 at 12:52 PM, Enrico Olivelli <eo...@gmail.com>
> wrote:
>
>> I apologize, did you have time to check the wiki?
>> Thanks
>> Enrico
>>
>> Il mar 16 mag 2017, 16:16 Enrico Olivelli <eo...@gmail.com> ha
>> scritto:
>>
>> > 2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>> > > Gotcha. Let me check the wiki. (I am currently traveling.) I will try
>> to
>> > > get this ready for you when I have a better access to internet.
>> > >
>> >
>> > Did you have time to check this activity ?
>> >
>> > Thanks
>> >
>> > -- Enrico
>> >
>> > > - Sijie
>> > >
>> > > On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <eo...@gmail.com>
>> > wrote:
>> > >
>> > >> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>> > >> > Enrico,
>> > >> >
>> > >> > Let me check it out. But I think you can apply for permissions to
>> > access
>> > >> > apache jenkins. Probably an INFRA ticket?
>> > >> >
>> > >>
>> > >>
>> > >> I'm sorry I cannot edit the configuration.
>> > >>
>> > >> According to this guide
>> > >> https://wiki.apache.org/general/Jenkins
>> > >> you (only the PMC chair) can give me access to job administration by
>> > >> adding my id to the "hudson-jobadmin" group.
>> > >> My Apache ID is 'eolivelli'.
>> > >>
>> > >>
>> > >> Thank you
>> > >> -- Enrico
>> > >>
>> > >>
>> > >>
>> > >>
>> > >> > - Sijie
>> > >> >
>> > >> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <
>> eolivelli@gmail.com>
>> > >> wrote:
>> > >> >
>> > >> >> The PR has been merged, so now any committer can publish all the
>> > >> >> artifacts to the Apache snapshots repo
>> > >> >> just issuing from the cmd line:
>> > >> >> mvn clean deploy -DskipTests -Pdeploy
>> > >> >>
>> > >> >> I would like to try to add the 'deploy' goal to our daily build on
>> > >> jenkins
>> > >> >> On the users@infra list they told me that it would be enough to
>> add
>> > >> >> the deploy goal and all is already 'ready' (deploy credentials and
>> > PGP
>> > >> >> I think)
>> > >> >> I think I do no have enough permissions to modify the configuration
>> > of
>> > >> the
>> > >> >> Job
>> > >> >> so Sijie can you try ?
>> > >> >>
>> > >> >> note:
>> > >> >> the "official" guide (1) tells to use a special maven profile to
>> > >> >> deploy the artifacts (-Papache-release), but for us it is failing
>> > >> >> because it tries to create the javadocs for the 'compat' deps.
>> > >> >> IMHO our custom 'deploy' profile will be enough
>> > >> >>
>> > >> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
>> > >> >>
>> > >> >> -- Enrico
>> > >> >>
>> > >> >>
>> > >> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> > >> >> > I am currently discussing on the users@infra mailing list about
>> > how
>> > >> to
>> > >> >> > achieve our goal.
>> > >> >> > While playing with the deploy goal I succeeded in publishing the
>> > >> >> > -SNAPSHOT version to the official apache snapshots repository
>> > >> >> >
>> > >> >> > In order to achieve it manually it is enough to follow the guide
>> > >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
>> > >> >> >
>> > >> >> > Actually the goal for us is
>> > >> >> > mvn clean install -Pdeploy
>> > >> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the
>> > apache
>> > >> >> > snapshots repository automatically (as written in the Apache
>> Parent
>> > >> >> > pom)
>> > >> >> >
>> > >> >> > But currently we have an issue on the versioning scheme of the
>> > >> >> > "compats" subproject, so that the 'deploy' goal against the
>> > snapshots
>> > >> >> > repository cannot be performed.
>> > >> >> >
>> > >> >> > This is our JIRA ticket
>> > >> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
>> > >> >> >
>> > >> >> > This is the PR
>> > >> >> > https://github.com/apache/bookkeeper/pull/134
>> > >> >> >
>> > >> >> > This is our first public SNAPSHOT
>> > >> >> > https://repository.apache.org/content/repositories/
>> > >> snapshots/org/apache/
>> > >> >> bookkeeper/
>> > >> >> >
>> > >> >> > I need any committer to check and merge the PR in order to
>> continue
>> > >> the
>> > >> >> work.
>> > >> >> >
>> > >> >> > Once we have a compliant versioning scheme a think we can
>> continue
>> > the
>> > >> >> > discussion with the infra team in order to add an automatic
>> > deployment
>> > >> >> > on our Jenkins builds
>> > >> >> >
>> > >> >> > Notes:
>> > >> >> > 1) It seems that only one snapshot is retained and this is OK
>> > >> >> > 2) We will need to update the docs and write somewhere how to use
>> > the
>> > >> >> > snapshots repository (just an example and a simple explanation).
>> > Maybe
>> > >> >> > just on Confluence (I will do)
>> > >> >> > 3) Currently I have published the snapshot of the current master,
>> > but
>> > >> >> > I have used my Apache PGP key (eolivelli@apache.org) but it is
>> not
>> > >> >> > signed by any other person on the Apache Web Of Trust (I need to
>> > find
>> > >> >> > some Apache fellow to sign my key, and it is not so simple in
>> > Italy).
>> > >> >> > I think this is not good. Maybe once the pom is OK and the
>> > procedure
>> > >> >> > is OK it will be better that some other committer with a signed
>> PGP
>> > >> >> > key will publish a new version of the snapshot (maybe Sijie or
>> > Matteo
>> > >> >> > which were the last release managers)
>> > >> >> >
>> > >> >> >
>> > >> >> > -- Enrico
>> > >> >> >
>> > >> >> >
>> > >> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eolivelli@gmail.com
>> >:
>> > >> >> >> I will start inspecting the possibilities with the INFRA team
>> > >> >> >>
>> > >> >> >> I will come back to the list with some proposal
>> > >> >> >>
>> > >> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans
>> > <evans@yahoo-inc.com.invalid
>> > >> >:
>> > >> >> >>> There is a special SNAPSHOTS repo that is already setup. I
>> know
>> > >> that
>> > >> >> hadoop has been using it for a while, so you should just need to
>> ask
>> > >> where
>> > >> >> the snapshot repo is. Maven also will only push a -SNAPSHOT build
>> > to a
>> > >> >> repo that has been confiugred to accept snapshots.
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>> - Bobby
>> > >> >> >>>
>> > >> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
>> > >> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
>> > >> >> guosijie@gmail.com>:
>> > >> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
>> > >> >> eolivelli@gmail.com>
>> > >> >> >>>> wrote:
>> > >> >> >>>>
>> > >> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha
>> > >> scritto:
>> > >> >> >>>>>
>> > >> >> >>>>> > I don't have any objections on doing this, if we can figure
>> > out
>> > >> >> >>>>> following:
>> > >> >> >>>>> >
>> > >> >> >>>>> > - does Apache infra allow doing this?
>> > >> >> >>>>> >
>> > >> >> >>>>>
>> > >> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask
>> > Mark.
>> > >> >> >>>>>
>> > >> >> >>>>
>> > >> >> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT
>> or
>> > >> >> SNAPSHOT
>> > >> >> >>>> with gitsha suffix.
>> > >> >> >>>>
>> > >> >> >>>> The reason I asked this -
>> > >> >> >>>>
>> > >> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the
>> > packages
>> > >> >> every
>> > >> >> >>>> time?
>> > >> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC
>> releases
>> > >> >> within a
>> > >> >> >>>> big release?
>> > >> >> >>>>
>> > >> >> >>>
>> > >> >> >>> I think we can ask infra help to setup an auto-clean up of the
>> > >> >> >>> repository, usually -SNASHOT is deployed with a timestamp
>> suffix
>> > of
>> > >> >> >>> whatever
>> > >> >> >>>
>> > >> >> >>> If you are OK a can contact infra in order to ask for help and
>> > ask
>> > >> if
>> > >> >> >>> is feasible
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>>
>> > >> >> >>>>
>> > >> >> >>>>>
>> > >> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want
>> to
>> > >> >> publish?
>> > >> >> >>>>> >
>> > >> >> >>>>> Only the last successful build on jenkins
>> > >> >> >>>>>
>> > >> >> >>>>> - why not shorten the release scope and publish a release
>> > instead?
>> > >> >> >>>>>
>> > >> >> >>>>>
>> > >> >> >>>>> I really would like to have a release ASAP but I think this
>> is
>> > a
>> > >> >> different
>> > >> >> >>>>> problem.
>> > >> >> >>>>>
>> > >> >> >>>>> The idea is to simplify testing of other downstream project
>> > >> against
>> > >> >> the
>> > >> >> >>>>> current master without the need to publish local forks of BK
>> to
>> > >> >> local maven
>> > >> >> >>>>> repositories.
>> > >> >> >>>>> For all downstream open source projects this will be very
>> > useful
>> > >> >> >>>>>
>> > >> >> >>>>> I volunteer to setup the jenkins job and deal with infra
>> > >> >> >>>>>
>> > >> >> >>>>
>> > >> >> >>>> +1 on this.
>> > >> >> >>>>
>> > >> >> >>>>>
>> > >> >> >>>>> >
>> > >> >> >>>>> >
>> > >> >> >>>>> > Thoughts?
>> > >> >> >>>>> >
>> > >> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
>> > >> >> jujjuri@gmail.com>
>> > >> >> >>>>> > wrote:
>> > >> >> >>>>> >
>> > >> >> >>>>> > +1
>> > >> >> >>>>> >
>> > >> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
>> > >> >> matteo.merli@gmail.com>
>> > >> >> >>>>> > wrote:
>> > >> >> >>>>> >
>> > >> >> >>>>> > > +1
>> > >> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
>> > >> >> eolivelli@gmail.com>
>> > >> >> >>>>> > > wrote:
>> > >> >> >>>>> > >
>> > >> >> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
>> > >> >> binaries on
>> > >> >> >>>>> > > > Maven Central.
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > > This will help projects which want to try the upcoming
>> > >> version
>> > >> >> >>>>> without
>> > >> >> >>>>> > > > dealing with custom local Maven Repositories.
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > > I see recently Apache Tomcat started doing so
>> > >> >> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > > I you all agree I would like to work on this.
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > > > -- Enrico
>> > >> >> >>>>> > > >
>> > >> >> >>>>> > >
>> > >> >> >>>>> >
>> > >> >> >>>>> >
>> > >> >> >>>>> >
>> > >> >> >>>>> > --
>> > >> >> >>>>> > Jvrao
>> > >> >> >>>>> > ---
>> > >> >> >>>>> > First they ignore you, then they laugh at you, then they
>> > fight
>> > >> >> you, then
>> > >> >> >>>>> > you win. - Mahatma Gandhi
>> > >> >> >>>>> >
>> > >> >> >>>>> --
>> > >> >> >>>>>
>> > >> >> >>>>>
>> > >> >> >>>>> -- Enrico Olivelli
>> > >> >> >>>>>
>> > >> >>
>> > >>
>> >
>> --
>>
>>
>> -- Enrico Olivelli
>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
Sorry for late response.
I just added you. Please check and let me know if it works.
- Sijie
On Tue, May 30, 2017 at 12:52 PM, Enrico Olivelli <eo...@gmail.com>
wrote:
> I apologize, did you have time to check the wiki?
> Thanks
> Enrico
>
> Il mar 16 mag 2017, 16:16 Enrico Olivelli <eo...@gmail.com> ha
> scritto:
>
> > 2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > > Gotcha. Let me check the wiki. (I am currently traveling.) I will try
> to
> > > get this ready for you when I have a better access to internet.
> > >
> >
> > Did you have time to check this activity ?
> >
> > Thanks
> >
> > -- Enrico
> >
> > > - Sijie
> > >
> > > On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <eo...@gmail.com>
> > wrote:
> > >
> > >> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > >> > Enrico,
> > >> >
> > >> > Let me check it out. But I think you can apply for permissions to
> > access
> > >> > apache jenkins. Probably an INFRA ticket?
> > >> >
> > >>
> > >>
> > >> I'm sorry I cannot edit the configuration.
> > >>
> > >> According to this guide
> > >> https://wiki.apache.org/general/Jenkins
> > >> you (only the PMC chair) can give me access to job administration by
> > >> adding my id to the "hudson-jobadmin" group.
> > >> My Apache ID is 'eolivelli'.
> > >>
> > >>
> > >> Thank you
> > >> -- Enrico
> > >>
> > >>
> > >>
> > >>
> > >> > - Sijie
> > >> >
> > >> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <
> eolivelli@gmail.com>
> > >> wrote:
> > >> >
> > >> >> The PR has been merged, so now any committer can publish all the
> > >> >> artifacts to the Apache snapshots repo
> > >> >> just issuing from the cmd line:
> > >> >> mvn clean deploy -DskipTests -Pdeploy
> > >> >>
> > >> >> I would like to try to add the 'deploy' goal to our daily build on
> > >> jenkins
> > >> >> On the users@infra list they told me that it would be enough to
> add
> > >> >> the deploy goal and all is already 'ready' (deploy credentials and
> > PGP
> > >> >> I think)
> > >> >> I think I do no have enough permissions to modify the configuration
> > of
> > >> the
> > >> >> Job
> > >> >> so Sijie can you try ?
> > >> >>
> > >> >> note:
> > >> >> the "official" guide (1) tells to use a special maven profile to
> > >> >> deploy the artifacts (-Papache-release), but for us it is failing
> > >> >> because it tries to create the javadocs for the 'compat' deps.
> > >> >> IMHO our custom 'deploy' profile will be enough
> > >> >>
> > >> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> >>
> > >> >> -- Enrico
> > >> >>
> > >> >>
> > >> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> > >> >> > I am currently discussing on the users@infra mailing list about
> > how
> > >> to
> > >> >> > achieve our goal.
> > >> >> > While playing with the deploy goal I succeeded in publishing the
> > >> >> > -SNAPSHOT version to the official apache snapshots repository
> > >> >> >
> > >> >> > In order to achieve it manually it is enough to follow the guide
> > >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
> > >> >> >
> > >> >> > Actually the goal for us is
> > >> >> > mvn clean install -Pdeploy
> > >> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the
> > apache
> > >> >> > snapshots repository automatically (as written in the Apache
> Parent
> > >> >> > pom)
> > >> >> >
> > >> >> > But currently we have an issue on the versioning scheme of the
> > >> >> > "compats" subproject, so that the 'deploy' goal against the
> > snapshots
> > >> >> > repository cannot be performed.
> > >> >> >
> > >> >> > This is our JIRA ticket
> > >> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> > >> >> >
> > >> >> > This is the PR
> > >> >> > https://github.com/apache/bookkeeper/pull/134
> > >> >> >
> > >> >> > This is our first public SNAPSHOT
> > >> >> > https://repository.apache.org/content/repositories/
> > >> snapshots/org/apache/
> > >> >> bookkeeper/
> > >> >> >
> > >> >> > I need any committer to check and merge the PR in order to
> continue
> > >> the
> > >> >> work.
> > >> >> >
> > >> >> > Once we have a compliant versioning scheme a think we can
> continue
> > the
> > >> >> > discussion with the infra team in order to add an automatic
> > deployment
> > >> >> > on our Jenkins builds
> > >> >> >
> > >> >> > Notes:
> > >> >> > 1) It seems that only one snapshot is retained and this is OK
> > >> >> > 2) We will need to update the docs and write somewhere how to use
> > the
> > >> >> > snapshots repository (just an example and a simple explanation).
> > Maybe
> > >> >> > just on Confluence (I will do)
> > >> >> > 3) Currently I have published the snapshot of the current master,
> > but
> > >> >> > I have used my Apache PGP key (eolivelli@apache.org) but it is
> not
> > >> >> > signed by any other person on the Apache Web Of Trust (I need to
> > find
> > >> >> > some Apache fellow to sign my key, and it is not so simple in
> > Italy).
> > >> >> > I think this is not good. Maybe once the pom is OK and the
> > procedure
> > >> >> > is OK it will be better that some other committer with a signed
> PGP
> > >> >> > key will publish a new version of the snapshot (maybe Sijie or
> > Matteo
> > >> >> > which were the last release managers)
> > >> >> >
> > >> >> >
> > >> >> > -- Enrico
> > >> >> >
> > >> >> >
> > >> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eolivelli@gmail.com
> >:
> > >> >> >> I will start inspecting the possibilities with the INFRA team
> > >> >> >>
> > >> >> >> I will come back to the list with some proposal
> > >> >> >>
> > >> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans
> > <evans@yahoo-inc.com.invalid
> > >> >:
> > >> >> >>> There is a special SNAPSHOTS repo that is already setup. I
> know
> > >> that
> > >> >> hadoop has been using it for a while, so you should just need to
> ask
> > >> where
> > >> >> the snapshot repo is. Maven also will only push a -SNAPSHOT build
> > to a
> > >> >> repo that has been confiugred to accept snapshots.
> > >> >> >>>
> > >> >> >>>
> > >> >> >>> - Bobby
> > >> >> >>>
> > >> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
> > >> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
> > >> >> guosijie@gmail.com>:
> > >> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> > >> >> eolivelli@gmail.com>
> > >> >> >>>> wrote:
> > >> >> >>>>
> > >> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha
> > >> scritto:
> > >> >> >>>>>
> > >> >> >>>>> > I don't have any objections on doing this, if we can figure
> > out
> > >> >> >>>>> following:
> > >> >> >>>>> >
> > >> >> >>>>> > - does Apache infra allow doing this?
> > >> >> >>>>> >
> > >> >> >>>>>
> > >> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask
> > Mark.
> > >> >> >>>>>
> > >> >> >>>>
> > >> >> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT
> or
> > >> >> SNAPSHOT
> > >> >> >>>> with gitsha suffix.
> > >> >> >>>>
> > >> >> >>>> The reason I asked this -
> > >> >> >>>>
> > >> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the
> > packages
> > >> >> every
> > >> >> >>>> time?
> > >> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC
> releases
> > >> >> within a
> > >> >> >>>> big release?
> > >> >> >>>>
> > >> >> >>>
> > >> >> >>> I think we can ask infra help to setup an auto-clean up of the
> > >> >> >>> repository, usually -SNASHOT is deployed with a timestamp
> suffix
> > of
> > >> >> >>> whatever
> > >> >> >>>
> > >> >> >>> If you are OK a can contact infra in order to ask for help and
> > ask
> > >> if
> > >> >> >>> is feasible
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>
> > >> >> >>>>
> > >> >> >>>>>
> > >> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want
> to
> > >> >> publish?
> > >> >> >>>>> >
> > >> >> >>>>> Only the last successful build on jenkins
> > >> >> >>>>>
> > >> >> >>>>> - why not shorten the release scope and publish a release
> > instead?
> > >> >> >>>>>
> > >> >> >>>>>
> > >> >> >>>>> I really would like to have a release ASAP but I think this
> is
> > a
> > >> >> different
> > >> >> >>>>> problem.
> > >> >> >>>>>
> > >> >> >>>>> The idea is to simplify testing of other downstream project
> > >> against
> > >> >> the
> > >> >> >>>>> current master without the need to publish local forks of BK
> to
> > >> >> local maven
> > >> >> >>>>> repositories.
> > >> >> >>>>> For all downstream open source projects this will be very
> > useful
> > >> >> >>>>>
> > >> >> >>>>> I volunteer to setup the jenkins job and deal with infra
> > >> >> >>>>>
> > >> >> >>>>
> > >> >> >>>> +1 on this.
> > >> >> >>>>
> > >> >> >>>>>
> > >> >> >>>>> >
> > >> >> >>>>> >
> > >> >> >>>>> > Thoughts?
> > >> >> >>>>> >
> > >> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> > >> >> jujjuri@gmail.com>
> > >> >> >>>>> > wrote:
> > >> >> >>>>> >
> > >> >> >>>>> > +1
> > >> >> >>>>> >
> > >> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> > >> >> matteo.merli@gmail.com>
> > >> >> >>>>> > wrote:
> > >> >> >>>>> >
> > >> >> >>>>> > > +1
> > >> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> > >> >> eolivelli@gmail.com>
> > >> >> >>>>> > > wrote:
> > >> >> >>>>> > >
> > >> >> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
> > >> >> binaries on
> > >> >> >>>>> > > > Maven Central.
> > >> >> >>>>> > > >
> > >> >> >>>>> > > > This will help projects which want to try the upcoming
> > >> version
> > >> >> >>>>> without
> > >> >> >>>>> > > > dealing with custom local Maven Repositories.
> > >> >> >>>>> > > >
> > >> >> >>>>> > > > I see recently Apache Tomcat started doing so
> > >> >> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> > >> >> >>>>> > > >
> > >> >> >>>>> > > >
> > >> >> >>>>> > > > I you all agree I would like to work on this.
> > >> >> >>>>> > > >
> > >> >> >>>>> > > >
> > >> >> >>>>> > > > -- Enrico
> > >> >> >>>>> > > >
> > >> >> >>>>> > >
> > >> >> >>>>> >
> > >> >> >>>>> >
> > >> >> >>>>> >
> > >> >> >>>>> > --
> > >> >> >>>>> > Jvrao
> > >> >> >>>>> > ---
> > >> >> >>>>> > First they ignore you, then they laugh at you, then they
> > fight
> > >> >> you, then
> > >> >> >>>>> > you win. - Mahatma Gandhi
> > >> >> >>>>> >
> > >> >> >>>>> --
> > >> >> >>>>>
> > >> >> >>>>>
> > >> >> >>>>> -- Enrico Olivelli
> > >> >> >>>>>
> > >> >>
> > >>
> >
> --
>
>
> -- Enrico Olivelli
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
I apologize, did you have time to check the wiki?
Thanks
Enrico
Il mar 16 mag 2017, 16:16 Enrico Olivelli <eo...@gmail.com> ha scritto:
> 2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > Gotcha. Let me check the wiki. (I am currently traveling.) I will try to
> > get this ready for you when I have a better access to internet.
> >
>
> Did you have time to check this activity ?
>
> Thanks
>
> -- Enrico
>
> > - Sijie
> >
> > On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <eo...@gmail.com>
> wrote:
> >
> >> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> >> > Enrico,
> >> >
> >> > Let me check it out. But I think you can apply for permissions to
> access
> >> > apache jenkins. Probably an INFRA ticket?
> >> >
> >>
> >>
> >> I'm sorry I cannot edit the configuration.
> >>
> >> According to this guide
> >> https://wiki.apache.org/general/Jenkins
> >> you (only the PMC chair) can give me access to job administration by
> >> adding my id to the "hudson-jobadmin" group.
> >> My Apache ID is 'eolivelli'.
> >>
> >>
> >> Thank you
> >> -- Enrico
> >>
> >>
> >>
> >>
> >> > - Sijie
> >> >
> >> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <eo...@gmail.com>
> >> wrote:
> >> >
> >> >> The PR has been merged, so now any committer can publish all the
> >> >> artifacts to the Apache snapshots repo
> >> >> just issuing from the cmd line:
> >> >> mvn clean deploy -DskipTests -Pdeploy
> >> >>
> >> >> I would like to try to add the 'deploy' goal to our daily build on
> >> jenkins
> >> >> On the users@infra list they told me that it would be enough to add
> >> >> the deploy goal and all is already 'ready' (deploy credentials and
> PGP
> >> >> I think)
> >> >> I think I do no have enough permissions to modify the configuration
> of
> >> the
> >> >> Job
> >> >> so Sijie can you try ?
> >> >>
> >> >> note:
> >> >> the "official" guide (1) tells to use a special maven profile to
> >> >> deploy the artifacts (-Papache-release), but for us it is failing
> >> >> because it tries to create the javadocs for the 'compat' deps.
> >> >> IMHO our custom 'deploy' profile will be enough
> >> >>
> >> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
> >> >>
> >> >> -- Enrico
> >> >>
> >> >>
> >> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> >> >> > I am currently discussing on the users@infra mailing list about
> how
> >> to
> >> >> > achieve our goal.
> >> >> > While playing with the deploy goal I succeeded in publishing the
> >> >> > -SNAPSHOT version to the official apache snapshots repository
> >> >> >
> >> >> > In order to achieve it manually it is enough to follow the guide
> >> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
> >> >> >
> >> >> > Actually the goal for us is
> >> >> > mvn clean install -Pdeploy
> >> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the
> apache
> >> >> > snapshots repository automatically (as written in the Apache Parent
> >> >> > pom)
> >> >> >
> >> >> > But currently we have an issue on the versioning scheme of the
> >> >> > "compats" subproject, so that the 'deploy' goal against the
> snapshots
> >> >> > repository cannot be performed.
> >> >> >
> >> >> > This is our JIRA ticket
> >> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> >> >> >
> >> >> > This is the PR
> >> >> > https://github.com/apache/bookkeeper/pull/134
> >> >> >
> >> >> > This is our first public SNAPSHOT
> >> >> > https://repository.apache.org/content/repositories/
> >> snapshots/org/apache/
> >> >> bookkeeper/
> >> >> >
> >> >> > I need any committer to check and merge the PR in order to continue
> >> the
> >> >> work.
> >> >> >
> >> >> > Once we have a compliant versioning scheme a think we can continue
> the
> >> >> > discussion with the infra team in order to add an automatic
> deployment
> >> >> > on our Jenkins builds
> >> >> >
> >> >> > Notes:
> >> >> > 1) It seems that only one snapshot is retained and this is OK
> >> >> > 2) We will need to update the docs and write somewhere how to use
> the
> >> >> > snapshots repository (just an example and a simple explanation).
> Maybe
> >> >> > just on Confluence (I will do)
> >> >> > 3) Currently I have published the snapshot of the current master,
> but
> >> >> > I have used my Apache PGP key (eolivelli@apache.org) but it is not
> >> >> > signed by any other person on the Apache Web Of Trust (I need to
> find
> >> >> > some Apache fellow to sign my key, and it is not so simple in
> Italy).
> >> >> > I think this is not good. Maybe once the pom is OK and the
> procedure
> >> >> > is OK it will be better that some other committer with a signed PGP
> >> >> > key will publish a new version of the snapshot (maybe Sijie or
> Matteo
> >> >> > which were the last release managers)
> >> >> >
> >> >> >
> >> >> > -- Enrico
> >> >> >
> >> >> >
> >> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> >> >> >> I will start inspecting the possibilities with the INFRA team
> >> >> >>
> >> >> >> I will come back to the list with some proposal
> >> >> >>
> >> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans
> <evans@yahoo-inc.com.invalid
> >> >:
> >> >> >>> There is a special SNAPSHOTS repo that is already setup. I know
> >> that
> >> >> hadoop has been using it for a while, so you should just need to ask
> >> where
> >> >> the snapshot repo is. Maven also will only push a -SNAPSHOT build
> to a
> >> >> repo that has been confiugred to accept snapshots.
> >> >> >>>
> >> >> >>>
> >> >> >>> - Bobby
> >> >> >>>
> >> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
> >> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
> >> >> guosijie@gmail.com>:
> >> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> >> >> eolivelli@gmail.com>
> >> >> >>>> wrote:
> >> >> >>>>
> >> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha
> >> scritto:
> >> >> >>>>>
> >> >> >>>>> > I don't have any objections on doing this, if we can figure
> out
> >> >> >>>>> following:
> >> >> >>>>> >
> >> >> >>>>> > - does Apache infra allow doing this?
> >> >> >>>>> >
> >> >> >>>>>
> >> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask
> Mark.
> >> >> >>>>>
> >> >> >>>>
> >> >> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or
> >> >> SNAPSHOT
> >> >> >>>> with gitsha suffix.
> >> >> >>>>
> >> >> >>>> The reason I asked this -
> >> >> >>>>
> >> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the
> packages
> >> >> every
> >> >> >>>> time?
> >> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases
> >> >> within a
> >> >> >>>> big release?
> >> >> >>>>
> >> >> >>>
> >> >> >>> I think we can ask infra help to setup an auto-clean up of the
> >> >> >>> repository, usually -SNASHOT is deployed with a timestamp suffix
> of
> >> >> >>> whatever
> >> >> >>>
> >> >> >>> If you are OK a can contact infra in order to ask for help and
> ask
> >> if
> >> >> >>> is feasible
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>>
> >> >> >>>>>
> >> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want to
> >> >> publish?
> >> >> >>>>> >
> >> >> >>>>> Only the last successful build on jenkins
> >> >> >>>>>
> >> >> >>>>> - why not shorten the release scope and publish a release
> instead?
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> I really would like to have a release ASAP but I think this is
> a
> >> >> different
> >> >> >>>>> problem.
> >> >> >>>>>
> >> >> >>>>> The idea is to simplify testing of other downstream project
> >> against
> >> >> the
> >> >> >>>>> current master without the need to publish local forks of BK to
> >> >> local maven
> >> >> >>>>> repositories.
> >> >> >>>>> For all downstream open source projects this will be very
> useful
> >> >> >>>>>
> >> >> >>>>> I volunteer to setup the jenkins job and deal with infra
> >> >> >>>>>
> >> >> >>>>
> >> >> >>>> +1 on this.
> >> >> >>>>
> >> >> >>>>>
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> > Thoughts?
> >> >> >>>>> >
> >> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> >> >> jujjuri@gmail.com>
> >> >> >>>>> > wrote:
> >> >> >>>>> >
> >> >> >>>>> > +1
> >> >> >>>>> >
> >> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> >> >> matteo.merli@gmail.com>
> >> >> >>>>> > wrote:
> >> >> >>>>> >
> >> >> >>>>> > > +1
> >> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> >> >> eolivelli@gmail.com>
> >> >> >>>>> > > wrote:
> >> >> >>>>> > >
> >> >> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
> >> >> binaries on
> >> >> >>>>> > > > Maven Central.
> >> >> >>>>> > > >
> >> >> >>>>> > > > This will help projects which want to try the upcoming
> >> version
> >> >> >>>>> without
> >> >> >>>>> > > > dealing with custom local Maven Repositories.
> >> >> >>>>> > > >
> >> >> >>>>> > > > I see recently Apache Tomcat started doing so
> >> >> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> >> >> >>>>> > > >
> >> >> >>>>> > > >
> >> >> >>>>> > > > I you all agree I would like to work on this.
> >> >> >>>>> > > >
> >> >> >>>>> > > >
> >> >> >>>>> > > > -- Enrico
> >> >> >>>>> > > >
> >> >> >>>>> > >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> >
> >> >> >>>>> > --
> >> >> >>>>> > Jvrao
> >> >> >>>>> > ---
> >> >> >>>>> > First they ignore you, then they laugh at you, then they
> fight
> >> >> you, then
> >> >> >>>>> > you win. - Mahatma Gandhi
> >> >> >>>>> >
> >> >> >>>>> --
> >> >> >>>>>
> >> >> >>>>>
> >> >> >>>>> -- Enrico Olivelli
> >> >> >>>>>
> >> >>
> >>
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
2017-05-03 11:23 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> Gotcha. Let me check the wiki. (I am currently traveling.) I will try to
> get this ready for you when I have a better access to internet.
>
Did you have time to check this activity ?
Thanks
-- Enrico
> - Sijie
>
> On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <eo...@gmail.com> wrote:
>
>> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>> > Enrico,
>> >
>> > Let me check it out. But I think you can apply for permissions to access
>> > apache jenkins. Probably an INFRA ticket?
>> >
>>
>>
>> I'm sorry I cannot edit the configuration.
>>
>> According to this guide
>> https://wiki.apache.org/general/Jenkins
>> you (only the PMC chair) can give me access to job administration by
>> adding my id to the "hudson-jobadmin" group.
>> My Apache ID is 'eolivelli'.
>>
>>
>> Thank you
>> -- Enrico
>>
>>
>>
>>
>> > - Sijie
>> >
>> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <eo...@gmail.com>
>> wrote:
>> >
>> >> The PR has been merged, so now any committer can publish all the
>> >> artifacts to the Apache snapshots repo
>> >> just issuing from the cmd line:
>> >> mvn clean deploy -DskipTests -Pdeploy
>> >>
>> >> I would like to try to add the 'deploy' goal to our daily build on
>> jenkins
>> >> On the users@infra list they told me that it would be enough to add
>> >> the deploy goal and all is already 'ready' (deploy credentials and PGP
>> >> I think)
>> >> I think I do no have enough permissions to modify the configuration of
>> the
>> >> Job
>> >> so Sijie can you try ?
>> >>
>> >> note:
>> >> the "official" guide (1) tells to use a special maven profile to
>> >> deploy the artifacts (-Papache-release), but for us it is failing
>> >> because it tries to create the javadocs for the 'compat' deps.
>> >> IMHO our custom 'deploy' profile will be enough
>> >>
>> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
>> >>
>> >> -- Enrico
>> >>
>> >>
>> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> >> > I am currently discussing on the users@infra mailing list about how
>> to
>> >> > achieve our goal.
>> >> > While playing with the deploy goal I succeeded in publishing the
>> >> > -SNAPSHOT version to the official apache snapshots repository
>> >> >
>> >> > In order to achieve it manually it is enough to follow the guide
>> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
>> >> >
>> >> > Actually the goal for us is
>> >> > mvn clean install -Pdeploy
>> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the apache
>> >> > snapshots repository automatically (as written in the Apache Parent
>> >> > pom)
>> >> >
>> >> > But currently we have an issue on the versioning scheme of the
>> >> > "compats" subproject, so that the 'deploy' goal against the snapshots
>> >> > repository cannot be performed.
>> >> >
>> >> > This is our JIRA ticket
>> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
>> >> >
>> >> > This is the PR
>> >> > https://github.com/apache/bookkeeper/pull/134
>> >> >
>> >> > This is our first public SNAPSHOT
>> >> > https://repository.apache.org/content/repositories/
>> snapshots/org/apache/
>> >> bookkeeper/
>> >> >
>> >> > I need any committer to check and merge the PR in order to continue
>> the
>> >> work.
>> >> >
>> >> > Once we have a compliant versioning scheme a think we can continue the
>> >> > discussion with the infra team in order to add an automatic deployment
>> >> > on our Jenkins builds
>> >> >
>> >> > Notes:
>> >> > 1) It seems that only one snapshot is retained and this is OK
>> >> > 2) We will need to update the docs and write somewhere how to use the
>> >> > snapshots repository (just an example and a simple explanation). Maybe
>> >> > just on Confluence (I will do)
>> >> > 3) Currently I have published the snapshot of the current master, but
>> >> > I have used my Apache PGP key (eolivelli@apache.org) but it is not
>> >> > signed by any other person on the Apache Web Of Trust (I need to find
>> >> > some Apache fellow to sign my key, and it is not so simple in Italy).
>> >> > I think this is not good. Maybe once the pom is OK and the procedure
>> >> > is OK it will be better that some other committer with a signed PGP
>> >> > key will publish a new version of the snapshot (maybe Sijie or Matteo
>> >> > which were the last release managers)
>> >> >
>> >> >
>> >> > -- Enrico
>> >> >
>> >> >
>> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> >> >> I will start inspecting the possibilities with the INFRA team
>> >> >>
>> >> >> I will come back to the list with some proposal
>> >> >>
>> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans <evans@yahoo-inc.com.invalid
>> >:
>> >> >>> There is a special SNAPSHOTS repo that is already setup. I know
>> that
>> >> hadoop has been using it for a while, so you should just need to ask
>> where
>> >> the snapshot repo is. Maven also will only push a -SNAPSHOT build to a
>> >> repo that has been confiugred to accept snapshots.
>> >> >>>
>> >> >>>
>> >> >>> - Bobby
>> >> >>>
>> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
>> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
>> >> guosijie@gmail.com>:
>> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
>> >> eolivelli@gmail.com>
>> >> >>>> wrote:
>> >> >>>>
>> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha
>> scritto:
>> >> >>>>>
>> >> >>>>> > I don't have any objections on doing this, if we can figure out
>> >> >>>>> following:
>> >> >>>>> >
>> >> >>>>> > - does Apache infra allow doing this?
>> >> >>>>> >
>> >> >>>>>
>> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>> >> >>>>>
>> >> >>>>
>> >> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or
>> >> SNAPSHOT
>> >> >>>> with gitsha suffix.
>> >> >>>>
>> >> >>>> The reason I asked this -
>> >> >>>>
>> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the packages
>> >> every
>> >> >>>> time?
>> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases
>> >> within a
>> >> >>>> big release?
>> >> >>>>
>> >> >>>
>> >> >>> I think we can ask infra help to setup an auto-clean up of the
>> >> >>> repository, usually -SNASHOT is deployed with a timestamp suffix of
>> >> >>> whatever
>> >> >>>
>> >> >>> If you are OK a can contact infra in order to ask for help and ask
>> if
>> >> >>> is feasible
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>>
>> >> >>>>>
>> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want to
>> >> publish?
>> >> >>>>> >
>> >> >>>>> Only the last successful build on jenkins
>> >> >>>>>
>> >> >>>>> - why not shorten the release scope and publish a release instead?
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> I really would like to have a release ASAP but I think this is a
>> >> different
>> >> >>>>> problem.
>> >> >>>>>
>> >> >>>>> The idea is to simplify testing of other downstream project
>> against
>> >> the
>> >> >>>>> current master without the need to publish local forks of BK to
>> >> local maven
>> >> >>>>> repositories.
>> >> >>>>> For all downstream open source projects this will be very useful
>> >> >>>>>
>> >> >>>>> I volunteer to setup the jenkins job and deal with infra
>> >> >>>>>
>> >> >>>>
>> >> >>>> +1 on this.
>> >> >>>>
>> >> >>>>>
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > Thoughts?
>> >> >>>>> >
>> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
>> >> jujjuri@gmail.com>
>> >> >>>>> > wrote:
>> >> >>>>> >
>> >> >>>>> > +1
>> >> >>>>> >
>> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
>> >> matteo.merli@gmail.com>
>> >> >>>>> > wrote:
>> >> >>>>> >
>> >> >>>>> > > +1
>> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
>> >> eolivelli@gmail.com>
>> >> >>>>> > > wrote:
>> >> >>>>> > >
>> >> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
>> >> binaries on
>> >> >>>>> > > > Maven Central.
>> >> >>>>> > > >
>> >> >>>>> > > > This will help projects which want to try the upcoming
>> version
>> >> >>>>> without
>> >> >>>>> > > > dealing with custom local Maven Repositories.
>> >> >>>>> > > >
>> >> >>>>> > > > I see recently Apache Tomcat started doing so
>> >> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> >> >>>>> > > >
>> >> >>>>> > > >
>> >> >>>>> > > > I you all agree I would like to work on this.
>> >> >>>>> > > >
>> >> >>>>> > > >
>> >> >>>>> > > > -- Enrico
>> >> >>>>> > > >
>> >> >>>>> > >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> >
>> >> >>>>> > --
>> >> >>>>> > Jvrao
>> >> >>>>> > ---
>> >> >>>>> > First they ignore you, then they laugh at you, then they fight
>> >> you, then
>> >> >>>>> > you win. - Mahatma Gandhi
>> >> >>>>> >
>> >> >>>>> --
>> >> >>>>>
>> >> >>>>>
>> >> >>>>> -- Enrico Olivelli
>> >> >>>>>
>> >>
>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
Gotcha. Let me check the wiki. (I am currently traveling.) I will try to
get this ready for you when I have a better access to internet.
- Sijie
On Tue, May 2, 2017 at 8:48 PM, Enrico Olivelli <eo...@gmail.com> wrote:
> 2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> > Enrico,
> >
> > Let me check it out. But I think you can apply for permissions to access
> > apache jenkins. Probably an INFRA ticket?
> >
>
>
> I'm sorry I cannot edit the configuration.
>
> According to this guide
> https://wiki.apache.org/general/Jenkins
> you (only the PMC chair) can give me access to job administration by
> adding my id to the "hudson-jobadmin" group.
> My Apache ID is 'eolivelli'.
>
>
> Thank you
> -- Enrico
>
>
>
>
> > - Sijie
> >
> > On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <eo...@gmail.com>
> wrote:
> >
> >> The PR has been merged, so now any committer can publish all the
> >> artifacts to the Apache snapshots repo
> >> just issuing from the cmd line:
> >> mvn clean deploy -DskipTests -Pdeploy
> >>
> >> I would like to try to add the 'deploy' goal to our daily build on
> jenkins
> >> On the users@infra list they told me that it would be enough to add
> >> the deploy goal and all is already 'ready' (deploy credentials and PGP
> >> I think)
> >> I think I do no have enough permissions to modify the configuration of
> the
> >> Job
> >> so Sijie can you try ?
> >>
> >> note:
> >> the "official" guide (1) tells to use a special maven profile to
> >> deploy the artifacts (-Papache-release), but for us it is failing
> >> because it tries to create the javadocs for the 'compat' deps.
> >> IMHO our custom 'deploy' profile will be enough
> >>
> >> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
> >>
> >> -- Enrico
> >>
> >>
> >> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> >> > I am currently discussing on the users@infra mailing list about how
> to
> >> > achieve our goal.
> >> > While playing with the deploy goal I succeeded in publishing the
> >> > -SNAPSHOT version to the official apache snapshots repository
> >> >
> >> > In order to achieve it manually it is enough to follow the guide
> >> > http://www.apache.org/dev/publishing-maven-artifacts.html
> >> >
> >> > Actually the goal for us is
> >> > mvn clean install -Pdeploy
> >> > as we have a "-SNAPSHOT" version the deploy is targeted to the apache
> >> > snapshots repository automatically (as written in the Apache Parent
> >> > pom)
> >> >
> >> > But currently we have an issue on the versioning scheme of the
> >> > "compats" subproject, so that the 'deploy' goal against the snapshots
> >> > repository cannot be performed.
> >> >
> >> > This is our JIRA ticket
> >> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> >> >
> >> > This is the PR
> >> > https://github.com/apache/bookkeeper/pull/134
> >> >
> >> > This is our first public SNAPSHOT
> >> > https://repository.apache.org/content/repositories/
> snapshots/org/apache/
> >> bookkeeper/
> >> >
> >> > I need any committer to check and merge the PR in order to continue
> the
> >> work.
> >> >
> >> > Once we have a compliant versioning scheme a think we can continue the
> >> > discussion with the infra team in order to add an automatic deployment
> >> > on our Jenkins builds
> >> >
> >> > Notes:
> >> > 1) It seems that only one snapshot is retained and this is OK
> >> > 2) We will need to update the docs and write somewhere how to use the
> >> > snapshots repository (just an example and a simple explanation). Maybe
> >> > just on Confluence (I will do)
> >> > 3) Currently I have published the snapshot of the current master, but
> >> > I have used my Apache PGP key (eolivelli@apache.org) but it is not
> >> > signed by any other person on the Apache Web Of Trust (I need to find
> >> > some Apache fellow to sign my key, and it is not so simple in Italy).
> >> > I think this is not good. Maybe once the pom is OK and the procedure
> >> > is OK it will be better that some other committer with a signed PGP
> >> > key will publish a new version of the snapshot (maybe Sijie or Matteo
> >> > which were the last release managers)
> >> >
> >> >
> >> > -- Enrico
> >> >
> >> >
> >> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> >> >> I will start inspecting the possibilities with the INFRA team
> >> >>
> >> >> I will come back to the list with some proposal
> >> >>
> >> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans <evans@yahoo-inc.com.invalid
> >:
> >> >>> There is a special SNAPSHOTS repo that is already setup. I know
> that
> >> hadoop has been using it for a while, so you should just need to ask
> where
> >> the snapshot repo is. Maven also will only push a -SNAPSHOT build to a
> >> repo that has been confiugred to accept snapshots.
> >> >>>
> >> >>>
> >> >>> - Bobby
> >> >>>
> >> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
> >> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
> >> guosijie@gmail.com>:
> >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> >> eolivelli@gmail.com>
> >> >>>> wrote:
> >> >>>>
> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha
> scritto:
> >> >>>>>
> >> >>>>> > I don't have any objections on doing this, if we can figure out
> >> >>>>> following:
> >> >>>>> >
> >> >>>>> > - does Apache infra allow doing this?
> >> >>>>> >
> >> >>>>>
> >> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
> >> >>>>>
> >> >>>>
> >> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or
> >> SNAPSHOT
> >> >>>> with gitsha suffix.
> >> >>>>
> >> >>>> The reason I asked this -
> >> >>>>
> >> >>>> - If we just use SNAPSHOT, does the CI job overwrite the packages
> >> every
> >> >>>> time?
> >> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases
> >> within a
> >> >>>> big release?
> >> >>>>
> >> >>>
> >> >>> I think we can ask infra help to setup an auto-clean up of the
> >> >>> repository, usually -SNASHOT is deployed with a timestamp suffix of
> >> >>> whatever
> >> >>>
> >> >>> If you are OK a can contact infra in order to ask for help and ask
> if
> >> >>> is feasible
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>>>
> >> >>>>>
> >> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want to
> >> publish?
> >> >>>>> >
> >> >>>>> Only the last successful build on jenkins
> >> >>>>>
> >> >>>>> - why not shorten the release scope and publish a release instead?
> >> >>>>>
> >> >>>>>
> >> >>>>> I really would like to have a release ASAP but I think this is a
> >> different
> >> >>>>> problem.
> >> >>>>>
> >> >>>>> The idea is to simplify testing of other downstream project
> against
> >> the
> >> >>>>> current master without the need to publish local forks of BK to
> >> local maven
> >> >>>>> repositories.
> >> >>>>> For all downstream open source projects this will be very useful
> >> >>>>>
> >> >>>>> I volunteer to setup the jenkins job and deal with infra
> >> >>>>>
> >> >>>>
> >> >>>> +1 on this.
> >> >>>>
> >> >>>>>
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > Thoughts?
> >> >>>>> >
> >> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> >> jujjuri@gmail.com>
> >> >>>>> > wrote:
> >> >>>>> >
> >> >>>>> > +1
> >> >>>>> >
> >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> >> matteo.merli@gmail.com>
> >> >>>>> > wrote:
> >> >>>>> >
> >> >>>>> > > +1
> >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> >> eolivelli@gmail.com>
> >> >>>>> > > wrote:
> >> >>>>> > >
> >> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
> >> binaries on
> >> >>>>> > > > Maven Central.
> >> >>>>> > > >
> >> >>>>> > > > This will help projects which want to try the upcoming
> version
> >> >>>>> without
> >> >>>>> > > > dealing with custom local Maven Repositories.
> >> >>>>> > > >
> >> >>>>> > > > I see recently Apache Tomcat started doing so
> >> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> >> >>>>> > > >
> >> >>>>> > > >
> >> >>>>> > > > I you all agree I would like to work on this.
> >> >>>>> > > >
> >> >>>>> > > >
> >> >>>>> > > > -- Enrico
> >> >>>>> > > >
> >> >>>>> > >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> >
> >> >>>>> > --
> >> >>>>> > Jvrao
> >> >>>>> > ---
> >> >>>>> > First they ignore you, then they laugh at you, then they fight
> >> you, then
> >> >>>>> > you win. - Mahatma Gandhi
> >> >>>>> >
> >> >>>>> --
> >> >>>>>
> >> >>>>>
> >> >>>>> -- Enrico Olivelli
> >> >>>>>
> >>
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
2017-05-02 3:27 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> Enrico,
>
> Let me check it out. But I think you can apply for permissions to access
> apache jenkins. Probably an INFRA ticket?
>
I'm sorry I cannot edit the configuration.
According to this guide
https://wiki.apache.org/general/Jenkins
you (only the PMC chair) can give me access to job administration by
adding my id to the "hudson-jobadmin" group.
My Apache ID is 'eolivelli'.
Thank you
-- Enrico
> - Sijie
>
> On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <eo...@gmail.com> wrote:
>
>> The PR has been merged, so now any committer can publish all the
>> artifacts to the Apache snapshots repo
>> just issuing from the cmd line:
>> mvn clean deploy -DskipTests -Pdeploy
>>
>> I would like to try to add the 'deploy' goal to our daily build on jenkins
>> On the users@infra list they told me that it would be enough to add
>> the deploy goal and all is already 'ready' (deploy credentials and PGP
>> I think)
>> I think I do no have enough permissions to modify the configuration of the
>> Job
>> so Sijie can you try ?
>>
>> note:
>> the "official" guide (1) tells to use a special maven profile to
>> deploy the artifacts (-Papache-release), but for us it is failing
>> because it tries to create the javadocs for the 'compat' deps.
>> IMHO our custom 'deploy' profile will be enough
>>
>> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> -- Enrico
>>
>>
>> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> > I am currently discussing on the users@infra mailing list about how to
>> > achieve our goal.
>> > While playing with the deploy goal I succeeded in publishing the
>> > -SNAPSHOT version to the official apache snapshots repository
>> >
>> > In order to achieve it manually it is enough to follow the guide
>> > http://www.apache.org/dev/publishing-maven-artifacts.html
>> >
>> > Actually the goal for us is
>> > mvn clean install -Pdeploy
>> > as we have a "-SNAPSHOT" version the deploy is targeted to the apache
>> > snapshots repository automatically (as written in the Apache Parent
>> > pom)
>> >
>> > But currently we have an issue on the versioning scheme of the
>> > "compats" subproject, so that the 'deploy' goal against the snapshots
>> > repository cannot be performed.
>> >
>> > This is our JIRA ticket
>> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
>> >
>> > This is the PR
>> > https://github.com/apache/bookkeeper/pull/134
>> >
>> > This is our first public SNAPSHOT
>> > https://repository.apache.org/content/repositories/snapshots/org/apache/
>> bookkeeper/
>> >
>> > I need any committer to check and merge the PR in order to continue the
>> work.
>> >
>> > Once we have a compliant versioning scheme a think we can continue the
>> > discussion with the infra team in order to add an automatic deployment
>> > on our Jenkins builds
>> >
>> > Notes:
>> > 1) It seems that only one snapshot is retained and this is OK
>> > 2) We will need to update the docs and write somewhere how to use the
>> > snapshots repository (just an example and a simple explanation). Maybe
>> > just on Confluence (I will do)
>> > 3) Currently I have published the snapshot of the current master, but
>> > I have used my Apache PGP key (eolivelli@apache.org) but it is not
>> > signed by any other person on the Apache Web Of Trust (I need to find
>> > some Apache fellow to sign my key, and it is not so simple in Italy).
>> > I think this is not good. Maybe once the pom is OK and the procedure
>> > is OK it will be better that some other committer with a signed PGP
>> > key will publish a new version of the snapshot (maybe Sijie or Matteo
>> > which were the last release managers)
>> >
>> >
>> > -- Enrico
>> >
>> >
>> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> >> I will start inspecting the possibilities with the INFRA team
>> >>
>> >> I will come back to the list with some proposal
>> >>
>> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
>> >>> There is a special SNAPSHOTS repo that is already setup. I know that
>> hadoop has been using it for a while, so you should just need to ask where
>> the snapshot repo is. Maven also will only push a -SNAPSHOT build to a
>> repo that has been confiugred to accept snapshots.
>> >>>
>> >>>
>> >>> - Bobby
>> >>>
>> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
>> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
>> guosijie@gmail.com>:
>> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
>> eolivelli@gmail.com>
>> >>>> wrote:
>> >>>>
>> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>> >>>>>
>> >>>>> > I don't have any objections on doing this, if we can figure out
>> >>>>> following:
>> >>>>> >
>> >>>>> > - does Apache infra allow doing this?
>> >>>>> >
>> >>>>>
>> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>> >>>>>
>> >>>>
>> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or
>> SNAPSHOT
>> >>>> with gitsha suffix.
>> >>>>
>> >>>> The reason I asked this -
>> >>>>
>> >>>> - If we just use SNAPSHOT, does the CI job overwrite the packages
>> every
>> >>>> time?
>> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases
>> within a
>> >>>> big release?
>> >>>>
>> >>>
>> >>> I think we can ask infra help to setup an auto-clean up of the
>> >>> repository, usually -SNASHOT is deployed with a timestamp suffix of
>> >>> whatever
>> >>>
>> >>> If you are OK a can contact infra in order to ask for help and ask if
>> >>> is feasible
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>>
>> >>>>>
>> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want to
>> publish?
>> >>>>> >
>> >>>>> Only the last successful build on jenkins
>> >>>>>
>> >>>>> - why not shorten the release scope and publish a release instead?
>> >>>>>
>> >>>>>
>> >>>>> I really would like to have a release ASAP but I think this is a
>> different
>> >>>>> problem.
>> >>>>>
>> >>>>> The idea is to simplify testing of other downstream project against
>> the
>> >>>>> current master without the need to publish local forks of BK to
>> local maven
>> >>>>> repositories.
>> >>>>> For all downstream open source projects this will be very useful
>> >>>>>
>> >>>>> I volunteer to setup the jenkins job and deal with infra
>> >>>>>
>> >>>>
>> >>>> +1 on this.
>> >>>>
>> >>>>>
>> >>>>> >
>> >>>>> >
>> >>>>> > Thoughts?
>> >>>>> >
>> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
>> jujjuri@gmail.com>
>> >>>>> > wrote:
>> >>>>> >
>> >>>>> > +1
>> >>>>> >
>> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
>> matteo.merli@gmail.com>
>> >>>>> > wrote:
>> >>>>> >
>> >>>>> > > +1
>> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
>> eolivelli@gmail.com>
>> >>>>> > > wrote:
>> >>>>> > >
>> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
>> binaries on
>> >>>>> > > > Maven Central.
>> >>>>> > > >
>> >>>>> > > > This will help projects which want to try the upcoming version
>> >>>>> without
>> >>>>> > > > dealing with custom local Maven Repositories.
>> >>>>> > > >
>> >>>>> > > > I see recently Apache Tomcat started doing so
>> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> >>>>> > > >
>> >>>>> > > >
>> >>>>> > > > I you all agree I would like to work on this.
>> >>>>> > > >
>> >>>>> > > >
>> >>>>> > > > -- Enrico
>> >>>>> > > >
>> >>>>> > >
>> >>>>> >
>> >>>>> >
>> >>>>> >
>> >>>>> > --
>> >>>>> > Jvrao
>> >>>>> > ---
>> >>>>> > First they ignore you, then they laugh at you, then they fight
>> you, then
>> >>>>> > you win. - Mahatma Gandhi
>> >>>>> >
>> >>>>> --
>> >>>>>
>> >>>>>
>> >>>>> -- Enrico Olivelli
>> >>>>>
>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
Enrico,
Let me check it out. But I think you can apply for permissions to access
apache jenkins. Probably an INFRA ticket?
- Sijie
On Mon, May 1, 2017 at 1:07 PM, Enrico Olivelli <eo...@gmail.com> wrote:
> The PR has been merged, so now any committer can publish all the
> artifacts to the Apache snapshots repo
> just issuing from the cmd line:
> mvn clean deploy -DskipTests -Pdeploy
>
> I would like to try to add the 'deploy' goal to our daily build on jenkins
> On the users@infra list they told me that it would be enough to add
> the deploy goal and all is already 'ready' (deploy credentials and PGP
> I think)
> I think I do no have enough permissions to modify the configuration of the
> Job
> so Sijie can you try ?
>
> note:
> the "official" guide (1) tells to use a special maven profile to
> deploy the artifacts (-Papache-release), but for us it is failing
> because it tries to create the javadocs for the 'compat' deps.
> IMHO our custom 'deploy' profile will be enough
>
> 1 - http://www.apache.org/dev/publishing-maven-artifacts.html
>
> -- Enrico
>
>
> 2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> > I am currently discussing on the users@infra mailing list about how to
> > achieve our goal.
> > While playing with the deploy goal I succeeded in publishing the
> > -SNAPSHOT version to the official apache snapshots repository
> >
> > In order to achieve it manually it is enough to follow the guide
> > http://www.apache.org/dev/publishing-maven-artifacts.html
> >
> > Actually the goal for us is
> > mvn clean install -Pdeploy
> > as we have a "-SNAPSHOT" version the deploy is targeted to the apache
> > snapshots repository automatically (as written in the Apache Parent
> > pom)
> >
> > But currently we have an issue on the versioning scheme of the
> > "compats" subproject, so that the 'deploy' goal against the snapshots
> > repository cannot be performed.
> >
> > This is our JIRA ticket
> > https://issues.apache.org/jira/browse/BOOKKEEPER-1042
> >
> > This is the PR
> > https://github.com/apache/bookkeeper/pull/134
> >
> > This is our first public SNAPSHOT
> > https://repository.apache.org/content/repositories/snapshots/org/apache/
> bookkeeper/
> >
> > I need any committer to check and merge the PR in order to continue the
> work.
> >
> > Once we have a compliant versioning scheme a think we can continue the
> > discussion with the infra team in order to add an automatic deployment
> > on our Jenkins builds
> >
> > Notes:
> > 1) It seems that only one snapshot is retained and this is OK
> > 2) We will need to update the docs and write somewhere how to use the
> > snapshots repository (just an example and a simple explanation). Maybe
> > just on Confluence (I will do)
> > 3) Currently I have published the snapshot of the current master, but
> > I have used my Apache PGP key (eolivelli@apache.org) but it is not
> > signed by any other person on the Apache Web Of Trust (I need to find
> > some Apache fellow to sign my key, and it is not so simple in Italy).
> > I think this is not good. Maybe once the pom is OK and the procedure
> > is OK it will be better that some other committer with a signed PGP
> > key will publish a new version of the snapshot (maybe Sijie or Matteo
> > which were the last release managers)
> >
> >
> > -- Enrico
> >
> >
> > 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> >> I will start inspecting the possibilities with the INFRA team
> >>
> >> I will come back to the list with some proposal
> >>
> >> 2017-04-27 15:31 GMT+02:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
> >>> There is a special SNAPSHOTS repo that is already setup. I know that
> hadoop has been using it for a while, so you should just need to ask where
> the snapshot repo is. Maven also will only push a -SNAPSHOT build to a
> repo that has been confiugred to accept snapshots.
> >>>
> >>>
> >>> - Bobby
> >>>
> >>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <
> eolivelli@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <
> guosijie@gmail.com>:
> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <
> eolivelli@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
> >>>>>
> >>>>> > I don't have any objections on doing this, if we can figure out
> >>>>> following:
> >>>>> >
> >>>>> > - does Apache infra allow doing this?
> >>>>> >
> >>>>>
> >>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
> >>>>>
> >>>>
> >>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or
> SNAPSHOT
> >>>> with gitsha suffix.
> >>>>
> >>>> The reason I asked this -
> >>>>
> >>>> - If we just use SNAPSHOT, does the CI job overwrite the packages
> every
> >>>> time?
> >>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases
> within a
> >>>> big release?
> >>>>
> >>>
> >>> I think we can ask infra help to setup an auto-clean up of the
> >>> repository, usually -SNASHOT is deployed with a timestamp suffix of
> >>> whatever
> >>>
> >>> If you are OK a can contact infra in order to ask for help and ask if
> >>> is feasible
> >>>
> >>>
> >>>
> >>>
> >>>>
> >>>>>
> >>>>> > - what does SNAPSHOT mean? How many snapshots do you want to
> publish?
> >>>>> >
> >>>>> Only the last successful build on jenkins
> >>>>>
> >>>>> - why not shorten the release scope and publish a release instead?
> >>>>>
> >>>>>
> >>>>> I really would like to have a release ASAP but I think this is a
> different
> >>>>> problem.
> >>>>>
> >>>>> The idea is to simplify testing of other downstream project against
> the
> >>>>> current master without the need to publish local forks of BK to
> local maven
> >>>>> repositories.
> >>>>> For all downstream open source projects this will be very useful
> >>>>>
> >>>>> I volunteer to setup the jenkins job and deal with infra
> >>>>>
> >>>>
> >>>> +1 on this.
> >>>>
> >>>>>
> >>>>> >
> >>>>> >
> >>>>> > Thoughts?
> >>>>> >
> >>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <
> jujjuri@gmail.com>
> >>>>> > wrote:
> >>>>> >
> >>>>> > +1
> >>>>> >
> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <
> matteo.merli@gmail.com>
> >>>>> > wrote:
> >>>>> >
> >>>>> > > +1
> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <
> eolivelli@gmail.com>
> >>>>> > > wrote:
> >>>>> > >
> >>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT
> binaries on
> >>>>> > > > Maven Central.
> >>>>> > > >
> >>>>> > > > This will help projects which want to try the upcoming version
> >>>>> without
> >>>>> > > > dealing with custom local Maven Repositories.
> >>>>> > > >
> >>>>> > > > I see recently Apache Tomcat started doing so
> >>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > I you all agree I would like to work on this.
> >>>>> > > >
> >>>>> > > >
> >>>>> > > > -- Enrico
> >>>>> > > >
> >>>>> > >
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > Jvrao
> >>>>> > ---
> >>>>> > First they ignore you, then they laugh at you, then they fight
> you, then
> >>>>> > you win. - Mahatma Gandhi
> >>>>> >
> >>>>> --
> >>>>>
> >>>>>
> >>>>> -- Enrico Olivelli
> >>>>>
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
The PR has been merged, so now any committer can publish all the
artifacts to the Apache snapshots repo
just issuing from the cmd line:
mvn clean deploy -DskipTests -Pdeploy
I would like to try to add the 'deploy' goal to our daily build on jenkins
On the users@infra list they told me that it would be enough to add
the deploy goal and all is already 'ready' (deploy credentials and PGP
I think)
I think I do no have enough permissions to modify the configuration of the Job
so Sijie can you try ?
note:
the "official" guide (1) tells to use a special maven profile to
deploy the artifacts (-Papache-release), but for us it is failing
because it tries to create the javadocs for the 'compat' deps.
IMHO our custom 'deploy' profile will be enough
1 - http://www.apache.org/dev/publishing-maven-artifacts.html
-- Enrico
2017-04-28 12:43 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> I am currently discussing on the users@infra mailing list about how to
> achieve our goal.
> While playing with the deploy goal I succeeded in publishing the
> -SNAPSHOT version to the official apache snapshots repository
>
> In order to achieve it manually it is enough to follow the guide
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> Actually the goal for us is
> mvn clean install -Pdeploy
> as we have a "-SNAPSHOT" version the deploy is targeted to the apache
> snapshots repository automatically (as written in the Apache Parent
> pom)
>
> But currently we have an issue on the versioning scheme of the
> "compats" subproject, so that the 'deploy' goal against the snapshots
> repository cannot be performed.
>
> This is our JIRA ticket
> https://issues.apache.org/jira/browse/BOOKKEEPER-1042
>
> This is the PR
> https://github.com/apache/bookkeeper/pull/134
>
> This is our first public SNAPSHOT
> https://repository.apache.org/content/repositories/snapshots/org/apache/bookkeeper/
>
> I need any committer to check and merge the PR in order to continue the work.
>
> Once we have a compliant versioning scheme a think we can continue the
> discussion with the infra team in order to add an automatic deployment
> on our Jenkins builds
>
> Notes:
> 1) It seems that only one snapshot is retained and this is OK
> 2) We will need to update the docs and write somewhere how to use the
> snapshots repository (just an example and a simple explanation). Maybe
> just on Confluence (I will do)
> 3) Currently I have published the snapshot of the current master, but
> I have used my Apache PGP key (eolivelli@apache.org) but it is not
> signed by any other person on the Apache Web Of Trust (I need to find
> some Apache fellow to sign my key, and it is not so simple in Italy).
> I think this is not good. Maybe once the pom is OK and the procedure
> is OK it will be better that some other committer with a signed PGP
> key will publish a new version of the snapshot (maybe Sijie or Matteo
> which were the last release managers)
>
>
> -- Enrico
>
>
> 2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
>> I will start inspecting the possibilities with the INFRA team
>>
>> I will come back to the list with some proposal
>>
>> 2017-04-27 15:31 GMT+02:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
>>> There is a special SNAPSHOTS repo that is already setup. I know that hadoop has been using it for a while, so you should just need to ask where the snapshot repo is. Maven also will only push a -SNAPSHOT build to a repo that has been confiugred to accept snapshots.
>>>
>>>
>>> - Bobby
>>>
>>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <eo...@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
>>>> wrote:
>>>>
>>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>>>>>
>>>>> > I don't have any objections on doing this, if we can figure out
>>>>> following:
>>>>> >
>>>>> > - does Apache infra allow doing this?
>>>>> >
>>>>>
>>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>>>>>
>>>>
>>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
>>>> with gitsha suffix.
>>>>
>>>> The reason I asked this -
>>>>
>>>> - If we just use SNAPSHOT, does the CI job overwrite the packages every
>>>> time?
>>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
>>>> big release?
>>>>
>>>
>>> I think we can ask infra help to setup an auto-clean up of the
>>> repository, usually -SNASHOT is deployed with a timestamp suffix of
>>> whatever
>>>
>>> If you are OK a can contact infra in order to ask for help and ask if
>>> is feasible
>>>
>>>
>>>
>>>
>>>>
>>>>>
>>>>> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
>>>>> >
>>>>> Only the last successful build on jenkins
>>>>>
>>>>> - why not shorten the release scope and publish a release instead?
>>>>>
>>>>>
>>>>> I really would like to have a release ASAP but I think this is a different
>>>>> problem.
>>>>>
>>>>> The idea is to simplify testing of other downstream project against the
>>>>> current master without the need to publish local forks of BK to local maven
>>>>> repositories.
>>>>> For all downstream open source projects this will be very useful
>>>>>
>>>>> I volunteer to setup the jenkins job and deal with infra
>>>>>
>>>>
>>>> +1 on this.
>>>>
>>>>>
>>>>> >
>>>>> >
>>>>> > Thoughts?
>>>>> >
>>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> > +1
>>>>> >
>>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>>>>> > wrote:
>>>>> >
>>>>> > > +1
>>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>>>>> > > wrote:
>>>>> > >
>>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>>>>> > > > Maven Central.
>>>>> > > >
>>>>> > > > This will help projects which want to try the upcoming version
>>>>> without
>>>>> > > > dealing with custom local Maven Repositories.
>>>>> > > >
>>>>> > > > I see recently Apache Tomcat started doing so
>>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>>>>> > > >
>>>>> > > >
>>>>> > > > I you all agree I would like to work on this.
>>>>> > > >
>>>>> > > >
>>>>> > > > -- Enrico
>>>>> > > >
>>>>> > >
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Jvrao
>>>>> > ---
>>>>> > First they ignore you, then they laugh at you, then they fight you, then
>>>>> > you win. - Mahatma Gandhi
>>>>> >
>>>>> --
>>>>>
>>>>>
>>>>> -- Enrico Olivelli
>>>>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
I am currently discussing on the users@infra mailing list about how to
achieve our goal.
While playing with the deploy goal I succeeded in publishing the
-SNAPSHOT version to the official apache snapshots repository
In order to achieve it manually it is enough to follow the guide
http://www.apache.org/dev/publishing-maven-artifacts.html
Actually the goal for us is
mvn clean install -Pdeploy
as we have a "-SNAPSHOT" version the deploy is targeted to the apache
snapshots repository automatically (as written in the Apache Parent
pom)
But currently we have an issue on the versioning scheme of the
"compats" subproject, so that the 'deploy' goal against the snapshots
repository cannot be performed.
This is our JIRA ticket
https://issues.apache.org/jira/browse/BOOKKEEPER-1042
This is the PR
https://github.com/apache/bookkeeper/pull/134
This is our first public SNAPSHOT
https://repository.apache.org/content/repositories/snapshots/org/apache/bookkeeper/
I need any committer to check and merge the PR in order to continue the work.
Once we have a compliant versioning scheme a think we can continue the
discussion with the infra team in order to add an automatic deployment
on our Jenkins builds
Notes:
1) It seems that only one snapshot is retained and this is OK
2) We will need to update the docs and write somewhere how to use the
snapshots repository (just an example and a simple explanation). Maybe
just on Confluence (I will do)
3) Currently I have published the snapshot of the current master, but
I have used my Apache PGP key (eolivelli@apache.org) but it is not
signed by any other person on the Apache Web Of Trust (I need to find
some Apache fellow to sign my key, and it is not so simple in Italy).
I think this is not good. Maybe once the pom is OK and the procedure
is OK it will be better that some other committer with a signed PGP
key will publish a new version of the snapshot (maybe Sijie or Matteo
which were the last release managers)
-- Enrico
2017-04-27 16:51 GMT+02:00 Enrico Olivelli <eo...@gmail.com>:
> I will start inspecting the possibilities with the INFRA team
>
> I will come back to the list with some proposal
>
> 2017-04-27 15:31 GMT+02:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
>> There is a special SNAPSHOTS repo that is already setup. I know that hadoop has been using it for a while, so you should just need to ask where the snapshot repo is. Maven also will only push a -SNAPSHOT build to a repo that has been confiugred to accept snapshots.
>>
>>
>> - Bobby
>>
>> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <eo...@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
>>> wrote:
>>>
>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>>>>
>>>> > I don't have any objections on doing this, if we can figure out
>>>> following:
>>>> >
>>>> > - does Apache infra allow doing this?
>>>> >
>>>>
>>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>>>>
>>>
>>> How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
>>> with gitsha suffix.
>>>
>>> The reason I asked this -
>>>
>>> - If we just use SNAPSHOT, does the CI job overwrite the packages every
>>> time?
>>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
>>> big release?
>>>
>>
>> I think we can ask infra help to setup an auto-clean up of the
>> repository, usually -SNASHOT is deployed with a timestamp suffix of
>> whatever
>>
>> If you are OK a can contact infra in order to ask for help and ask if
>> is feasible
>>
>>
>>
>>
>>>
>>>>
>>>> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
>>>> >
>>>> Only the last successful build on jenkins
>>>>
>>>> - why not shorten the release scope and publish a release instead?
>>>>
>>>>
>>>> I really would like to have a release ASAP but I think this is a different
>>>> problem.
>>>>
>>>> The idea is to simplify testing of other downstream project against the
>>>> current master without the need to publish local forks of BK to local maven
>>>> repositories.
>>>> For all downstream open source projects this will be very useful
>>>>
>>>> I volunteer to setup the jenkins job and deal with infra
>>>>
>>>
>>> +1 on this.
>>>
>>>>
>>>> >
>>>> >
>>>> > Thoughts?
>>>> >
>>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>>>> > wrote:
>>>> >
>>>> > +1
>>>> >
>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>>>> > wrote:
>>>> >
>>>> > > +1
>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>>>> > > wrote:
>>>> > >
>>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>>>> > > > Maven Central.
>>>> > > >
>>>> > > > This will help projects which want to try the upcoming version
>>>> without
>>>> > > > dealing with custom local Maven Repositories.
>>>> > > >
>>>> > > > I see recently Apache Tomcat started doing so
>>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>>>> > > >
>>>> > > >
>>>> > > > I you all agree I would like to work on this.
>>>> > > >
>>>> > > >
>>>> > > > -- Enrico
>>>> > > >
>>>> > >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > Jvrao
>>>> > ---
>>>> > First they ignore you, then they laugh at you, then they fight you, then
>>>> > you win. - Mahatma Gandhi
>>>> >
>>>> --
>>>>
>>>>
>>>> -- Enrico Olivelli
>>>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
I will start inspecting the possibilities with the INFRA team
I will come back to the list with some proposal
2017-04-27 15:31 GMT+02:00 Bobby Evans <ev...@yahoo-inc.com.invalid>:
> There is a special SNAPSHOTS repo that is already setup. I know that hadoop has been using it for a while, so you should just need to ask where the snapshot repo is. Maven also will only push a -SNAPSHOT build to a repo that has been confiugred to accept snapshots.
>
>
> - Bobby
>
> On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <eo...@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <gu...@gmail.com>:
>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
>> wrote:
>>
>>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>>>
>>> > I don't have any objections on doing this, if we can figure out
>>> following:
>>> >
>>> > - does Apache infra allow doing this?
>>> >
>>>
>>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>>>
>>
>> How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
>> with gitsha suffix.
>>
>> The reason I asked this -
>>
>> - If we just use SNAPSHOT, does the CI job overwrite the packages every
>> time?
>> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
>> big release?
>>
>
> I think we can ask infra help to setup an auto-clean up of the
> repository, usually -SNASHOT is deployed with a timestamp suffix of
> whatever
>
> If you are OK a can contact infra in order to ask for help and ask if
> is feasible
>
>
>
>
>>
>>>
>>> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
>>> >
>>> Only the last successful build on jenkins
>>>
>>> - why not shorten the release scope and publish a release instead?
>>>
>>>
>>> I really would like to have a release ASAP but I think this is a different
>>> problem.
>>>
>>> The idea is to simplify testing of other downstream project against the
>>> current master without the need to publish local forks of BK to local maven
>>> repositories.
>>> For all downstream open source projects this will be very useful
>>>
>>> I volunteer to setup the jenkins job and deal with infra
>>>
>>
>> +1 on this.
>>
>>>
>>> >
>>> >
>>> > Thoughts?
>>> >
>>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>>> > wrote:
>>> >
>>> > +1
>>> >
>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>>> > wrote:
>>> >
>>> > > +1
>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>>> > > wrote:
>>> > >
>>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>>> > > > Maven Central.
>>> > > >
>>> > > > This will help projects which want to try the upcoming version
>>> without
>>> > > > dealing with custom local Maven Repositories.
>>> > > >
>>> > > > I see recently Apache Tomcat started doing so
>>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>>> > > >
>>> > > >
>>> > > > I you all agree I would like to work on this.
>>> > > >
>>> > > >
>>> > > > -- Enrico
>>> > > >
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Jvrao
>>> > ---
>>> > First they ignore you, then they laugh at you, then they fight you, then
>>> > you win. - Mahatma Gandhi
>>> >
>>> --
>>>
>>>
>>> -- Enrico Olivelli
>>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Bobby Evans <ev...@yahoo-inc.com.INVALID>.
There is a special SNAPSHOTS repo that is already setup. I know that hadoop has been using it for a while, so you should just need to ask where the snapshot repo is. Maven also will only push a -SNAPSHOT build to a repo that has been confiugred to accept snapshots.
- Bobby
On Thursday, April 27, 2017, 7:57:31 AM CDT, Enrico Olivelli <eo...@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
> wrote:
>
>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>>
>> > I don't have any objections on doing this, if we can figure out
>> following:
>> >
>> > - does Apache infra allow doing this?
>> >
>>
>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>>
>
> How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
> with gitsha suffix.
>
> The reason I asked this -
>
> - If we just use SNAPSHOT, does the CI job overwrite the packages every
> time?
> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
> big release?
>
I think we can ask infra help to setup an auto-clean up of the
repository, usually -SNASHOT is deployed with a timestamp suffix of
whatever
If you are OK a can contact infra in order to ask for help and ask if
is feasible
>
>>
>> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
>> >
>> Only the last successful build on jenkins
>>
>> - why not shorten the release scope and publish a release instead?
>>
>>
>> I really would like to have a release ASAP but I think this is a different
>> problem.
>>
>> The idea is to simplify testing of other downstream project against the
>> current master without the need to publish local forks of BK to local maven
>> repositories.
>> For all downstream open source projects this will be very useful
>>
>> I volunteer to setup the jenkins job and deal with infra
>>
>
> +1 on this.
>
>>
>> >
>> >
>> > Thoughts?
>> >
>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>> > wrote:
>> >
>> > +1
>> >
>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>> > wrote:
>> >
>> > > +1
>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>> > > wrote:
>> > >
>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>> > > > Maven Central.
>> > > >
>> > > > This will help projects which want to try the upcoming version
>> without
>> > > > dealing with custom local Maven Repositories.
>> > > >
>> > > > I see recently Apache Tomcat started doing so
>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> > > >
>> > > >
>> > > > I you all agree I would like to work on this.
>> > > >
>> > > >
>> > > > -- Enrico
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Jvrao
>> > ---
>> > First they ignore you, then they laugh at you, then they fight you, then
>> > you win. - Mahatma Gandhi
>> >
>> --
>>
>>
>> -- Enrico Olivelli
>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
2017-04-24 23:35 GMT+02:00 Sijie Guo <gu...@gmail.com>:
> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
> wrote:
>
>> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>>
>> > I don't have any objections on doing this, if we can figure out
>> following:
>> >
>> > - does Apache infra allow doing this?
>> >
>>
>> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>>
>
> How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
> with gitsha suffix.
>
> The reason I asked this -
>
> - If we just use SNAPSHOT, does the CI job overwrite the packages every
> time?
> - If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
> big release?
>
I think we can ask infra help to setup an auto-clean up of the
repository, usually -SNASHOT is deployed with a timestamp suffix of
whatever
If you are OK a can contact infra in order to ask for help and ask if
is feasible
>
>>
>> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
>> >
>> Only the last successful build on jenkins
>>
>> - why not shorten the release scope and publish a release instead?
>>
>>
>> I really would like to have a release ASAP but I think this is a different
>> problem.
>>
>> The idea is to simplify testing of other downstream project against the
>> current master without the need to publish local forks of BK to local maven
>> repositories.
>> For all downstream open source projects this will be very useful
>>
>> I volunteer to setup the jenkins job and deal with infra
>>
>
> +1 on this.
>
>>
>> >
>> >
>> > Thoughts?
>> >
>> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>> > wrote:
>> >
>> > +1
>> >
>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>> > wrote:
>> >
>> > > +1
>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>> > > wrote:
>> > >
>> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>> > > > Maven Central.
>> > > >
>> > > > This will help projects which want to try the upcoming version
>> without
>> > > > dealing with custom local Maven Repositories.
>> > > >
>> > > > I see recently Apache Tomcat started doing so
>> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> > > >
>> > > >
>> > > > I you all agree I would like to work on this.
>> > > >
>> > > >
>> > > > -- Enrico
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Jvrao
>> > ---
>> > First they ignore you, then they laugh at you, then they fight you, then
>> > you win. - Mahatma Gandhi
>> >
>> --
>>
>>
>> -- Enrico Olivelli
>>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli <eo...@gmail.com>
wrote:
> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>
> > I don't have any objections on doing this, if we can figure out
> following:
> >
> > - does Apache infra allow doing this?
> >
>
> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>
How does the SNAPSHOT version look like? is it just SNAPSHOT or SNAPSHOT
with gitsha suffix.
The reason I asked this -
- If we just use SNAPSHOT, does the CI job overwrite the packages every
time?
- If we use SNAPSHOT-gitsha, then can we do smaller RC releases within a
big release?
>
> > - what does SNAPSHOT mean? How many snapshots do you want to publish?
> >
> Only the last successful build on jenkins
>
> - why not shorten the release scope and publish a release instead?
>
>
> I really would like to have a release ASAP but I think this is a different
> problem.
>
> The idea is to simplify testing of other downstream project against the
> current master without the need to publish local forks of BK to local maven
> repositories.
> For all downstream open source projects this will be very useful
>
> I volunteer to setup the jenkins job and deal with infra
>
+1 on this.
>
> >
> >
> > Thoughts?
> >
> > On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
> > wrote:
> >
> > +1
> >
> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
> > wrote:
> >
> > > +1
> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
> > > wrote:
> > >
> > > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> > > > Maven Central.
> > > >
> > > > This will help projects which want to try the upcoming version
> without
> > > > dealing with custom local Maven Repositories.
> > > >
> > > > I see recently Apache Tomcat started doing so
> > > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> > > >
> > > >
> > > > I you all agree I would like to work on this.
> > > >
> > > >
> > > > -- Enrico
> > > >
> > >
> >
> >
> >
> > --
> > Jvrao
> > ---
> > First they ignore you, then they laugh at you, then they fight you, then
> > you win. - Mahatma Gandhi
> >
> --
>
>
> -- Enrico Olivelli
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 22 apr 2017, 12:21 Enrico Olivelli <eo...@gmail.com> ha scritto:
>
>
> Il sab 22 apr 2017, 12:10 Ivan Kelly <iv...@apache.org> ha scritto:
>
>> > Now we have a nightly job. We can make it deploy the artifacts in case
>> of
>> > full success.
>> > I think that adding the 'deploy' goal to the config of the job will do
>> the
>> > trick
>> > Like
>> > Mvn clean deploy
>> Does it not need some credentials configured to be able to push to nexus?
>>
>
>
> Yes I think so. We need to ask infra.
> If I can (as I am only committer) I will pick up this issue and talk to
> infra team.
>
> For manual deploy I think that only personal credentials will be enough.
> But I will start working on this only when we are all ok on how to
> achieve: manual vs automatic
>
> I will create a JIRA to track this work today
>
Here it is
https://issues.apache.org/jira/browse/BOOKKEEPER-1042
>
>
>>
>> -Ivan
>>
> --
>
>
> -- Enrico Olivelli
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 22 apr 2017, 12:10 Ivan Kelly <iv...@apache.org> ha scritto:
> > Now we have a nightly job. We can make it deploy the artifacts in case of
> > full success.
> > I think that adding the 'deploy' goal to the config of the job will do
> the
> > trick
> > Like
> > Mvn clean deploy
> Does it not need some credentials configured to be able to push to nexus?
>
Yes I think so. We need to ask infra.
If I can (as I am only committer) I will pick up this issue and talk to
infra team.
For manual deploy I think that only personal credentials will be enough.
But I will start working on this only when we are all ok on how to achieve:
manual vs automatic
I will create a JIRA to track this work today
>
> -Ivan
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Ivan Kelly <iv...@apache.org>.
> Now we have a nightly job. We can make it deploy the artifacts in case of
> full success.
> I think that adding the 'deploy' goal to the config of the job will do the
> trick
> Like
> Mvn clean deploy
Does it not need some credentials configured to be able to push to nexus?
-Ivan
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 22 apr 2017, 11:43 Ivan Kelly <iv...@apache.org> ha scritto:
> > I volunteer to setup the jenkins job and deal with infra
> Is there already a nightly job? I remember in the past there was only
> a precommit job. It would be good to have a nightly job so that flakes
> can be easily tracked. It's hard to do this with a precommit, as the
> failures may be in the patch that's being tested.
>
Now we have a nightly job. We can make it deploy the artifacts in case of
full success.
I think that adding the 'deploy' goal to the config of the job will do the
trick
Like
Mvn clean deploy
> I'd also recommend using jenkins job builder [1] for the job setup.
> This way the job specification can be pushed to the bookkeeper repo.
>
> -Ivan
>
>
> [1] https://docs.openstack.org/infra/jenkins-job-builder/
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Just for.completeness I have found this
https://github.com/jenkinsci/job-dsl-plugin
It is a language for describing jobs
But It requires a plugin.
I prefer openstack jobs builder
Enrico
Il mer 21 giu 2017, 14:28 Jia Zhai <zh...@gmail.com> ha scritto:
> FYI. Here is the wiki page from INFRA Jenkins:
> https://cwiki.apache.org/confluence/display/INFRA/Jenkins
>
> On Wed, Jun 21, 2017 at 5:49 PM, Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > 2017-06-06 9:28 GMT+02:00 Flavio Junqueira <fp...@apache.org>:
> > > I have used Jenkins extensively, but not the job builder you're
> > referring to, which I think is this one:
> > >
> > > https://docs.openstack.org/infra/jenkins-job-builder/ <
> > https://docs.openstack.org/infra/jenkins-job-builder/>
> > >
> > > I like Travis too, but it is indeed more limited as Sijie says. If all
> > you need is to run nightly and PR builds, then Travis will do it just
> fine.
> > >
> > > -Flavio
> > >
> > >> On 05 Jun 2017, at 15:31, Enrico Olivelli <eo...@gmail.com>
> wrote:
> > >>
> > >> I took a look at jenkins job builder, it seems a great tool.
> > >> Two points before getting started:
> > >> 1) do anyone ever used this tool or something like that?
> > >> 2) it needs calling the API and it is possible to delete all jenkins
> > jobs
> > >> with a single command, surely there will be some kind of permissions
> to
> > be
> > >> set on jenkins side, but maybe we should ask to infra team if there is
> > >> already some other user of such tool in ASF
> > >>
> > >> Travis looks really more simple from this point of view at first
> glance
> > >>
> > >> Enrico
> > >>
> > >> Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha
> > scritto:
> > >>
> > >>>
> > >>>
> > >>> Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
> > >>>
> > >>>> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org>
> wrote:
> > >>>>
> > >>>>>> I volunteer to setup the jenkins job and deal with infra
> > >>>>> Is there already a nightly job? I remember in the past there was
> only
> > >>>>> a precommit job. It would be good to have a nightly job so that
> > flakes
> > >>>>> can be easily tracked. It's hard to do this with a precommit, as
> the
> > >>>>> failures may be in the patch that's being tested.
> > >>>>>
> > >>>>> I'd also recommend using jenkins job builder [1] for the job setup.
> > >>>>> This way the job specification can be pushed to the bookkeeper
> repo.
> > >>>>>
> > >>>>
> > >>>> I actually liked the idea to also have the job specification in
> > bookkeeper
> > >>>> repo. So we also manages the job specification changes in same
> review
> > >>>> process. anyone is interested in exploring this?
> > >>>>
> > >>>
> > >>> Sure I will try
> >
> > This is the issue
> > https://github.com/apache/bookkeeper/issues/196
> >
> > I have started working at it with my collegue Nicolò Boschi
> > we are going to submit a first proof-of-concept configuration file
> >
> > >>>
> > >>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>
> > >>>>>
> > >>>>> -Ivan
> > >>>>>
> > >>>>>
> > >>>>> [1] https://docs.openstack.org/infra/jenkins-job-builder/
> > >>>>>
> > >>>>
> > >>> --
> > >>>
> > >>>
> > >>> -- Enrico Olivelli
> > >>>
> > >> --
> > >>
> > >>
> > >> -- Enrico Olivelli
> > >
> >
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Jia Zhai <zh...@gmail.com>.
FYI. Here is the wiki page from INFRA Jenkins:
https://cwiki.apache.org/confluence/display/INFRA/Jenkins
On Wed, Jun 21, 2017 at 5:49 PM, Enrico Olivelli <eo...@gmail.com>
wrote:
> 2017-06-06 9:28 GMT+02:00 Flavio Junqueira <fp...@apache.org>:
> > I have used Jenkins extensively, but not the job builder you're
> referring to, which I think is this one:
> >
> > https://docs.openstack.org/infra/jenkins-job-builder/ <
> https://docs.openstack.org/infra/jenkins-job-builder/>
> >
> > I like Travis too, but it is indeed more limited as Sijie says. If all
> you need is to run nightly and PR builds, then Travis will do it just fine.
> >
> > -Flavio
> >
> >> On 05 Jun 2017, at 15:31, Enrico Olivelli <eo...@gmail.com> wrote:
> >>
> >> I took a look at jenkins job builder, it seems a great tool.
> >> Two points before getting started:
> >> 1) do anyone ever used this tool or something like that?
> >> 2) it needs calling the API and it is possible to delete all jenkins
> jobs
> >> with a single command, surely there will be some kind of permissions to
> be
> >> set on jenkins side, but maybe we should ask to infra team if there is
> >> already some other user of such tool in ASF
> >>
> >> Travis looks really more simple from this point of view at first glance
> >>
> >> Enrico
> >>
> >> Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha
> scritto:
> >>
> >>>
> >>>
> >>> Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
> >>>
> >>>> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
> >>>>
> >>>>>> I volunteer to setup the jenkins job and deal with infra
> >>>>> Is there already a nightly job? I remember in the past there was only
> >>>>> a precommit job. It would be good to have a nightly job so that
> flakes
> >>>>> can be easily tracked. It's hard to do this with a precommit, as the
> >>>>> failures may be in the patch that's being tested.
> >>>>>
> >>>>> I'd also recommend using jenkins job builder [1] for the job setup.
> >>>>> This way the job specification can be pushed to the bookkeeper repo.
> >>>>>
> >>>>
> >>>> I actually liked the idea to also have the job specification in
> bookkeeper
> >>>> repo. So we also manages the job specification changes in same review
> >>>> process. anyone is interested in exploring this?
> >>>>
> >>>
> >>> Sure I will try
>
> This is the issue
> https://github.com/apache/bookkeeper/issues/196
>
> I have started working at it with my collegue Nicolò Boschi
> we are going to submit a first proof-of-concept configuration file
>
> >>>
> >>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>
> >>>>> -Ivan
> >>>>>
> >>>>>
> >>>>> [1] https://docs.openstack.org/infra/jenkins-job-builder/
> >>>>>
> >>>>
> >>> --
> >>>
> >>>
> >>> -- Enrico Olivelli
> >>>
> >> --
> >>
> >>
> >> -- Enrico Olivelli
> >
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
2017-06-06 9:28 GMT+02:00 Flavio Junqueira <fp...@apache.org>:
> I have used Jenkins extensively, but not the job builder you're referring to, which I think is this one:
>
> https://docs.openstack.org/infra/jenkins-job-builder/ <https://docs.openstack.org/infra/jenkins-job-builder/>
>
> I like Travis too, but it is indeed more limited as Sijie says. If all you need is to run nightly and PR builds, then Travis will do it just fine.
>
> -Flavio
>
>> On 05 Jun 2017, at 15:31, Enrico Olivelli <eo...@gmail.com> wrote:
>>
>> I took a look at jenkins job builder, it seems a great tool.
>> Two points before getting started:
>> 1) do anyone ever used this tool or something like that?
>> 2) it needs calling the API and it is possible to delete all jenkins jobs
>> with a single command, surely there will be some kind of permissions to be
>> set on jenkins side, but maybe we should ask to infra team if there is
>> already some other user of such tool in ASF
>>
>> Travis looks really more simple from this point of view at first glance
>>
>> Enrico
>>
>> Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha scritto:
>>
>>>
>>>
>>> Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
>>>
>>>> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
>>>>
>>>>>> I volunteer to setup the jenkins job and deal with infra
>>>>> Is there already a nightly job? I remember in the past there was only
>>>>> a precommit job. It would be good to have a nightly job so that flakes
>>>>> can be easily tracked. It's hard to do this with a precommit, as the
>>>>> failures may be in the patch that's being tested.
>>>>>
>>>>> I'd also recommend using jenkins job builder [1] for the job setup.
>>>>> This way the job specification can be pushed to the bookkeeper repo.
>>>>>
>>>>
>>>> I actually liked the idea to also have the job specification in bookkeeper
>>>> repo. So we also manages the job specification changes in same review
>>>> process. anyone is interested in exploring this?
>>>>
>>>
>>> Sure I will try
This is the issue
https://github.com/apache/bookkeeper/issues/196
I have started working at it with my collegue Nicolò Boschi
we are going to submit a first proof-of-concept configuration file
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> -Ivan
>>>>>
>>>>>
>>>>> [1] https://docs.openstack.org/infra/jenkins-job-builder/
>>>>>
>>>>
>>> --
>>>
>>>
>>> -- Enrico Olivelli
>>>
>> --
>>
>>
>> -- Enrico Olivelli
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Flavio Junqueira <fp...@apache.org>.
I have used Jenkins extensively, but not the job builder you're referring to, which I think is this one:
https://docs.openstack.org/infra/jenkins-job-builder/ <https://docs.openstack.org/infra/jenkins-job-builder/>
I like Travis too, but it is indeed more limited as Sijie says. If all you need is to run nightly and PR builds, then Travis will do it just fine.
-Flavio
> On 05 Jun 2017, at 15:31, Enrico Olivelli <eo...@gmail.com> wrote:
>
> I took a look at jenkins job builder, it seems a great tool.
> Two points before getting started:
> 1) do anyone ever used this tool or something like that?
> 2) it needs calling the API and it is possible to delete all jenkins jobs
> with a single command, surely there will be some kind of permissions to be
> set on jenkins side, but maybe we should ask to infra team if there is
> already some other user of such tool in ASF
>
> Travis looks really more simple from this point of view at first glance
>
> Enrico
>
> Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha scritto:
>
>>
>>
>> Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
>>
>>> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
>>>
>>>>> I volunteer to setup the jenkins job and deal with infra
>>>> Is there already a nightly job? I remember in the past there was only
>>>> a precommit job. It would be good to have a nightly job so that flakes
>>>> can be easily tracked. It's hard to do this with a precommit, as the
>>>> failures may be in the patch that's being tested.
>>>>
>>>> I'd also recommend using jenkins job builder [1] for the job setup.
>>>> This way the job specification can be pushed to the bookkeeper repo.
>>>>
>>>
>>> I actually liked the idea to also have the job specification in bookkeeper
>>> repo. So we also manages the job specification changes in same review
>>> process. anyone is interested in exploring this?
>>>
>>
>> Sure I will try
>>
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>>
>>>> -Ivan
>>>>
>>>>
>>>> [1] https://docs.openstack.org/infra/jenkins-job-builder/
>>>>
>>>
>> --
>>
>>
>> -- Enrico Olivelli
>>
> --
>
>
> -- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
I think we will still need Jenkins, because it has more flexibilities than
Travis.
On Mon, Jun 5, 2017 at 6:31 AM, Enrico Olivelli <eo...@gmail.com> wrote:
> I took a look at jenkins job builder, it seems a great tool.
> Two points before getting started:
> 1) do anyone ever used this tool or something like that?
> 2) it needs calling the API and it is possible to delete all jenkins jobs
> with a single command, surely there will be some kind of permissions to be
> set on jenkins side, but maybe we should ask to infra team if there is
> already some other user of such tool in ASF
>
I believe there are projects using this tool. you might just search INFRA
tickets to see if there were related tickets.
>
> Travis looks really more simple from this point of view at first glance
>
> Enrico
>
> Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha scritto:
>
> >
> >
> > Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
> >
> >> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
> >>
> >> > > I volunteer to setup the jenkins job and deal with infra
> >> > Is there already a nightly job? I remember in the past there was only
> >> > a precommit job. It would be good to have a nightly job so that flakes
> >> > can be easily tracked. It's hard to do this with a precommit, as the
> >> > failures may be in the patch that's being tested.
> >> >
> >> > I'd also recommend using jenkins job builder [1] for the job setup.
> >> > This way the job specification can be pushed to the bookkeeper repo.
> >> >
> >>
> >> I actually liked the idea to also have the job specification in
> bookkeeper
> >> repo. So we also manages the job specification changes in same review
> >> process. anyone is interested in exploring this?
> >>
> >
> > Sure I will try
> >
> >
> >>
> >>
> >>
> >>
> >>
> >>
> >> >
> >> > -Ivan
> >> >
> >> >
> >> > [1] https://docs.openstack.org/infra/jenkins-job-builder/
> >> >
> >>
> > --
> >
> >
> > -- Enrico Olivelli
> >
> --
>
>
> -- Enrico Olivelli
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
I took a look at jenkins job builder, it seems a great tool.
Two points before getting started:
1) do anyone ever used this tool or something like that?
2) it needs calling the API and it is possible to delete all jenkins jobs
with a single command, surely there will be some kind of permissions to be
set on jenkins side, but maybe we should ask to infra team if there is
already some other user of such tool in ASF
Travis looks really more simple from this point of view at first glance
Enrico
Il sab 3 giu 2017, 08:38 Enrico Olivelli <eo...@gmail.com> ha scritto:
>
>
> Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
>
>> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
>>
>> > > I volunteer to setup the jenkins job and deal with infra
>> > Is there already a nightly job? I remember in the past there was only
>> > a precommit job. It would be good to have a nightly job so that flakes
>> > can be easily tracked. It's hard to do this with a precommit, as the
>> > failures may be in the patch that's being tested.
>> >
>> > I'd also recommend using jenkins job builder [1] for the job setup.
>> > This way the job specification can be pushed to the bookkeeper repo.
>> >
>>
>> I actually liked the idea to also have the job specification in bookkeeper
>> repo. So we also manages the job specification changes in same review
>> process. anyone is interested in exploring this?
>>
>
> Sure I will try
>
>
>>
>>
>>
>>
>>
>>
>> >
>> > -Ivan
>> >
>> >
>> > [1] https://docs.openstack.org/infra/jenkins-job-builder/
>> >
>>
> --
>
>
> -- Enrico Olivelli
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 3 giu 2017, 02:24 Sijie Guo <gu...@gmail.com> ha scritto:
> On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
>
> > > I volunteer to setup the jenkins job and deal with infra
> > Is there already a nightly job? I remember in the past there was only
> > a precommit job. It would be good to have a nightly job so that flakes
> > can be easily tracked. It's hard to do this with a precommit, as the
> > failures may be in the patch that's being tested.
> >
> > I'd also recommend using jenkins job builder [1] for the job setup.
> > This way the job specification can be pushed to the bookkeeper repo.
> >
>
> I actually liked the idea to also have the job specification in bookkeeper
> repo. So we also manages the job specification changes in same review
> process. anyone is interested in exploring this?
>
Sure I will try
>
>
>
>
>
>
> >
> > -Ivan
> >
> >
> > [1] https://docs.openstack.org/infra/jenkins-job-builder/
> >
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
On Sat, Apr 22, 2017 at 2:43 AM, Ivan Kelly <iv...@apache.org> wrote:
> > I volunteer to setup the jenkins job and deal with infra
> Is there already a nightly job? I remember in the past there was only
> a precommit job. It would be good to have a nightly job so that flakes
> can be easily tracked. It's hard to do this with a precommit, as the
> failures may be in the patch that's being tested.
>
> I'd also recommend using jenkins job builder [1] for the job setup.
> This way the job specification can be pushed to the bookkeeper repo.
>
I actually liked the idea to also have the job specification in bookkeeper
repo. So we also manages the job specification changes in same review
process. anyone is interested in exploring this?
>
> -Ivan
>
>
> [1] https://docs.openstack.org/infra/jenkins-job-builder/
>
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Ivan Kelly <iv...@apache.org>.
> I volunteer to setup the jenkins job and deal with infra
Is there already a nightly job? I remember in the past there was only
a precommit job. It would be good to have a nightly job so that flakes
can be easily tracked. It's hard to do this with a precommit, as the
failures may be in the patch that's being tested.
I'd also recommend using jenkins job builder [1] for the job setup.
This way the job specification can be pushed to the bookkeeper repo.
-Ivan
[1] https://docs.openstack.org/infra/jenkins-job-builder/
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 22 apr 2017, 09:30 Enrico Olivelli <eo...@gmail.com> ha scritto:
>
>
> Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
>
>> I don't have any objections on doing this, if we can figure out following:
>>
>> - does Apache infra allow doing this?
>>
>
> Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
>
>> - what does SNAPSHOT mean? How many snapshots do you want to publish?
>>
> Only the last successful build on jenkins
>
> - why not shorten the release scope and publish a release instead?
>
>
> I really would like to have a release ASAP but I think this is a different
> problem.
>
> The idea is to simplify testing of other downstream project against the
> current master without the need to publish local forks of BK to local maven
> repositories.
> For all downstream open source projects this will be very useful
>
> I volunteer to setup the jenkins job and deal with infra
>
>>
Eventually we can push specific snapshots manually, see
http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> Thoughts?
>>
>> On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
>> wrote:
>>
>> +1
>>
>> On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
>> wrote:
>>
>> > +1
>> > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
>> > wrote:
>> >
>> > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
>> > > Maven Central.
>> > >
>> > > This will help projects which want to try the upcoming version without
>> > > dealing with custom local Maven Repositories.
>> > >
>> > > I see recently Apache Tomcat started doing so
>> > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>> > >
>> > >
>> > > I you all agree I would like to work on this.
>> > >
>> > >
>> > > -- Enrico
>> > >
>> >
>>
>>
>>
>> --
>> Jvrao
>> ---
>> First they ignore you, then they laugh at you, then they fight you, then
>> you win. - Mahatma Gandhi
>>
> --
>
>
> -- Enrico Olivelli
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Enrico Olivelli <eo...@gmail.com>.
Il sab 22 apr 2017, 02:27 Sijie Guo <gu...@gmail.com> ha scritto:
> I don't have any objections on doing this, if we can figure out following:
>
> - does Apache infra allow doing this?
>
Yes. See the lonk from tomcat mailing kist. Maybe we can ask Mark.
> - what does SNAPSHOT mean? How many snapshots do you want to publish?
>
Only the last successful build on jenkins
- why not shorten the release scope and publish a release instead?
I really would like to have a release ASAP but I think this is a different
problem.
The idea is to simplify testing of other downstream project against the
current master without the need to publish local forks of BK to local maven
repositories.
For all downstream open source projects this will be very useful
I volunteer to setup the jenkins job and deal with infra
>
>
> Thoughts?
>
> On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
> wrote:
>
> +1
>
> On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
> wrote:
>
> > +1
> > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
> > wrote:
> >
> > > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> > > Maven Central.
> > >
> > > This will help projects which want to try the upcoming version without
> > > dealing with custom local Maven Repositories.
> > >
> > > I see recently Apache Tomcat started doing so
> > > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> > >
> > >
> > > I you all agree I would like to work on this.
> > >
> > >
> > > -- Enrico
> > >
> >
>
>
>
> --
> Jvrao
> ---
> First they ignore you, then they laugh at you, then they fight you, then
> you win. - Mahatma Gandhi
>
--
-- Enrico Olivelli
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Sijie Guo <gu...@gmail.com>.
I don't have any objections on doing this, if we can figure out following:
- does Apache infra allow doing this?
- what does SNAPSHOT mean? How many snapshots do you want to publish?
- why not shorten the release scope and publish a release instead?
Thoughts?
On Apr 21, 2017 9:29 AM, "Venkateswara Rao Jujjuri" <ju...@gmail.com>
wrote:
+1
On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
wrote:
> +1
> On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> > Maven Central.
> >
> > This will help projects which want to try the upcoming version without
> > dealing with custom local Maven Repositories.
> >
> > I see recently Apache Tomcat started doing so
> > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> >
> >
> > I you all agree I would like to work on this.
> >
> >
> > -- Enrico
> >
>
--
Jvrao
---
First they ignore you, then they laugh at you, then they fight you, then
you win. - Mahatma Gandhi
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Venkateswara Rao Jujjuri <ju...@gmail.com>.
+1
On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli <ma...@gmail.com>
wrote:
> +1
> On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com>
> wrote:
>
> > I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> > Maven Central.
> >
> > This will help projects which want to try the upcoming version without
> > dealing with custom local Maven Repositories.
> >
> > I see recently Apache Tomcat started doing so
> > http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
> >
> >
> > I you all agree I would like to work on this.
> >
> >
> > -- Enrico
> >
>
--
Jvrao
---
First they ignore you, then they laugh at you, then they fight you, then
you win. - Mahatma Gandhi
Re: Publish SNAPSHOT artifacts on Maven Central
Posted by Matteo Merli <ma...@gmail.com>.
+1
On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli <eo...@gmail.com> wrote:
> I wonder if we can start publishing the 4.5.0-SNAPSHOT binaries on
> Maven Central.
>
> This will help projects which want to try the upcoming version without
> dealing with custom local Maven Repositories.
>
> I see recently Apache Tomcat started doing so
> http://marc.info/?l=tomcat-dev&m=149269803006113&w=2
>
>
> I you all agree I would like to work on this.
>
>
> -- Enrico
>