mirror of
https://github.com/nektos/act.git
synced 2026-04-26 17:35:49 +03:00
[GH-ISSUE #839] Issue: dockerfile action is not able to set output variables #509
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#509
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @josecelano on GitHub (Oct 11, 2021).
Original GitHub issue: https://github.com/nektos/act/issues/839
I do not have the value of an output var from a previous step.
The action that generates the output var is a docker action. I can't use the next step.
It's working fine on the GitHub runner.
I've created a sample repo to reproduce the error: https://github.com/josecelano/act-output-bug
System information
act: catthehacker/ubuntu:act-latestactversion: 0.2.24Expected behaviour
I would expect the same output as on GitHub runner: https://github.com/josecelano/act-output-bug/actions/workflows/act-bug-workflow.yml
I expect the variable to be available in the next step (same job).
Actual behaviour
The output variable is empty.
Workflow and/or repository
Workflow: https://github.com/josecelano/act-output-bug
Repo: https://github.com/josecelano/act-output-bug
Steps to reproduce
actoutputLog
@ChristopherHX commented on GitHub (Oct 11, 2021):
Interesting,
This line indicates the output is interpreted correctly (https://github.com/nektos/act/blob/master/pkg/runner/command.go#L47) by act as command, this issue seems to be more complex.
This feature is implemented in act, however act refuses to rebuild an existing docker action image. So if you make changes to your dockerfile, act still uses the first one build unless you delete it with
docker image rm .....It does work with act-0.2.24-windows-x86_64 (also on master) on my machine (different docker image:
node:12.20.1-buster-slim) after editing the entrypoint of your action toENTRYPOINT ["sh", "/entrypoint.sh"], because act on windows seems to drop the exec permission of your entrypoint.shLog
This log indicates there is a different issue in windows
\mnt\c\Users\Christopher\act-output-bugdoesn't use the correct slash, while it doesn't impact the run.@github-actions[bot] commented on GitHub (Nov 11, 2021):
Issue is stale and will be closed in 14 days unless there is new activity