Equal configurations lead to different workflows #25715
-
Hi, I have two projects with pretty much the same action and workflow configurations but their workflow is not the same. One of them works as expected. It checks out master, and then runs the workflow. The container is built inside “Test” and the entrypoint is run there too: In the other one, the docker container is first built, then it performs a checkout that overwrites some changes that were made in the dockerfile and then tries to run the containter entrypoint. The container is built previous to the checkout, and not in “Test”. The entrypoint is run in “Test” but fails because it expects some changes in files that were done in the dockerfile but are overwritten by the checkout: As you can see, the workflows are not the same. However, the config files are the following: The correct one:
The problematic one:
I really can’t figure out what is making it behave differently and haven’t found any other post mentioning this… |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I ended up figuring it out by my self but I wanted to post it anyway in case someone has the same issue. The difference is that the correct one uses a relative path while the wrong one uses an absolute path:
This makes it behave differently and overwrite any changes made in the dockerfile. |
Beta Was this translation helpful? Give feedback.
I ended up figuring it out by my self but I wanted to post it anyway in case someone has the same issue. The difference is that the correct one uses a relative path while the wrong one uses an absolute path:
- uses: some_user_name/app/.github/actions/test_on_master_push@master
This makes it behave differently and overwrite any changes made in the dockerfile.