Shindig Assembly On builds.a.o

[Ryan Baxter <rb...@apache.org>]

Yesterday when I staged the release of 2.5.0 the Shindig Assembly
build on builds.a.o started to fail.  It was unable to find the
2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
build was passing was because someone published SNAPSHOT artifacts [1]
a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
Assembly build started passing again.

Ideally we want the publishing of these SNAPSHOT artifacts to happen
often and automatically.  Does anyone know if there are any best
practices on doing this from Apache?  I couldn't seem to locate
anything.

[1] https://repository.apache.org/content/repositories/snapshots/org/apache/shindig

Re: Shindig Assembly On builds.a.o

[Ryan Baxter <rb...@gmail.com>]

Matt, the mvn command that job runs is clean install
cobertura:cobertura.  That doesn't do a deploy as far as I know so how
does that job deploy your snapshots?

On Fri, Jul 19, 2013 at 12:04 AM, Matt Franklin
<m....@gmail.com> wrote:
> There shouldn't be any config.  That job deploys our snapshots
>
>> On Jul 18, 2013, at 16:19, Ryan Baxter <rb...@gmail.com> wrote:
>>
>> I looked at the rave-project-trunk job in Jenkins on builds.a.o and
>> there is a Deploy Artifacts To Maven Repository post build action but
>> it is not configured, so it doesn't look like it is.
>>
>> On Tue, Jul 16, 2013 at 10:51 PM, Matt Franklin
>> <m....@gmail.com> wrote:
>>> Jenkins should have the creds.  That is the same config we use in Rave...
>>>
>>>> On Jul 16, 2013, at 20:56, Ryan Baxter <rb...@gmail.com> wrote:
>>>>
>>>> As I expected when doing this in Jenkins on builds.a.o the build fails
>>>> because the build machine does not have the necessary creds to publish
>>>> the artifacts.  Are you suggesting we don't do this from builds.a.o?
>>>>
>>>>>> On Tue, Jul 16, 2013 at 9:30 PM, Matt Franklin <m....@gmail.com> wrote:
>>>>>> On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:
>>>>>>
>>>>>> Because we are not deploying any snapshots in the CI build.  I can
>>>>>> look into it, is there any documentation that you know of?
>>>>>
>>>>> Add a post-build action to deploy to Maven repository.  No further
>>>>> configuration needed.
>>>>>
>>>>>
>>>>>>
>>>>>> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
>>>>>> wrote:
>>>>>>> Best practice is to deploy them as part of the build CI build.  Why was
>>>>>> the
>>>>>>> CI build failing when it was building 2.5.1-SNAPSHOT?
>>>>>>>
>>>>>>>
>>>>>>>> On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>>>>>>>> build on builds.a.o started to fail.  It was unable to find the
>>>>>>>> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>>>>>>>> build was passing was because someone published SNAPSHOT artifacts [1]
>>>>>>>> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>>>>>>>> Assembly build started passing again.
>>>>>>>>
>>>>>>>> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>>>>>>>> often and automatically.  Does anyone know if there are any best
>>>>>>>> practices on doing this from Apache?  I couldn't seem to locate
>>>>>>>> anything.
>>>>>>>>
>>>>>>>> [1]
>>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>>>>>>

Re: Shindig Assembly On builds.a.o

[Matt Franklin <m....@gmail.com>]

There shouldn't be any config.  That job deploys our snapshots

> On Jul 18, 2013, at 16:19, Ryan Baxter <rb...@gmail.com> wrote:
> 
> I looked at the rave-project-trunk job in Jenkins on builds.a.o and
> there is a Deploy Artifacts To Maven Repository post build action but
> it is not configured, so it doesn't look like it is.
> 
> On Tue, Jul 16, 2013 at 10:51 PM, Matt Franklin
> <m....@gmail.com> wrote:
>> Jenkins should have the creds.  That is the same config we use in Rave...
>> 
>>> On Jul 16, 2013, at 20:56, Ryan Baxter <rb...@gmail.com> wrote:
>>> 
>>> As I expected when doing this in Jenkins on builds.a.o the build fails
>>> because the build machine does not have the necessary creds to publish
>>> the artifacts.  Are you suggesting we don't do this from builds.a.o?
>>> 
>>>>> On Tue, Jul 16, 2013 at 9:30 PM, Matt Franklin <m....@gmail.com> wrote:
>>>>> On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:
>>>>> 
>>>>> Because we are not deploying any snapshots in the CI build.  I can
>>>>> look into it, is there any documentation that you know of?
>>>> 
>>>> Add a post-build action to deploy to Maven repository.  No further
>>>> configuration needed.
>>>> 
>>>> 
>>>>> 
>>>>> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
>>>>> wrote:
>>>>>> Best practice is to deploy them as part of the build CI build.  Why was
>>>>> the
>>>>>> CI build failing when it was building 2.5.1-SNAPSHOT?
>>>>>> 
>>>>>> 
>>>>>>> On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
>>>>>> wrote:
>>>>>> 
>>>>>>> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>>>>>>> build on builds.a.o started to fail.  It was unable to find the
>>>>>>> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>>>>>>> build was passing was because someone published SNAPSHOT artifacts [1]
>>>>>>> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>>>>>>> Assembly build started passing again.
>>>>>>> 
>>>>>>> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>>>>>>> often and automatically.  Does anyone know if there are any best
>>>>>>> practices on doing this from Apache?  I couldn't seem to locate
>>>>>>> anything.
>>>>>>> 
>>>>>>> [1]
>>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>>>>> 

