Workflow artifacts from forgejo runner not accessible from other workflows
Hi all, I have recently started using Forgejo runners and it's a great tool. I have run into this surprising limitation with accessing artifacts and I wonder if I am just doing something totally wrong?
If I use the artifacts within the same workflow file as per the tests: e2e test then this works as you would expect. But if you have two separate workflow files, so example one with a build step, and one with a deploy step. then the deploy step has no way to access the artifacts?
I also found an open issue which indicates that the github implementation for accessing the artifacts using a token is not currently possible either.
I am surprised I have not seen more people talking about this, so I wonder if I am just doing something really obviously wrong!
The fundamental part is that I am using uses: to specify the first stage from the other workflow file.
Where am I going wrong?
jobs:
build:
runs-on: docker
uses: ./.forgejo/workflows/build.yml
deploy:
needs: build
How's everything else getting to your storage from your main container? They don't share.
@[email protected] sorry to answer your actual question: Using https://data.forgejo.org/forgejo/upload-artifact@v4 and https://data.forgejo.org/forgejo/download-artifact@v4
@[email protected] The runner picks up the task and when they are in the same workflow file the tasks are executed on the same run_id (as far as I understand) which means when using download artifacts code: https://code.forgejo.org/forgejo/download-artifact/src/tag/v4/ the request for artifacts works correctly as the request has the right ID. But sadly when they are separate tasks it requests the wrong ID (as I understand) and the section in the readme about downloading from other workflow runs is incorrect as its just mirrored from github, and the run_id and token field is not implemented which is discussed in this ticket. But I am shocked that everyone is not running into this? Still think im being dumb...