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.

Sign up for GitHub

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

Jump to bottom

Apply go module caching and build caching to Prow jobs #2466

Open
Tracked by #3104
chizhg opened this issue Sep 26, 2020 · 5 comments
Open
Tracked by #3104

Apply go module caching and build caching to Prow jobs #2466

chizhg opened this issue Sep 26, 2020 · 5 comments
Labels
kind/cncf-infra kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@chizhg
Copy link
Member

chizhg commented Sep 26, 2020

Istio Prow had some work on enabling go module cache and build cache, and got pretty good improvement on reducing the job running time, see the comments and descriptions in https://github.com/istio/test-infra/pulls?q=is%3Apr+cache.

Since it has been reported by some contributors that Prow is significantly slower than GitHub actions in build images, we should try if the same trick can be used to improve the performance of running Prow jobs for Knative.

/kind enhancement
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 25, 2020
@chizhg
Copy link
Member Author

chizhg commented Jan 24, 2021

/remove-lifecycle stale
/lifecycle frozen

@knative-prow-robot knative-prow-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 24, 2021
@chizhg chizhg reopened this Jan 24, 2021
@chizhg chizhg mentioned this issue Feb 28, 2022
Closed
14 tasks
@krsna-m
Copy link
Contributor

krsna-m commented Mar 3, 2022

/assign upodroid

@krsna-m
Copy link
Contributor

krsna-m commented Mar 3, 2022

/kind cncf-infra

@krsna-m krsna-m moved this to Ready To Work in Infra (Productivity) Mar 3, 2022
@krsna-m krsna-m moved this from Ready To Work to In Design/Discussion in Infra (Productivity) Jun 15, 2022
@chizhg
Copy link
Member Author

chizhg commented Jul 13, 2022

/priority backlog

@knative-prow knative-prow bot added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/cncf-infra kind/enhancement lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
Infra (Productivity)
Status: In Design/Discussion
Milestone
No milestone
Development

No branches or pull requests
4 participants
@chizhg @upodroid @knative-prow-robot @krsna-m