Conversation
Signed-off-by: Javier Rodriguez <javier@chainloop.dev>
| run: source <(/usr/local/bin/chainloop_bin/c8l source) && chainloop_collect_logs_for_github_jobs | ||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| # - name: logs |
There was a problem hiding this comment.
did you have a chance to look into the possible root cause?
Do you know if these logs are then chainloop att add'ed?
There was a problem hiding this comment.
I was reading the other day that it could be due to several reasons, including a lack of permissions in the token or the resource not being ready.
The point is that I've ran the same command locally with a failed pipeline and it works.
There was a problem hiding this comment.
So token then? I believe we made some changes in the permissions to support slsa, that might be the reason, that we are generating a token that doesn't have enough permissions?
Is that a PAT or an OIDC token?
There was a problem hiding this comment.
I've compared two Workflow files, one successful and another failing, there are no difference in them:
- Good: https://github.com/chainloop-dev/chainloop/actions/runs/15214098832/workflow
- Bad: https://github.com/chainloop-dev/chainloop/actions/runs/15214604803/workflow
The one failing is the GitHub token but I don't see any difference in permissions.
2 participants
This patch deactivates the logs retrieval from the GitHub workflow until we figure out why it's not working as it used before.