Actions
Feature #4912
closedmake osmo-gsm-manuals part of the docker images
Start date:
12/17/2020
Due date:
% Done:
100%
Spec Reference:
Description
I don't think there is a lot be gained by re-building osmo-gsm-manuals all the time (via osmo-build-dep.sh osmo-gsm-manuals) from virtually every one of our build jobs. - particularly as that will do a 'make check" and hence build test user manuals every time.
I would guess it made more sense to simply include osmo-gsm-manuals.git into the build container. This way it is always pre-installed without having to explicitly install it.
Checklist
- interim measure: workaround for 'osmo-build-dep.sh osmo-gsm-manuals' to only clone, not build
- clone osmo-gsm-manuals in the docker image and on build slaves (for osmo-trx,bts which can't build in docker)
- add job to trigger update-osmo-ci-on-slaves when pushing to osmo-gsm-manuals.git, so the build slaves and docker images always have the latest version of osmo-gsm-manuals
- update OSMO_GSM_MANUALS_DIR
- remove 'osmo-build-dep.sh osmo-gsm-manuals' from contrib/jenkins.sh of all projects
- remove workaround for 'osmo-build-dep.sh osmo-gsm-manuals' again
Actions