Skip to content
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

Speedup Github Action runs #10428

Open
poikilotherm opened this issue Mar 26, 2024 · 5 comments
Open

Speedup Github Action runs #10428

poikilotherm opened this issue Mar 26, 2024 · 5 comments
Assignees
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Component: Containers Anything related to cloudy Dataverse, shipped in containers.

Comments

@poikilotherm
Copy link
Contributor

Artifacts: Uploads are slow!

  • Do not include the WAR file in the java-builddir.tar (140 MB)
  • Maybe do not include the dataverse/WEB-INF/lib dir (160MB)

Caching:

  • Analyse why there are 240 MB and 800 MB caches
  • Do not use a cache for very different versions of the POM. We're stable enough, just make it one cache.
  • Delete the cache at certain intervals (time based? closed PR based?)
  • Optimize cache ignores, do not include installed build artifacts
@poikilotherm poikilotherm added Type: Bug a defect Component: Code Infrastructure formerly "Feature: Code Infrastructure" Component: Containers Anything related to cloudy Dataverse, shipped in containers. and removed Type: Bug a defect labels Mar 26, 2024
@poikilotherm poikilotherm self-assigned this Mar 26, 2024
poikilotherm added a commit that referenced this issue Apr 12, 2024
Contains the feature branch for now, too. Will be deleted later before merging it to develop.
poikilotherm added a commit that referenced this issue Apr 12, 2024
Contains the feature branch for now, too. Will be deleted later before merging it to develop.
poikilotherm added a commit that referenced this issue Apr 15, 2024
- Create a common cache to draw from when no branch caches exist
- Rejuvenate the common cache to ensure it's around using pushes,
  schedule or manual runs
- To save space, we automatically trigger a job on a closed PR to delete
  any caches for the feature branch just merged
@poikilotherm poikilotherm reopened this Apr 16, 2024
@poikilotherm
Copy link
Contributor Author

@pdurbin this is not yet resolved.

@pdurbin
Copy link
Member

pdurbin commented Apr 16, 2024

It wasn't me! The automation got us! You had resolve #10428 in the PR. 😄

@cmbz
Copy link

cmbz commented Jul 19, 2024

2024/07/19 - 6.4 proposal request from @poikilotherm

@cmbz
Copy link

cmbz commented Nov 18, 2024

2024/11/18: Whoever picks up this issue, please also reach out to @poikilotherm for any additional context.

@cmbz cmbz moved this to SPRINT- NEEDS SIZING in IQSS Dataverse Project Nov 18, 2024
@cmbz
Copy link

cmbz commented Nov 18, 2024

@poikilotherm can you take a look and advise on a size for this one?

@cmbz cmbz removed the status in IQSS Dataverse Project Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Code Infrastructure formerly "Feature: Code Infrastructure" Component: Containers Anything related to cloudy Dataverse, shipped in containers.
Projects
Status: No status
Development

No branches or pull requests

3 participants