-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support artifacts #169
Comments
👍 for supporting artifacts. Or at the very least it could be helpful to produce an explicit warning/error when these actions are used. AFAICT, a step using the artifact actions will succeed but no artifact will be uploaded/downloaded. |
Great call, good feature to add. Anyone have a sample workflow to use? |
This is use case we have in The source can be found here: |
Issue is stale and will be closed in 7 days unless there is new activity |
Is there any progress? Can I help with something? |
Typically these artifacts are shipped via the gh API and then referenced by url. I don't know how other parts, if any, work with mocking or intercepting GH API calls but I would think that is necessary to properly mock this locally. Am I wrong? |
How works actions/cache? Seems similar no? |
we also have the same issue while using upload-artifacts, we got the error
it would be great if it can be mocked. |
Issue is stale and will be closed in 7 days unless there is new activity |
Seems like this should have remained open. It's a pretty big blocker for full use. |
Artifacts is one of those key actions that many workflows use, and bc of that its a blocker for local dev working... Having this along with cache support would make act the tool we all need to fully develop workflows locally, instead of running workflows to try things and waiting a lot of time |
Issue is stale and will be closed in 14 days unless there is new activity |
Still waiting for this :-( |
It's a bit complicated since #329 |
Issue is stale and will be closed in 14 days unless there is new activity |
Sorry bot, I hate to just 👍 issues |
Issue is stale and will be closed in 14 days unless there is new activity |
Sorry bot, I hate to just +1 issues, but it's necessary in this case. |
Issue is stale and will be closed in 14 days unless there is new activity |
Hey, we still need a solution, either an artifact server or a mock. |
The above is not true for me. Running 0.2.23 and seeing actions/upload-artifact fail with error ::error::Unable to get ACTIONS_RUNTIME_TOKEN env variable Agree that this is a great idea to support the goal - for typical workflows that run fine in GH will run in ACT without modification. |
I know this feature exists now, but I'm still getting the "unable to get ACTIONS_RUNTIME_TOKEN" error. I wonder if I'm missing something? I set up the artifact path/port in my NM, I see this now on the related PR: |
i set this, using |
was getting the same error , discovered I can pass GitHub token into the with: element of the step , remembering to keep in mind that the token in this case is stored in a secrets file act --secret-file ./act/act.secrets -W ./.github/workflows/deploy_dev.yml
|
It would be really helpful if artifacts could be supported
The text was updated successfully, but these errors were encountered: