|
Hi GianMaria,
thank you very much for your quick reply! I am afraid we cannot
do that, since we need to dynamically add and remove the plans. We
are using a Maven job on a Jenkins server for building our
software. During the development, we repeatedly need to re-build
and re-deploy our bundles and plans, which roughly means:
* Build the bundles on Jenkins
* Remove the old bundles/plans from the Virgo - wait until it is
undeployed
* Add the new bundles/plan to the Virgo
I would assume if we had one or more "master plans", we could not
dynamically add or remove random plans?
Cheers,
Stefan
On 29.08.2017 13:56, Giamma wrote:
Hi Stefan
Did you consider something as simple as creating one
or more "master plan" that lists other plans (which you move
from pickup to repository) to get them started in a controlled
sequence?
GianMaria.
Hi all,
we are happily using Virgo for some years now - so we have
accumulated
quite some bundles and plans in our development servers. Even
though
Virgo runs nicely and stable as it is started, the startup
itself causes
us some troubles. Particularly, in one of the Virgos we have
~35 plans
with ~25 bundles each - hence requiring to start about ~875
bundles. It
seems that when Virgo starts, all plans in the pickup folder
are
automatically detected and started. Even though it is nice
that through
this parallel startup multiple cpu cores are used, in our case
the
overall startup takes too long, which in turn causes timeouts
when
waiting for certain services.
So we were wondering whether there is a way to restrict the
parallelism
of starting bundles/plans during startup of Virgo?
Cheers,
Stefan
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/virgo-dev
|
