yade-dev team mailing list archive
Mailing list archive
Re: Call for testing, updated yadedaily packages
Bruno Chareyre <bruno.chareyre@xxxxxxxxxxxxxxx>
Janek Kozicki <janek_listy@xxxxx>
Fri, 5 Jul 2019 14:07:09 +0200
Yade developers <yade-dev@xxxxxxxxxxxxxxxxxxx>
Bruno Chareyre said: (by the date of Fri, 28 Jun 2019 17:05:09 +0200)
> Hi Anton,
> Thank you very much!
> I confirm installation on ubuntu 18.04.
> p.s. just curious about the amazonaws hosting, issues with gitlab.com? If
> it helps local server yade-dem.org can be used to. Nothing against
Just a quick reminder: you can manipulate the 5 supported docker
images as you want on:
They are correctly built by gitlab after each git push. Then the
gitlab pipeline CI automatically checks the timestamp/crc and fetches
the latest docker image to build and test like this one:
So if you need any other package or whatever else in the docker
image, just push to the relevant branch
Maybe we should rename those branches so that their names are more
clear about how they correspond to our pipeline.
If the process:
1. "git push" ← you do only this one, rest is automatic.
2. "build docker image",
3. "use new image in gitlab-runner"
is not working, then we have a bug, and I will fix it. I should write
about this process in the developer documentation also.
The two remaining branches are:
* master - this was the jump-start branch for all other branches. Now
it is a little out of date, but was supposed to follow closely the
* ubuntu18.04_foam - this branch won't built correctly on gitlab,
becuse it involves total OpenFOAM recompilation. Maybe we can fix
it later. I have built it locally in docker on 4pak, then later I
will use it on https://gitlab.com/yade-dev/trunk/merge_requests/143
If you need somehow different docker images than those five present
in gitlab CI, you can clone the relevant branch and make your own
variation. The gitlab runner uses the name as it is given inside
After it is built, it lands in https://gitlab.com/yade-dev/docker-yade/container_registry