Skip to content
This repository has been archived by the owner on Feb 28, 2023. It is now read-only.

Merge all of our improvements upstream #155

Open
Xanewok opened this issue Mar 22, 2022 · 6 comments
Open

Merge all of our improvements upstream #155

Xanewok opened this issue Mar 22, 2022 · 6 comments

Comments

@Xanewok
Copy link
Contributor

Xanewok commented Mar 22, 2022

Since we forked, there has been some improvements made here but also we missed out on some of the PRs made against sccache (after the project got more action since the fork). This will be beneficial by getting new features/bug fixes but also will facilitate upstreaming some of our improvements as well.

@Xanewok Xanewok changed the title Decreate feature gap between sccache and cachepot Decrease feature gap between sccache and cachepot Mar 22, 2022
@Vovke Vovke added migration and removed migration labels Mar 22, 2022
@Xanewok Xanewok changed the title Decrease feature gap between sccache and cachepot Merge all of our improvements upstream May 11, 2022
@Xanewok
Copy link
Contributor Author

Xanewok commented May 11, 2022

We will be winding down cachepot as a separate project and instead plan to upstream all of our fixes to the sccache project, now that we have maintainer access and help maintain the crate and publish it. This issue tracks the required work.

@Xanewok Xanewok self-assigned this May 11, 2022
@TriplEight
Copy link
Contributor

TriplEight commented May 17, 2022

As proposed at the meeting:

MVP for sccache in CI/CD

Outside of MVP

  • distributed compilation for CI
  • encrypted/signed shared artifacts
  • undep OpenSSL Prune openssl #87
  • metrics support

Stuff not related to the CI use-case, but nonetheless important

  • distributed compilation for devs

cc @drahnr @kirushik

@equal-l2
Copy link

Hello, any progress in here?

@drahnr
Copy link
Contributor

drahnr commented Jun 24, 2022

@Xanewok will be chipping away on that in the long run, I'll be focused on merging and reviewing upstream PRs. So there is no timeframe right now when which fix will be upstreamed.

@abhiss
Copy link

abhiss commented Jul 27, 2022

We will be winding down cachepot as a separate project and instead plan to upstream all of our fixes to the sccache project, now that we have maintainer access and help maintain the crate and publish it. This issue tracks the required work.

Does this mean cachepot is basically deprecated and we should use sccache instead? I just want to confirm since it looks like this project is still fixing bugs and updating dependencies.

@Xanewok
Copy link
Contributor Author

Xanewok commented Aug 10, 2022

Yes, since sccache increased its dev bandwidth and we can actually upstream the work, I think it's fair to say you should use sccache now, as we merge our stuff there.

@jsdw jsdw unassigned Xanewok Feb 8, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants