You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@accumulo.apache.org by Josh Elser <jo...@gmail.com> on 2014/06/10 20:34:55 UTC
Deploying SNAPSHOTs to nexus
Before we released 1.6.0, I got a request to upload some new
1.6.0-SNAPSHOT jars. After thinking about it some more, I convinced
myself that we, at one point, had SNAPSHOTs being automatically deployed
by Jenkins.
Does anyone remember for sure? Was it lost in the svn->git transition?
Any arguments against not trying to make this work again?
Re: Deploying SNAPSHOTs to nexus
Posted by Josh Elser <jo...@gmail.com>.
Finally found a job that does deploy SNAPSHOTs
https://builds.apache.org/view/All/job/Hadoop-trunk-Commit
I'm guessing that the way they're executing things source's some
environment variable that has the sensitive bits to deploy.
On 6/11/14, 2:25 PM, Josh Elser wrote:
> On http://www.apache.org/dev/repository-faq.html
>
> They call out deploying a SNAPSHOT as long as the PMC is ok with it, but
> they also mention Maven 1 which, I believe, is older than me.
>
> I don't think that deploying artifacts to the snapshots area of Nexus
> equates to an official release, but that's my opinion and the lack of
> any other docs that make me think otherwise (if we weren't allowed to
> deploy snapshots, why would we even have that repository available to us).
>
> I looked at the Jenkins job briefly too. The job does have an option to
> auto-deploy, but I'm not sure if the permissions would be implicitly
> handled for us. I haven't found another project which appears to publish
> snapshots on each build yet.
>
> On 6/11/14, 10:31 AM, Christopher wrote:
>> I don't know for sure about what was done in the past, but we should
>> consider the ASF policy about not making non releases generally available
>> to non devs before we make this change. Can try to find link to policy
>> later.
>> Before we released 1.6.0, I got a request to upload some new
>> 1.6.0-SNAPSHOT
>> jars. After thinking about it some more, I convinced myself that we,
>> at one
>> point, had SNAPSHOTs being automatically deployed by Jenkins.
>>
>> Does anyone remember for sure? Was it lost in the svn->git transition?
>> Any
>> arguments against not trying to make this work again?
>>
Re: Deploying SNAPSHOTs to nexus
Posted by Josh Elser <jo...@gmail.com>.
On http://www.apache.org/dev/repository-faq.html
They call out deploying a SNAPSHOT as long as the PMC is ok with it, but
they also mention Maven 1 which, I believe, is older than me.
I don't think that deploying artifacts to the snapshots area of Nexus
equates to an official release, but that's my opinion and the lack of
any other docs that make me think otherwise (if we weren't allowed to
deploy snapshots, why would we even have that repository available to us).
I looked at the Jenkins job briefly too. The job does have an option to
auto-deploy, but I'm not sure if the permissions would be implicitly
handled for us. I haven't found another project which appears to publish
snapshots on each build yet.
On 6/11/14, 10:31 AM, Christopher wrote:
> I don't know for sure about what was done in the past, but we should
> consider the ASF policy about not making non releases generally available
> to non devs before we make this change. Can try to find link to policy
> later.
> Before we released 1.6.0, I got a request to upload some new 1.6.0-SNAPSHOT
> jars. After thinking about it some more, I convinced myself that we, at one
> point, had SNAPSHOTs being automatically deployed by Jenkins.
>
> Does anyone remember for sure? Was it lost in the svn->git transition? Any
> arguments against not trying to make this work again?
>
Re: Deploying SNAPSHOTs to nexus
Posted by Josh Elser <jo...@gmail.com>.
Noted, assuming I can follow through and get this working, I'll try to
remember to notate that as well.
Thanks.
On 6/12/14, 9:58 AM, Christopher wrote:
> Yeah. I think it's fine. I think intent matters and how we promote these
> snapshots. It just needs to be clear that it's for dev, not for consumption
> by others.
> On Jun 11, 2014 3:04 PM, "Billie Rinaldi" <bi...@gmail.com> wrote:
>
>> I think snapshots are okay. This link [1] on release distribution says
>> there is also a dev release area for things like snapshots and release
>> candidates. So I would imagine maven snapshots are okay too, as long as
>> we're deploying to the snapshots repo and not the releases repo. We just
>> aren't allowed to link to or direct people to download snapshot versions as
>> if they were releases.
>>
>> [1]: http://www.apache.org/dev/release.html#upload-ci
>>
>>
>> On Wed, Jun 11, 2014 at 7:31 AM, Christopher <ct...@apache.org> wrote:
>>
>>> I don't know for sure about what was done in the past, but we should
>>> consider the ASF policy about not making non releases generally available
>>> to non devs before we make this change. Can try to find link to policy
>>> later.
>>> Before we released 1.6.0, I got a request to upload some new
>> 1.6.0-SNAPSHOT
>>> jars. After thinking about it some more, I convinced myself that we, at
>> one
>>> point, had SNAPSHOTs being automatically deployed by Jenkins.
>>>
>>> Does anyone remember for sure? Was it lost in the svn->git transition?
>> Any
>>> arguments against not trying to make this work again?
>>>
>>
>
Re: Deploying SNAPSHOTs to nexus
Posted by Christopher <ct...@apache.org>.
Yeah. I think it's fine. I think intent matters and how we promote these
snapshots. It just needs to be clear that it's for dev, not for consumption
by others.
On Jun 11, 2014 3:04 PM, "Billie Rinaldi" <bi...@gmail.com> wrote:
> I think snapshots are okay. This link [1] on release distribution says
> there is also a dev release area for things like snapshots and release
> candidates. So I would imagine maven snapshots are okay too, as long as
> we're deploying to the snapshots repo and not the releases repo. We just
> aren't allowed to link to or direct people to download snapshot versions as
> if they were releases.
>
> [1]: http://www.apache.org/dev/release.html#upload-ci
>
>
> On Wed, Jun 11, 2014 at 7:31 AM, Christopher <ct...@apache.org> wrote:
>
> > I don't know for sure about what was done in the past, but we should
> > consider the ASF policy about not making non releases generally available
> > to non devs before we make this change. Can try to find link to policy
> > later.
> > Before we released 1.6.0, I got a request to upload some new
> 1.6.0-SNAPSHOT
> > jars. After thinking about it some more, I convinced myself that we, at
> one
> > point, had SNAPSHOTs being automatically deployed by Jenkins.
> >
> > Does anyone remember for sure? Was it lost in the svn->git transition?
> Any
> > arguments against not trying to make this work again?
> >
>
Re: Deploying SNAPSHOTs to nexus
Posted by Billie Rinaldi <bi...@gmail.com>.
I think snapshots are okay. This link [1] on release distribution says
there is also a dev release area for things like snapshots and release
candidates. So I would imagine maven snapshots are okay too, as long as
we're deploying to the snapshots repo and not the releases repo. We just
aren't allowed to link to or direct people to download snapshot versions as
if they were releases.
[1]: http://www.apache.org/dev/release.html#upload-ci
On Wed, Jun 11, 2014 at 7:31 AM, Christopher <ct...@apache.org> wrote:
> I don't know for sure about what was done in the past, but we should
> consider the ASF policy about not making non releases generally available
> to non devs before we make this change. Can try to find link to policy
> later.
> Before we released 1.6.0, I got a request to upload some new 1.6.0-SNAPSHOT
> jars. After thinking about it some more, I convinced myself that we, at one
> point, had SNAPSHOTs being automatically deployed by Jenkins.
>
> Does anyone remember for sure? Was it lost in the svn->git transition? Any
> arguments against not trying to make this work again?
>
Re: Deploying SNAPSHOTs to nexus
Posted by Christopher <ct...@apache.org>.
I don't know for sure about what was done in the past, but we should
consider the ASF policy about not making non releases generally available
to non devs before we make this change. Can try to find link to policy
later.
Before we released 1.6.0, I got a request to upload some new 1.6.0-SNAPSHOT
jars. After thinking about it some more, I convinced myself that we, at one
point, had SNAPSHOTs being automatically deployed by Jenkins.
Does anyone remember for sure? Was it lost in the svn->git transition? Any
arguments against not trying to make this work again?