-
Notifications
You must be signed in to change notification settings - Fork 525
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
Idea: reduce resource consumption during GitHub Actions workflows #1340
Comments
Partially-related:
|
This is probably mostly-pointless; narrowing it to |
Ok, I'm going to pause: it seems that the content of the logs for many of these entries cannot be viewed in the web UI, despite there existing an option to 'delete all logs' (associated with each item). Basically I'd like to figure out whether we can upper-bound our usage of log storage space, because I don't want this project to exert unnecessary resource usage expenditure. My sense is that over the past few weeks, we've increased resource usage in various ways, but I don't have good statistics for those currently (but despite that, can think of some ways to reduce evident usage - e.g. duration of test workflows, and removal of duplicate work). |
The relevant documentation for this style of approach is described here: https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/storing-and-sharing-data-from-a-workflow#passing-data-between-jobs-in-a-workflow - note again that there remains a question about integrity-checks of the resulting data. |
At the moment each of our individual GitHub Actions workflows - of which we generally launch at least 3x5 (unit tests: 3 operating systems, 5 Python versions) performs a checkout of the complete
git
repository, and subsequently performs build actions from there.This seems wasteful for various reasons:
publish
workflows, that have a recently-added conditional (GitHub Actions: releases: confirm commit exists on release branch #1312) to confirm that their commit ref is on a release branch).Could we do better?
git archive
to produce an artifact that each of the subsequent workflows use to build from?I think that an effective solution here might be able to reduce the sum duration of continuous integration workflows for a single commit by ~2 minutes (10 seconds for each of 15+ jobs == more than two minutes, but I also going to assume that we'd lose some time because each of the tasks would depend upon the initial export-from-git task).
The text was updated successfully, but these errors were encountered: