Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/gtramontina/docker-semantic-release
An image for https://github.com/semantic-release/semantic-release
https://github.com/gtramontina/docker-semantic-release
docker docker-image git node semantic-release
Last synced: 10 days ago
JSON representation
An image for https://github.com/semantic-release/semantic-release
- Host: GitHub
- URL: https://github.com/gtramontina/docker-semantic-release
- Owner: gtramontina
- Created: 2018-01-04T10:50:14.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2024-02-24T09:48:01.000Z (9 months ago)
- Last Synced: 2024-10-15T04:44:23.286Z (23 days ago)
- Topics: docker, docker-image, git, node, semantic-release
- Language: Makefile
- Size: 528 KB
- Stars: 7
- Watchers: 2
- Forks: 1
- Open Issues: 23
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Docker image for semantic-release
---
#### _Running:_
```sh
$ docker run --rm gtramontina/semantic-release:
```
**Note**: Because running `semantic-release` alone automatically runs the application, the default command in this image is `--help`. If you want to actually run `semantic-release`, run the above command with your set of arguments, or simply `--` if no arguments are needed, like so:
```sh
$ docker run --rm gtramontina/semantic-release: --
```
**Note 2**: You'll need to mount your `git`-based project in the container, as well as the necessary environment variables. The example below mounts the current directory as `/app` in the container and sets it as the working directory (`-w`). It also sets the required `GH_TOKEN` and `NPM_TOKEN` environment variables (because we're using the default verification/publication settings).
```sh
$ docker run --rm \
-w /app \
-v $(pwd):/app \
-e GH_TOKEN=$GH_TOKEN \
-e NPM_TOKEN=$NPM_TOKEN \
gtramontina/semantic-release:
```
**Note 3**: If you're running `semantic-release` in Travis, AppVeyor or any other CI environment, remember to forward the relevant environment variables to your container. The following example forwards Travis' variables:
```sh
$ docker run --rm \
-w /app \
-v $(pwd):/app \
-e GH_TOKEN=$GH_TOKEN \
-e NPM_TOKEN=$NPM_TOKEN \
-e TRAVIS_COMMIT=$TRAVIS_COMMIT \
-e TRAVIS_BUILD_NUMBER=$TRAVIS_BUILD_NUMBER \
-e TRAVIS_BRANCH=$TRAVIS_BRANCH \
-e TRAVIS_JOB_NUMBER=$TRAVIS_JOB_NUMBER \
-e TRAVIS_PULL_REQUEST=$TRAVIS_PULL_REQUEST \
-e TRAVIS_REPO_SLUG=$TRAVIS_REPO_SLUG \
-e TRAVIS_BUILD_DIR=$TRAVIS_BUILD_DIR \
gtramontina/semantic-release:
```
At the time of this writing, `semantic-release` was making use of [`env-ci`](https://github.com/pvdlg/env-ci) to detect CI environments. Take a look at the [environment variables it uses for your CI](https://github.com/pvdlg/env-ci/tree/master/lib) so you can forward them to your container.
---
#### _Developing:_
```sh
$ make build # Builds a new image
$ make test # Runs/tests the image
$ make push # Pushes the image up
$ make clean # Removes any generated artifacts
$ make clobber # Removes artifacts and generated images
```
---
🐳