The problem is in Jenkins. We know that it doesn't build reliably and we have worked with Apache Infra to improve this but unfortunately Jenkins is still not reliable for me.
wicket-bot in our IRC channel works with BuildBot ( http://ci.apache.org/builders/wicket-master). And behaves much more stable. But it uploads only the javadoc to http://ci.apache.org/projects/wicket/apidocs/6.0.x/. It doesn't copy the produced .jar/.war files to Nexus. On Fri, Mar 8, 2013 at 3:39 PM, Nick Pratt <[email protected]> wrote: > The last snapshot build was pushed to the snapshot repo yesterday morning > (or it was when I looked last night). Sven kindly made a fix for an issue > that I need to pick up - I forced a new build via wicketbot (as it turns > out, I didnt need to do that since the CI server had already built his > change). However, neither build #1094 or #1095 ended up on the repo > yesterday, so I wanted to know how to trigger a CI build to be copied over > to the snapshot repo as it seems that not every CI build is being copied > and thus made available. > > N > > On Fri, Mar 8, 2013 at 7:36 AM, Martin Grigorov <[email protected] > >wrote: > > > Hi, > > > > I don't understand your question. > > You can take 6.7.0-SNAPSHOT from > > > https://repository.apache.org/content/groups/snapshots/org/apache/wicket/ > > > > > > On Thu, Mar 7, 2013 at 11:20 PM, Nick Pratt <[email protected]> wrote: > > > > > Assuming its ok to do so, how do I force a snapshot build to be built > > > (6.7.0) and then have the artifacts pushed to the snapshot repo? > > > > > > N > > > > > > > > > > > -- > > Martin Grigorov > > jWeekend > > Training, Consulting, Development > > http://jWeekend.com <http://jweekend.com/> > > > -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com <http://jweekend.com/>
