ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bram Pouwelse <b...@pouwelse.com>
Subject Re: Deployment breaks after adding new artifacts
Date Thu, 15 Aug 2013 06:38:19 GMT
Hi Marcel,

Thanks for the quick reply I'm using the 1.0 release, so I'll build from
source again ;)

Bram


2013/8/15 Marcel Offermans <marcel.offermans@luminis.nl>

> Hello Bram,
>
> On Aug 15, 2013, at 8:19 AM, Bram Pouwelse <bram@pouwelse.com> wrote:
>
> > A while ago I've shared my first impressions of Ace and got some valuable
> > feedback, thanks for that! I've made changes in the application to get
> rid
> > of start levels and added timestamps to the bundle version to make it
> > possible to just add the bundle to Ace.
> >
> > I'm using the ace cli Bram de Kruijff mentioned to upload the artifacts.
> >
> > Everything works fine, new bundle versions are available on the targets
> > faster than I can connect to them to check if the deployment is working
> :)
> >
> > BUT:
> > After a few updates the updates are not published to the target
> > anymore and when
> > I check the deployment servlet
> > http://<<ace-host>>:9090/deployment/defaultTargetID/versions
> > I get an empty 200 response.
> >
> > What would be a good place to look when this happens?
>
> If you're running the 1.0 release, then I am pretty sure you ran into an
> issue we recently fixed:
>
> https://issues.apache.org/jira/browse/ACE-399
>
> This issue typically caused the same symptom you describe.
>
> Greetings, Marcel
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message