The bare metal scenario:
--
> now, if you explain more, i can help you more, but the technical
> requirements (how) should came after the business requirements (what/why)
>
Forget about the outer virtualisation for a moment. In a bare metal world,
vagrant+vb are
The bare metal scenario:
--
> now, if you explain more, i can help you more, but the technical
> requirements (how) should came after the business requirements (what/why)
>
Forget about the outer virtualisation for a moment. In a bare metal world,
vagrant+vb are
hello
there are same technical aspects chosen before the scope of the
requirement, like you want to use virtualbox nested.
If that is the case, then you should look for:
- bare metal
- ideally per minute or per hour
check terraform + packet.net if you want to build and use later
now, if you
No no it is different. Jenkins runs inside a KVM guest. Jenkins uses
vagrant + virtual box to build the testing environment in which the actual
application tests run. The latter is common practice.
In deed this setup does not perform very well. Virtual box instances can be
set up, they do run
On Thursday 08 February 2018 at 18:21:43, Alvaro Miranda Aguilera wrote:
> hello
>
> how do people run a setup of vagrant + virtual box + jenkins in the cloud?
>
> they don't
Is that because it doesn't work, or because it's just not a useful idea?
> what do you want to achieve that vagrant +
