Skip to content

Commit 710fe9a

Browse files
authored
Merge pull request #3 from quartx-analytics/dev
Dev
2 parents c12b801 + 7522f32 commit 710fe9a

File tree

1 file changed

+8
-14
lines changed

1 file changed

+8
-14
lines changed

README.md

Lines changed: 8 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ steps:
1717

1818
- id: mender
1919
name: Create mender artifact
20-
uses: quartx-analytics/mender-docker-compose@v1.1.1
20+
uses: quartx-analytics/mender-docker-compose@v1.1.2
2121
with:
2222
compose-file: "docker-compose.yml"
2323
software-name: "project-name"
@@ -26,10 +26,11 @@ steps:
2626
compose-file-variables: "IMAGE_TAG=latest" # Optional
2727

2828
- name: Upload mender artifact
29-
uses: actions/upload-artifact@v2
29+
uses: quartx-analytics/mender-artifact-uploader@v1.0.0
3030
with:
31-
name: mender-artifacts
32-
path: ${{ steps.mender.outputs.artifact-file }}
31+
artifact: ${{ steps.mender.outputs.artifact-file }}
32+
username: ${{ secrets.MENDER_USER }}
33+
password: ${{ secrets.MENDER_PASS }}
3334
```
3435
Here we specify the filename for the docker compose file, the file that contains all the details required to
3536
build the docker container(s).
@@ -39,20 +40,13 @@ The artifact will not work on any other device but what is specified.
3940
A signing-key can also be specified if required, this will ensure that the artifact has not been changed after creation.
4041
It will also force the artifact to only work on the mender server that contains the corresponding private key.
4142
42-
GitHub's upload-artifact action can then be used to upload the created artifact to GitHub.
43-
Support for variables within the docker compose file is supported. See [here](https://docs.docker.com/compose/environment-variables/) for how to use compose file variables.
44-
The variables can be passed in using the "compose-file-variables" input key. The format is "NAME=VARIABLE", multiple variables are separated by a space.
45-
46-
GitHub's upload-artifact action can be used to upload the created artifact to GitHub.
47-
48-
49-
## Where does the upload go?
50-
At the bottom of the workflow summary page, there is a dedicated section for artifacts.
43+
We can then our other action that can upload the mender artifact to a mender server.
44+
See [upload-artifact](https://github.com/actions/upload-artifact)
5145
5246
5347
# Notes
5448
For the artifact to work on mender, all mender devices need to have docker compose installed.
55-
The docker-compose update module from this repo also needs to be placed in the
49+
The `docker-compose` update module from this repo also needs to be placed in the
5650
`/usr/share/mender/modules/v3` directory on all your mender devices.
5751

5852

0 commit comments

Comments
 (0)