Here is a plan to update our drone instance from 0.3 to 0.4.
There are many changes in drone which makes it incompatible. The .drone.yml must be rewrote. So we need to provide a smooth transition for all repositories. We can provide that by running two instances of drone on the testing server on different ports.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
...
Linked items
0
Link issues together to show that they're related.
Learn more.
- Use official python images
- Use matrix build for python version and database (with a fake database image for sqlite).
- Rename tox envlist to match the docker python image
- Use database copy from #6699 (closed)
I tested it locally and it works pretty well.
I will start the administrative task to prepare the support of two drone instances.
Cédric Krieradded 1 deleted label and removed 1 deleted label
- trypod runs as hg user with just access to SELECT on _user table of roundup
- drone.tryton.org is run by a reverse proxy nginx (to allow dispatch base on hostname) (rem: got some issue with websocket rule, go websocket required the hostname)
- ngnix server also cache for: hg.tryton.org and pypi.tryton.org
The pending issues for drone 0.8 are:
- support cache: http://discourse.drone.io/t/drone-caching-options-help-to-create-a-list/65
but I'm not 100% sure to depend on external plugin as drone change often its API.
- set proxy environment specific to the setup. In drone 0.3, we could set variable in repository setup. It is no more possible and I guess it is because build can be run on another host.
- repositories use drone-old.tryton.org now by default
- local mercurial proxy uses a valid certificate (copies from moretus)
- other cache is supported with volumes see last review37611002
- docker has been updated to last version on tycho
- old docker images have been restored
Problems: the old drone does not work with the new docker. So I will try to setup an old one inside a docker.