@@ -103,25 +103,21 @@ Example:
103103 id : generate-summary
104104 uses : cloudnative-pg/ciclops@<FULL_LENGTH_SHA>
105105 with :
106- artifact_directory : test-artifacts/da
106+ artifact_directory : test-artifacts
107107` ` `
108108
109109## How it works
110110
111- The files in this repository are needed for the Dockerfile to build and run, of
112- course. In addition, GitHub will copy the files in the **user's** GitHub
113- workflow location to the Dockerfile too. This is how the folder with the JSON
114- artifacts will get passed. When invoking with ` act`, we are simulating this with
115- the `-b` option.
111+ ` summarize_test_results.py` and its `requirements.txt` are needed for the
112+ Dockerfile to build and run.
113+ In addition, at runtime GitHub will copy the files in the **user's**
114+ ` GITHUB_WORKSPACE ` directory to the Dockerfile, by running the container with a
115+ bind mount similar to the following one :
116116
117- In the Dockerfile, the `COPY . .` line will include the directory with the
118- JSON test artifacts at build time.
119- See [GitHub support for Dockerfile](https://docs.github.com/en/actions/creating-actions/dockerfile-support-for-github-actions) :
120-
121- > Before the action executes, GitHub will mount the GITHUB_WORKSPACE directory
122- > on top of anything that was at that location in the Docker image and set
123- > GITHUB_WORKSPACE as the working directory.
117+ ` ` `
118+ -v "/home/runner/work/ciclops/ciclops":"/github/workspace"
119+ ` ` `
124120
125- **NOTE**: the behavior of the `COPY` command in Dockerfiles seems quite
126- finicky on whether it's done recursively or not. The invocation used,
127- ` COPY . . ` , ensures the copy is done recursively .
121+ and it will use that as the container's `WORKDIR`.
122+ This is how the folder with the JSON artifacts will get passed.
123+ When invoking with `act`, we are simulating this with the `-b` option .
0 commit comments