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

[Jed Brown]

You mean using it for all the dependencies?  Most commits don't change
anything in the config/ tree, so we don't need to re-run configure.  But
they do generally change the source so we'd still need to build PETSc.
We could set up caching to only rebuild what is needed, but the details
of the caching would be specific to the environment we're running in
(currently a mix of Satish's cron jobs and Jenkins).

I've been experimenting with GitLab-CI recently, which would be another
option (much less resource-hungry and click-around-configuration-heavy
than Jenkins).  (GitLab-CI works with repositories not hosted at GitLab,
though the PR integration and related features are much better when
hosted on GitLab.)

Matthew Knepley via petsc-dev <petsc-dev at mcs.anl.gov> writes:

> 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