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.ben.frank...@gmail.com> wrote: > On Tue, Jul 16, 2013 at 8:27 PM, Ryan Baxter <rbaxte...@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.ben.frank...@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 <rbaxte...@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 >> >> >>
