xmik/ideide repository overview

⁠ideide

An ide docker image to test ide⁠.

It has installed:

• shpec
• bats
• docker daemon
• docker-compose

⁠Usage

⁠Debian based

Example Idefile:

IDE_DOCKER_IMAGE="xmik/ideide:3.0.2"
# --privileged is for docker daemon
IDE_DOCKER_OPTIONS="--privileged"

⁠Alpine based

Example Idefile:

IDE_DOCKER_IMAGE="xmik/ideide-alpine:3.0.2"
# --privileged is for docker daemon
IDE_DOCKER_OPTIONS="--privileged"

⁠Commands

Current directory in docker container is /ide/work and docker daemon is running. Example commands:

$ ide shpec
$ ide docker ps -a
$ ide docker-compose --version
$ ide bats --version

⁠Configuration

Those files are used inside ideide docker image:

1. ~/.ssh/config -- will be generated on docker container start
2. ~/.ssh/id_rsa -- if exists locally, will be copied
3. ~/.gitconfig -- if exists locally, will be copied

⁠Development and contributions

⁠Dependencies

• Bash
• Docker daemon
• Bats
• Ide

⁠Lifecycle

1. You make changes in a feature branch and git push it.
2. You build docker images and test them:

• ./tasks build
• ./tasks itest
• ./tasks build_alpine
• ./tasks itest_alpine

1. If you decide that your code is ready, create a PR. Your job as a contributor is done.

Then:

1. Maintainer merges PR(s) into master branch.
2. Maintainer runs locally:

• ./tasks bump to bump the patch version fragment by 1 OR
• e.g. ./tasks bump 1.2.3 to bump to a particular version Version is bumped in Changelog, variables.sh file and OVersion backend.

1. Everything is pushed to master onto private git server.
2. CI server (GoCD) tests and releases.
3. After successful CI server pipeline, maintainer:

• pushes master code to github
• triggers build on docker hub
• tags ideide-alpine image as xmik/ideide-alpine and pushes to docker hub