Looks good to me. I have asked Srimanth to verify from Ambari perspective as well.
On Tue, Jan 20, 2015 at 3:27 PM, Ted Yu <[email protected]> wrote: > I browsed the staging repo - looks good. > > On Tue, Jan 20, 2015 at 6:05 AM, Steve Loughran <[email protected]> > wrote: > > > We have our first repository! > > > > > > > https://repository.apache.org/content/repositories/orgapacheslider-1002/org/apache/slider/ > > > > big zip file is in > > > > > > > https://repository.apache.org/content/repositories/orgapacheslider-1002/org/apache/slider/slider-assembly/0.61.0/ > > > > I couldn't stop the app packages getting in; the sequence of operations > was > > > > export RELARGS="-DskipTests -DskipITs -Papache-release" > > mvn release:clean > > mvn release:prepare -DautoVersionSubmodules=true > -Darguments="$RELARGS" > > -Dresume=false > > mvn release:perform -Darguments="$RELARGS" > > > > If I did -Papache-release in the prepare/perform targets things didn't > > work. > > > > I've wrritten a side-project which does nothing but download slider > > versions from a designated repo, this —when run on a machine/VM whose M2 > > repo isn't contaminated by local builds— It can to verify that all the > core > > slider artifacts and their source files are there., including the .zip > and > > .tar.gz files > > > > https://github.com/steveloughran/slider-dependency-check > > > > Have a look at the staging repo. If people are happy, I'll start the vote > > > > > > On 20 January 2015 at 09:35, Steve Loughran <[email protected]> > > wrote: > > > > > OK, I've got all this done & fixed a race in our build where the > > > agent.tar.gz didn't always make it into the tar file. Our manual build > > > steps got it in, but the mvn release didn't. > > > > > > now it's just that signing > > > > > > On 16 January 2015 at 18:39, Josh Elser <[email protected]> wrote: > > > > > >> Alright, a bit farther: > > >> > > >> With the slider-0.61.0 tag that Steve already made, I ran `mvn > > >> release:clean release:prepare` myself, modified the release.properties > > to > > >> to use "slider-0.61.0" instead of the dummy tag name I provided, and > > then > > >> `mvn release:perform -Darguments="-DskipTests"` to push it up to > > >> https://repository.apache.org/. > > >> > > >> Everyone should be able to see it under the staging repositories > > >> (orgapacheslider-1000), but the "close" on the repository failed > > because it > > >> doesn't have the crypto signature (.asc) included. Not sure if this is > > an > > >> artifact of me half-running the release perform or a sign that > something > > >> else is still wrong with the code :) > > >> > > >> > > >> Josh Elser wrote: > > >> > > >>> Billie caught it (despite me staring at it). > > >>> > > >>> Because we override the repository in distributionManagement, you > need > > >>> to have apache.staging.https defined in ~/.m2/settings.xml with your > > >>> credentials (not just the normal apache.releases.https from > > apache.pom). > > >>> > > >>> I have a release:perform of the tag Steve made (slider-0.61.0) > > currently > > >>> running... > > >>> > > >>> Josh Elser wrote: > > >>> > > >>>> I've been 401'ed as well -- I know my local creds are good because I > > >>>> just deployed a snapshot. > > >>>> > > >>>> [INFO] [ERROR] Failed to execute goal > > >>>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy > > >>>> (default-deploy) > > >>>> on project slider: Failed to deploy artifacts: Could not transfer > > >>>> artifact org.apache.slider:slider:pom:0.61.0 from/to > > >>>> apache.staging.https > > >>>> (https://repository.apache.org/service/local/staging/deploy/maven2 > ): > > >>>> Failed to transfer file: > > >>>> https://repository.apache.org/service/local/staging/deploy/ > > >>>> maven2/org/apache/slider/slider/0.61.0/slider-0.61.0.pom. > > >>>> > > >>>> Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1] > > >>>> > > >>>> Also verified that the information in our pom is correct per the > > >>>> apache.pom [1]. I'll search around a little bit, but I'm kind of > > >>>> perplexed too. > > >>>> > > >>>> - Josh > > >>>> > > >>>> [1] > > http://central.maven.org/maven2/org/apache/apache/14/apache-14.pom > > >>>> > > >>>> Josh Elser wrote: > > >>>> > > >>>>> I'm poking around with trying out your steps this morning. Will > > report > > >>>>> if I get stuck, too. > > >>>>> > > >>>>> Steve Loughran wrote: > > >>>>> > > >>>>>> I have to confess: I can't release using maven to automate the ASF > > >>>>>> artifact > > >>>>>> release process; I'm getting 401/unauthed, even though the > > >>>>>> infrastructure > > >>>>>> team can't see any problems > > >>>>>> > > >>>>>> Can someone else try? > > >>>>>> > > >>>>>> 1. release branch is branches/branch-0.6 ; tag tag-prerelease-0.61 > > >>>>>> being > > >>>>>> what I want to release. > > >>>>>> > > >>>>>> 2. I've documented what I think we are meant to do in: > > >>>>>> > > >>>>>> site/trunk/content/developing/releasing.md > > >>>>>> > > >>>>>> under: Work-in-Progress Automated releases via maven > > >>>>>> > > >>>>>> The release process includes updating the poms and pushing up > > versions > > >>>>>> onto > > >>>>>> the release branch, branches/branch-0.6; to stop the release you > not > > >>>>>> only > > >>>>>> need to do a mvn release:clean, you need to reset the head of the > > >>>>>> branch to > > >>>>>> the tag-prerelease-0.61 commit and force push the change back up. > > >>>>>> > > >>>>>> > > > > > > > -- > > CONFIDENTIALITY NOTICE > > NOTICE: This message is intended for the use of the individual or entity > to > > which it is addressed and may contain information that is confidential, > > privileged and exempt from disclosure under applicable law. If the reader > > of this message is not the intended recipient, you are hereby notified > that > > any printing, copying, dissemination, distribution, disclosure or > > forwarding of this communication is strictly prohibited. If you have > > received this communication in error, please contact the sender > immediately > > and delete it from your system. Thank You. > > > -- thanks Sumit
