Testing the source of docker.yml failure #45
Conversation
|
Interestingly, the last time this workflow ran successfully, it supplied In this workflow run and in #42, it's not: https://github.com/cometbft/cometbft-db/actions/runs/4373643991/jobs/7652076691#step:5:2 The action is the same version, and we're still supplying the parameters in the workflow itself: https://github.com/cometbft/cometbft-db/blob/main/.github/workflows/docker.yml#L59 Not sure why it's not propagating the parameters to the action though. Could be a bug in the action? |
|
I noticed! It's precisely why I opened this PR to see if I can manage to reproduce the CI failure in #42. Indeed it is not propagating the user/passwd parameters to the action. I can think of 2 other ways to continue debugging:
|
Did this in #46. Seems like the problem is related to the fork indeed. The user/passwd secrets get passed successfully in this PR, which is plain branch from this repo: https://github.com/cometbft/cometbft-db/actions/runs/4383442081/jobs/7673693619#step:5:2 Seems like this is the expected behavior: |
Ref: the CI docker failures in #42