Re: Shindig Assembly On builds.a.o

[Ryan Baxter <rb...@gmail.com>]

I looked at the rave-project-trunk job in Jenkins on builds.a.o and
there is a Deploy Artifacts To Maven Repository post build action but
it is not configured, so it doesn't look like it is.

On Tue, Jul 16, 2013 at 10:51 PM, Matt Franklin
<m....@gmail.com> wrote:
> Jenkins should have the creds.  That is the same config we use in Rave...
>
>> On Jul 16, 2013, at 20:56, Ryan Baxter <rb...@gmail.com> wrote:
>>
>> As I expected when doing this in Jenkins on builds.a.o the build fails
>> because the build machine does not have the necessary creds to publish
>> the artifacts.  Are you suggesting we don't do this from builds.a.o?
>>
>>> On Tue, Jul 16, 2013 at 9:30 PM, Matt Franklin <m....@gmail.com> wrote:
>>>> On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:
>>>>
>>>> Because we are not deploying any snapshots in the CI build.  I can
>>>> look into it, is there any documentation that you know of?
>>>
>>> Add a post-build action to deploy to Maven repository.  No further
>>> configuration needed.
>>>
>>>
>>>>
>>>> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
>>>> wrote:
>>>>> Best practice is to deploy them as part of the build CI build.  Why was
>>>> the
>>>>> CI build failing when it was building 2.5.1-SNAPSHOT?
>>>>>
>>>>>
>>>>>> On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
>>>>> wrote:
>>>>>
>>>>>> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>>>>>> build on builds.a.o started to fail.  It was unable to find the
>>>>>> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>>>>>> build was passing was because someone published SNAPSHOT artifacts [1]
>>>>>> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>>>>>> Assembly build started passing again.
>>>>>>
>>>>>> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>>>>>> often and automatically.  Does anyone know if there are any best
>>>>>> practices on doing this from Apache?  I couldn't seem to locate
>>>>>> anything.
>>>>>>
>>>>>> [1]
>>>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>>>>

Re: Shindig Assembly On builds.a.o

[Matt Franklin <m....@gmail.com>]

Jenkins should have the creds.  That is the same config we use in Rave...

> On Jul 16, 2013, at 20:56, Ryan Baxter <rb...@gmail.com> wrote:
> 
> As I expected when doing this in Jenkins on builds.a.o the build fails
> because the build machine does not have the necessary creds to publish
> the artifacts.  Are you suggesting we don't do this from builds.a.o?
> 
>> On Tue, Jul 16, 2013 at 9:30 PM, Matt Franklin <m....@gmail.com> wrote:
>>> On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:
>>> 
>>> Because we are not deploying any snapshots in the CI build.  I can
>>> look into it, is there any documentation that you know of?
>> 
>> Add a post-build action to deploy to Maven repository.  No further
>> configuration needed.
>> 
>> 
>>> 
>>> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
>>> wrote:
>>>> Best practice is to deploy them as part of the build CI build.  Why was
>>> the
>>>> CI build failing when it was building 2.5.1-SNAPSHOT?
>>>> 
>>>> 
>>>>> On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
>>>> wrote:
>>>> 
>>>>> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>>>>> build on builds.a.o started to fail.  It was unable to find the
>>>>> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>>>>> build was passing was because someone published SNAPSHOT artifacts [1]
>>>>> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>>>>> Assembly build started passing again.
>>>>> 
>>>>> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>>>>> often and automatically.  Does anyone know if there are any best
>>>>> practices on doing this from Apache?  I couldn't seem to locate
>>>>> anything.
>>>>> 
>>>>> [1]
>>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>>> 

Re: Shindig Assembly On builds.a.o

[Ryan Baxter <rb...@gmail.com>]

As I expected when doing this in Jenkins on builds.a.o the build fails
because the build machine does not have the necessary creds to publish
the artifacts.  Are you suggesting we don't do this from builds.a.o?

On Tue, Jul 16, 2013 at 9:30 PM, Matt Franklin <m....@gmail.com> wrote:
> On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:
>
>> Because we are not deploying any snapshots in the CI build.  I can
>> look into it, is there any documentation that you know of?
>>
>
> Add a post-build action to deploy to Maven repository.  No further
> configuration needed.
>
>
>>
>> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
>> wrote:
>> > Best practice is to deploy them as part of the build CI build.  Why was
>> the
>> > CI build failing when it was building 2.5.1-SNAPSHOT?
>> >
>> >
>> > On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
>> wrote:
>> >
>> >> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>> >> build on builds.a.o started to fail.  It was unable to find the
>> >> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>> >> build was passing was because someone published SNAPSHOT artifacts [1]
>> >> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>> >> Assembly build started passing again.
>> >>
>> >> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>> >> often and automatically.  Does anyone know if there are any best
>> >> practices on doing this from Apache?  I couldn't seem to locate
>> >> anything.
>> >>
>> >> [1]
>> >>
>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>> >>
>>

Re: Shindig Assembly On builds.a.o

[Matt Franklin <m....@gmail.com>]

On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rb...@gmail.com> wrote:

> Because we are not deploying any snapshots in the CI build.  I can
> look into it, is there any documentation that you know of?
>

Add a post-build action to deploy to Maven repository.  No further
configuration needed.


>
> On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com>
> wrote:
> > Best practice is to deploy them as part of the build CI build.  Why was
> the
> > CI build failing when it was building 2.5.1-SNAPSHOT?
> >
> >
> > On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org>
> wrote:
> >
> >> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
> >> build on builds.a.o started to fail.  It was unable to find the
> >> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
> >> build was passing was because someone published SNAPSHOT artifacts [1]
> >> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
> >> Assembly build started passing again.
> >>
> >> Ideally we want the publishing of these SNAPSHOT artifacts to happen
> >> often and automatically.  Does anyone know if there are any best
> >> practices on doing this from Apache?  I couldn't seem to locate
> >> anything.
> >>
> >> [1]
> >>
> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
> >>
>

Re: Shindig Assembly On builds.a.o

[Ryan Baxter <rb...@gmail.com>]

Because we are not deploying any snapshots in the CI build.  I can
look into it, is there any documentation that you know of?

On Tue, Jul 16, 2013 at 9:22 PM, Matt Franklin <m....@gmail.com> wrote:
> Best practice is to deploy them as part of the build CI build.  Why was the
> CI build failing when it was building 2.5.1-SNAPSHOT?
>
>
> On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org> wrote:
>
>> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
>> build on builds.a.o started to fail.  It was unable to find the
>> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
>> build was passing was because someone published SNAPSHOT artifacts [1]
>> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
>> Assembly build started passing again.
>>
>> Ideally we want the publishing of these SNAPSHOT artifacts to happen
>> often and automatically.  Does anyone know if there are any best
>> practices on doing this from Apache?  I couldn't seem to locate
>> anything.
>>
>> [1]
>> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>>

Re: Shindig Assembly On builds.a.o

[Matt Franklin <m....@gmail.com>]

Best practice is to deploy them as part of the build CI build.  Why was the
CI build failing when it was building 2.5.1-SNAPSHOT?


On Tue, Jul 16, 2013 at 7:29 PM, Ryan Baxter <rb...@apache.org> wrote:

> Yesterday when I staged the release of 2.5.0 the Shindig Assembly
> build on builds.a.o started to fail.  It was unable to find the
> 2.5.1-SNAPSHOT artifacts.  The only reason why the 2.5.0 Assembly
> build was passing was because someone published SNAPSHOT artifacts [1]
> a while ago.  After I published similar 2.5.1-SNAPSHOT artifacts the
> Assembly build started passing again.
>
> Ideally we want the publishing of these SNAPSHOT artifacts to happen
> often and automatically.  Does anyone know if there are any best
> practices on doing this from Apache?  I couldn't seem to locate
> anything.
>
> [1]
> https://repository.apache.org/content/repositories/snapshots/org/apache/shindig
>