Hey all - I did some additional sleuthing and discovered a misspelling in our CI job version - SNAPSTHOT - which might not be accepted by the snapshots repo. I pinged a PMC member to update that string.
In our regular build files SNAPSHOT is spelled correctly; the version is being explicitly set in the CI job config. I don't understand the reason for this and am looking into it. --travis On Tue, Oct 2, 2012 at 2:17 PM, Vinod Kumar Vavilapalli <[email protected]> wrote: > > I vaguely remember that while Hadoop had ant+ivy based builds, pushing to the > snapshots repo failed. > > Can you try apache.staging.https and then promote the repo on Nexus directly? > > Thanks, > +Vinod > > On Oct 2, 2012, at 8:41 AM, Travis Crawford wrote: > >> Hey Olivier - >> >> I worked with a PMC member with permissions to update our CI job, and added >> the ant target that publishes to the Apache snapshots repo. However, there >> was a publishing failure for what I'm guessing is a discrepancy between the >> repo ID we publish to, and the repo ID in settings.xml. >> >> OUR SETTINGS: >> >> mvn.deploy.repo.id=apache.snapshots.https >> mvn.deploy.repo.url= >> https://repository.apache.org/content/repositories/snapshots >> >> WHERE I GOT THE ID FROM: >> >> I got the ID and URL from the Apache parent POM. >> >> https://repository.apache.org/service/local/repositories/releases/content/org/apache/apache/11/apache-11.pom >> >> Can you look at the settings.xml file on the build machines and see what >> repository ID we should reference, so we pick up the correct credentials. >> >> Thanks! >> Travis >> >> >> >> On Mon, Oct 1, 2012 at 9:58 AM, Travis Crawford >> <[email protected]>wrote: >> >>> Ok, I'll ping our PMC folks. Thanks for the info. >>> >>> --travis >>> >>> >>> On Mon, Oct 1, 2012 at 9:42 AM, Olivier Lamy <[email protected]> wrote: >>>> Your pmc members are able to do that. >>>> And as it's an ant build I have no idea about the target for that :-) >>>> >>>> 2012/10/1 Travis Crawford <[email protected]>: >>>>> Hey Olivier - >>>>> >>>>> I don't have permissions to make this change. Can you please either >>>>> make the change on our behalf, or help me learn who has permissions to >>>>> do so? I poked around the CI job page but was not able to determine >>>>> who has permissions to modify it. Any tips on getting in touch with >>>>> the right people to make this change (or permissions changes so we can >>>>> do it ourselves) would be much appreciated. >>>>> >>>>> Thanks! >>>>> Travis >>>>> >>>>> >>>>> On Mon, Oct 1, 2012 at 9:14 AM, Olivier Lamy <[email protected]> wrote: >>>>>> 2012/10/1 Travis Crawford <[email protected]>: >>>>>>> Hi build gurus - >>>>>>> >>>>>>> In HCATALOG-132 we added maven publishing support to our build, and >>>>>>> would like to update our trunk Jenkins job to publish snapshots. >>>>>>> >>>>>>> https://builds.apache.org/job/Hcatalog-trunk-build/ >>>>>>> >>>>>>> From a previous thread the build machines should already have correct >>>>>>> settings.xml files. >>>>>>> >>>>>>> >>> http://mail-archives.apache.org/mod_mbox/www-builds/201208.mbox/%3ccabn7xtbkf2eampterrmj5+wc49vlst66uovjywq4nyqu0qg...@mail.gmail.com%3e >>>>>>> >>>>>>> I believe we just need to add "mvn-deploy" to the end of the current >>>>>>> command (default build properties publish to Apache snapshots repo). >>>>>>> Is this something I can work with y'all on? >>>>>> >>>>>> correct simply mvn-deploy should work. >>>>>> >>>>>>> >>>>>>> Thanks! >>>>>>> Travis >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Olivier Lamy >>>>>> Talend: http://coders.talend.com >>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>>> >>>> >>>> >>>> -- >>>> Olivier Lamy >>>> Talend: http://coders.talend.com >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >>> >
