-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add shallow checkout for azure pipelines #949
Comments
XFEL CI on Azure is so tight on space this kinda thing can help (plus it's good dinosaur management). But how does this affect developers? With depth=1, the old commit history is literally not there. Git log shows only the latest commit. So I think we'd only want this for Azure, right? Maybe a flag to bootstrap update that we can set in Azure? |
How much more disk space is needed? There is a disk clean up step in cctbx_project/.azure-pipelines/xfel/conda-linux.yml Lines 112 to 128 in 9983275
You essentially have root access to the virtual machine on Azure so you can delete whatever you want. There is sort of a limit in that in this pipeline, you are already inside the Docker image, but you can always make other host directories writeable here cctbx_project/.azure-pipelines/xfel/conda-linux.yml Lines 27 to 33 in 9983275
For example, in some pipelines, I clean up more stuff and make a swap file https://github.com/phenix-project/phenix-installer/blob/main/scripts/clean_linux.sh But that is done in the normal Azure image, not the Docker image. I get about 47 GB free in / after this step. Also, you do not need to use the 14 GB partition, you can use any partition on the image. I can probably help more next week once I get back. |
@phyy-nx to get the full git history, you can run either |
--depth=1
to git clone commands in bootstrap.py, so that only the necessary data is downloaded in the first placegit fetch --unshallow
Note to @nksauter, @bkpoon
The text was updated successfully, but these errors were encountered: