2017-05-02 3:27 GMT+02:00 Sijie Guo <guosi...@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 <eolive...@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 <eolive...@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 (eolive...@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 <eolive...@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 < >> eolive...@gmail.com> wrote:2017-04-24 23:35 GMT+02:00 Sijie Guo < >> guosi...@gmail.com>: >> >>>> On Sat, Apr 22, 2017 at 12:30 AM, Enrico Olivelli < >> eolive...@gmail.com> >> >>>> wrote: >> >>>> >> >>>>> Il sab 22 apr 2017, 02:27 Sijie Guo <guosi...@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" < >> jujj...@gmail.com> >> >>>>> > wrote: >> >>>>> > >> >>>>> > +1 >> >>>>> > >> >>>>> > On Fri, Apr 21, 2017 at 8:16 AM, Matteo Merli < >> matteo.me...@gmail.com> >> >>>>> > wrote: >> >>>>> > >> >>>>> > > +1 >> >>>>> > > On Fri, Apr 21, 2017 at 7:06 AM Enrico Olivelli < >> eolive...@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 >> >>>>> >>
