[GH-ISSUE #169 ] Support artifacts #111

Author

Owner

@SteadBytes commented on GitHub (Apr 2, 2020):

👍 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.

@SteadBytes commented on GitHub (Apr 2, 2020): :+1: 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.

kerem commented

Author

Owner

@cplee commented on GitHub (Apr 16, 2020):

Great call, good feature to add. Anyone have a sample workflow to use?

@cplee commented on GitHub (Apr 16, 2020): Great call, good feature to add. Anyone have a sample workflow to use?

kerem commented

Author

Owner

@jromero commented on GitHub (May 22, 2020):

This is use case we have in buildpacks/pack. We ultimately want to run test and build always and then use the artifacts for the release job.

The source can be found here:
Upload:
github.com/buildpacks/pack@c9745af053/.github/workflows/build.yml (L77-L81)

Download:
github.com/buildpacks/pack@c9745af053/.github/workflows/build.yml (L92-L104)

@jromero commented on GitHub (May 22, 2020): This is use case we have in [`buildpacks/pack`](https://github.com/buildpacks/pack/blob/master/.github/workflows/build.yml). We ultimately want to run test and build always and then use the artifacts for the release job. The source can be found here: Upload: https://github.com/buildpacks/pack/blob/c9745af053eabf812bf2fdab1695488a01022093/.github/workflows/build.yml#L77-L81 Download: https://github.com/buildpacks/pack/blob/c9745af053eabf812bf2fdab1695488a01022093/.github/workflows/build.yml#L92-L104

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Jul 22, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Jul 22, 2020): Issue is stale and will be closed in 7 days unless there is new activity

kerem commented

Author

Owner

@zaguiini commented on GitHub (Jul 22, 2020):

Is there any progress? Can I help with something?

@zaguiini commented on GitHub (Jul 22, 2020): Is there any progress? Can I help with something?

kerem commented

Author

Owner

@jromero commented on GitHub (Jul 22, 2020):

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?

@jromero commented on GitHub (Jul 22, 2020): 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?

kerem commented

Author

Owner

@krailler commented on GitHub (Jul 22, 2020):

How works actions/cache? Seems similar no?

@krailler commented on GitHub (Jul 22, 2020): How works actions/cache? Seems similar no?

kerem commented

Author

Owner

@wyTrivail commented on GitHub (Aug 6, 2020):

we also have the same issue while using upload-artifacts, we got the error

[CI/build]   💬  ::debug::Root artifact directory is /github/workspace/build
[CI/build]   ❗  ::error::Unable to get ACTIONS_RUNTIME_TOKEN env variable
[CI/build]   ❌  Failure - Upload

it would be great if it can be mocked.

@wyTrivail commented on GitHub (Aug 6, 2020): we also have the same issue while using upload-artifacts, we got the error ``` [CI/build] 💬 ::debug::Root artifact directory is /github/workspace/build [CI/build] ❗ ::error::Unable to get ACTIONS_RUNTIME_TOKEN env variable [CI/build] ❌ Failure - Upload ``` it would be great if it can be mocked.

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Oct 6, 2020):

Issue is stale and will be closed in 7 days unless there is new activity

@github-actions[bot] commented on GitHub (Oct 6, 2020): Issue is stale and will be closed in 7 days unless there is new activity

kerem commented

Author

Owner

@wagenet commented on GitHub (Oct 13, 2020):

Seems like this should have remained open. It's a pretty big blocker for full use.

@wagenet commented on GitHub (Oct 13, 2020): Seems like this should have remained open. It's a pretty big blocker for full use.

kerem commented

Author

Owner

@ayozemr commented on GitHub (Dec 9, 2020):

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

@ayozemr commented on GitHub (Dec 9, 2020): 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

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Jan 16, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Jan 16, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@ayozemr commented on GitHub (Jan 18, 2021):

Still waiting for this :-(

@ayozemr commented on GitHub (Jan 18, 2021): Still waiting for this :-(

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jan 19, 2021):

It's a bit complicated since https://github.com/nektos/act/issues/329

@catthehacker commented on GitHub (Jan 19, 2021): It's a bit complicated since https://github.com/nektos/act/issues/329

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Feb 19, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Feb 19, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@nicolo-ribaudo commented on GitHub (Feb 19, 2021):

Sorry bot, I hate to just 👍 issues

@nicolo-ribaudo commented on GitHub (Feb 19, 2021): Sorry bot, I hate to just :+1: issues

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Mar 22, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Mar 22, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@CreMindES commented on GitHub (Mar 22, 2021):

Sorry bot, I hate to just +1 issues, but it's necessary in this case.

@CreMindES commented on GitHub (Mar 22, 2021): Sorry bot, I hate to just +1 issues, but it's necessary in this case.

kerem commented

Author

Owner

@github-actions[bot] commented on GitHub (Apr 23, 2021):

Issue is stale and will be closed in 14 days unless there is new activity

@github-actions[bot] commented on GitHub (Apr 23, 2021): Issue is stale and will be closed in 14 days unless there is new activity

kerem commented

Author

Owner

@Smana commented on GitHub (Jun 10, 2021):

Hey, we still need a solution, either an artifact server or a mock.

@Smana commented on GitHub (Jun 10, 2021): Hey, we still need a solution, either an artifact server or a mock.

kerem commented

Author

Owner

@catthehacker commented on GitHub (Jun 10, 2021):

@Smana see #329

@catthehacker commented on GitHub (Jun 10, 2021): @Smana see #329

kerem commented

Author

Owner

@volleynerd commented on GitHub (Jun 24, 2021):

👍 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.

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.

@volleynerd commented on GitHub (Jun 24, 2021): > 👍 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. 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.

kerem commented

Author

Owner

@JoshMcCullough commented on GitHub (May 16, 2023):

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 act call. I'm using act-js.

NM, I see this now on the related PR: --env ACTIONS_RUNTIME_TOKEN=foo must be set (we do not have authentication implemented)

@JoshMcCullough commented on GitHub (May 16, 2023): 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 `act` call. I'm using act-js. NM, I see this now on the related PR: `--env ACTIONS_RUNTIME_TOKEN=foo` must be set (we do not have authentication implemented)

kerem commented

Author

Owner

@mcascone commented on GitHub (Aug 15, 2024):

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 act call. I'm using act-js.

NM, I see this now on the related PR: --env ACTIONS_RUNTIME_TOKEN=foo must be set (we do not have authentication implemented)

i set this, using foo (probably incorrect), and now I get:
Error: authentication required

@mcascone commented on GitHub (Aug 15, 2024): > 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 `act` call. I'm using act-js. > > NM, I see this now on the related PR: `--env ACTIONS_RUNTIME_TOKEN=foo` must be set (we do not have authentication implemented) i set this, using `foo` (probably incorrect), and now I get: `Error: authentication required`

kerem commented