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

feat(ci): add support to cache tools in CI #278

Closed
wants to merge 1 commit into from

Conversation

vprashar2929
Copy link
Collaborator

Signed-off-by: Vibhu Prashar <vibhu.sharma2929@gmail.com>
@vprashar2929 vprashar2929 requested a review from sthaha October 16, 2023 08:36
@@ -38,6 +38,9 @@ runs:
username: ${{ inputs.registry_login }}
password: ${{ inputs.registry_token }}

- name: Install all tools
uses: ./.github/tools-cache
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just a thought, perhaps we should move all actions to actions

id: tools-cache
with:
path: ./tmp/bin
key: ${{ runner.os }}-tools-${{ hashFiles('./.github/tools-cache') }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

We need to may be hash hack/tools.sh instead. What ObO does is to create a '.github/tools` file see: https://github.com/rhobs/observability-operator/blob/main/.github/tools
The hash of that file is used to check of new binaries need to be downloaded.

Copy link
Collaborator

@sthaha sthaha left a comment

Choose a reason for hiding this comment

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

We need a file that can be hashed. I think using hacks/tools.sh may be sufficient even if that means any changes to tools.sh will result in binaries bring downloaded again. Or make tools.sh write the .github/tools files like ObO

@sthaha sthaha closed this Oct 17, 2023
@sthaha sthaha deleted the cache-tools branch October 17, 2023 08:00
@sthaha
Copy link
Collaborator

sthaha commented Oct 17, 2023

@vprashar2929 this got closed automatically because the branch was deleted. Can you please create a PR from your fork?

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