[petsc-dev] Fwd: [firedrake] Dockerised build tests.

[Matthew Knepley]

Jed, should we be doing this? My first impression is that our builds catch
a lot of configure errors so we do not want it.


   Matt

---------- Forwarded message ---------
From: Ham, David A <david.ham at imperial.ac.uk>
Date: Thu, Apr 11, 2019, 12:11
Subject: [firedrake] Dockerised build tests.
To: firedrake <firedrake at imperial.ac.uk>


Dear Firedrakers,



As of this afternoon, the build test systems for Firedrake and Gusto master
branches are containerised, Thetis will follow shortly. This enables us to
use significantly more build resources. For Gusto and Thetis it also
removes the need for the build system to build Firedrake (and in particular
PETSc) on every push.



Short version: this makes build testing on Jenkins faster.



*If you maintain branches of Firedrake, Gusto or Thetis:* please merge or
rebase on the respective master. This will cause your Jenkinsfile to pick
up the necessary updates. For Thetis branch maintainers, you need to wait
until the branch lands. This will hopefully be in the next 24 hours.



*If you are using a continuous integration system for a project that builds
on Firedrake:* consider basing your builder on the
firedrakeproject/firedrake-vanilla:latest container on Docker Hub. This
will save you the load of rebuilding Firedrake every time.



*If you just use Firedrake*: You don’t need to do anything. You shouldn’t
notice the change.



Regards,



David



--

Dr David Ham

Department of Mathematics

Imperial College London

https://www.imperial.ac.uk/people/david.ham

https://www.firedrakeproject.org


_______________________________________________
firedrake mailing list
firedrake at imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/firedrake
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20190411/5093dac7/attachment.html>