You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running the actions-sync tool from a CronJob in K8s always results in an exception, while running the exact same command on local machine (Macbook Pro) always succeeds.
One thing I noticed is that it succeeds on the CronJob only when the organisation and repo are not existing before, so it creates them and works, but if org/repo are existing it fails.
Running the actions-sync tool from a CronJob in K8s always results in an exception, while running the exact same command on local machine (Macbook Pro) always succeeds.
Command I tried:
Results (inside CronJob):
On Macbook machine with exact same command:
One thing I noticed is that it succeeds on the CronJob only when the organisation and repo are not existing before, so it creates them and works, but if org/repo are existing it fails.
Used version: https://github.com/actions/actions-sync/releases/tag/v202009231612
Any idea what causes this discrepancy?
The text was updated successfully, but these errors were encountered: