Skip to content
Tiny clustered build server that aims to be customizable without relying on third party plugins.
Java HTML Other
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
gradle/wrapper
polymer
script
src
.travis.yml
Dockerfile
LICENSE
README.md
build.gradle
gradlew
gradlew.bat
preview.webp
zapperfly.yaml

README.md

zapperfly-asm Build Status

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

alt text

Installing

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

To save the default configuration to file (optional)
./zapperfly --configure
Add users with the following command.
./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'.

To start it all up, run the following on each host.
./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.

If you want to build it yourself, clone this repository with git and run:
./gradlew archiveZip

Run with docker

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:///.

Features 😎

  • 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.

Background

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. 🐇

Makes use of

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

License

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

See: LICENSE.md

Contributing

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

donate

You can’t perform that action at this time.