Hi Matt, I just tried to do a mvn deploy for the SNAPSHOT and got a "Access
denied" error. I believe that i have my settings.xml set up properly with
an appropriate entry like this (with username/password set of course):
<server>
<id>apache.snapshots.https</id>
<username></username>
<password></password>
</server>
so I assume that i just don't have rights to publish. Did you ever hear
anything from the infra list with respect to this? How should Marko and I
go about getting the appropriate rights to deploy?
Thanks,
Stephen
On Thu, Mar 12, 2015 at 5:51 PM, Matt Franklin <[email protected]>
wrote:
> On Wed, Mar 11, 2015 at 6:02 AM Stephen Mallette <[email protected]>
> wrote:
>
> > Matt, thanks for setting that up. I like that SNAPSHOT deployment is part
> > of the build process. I was wondering if you are able to share the
> > credentials for deploying SNAPSHOTs so that we could have the flexibility
> > to deploy manually if needed, to setup deployment from another external
> > build server, etc. Is that possible?
> >
>
> It is possible and will be required for the release manager (RM) when the
> release is cut.
>
> At one point they were manually enabling authentication for incubator
> projects. I will send an e-mail to the infra list to verify that this is
> not an issue. You could also attempt to do a mvn deploy, but in the event
> it fails, it will lock your account out and you will have to reset the
> password through https://id.apache.org.
>
>
> >
> > On Wed, Mar 11, 2015 at 6:34 AM, pieter-gmail <[email protected]>
> > wrote:
> >
> > > Thanks
> > > Pieter
> > >
> > >
> > > On 10/03/2015 20:40, Matt Franklin wrote:
> > >
> > >> On Mon, Mar 9, 2015 at 3:22 PM Matt Franklin <
> [email protected]>
> > >> wrote:
> > >>
> > >> I have configured the Jenkins build to publish SNAPSHOT artifacts.
> > >>>
> > >>> If the build ever finishes, I will verify SNAPSHOTs got published and
> > let
> > >>> the list know.
> > >>>
> > >>> https://builds.apache.org/job/tinkerpop-master/8
> > >>>
> > >>> The build seems to hang on certain servers. I am going to restrict
> > the
> > >> build to the machines that it has successfully completed on, or hasn't
> > run
> > >> on yet. Assuming this works, we will have consistent snapshots
> > deployed.
> > >>
> > >> Build 9 did succeed and produced the following SNAPSHOTs
> > >>
> > >> https://repository.apache.org/content/groups/snapshots/org/
> > >> apache/tinkerpop/
> > >>
> > >>
> > >>
> > >>>
> > >>> On Mon, Mar 2, 2015 at 7:53 AM Matt Franklin <
> [email protected]
> > >
> > >>> wrote:
> > >>>
> > >>> Apologies on the delay. I have been out of the country on business
> and
> > >>>> haven't had a free second. I will look into it this week.
> > >>>>
> > >>>> On Thu, Feb 26, 2015 at 8:16 AM pieter-gmail <
> [email protected]
> > >
> > >>>> wrote:
> > >>>>
> > >>>> Hi,
> > >>>>>
> > >>>>> Is this going to happen?
> > >>>>> Makes live way easier for (cutting edge) projects that are already
> > >>>>> developing against tp3.
> > >>>>>
> > >>>>> Thanks
> > >>>>> Pieter
> > >>>>>
> > >>>>> On 10/02/2015 18:11, Stephen Mallette wrote:
> > >>>>>
> > >>>>>> Mentors,
> > >>>>>>
> > >>>>>> We've always deployed SNAPSHOT releases to Sonatype:
> > >>>>>>
> > >>>>>> https://oss.sonatype.org/content/repositories/
> > >>>>>> snapshots/com/tinkerpop/
> > >>>>>>
> > >>>>>> Based on that, I have couple of questions:
> > >>>>>>
> > >>>>>> 1. Will we still deploy SNAPSHOT releases to Sonatype under
> Apache?
> > I
> > >>>>>>
> > >>>>> did
> > >>>>>
> > >>>>>> find this page[1] - do we simply follow those instructions?
> > >>>>>> 2. While under incubator, are we allowed to publish SNAPSHOT
> > releases?
> > >>>>>>
> > >>>>>> Thanks,
> > >>>>>>
> > >>>>>> Stephen
> > >>>>>>
> > >>>>>> [1] http://www.apache.org/dev/publishing-maven-artifacts.html
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >
> >
>
