Hi Chandan, Jarek The overall plan sounds good, thanks Chandan for organising this!
Replies inline. On 2020/08/18 21:25:35, Chandan Singh <[email protected]> wrote: > I can briefly elaborate what we mean by a cache in this context. For > our integration tests, we need to fetch some sources from various > locations. These operations can take a bit of time so we cache them in > our CI setup to save time. We want this to persist across runs. > > I suspect https://github.com/actions/cache is what we want. Ahh I see, so it looks like we want to achieve a 1:1 mapping to https://gitlab.com/BuildStream/buildstream/-/blob/85d8ee1d072abe204f3706f3aa92fe696efe8e04/.gitlab-ci.yml#L30 then? This is a 1:1 mapping to https://docs.gitlab.com/ee/ci/caching/ aiui ? On 2020/08/18 12:54:43 Jarek Potiuk <[email protected]> wrote: > As of last week GitHub actions support Composite Run steps: > https://github.blog/changelog/2020-08-07-github-actions-composite-run-steps/ > that > might do what you want to do regarding code reuse. On that's great, I agree that could be a neat solution. Many thanks, Chris
