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

Upgrade to new efficient artifact actions + mac code sign identity #52

Merged
merged 1 commit into from
Feb 16, 2024

Conversation

Supereg
Copy link
Member

@Supereg Supereg commented Feb 16, 2024

Upgrade to new efficient artifact actions + mac code sign identity

♻️ Current situation & Problem

This PR upgrades the actions to the new v4 version of the upload- and download-artifact actions. This results in a dramatic speed increase when uploading and download artifacts.
The workflow files from this PR were tested within this action run. You can compare timings to the previous run. Comparing these two examples, the coverage download takes 1s instead of 24s. Uploading takes 1s instead of 8s (for a successful run with this example project).

⚙️ Release Notes

  • Speed increase uploading and downloading code coverage artifacts.

📚 Documentation

--

✅ Testing

These changes were tested in the above linked action runs.

Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

Copy link
Member

@PSchmiedmayer PSchmiedmayer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for improving the upload and signing issue.

@Supereg Supereg marked this pull request as ready for review February 16, 2024 18:05
@Supereg Supereg merged commit 625d000 into main Feb 16, 2024
2 checks passed
@Supereg Supereg deleted the feature/artifact-actions-upgrade branch February 16, 2024 19:22
Supereg added a commit to StanfordSpezi/.github that referenced this pull request Feb 16, 2024
# Upgrade to new upload artifact versions

## ♻️ Current situation & Problem

This PR upgrades the upload artifact branch in this repository. Refer to
StanfordBDHG/.github#52 for more information.

## ⚙️ Release Notes 

* Upgraded the upload-artifact GitHub action for increased performance.

## 📚 Documentation

--

## ✅ Testing

--

## 📝 Code of Conduct & Contributing Guidelines 

By submitting creating this pull request, you agree to follow our [Code
of
Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md):
- [x] I agree to follow the [Code of
Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md).
@PSchmiedmayer
Copy link
Member

Thank you @Supereg!

Supereg added a commit that referenced this pull request Feb 24, 2024
# Upgrade artifact actions for archive and docker actions

## ♻️ Current situation & Problem
We upgraded our code-coverage artifact upload and download actions to
use the new `v4` version (see #52). Our xcframework creation process and
docker container actions still use the old, slow v3 actions. This PR
upgrades them as well.


## ⚙️ Release Notes 
* Increased performance for file uploads in xcframework creation


### Code of Conduct & Contributing Guidelines 

By submitting creating this pull request, you agree to follow our [Code
of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md):
- [x] I agree to follow the [Code of
Conduct](https://github.com/StanfordBDHG/.github/blob/main/CODE_OF_CONDUCT.md)
and [Contributing
Guidelines](https://github.com/StanfordBDHG/.github/blob/main/CONTRIBUTING.md).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants