ace-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daan Veldhof <daanveld...@gmail.com>
Subject Re: Login before automation is started
Date Tue, 27 Oct 2015 10:41:04 GMT
2015-10-23 16:19 GMT+02:00 Jan Willem Janssen <janwillem.janssen@luminis.eu>
:

>
> > On 23 Oct 2015, at 14:46, Daan Veldhof <daanveldhof@gmail.com> wrote:
> >
> > I've configured ACE so I create the artifacts, features,
> > artifact2features,distribution, feature2distribution and
> > distribution2target (didn't fix the issue with filtering on 2 tags yet)
> > through the REST API. I also added the org.apache.ace.client.automation
> > bundle to autoregister and autoapprove all the targets. The weird part
> is,
> > I have to get a workspace through the GoGo shell or the REST API before
> the
> > automation is started. Is this normal behaviour?
>
> No, this is normally not necessary. Do you need to do this once before the
> automation process is doing its task? Or every time?
>

Only when I start ACE. Once I have a workspace the automation is working.


>
> > Also when a target sends the second auditlog with it's tags the Ace
> server
> > should deploy the right distribution, but it doesn't deploy anything. I
> > have to log in to the web ui first, press store and retrieve and then it
> > deploys. This doesn't seem normal to me.
>
> No, this is not what I’d expect either. Have to replay this to get more
> insights on why this goes wrong. At what interval is the automation bundle
> doing its job? Isn’t that causing this behaviour (as in: shouldn’t you wait
> a little longer?)
>
> The interval is at 1000 ms right now, so that wouldn't be a problem

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