sure, but I never read docs. here is the job script:
```
whoami
export PATH=/home/jenkins/.rvm/bin:$PATH
export rvm_path=/home/jenkins/.rvm
export HOME=/home/jenkins/
cd tools/appliance
if [ -d iso ]; then
rm -fvr iso
fi
if [ -d dist ]; then
rm -fvr dist
fi
if [ -d box ]; then
rm -fvr
nice thanks.
Do not we have a doc page for that?
On Wed, Nov 11, 2015 at 7:03 PM, Daan Hoogland
wrote:
> Rafael, check the tools/appliance dir or the systemvm template builds in
> jenkins. you'll find the prereqs in there.
>
> On Wed, Nov 11, 2015 at 9:54 PM, Rafael Weingärtner <
> rafaelweingar
Rafael, check the tools/appliance dir or the systemvm template builds in
jenkins. you'll find the prereqs in there.
On Wed, Nov 11, 2015 at 9:54 PM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> Hi Daan,
> That is something I would like to use. However, there is somethings that I
> d
Hi Daan,
That is something I would like to use. However, there is somethings that I
do not fully understand when we create/customize the system VMs.
What does an Operating System need to work as a system VM? I mean, does it
need an agent to be installed into the VM? Does it need some version of
so
Devs,
This has bitten us in indecent places time after time and after some
contemplating the solution seems quite simple. An api call implemented in
the TemplateService that lets you MarkTemplateAsSystemVmTemplate(optional
uuid, optional name). No other params are needed as the template should
all
