Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/factisresearch/Frozone
blazingly fast continuous integration and delivery using docker
https://github.com/factisresearch/Frozone
Last synced: about 1 month ago
JSON representation
blazingly fast continuous integration and delivery using docker
- Host: GitHub
- URL: https://github.com/factisresearch/Frozone
- Owner: factisresearch
- License: mit
- Created: 2014-07-02T16:24:21.000Z (over 10 years ago)
- Default Branch: master
- Last Pushed: 2014-08-06T14:46:17.000Z (over 10 years ago)
- Last Synced: 2024-08-02T05:12:25.165Z (4 months ago)
- Language: Haskell
- Homepage:
- Size: 976 KB
- Stars: 2
- Watchers: 5
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-blazingly-fast - Frozone - blazingly fast continuous integration and delivery using docker (Haskell)
README
[](https://travis-ci.org/factisresearch/Frozone)
Frozone
=====
We're building Frozone to replace our Jenkins Continuous Integration system. Frozone will enable a team of developers to check source code changes by compiling the project and running the unit tests before the changes get commited to a collaboration repository. Frozone will be enable to automatically deploy and run those changes for review by other developers and the QA team. The reviewers will be able to review the changes and accept or reject them.
Using docker the developers can fully describe the system needed to run a program including the distribution (Ubuntu 14.04), packages that need to be installed (apt-get install nodejs), the libraries that are required (npm install bloomfilter) and all needed configuration. Even though a clean build of the complete system might take an hour Frozone will be able to give feedback about your changes much faster by using an intelligent cache that depends on the build description. For our project we're aiming to get feedback for most cases in less than 2 minutes.
Frozone is far from alpha quality and heavily under development. This is a description of what it will look like when we reach alpha quality. We're fast coders so stay tuned!
# Install
* From Source:
Check the Dockerfile located at ./docker/Dockerfile
* Docker:
```bash
git clone https://github.com/factisresearch/Frozone.git
cd Frozone
docker build --rm -t [your_name_here]/frozone docker
```
# Run
* Docker
```bash
docker run -v /var/run/docker.sock:/var/run/docker.sock -v $(which docker):$(which docker) -d -p 8080:8080 [your_name_here]/frozone
```
* Without docker
```bash
./Frozone [config_file]
```
# Usage
In your development repository, you'll need a `.frozone.yml` where you define your cook-file directory, your entry point and boring file. Example:
```yml
cookDir: server/cook
entryPoint: 07_fullbuild.cook
boringFile: .boring
```
(For more information on this, see [dockercook](https://github.com/factisresearch/dockercook))
Then write your cook files. To upload a darcs patch from your repository to Frozone, this script will help you:
```bash
#!/bin/bash
if [[ "$1" == "" || "$2" == "" || "$1" == "--help" || "$1" == "-h" ]]; then
echo "USAGE: $0 YOUR-EMAIL TARGET-REPO"
exit 1
fi
REPO=$2
EMAIL=$1
FROZONE_HOST="http://localhost:8080" # ADJUST THIS!
PATCHFILE="/tmp/bundle-$RANDOM.dpatch"
darcs send $REPO -o $PATCHFILE
echo "Uploading patches ($PATCHFILE) to $FROZONE_HOST ..."
RESP=$(curl --form "email=$EMAIL" --form "target-repo=$REPO" --form "patch-bundle=@$PATCHFILE" -s "$FROZONE_HOST/bundle/check")
if [[ $RESP == *message* ]]
then
echo "Ready. You'll be notified at $EMAIL"
else
echo "Some shit happened. Check the frozone log!"
fi
rm -rf $PATCHFILE
```
Send patches to Frozone by calling this script.
# Todo
* Continous deployment
* Hooks (Post-success, etc.)