Is your feature request related to a problem? Please describe.
Nearly every one of the CI workflows in ledgersmb/LedgerSMB fails, due to the fact that the action fails to download texlive.tlpdb (See https://github.com/ledgersmb/LedgerSMB/actions/runs/20163032528/job/57879723680#step:3:271).
Describe the solution you'd like
Since almost all jobs in our workflow download this file, chances of failure are huge. Ideally, the first job downloads it and all further jobs can use it. However, there's no way to instruct the action to re-use a file downloaded in the same workflow in a prior job.
I'm envisioning to tell one job to download and cache the file (and preferably the rest of the tinytex installation) and thereafter instructing to use the cached version, asking setup-tinytex to initialize the environment, but nothing more.
Describe alternatives you've considered
I have considered to do the caching and environment initialization myself. There are two problems with that, as far as I can tell: (1) the fact that caching is disabled for workflows to cache outside of the working directory - or so I believe; and (2) I'll have to look inside the setup-tinytex action to correctly set the PATH environment variables (and possibly others), which I'd rather not because I'll break the separation of concerns.
Additional context
https://github.com/ledgersmb/LedgerSMB/actions/runs/20163032528/job/57879723680#step:3:271
Is your feature request related to a problem? Please describe.
Nearly every one of the CI workflows in ledgersmb/LedgerSMB fails, due to the fact that the action fails to download texlive.tlpdb (See https://github.com/ledgersmb/LedgerSMB/actions/runs/20163032528/job/57879723680#step:3:271).
Describe the solution you'd like
Since almost all jobs in our workflow download this file, chances of failure are huge. Ideally, the first job downloads it and all further jobs can use it. However, there's no way to instruct the action to re-use a file downloaded in the same workflow in a prior job.
I'm envisioning to tell one job to download and cache the file (and preferably the rest of the tinytex installation) and thereafter instructing to use the cached version, asking setup-tinytex to initialize the environment, but nothing more.
Describe alternatives you've considered
I have considered to do the caching and environment initialization myself. There are two problems with that, as far as I can tell: (1) the fact that caching is disabled for workflows to cache outside of the working directory - or so I believe; and (2) I'll have to look inside the setup-tinytex action to correctly set the PATH environment variables (and possibly others), which I'd rather not because I'll break the separation of concerns.
Additional context
https://github.com/ledgersmb/LedgerSMB/actions/runs/20163032528/job/57879723680#step:3:271