https://github.com/bbmoz/ci-docker
Self-hosted CI with Docker Registry and Minio Server
https://github.com/bbmoz/ci-docker
Last synced: over 1 year ago
JSON representation
Self-hosted CI with Docker Registry and Minio Server
- Host: GitHub
- URL: https://github.com/bbmoz/ci-docker
- Owner: bbmoz
- Created: 2017-07-03T01:58:23.000Z (almost 9 years ago)
- Default Branch: master
- Last Pushed: 2017-07-10T06:23:07.000Z (almost 9 years ago)
- Last Synced: 2025-01-29T15:50:47.218Z (over 1 year ago)
- Language: Shell
- Homepage:
- Size: 6.84 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# CI
> Self-hosted with Docker Registry and Minio Server
## Setup
```bash
setup.sh
```
**You will get a warning about missing environment variables. It may be a good idea to have a `.env` file that contains these variables which you can source.*
## Run
```bash
docker-compose up -d
```
## Pipeline
1. Install the `fly` CLI by going to `localhost:8080` and clicking the download link for your platform.
2. Create a new target for your CI.
```bash
fly -t login -c http://localhost:8080
```
3. Create your project's pipeline by following the [docs](https://concourse.ci/pipelines.html).
## Example
A simple example and a way to structure your CI pipeline is in `example/`. The important files to consider are the main `pipeline.yml` and its corresponding tasks, each of which have the files `task.yml` and `run.sh`.
To update your pipeline, make sure to push to the master branch if you made any task file changes and run:
```bash
fly -t sp -p -c example/pipeline.yml -l
```
**The `` can be anything, and the `` are variables you want to load into the `pipeline.yml`. For example, both `MINIO_ACCESS_KEY` and `MINIO_SECRET_KEY` are needed for the example pipeline.*