Extra-simple clustered build servers for continuous integration. Minimal configuration required, installation is as simple as starting a Java application. Demo video!

Download the latest release from releases, unpack where you want to run it.

./zapperfly --configure

./zapperfly --user --name <userName> --pass <userPassword> --role <admin|user>

--pass: if omitted a random password will be generated.

--role: if omitted the role will default to 'user'.

./zapperfly --start --group <groupName> --name <instanceName> --website <port, default 443>

--group: specifies the virtual group for the instances, different groups will not cluster together.

--name: the name of the instance as displayed in the website or when listing available executors.

--website: starts the graphical user interface on port 443, or the specified port.

./gradlew archiveZip

Run the following command to build the docker image

gradlew archiveZip && docker build -f Dockerfile build/distributions

Running the container

docker run -it -p 5701:5701 -e ZAPPER_PWD=secret <image-id>

-p is optional, required for clustering. increase the first port in the pair for each container.

-e is optional, ZAPPER_PWD is the password of the 'root' user. if unset the default password is blank.

Once the container is started the web interface is available on https:///.

• build scheduling over multiple hosts
• real time log monitoring
• running the build sersver in a docker container.
• running builds in docker containers.
• tune workload per instance based on number of parallel builds.
• support for role-base authentication
• basic plugin system for integrations

There are three levels of authorization,

• admin: may add build configurations and edit existing. (is also an user)
• user: may view build logs and start builds.
• public: may view the build queue and build history - no build logs.

Build servers are often hard to setup and involves some serious configuration overhead. The purpose of the zapperfly assembly server is to provide the simplest build server experience there is, with clustering. To simplify installation, minimal environmental dependencies are required. An optimal installation experience should include no more than installing Java. We aim to make the core product small enough so that you can modify it according to your own needs. 🐇

This project makes use of chili-core, which means that vertx and hazelcast is on your classpath. What a boon!😵🌟

The MIT License (MIT) Copyright (c) 2018 Robin Duda

See: LICENSE.md

pull requests, code reviews, feature suggestions and more welcome. 😸 🌸