[Opendnssec-develop] About smoke/daily/weekly tests...

[Jerry Lundström]

On 21 Mar 2014, at 09:44 , Matthijs Mekking <matthijs at NLnetLabs.nl> wrote:

> I think it would be good to have the granularity between smoke and
> daily. I would call #build to run the smoke tests. Once I am satisfied
> (or rather: the bot is satisfied), I call #build-daily.
> 
> Because other users also wait on the bot, this could be scheduled the
> first upcoming evening/midnight. Drawback of that is that it will take
> you a long time to see if something is wrong in the daily tests (but we
> have that now too).

That is a resource issue and can be resolved by adding more.

We have received access to SURFnet’s new OpenStack and I will soon add a set of platforms to that cloud and add them into Jenkins. This will make Jenkins able to run 2 pull requests tests at the same time. If we ask for more resources in that cloud we could dynamically manage the number of instances running so that we always have one on standby but can start 3-4 to be able to test that many pull requests at the same time.

If this was the case would you still want the granularity?

--
Jerry Lundström - OpenDNSSEC Developer
http://www.opendnssec.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 625 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opendnssec.org/pipermail/opendnssec-develop/attachments/20140321/5ce920c1/attachment.bin>