Improve Running CI Locally #17372

1. 
   JeremyRubin commented at 11:14 pm on November 4, 2019: contributor

   One issue that can come up when running CI locally is that docker links directly to the current working directory. This has two unsavory side effects:

   1. When docker writes the files, it writes them as root, preventing local building
   2. It blows away your current build
2. JeremyRubin added the label Feature on Nov 4, 2019
3. fanquake added the label Tests on Nov 4, 2019
4. 
   MarcoFalke commented at 10:39 pm on November 8, 2019: member

   Please use the ci system locally only at your own risk, it might eat your laptop. ;)

   Running the ci completely in a docker, without leaving any traces on the host system is not possible right now because the ccache and depends dir needs to be propagated back and picked up by the host for caching.

   See #17423

5. 
   JeremyRubin commented at 11:17 pm on November 9, 2019: contributor

   Please use the ci system locally only at your own risk, it might eat your laptop. ;)

   If that’s actually the standard of code we have in there right now…. yikes! Maybe we should have some stronger warnings or something…

6. 
   MarcoFalke commented at 2:19 pm on November 10, 2019: member

   The code was initially written for travis (in the .travis.yml), and travis machines have no concerns. Then it was gradually moved into separate shell scripts and finally into the ci folder.

   I will try to document the expectations a bit better.

7. MarcoFalke closed this on Nov 20, 2019

   ---

8. sidhujag referenced this in commit f813bb5e43 on Nov 21, 2019
9. sidhujag referenced this in commit 064f7896af on Nov 10, 2020
10. MarcoFalke locked this on Dec 16, 2021
11. Munkybooty referenced this in commit 8646e637a7 on Jun 7, 2022
12. Munkybooty referenced this in commit 6d331dd4a5 on Jun 8, 2022
13. Munkybooty referenced this in commit 1c20456a52 on Jun 16, 2022

Contributors
JeremyRubin MarcoFalke

Labels
Feature Tests