Deis Builder v2
Deis (pronounced DAY-iss) Workflow is an open source Platform as a Service (PaaS) that adds a developer-friendly layer to any Kubernetes cluster, making it easy to deploy and manage applications on your own servers.
For more information about Deis Workflow, please visit the main project page at https://github.com/deis/workflow.
We welcome your input! If you have feedback, please submit an issue. If you'd like to participate in development, please read the "Development" section below and submit a pull request.
About
The builder is primarily a git server that responds to git push
es by executing either the git-receive-pack
or git-upload-pack
hook. After it executes one of those hooks, it takes the following high level steps in order:
- Calls
git archive
to produce a tarball (i.e. a .tar.gz
file) on the local file system
- Saves the tarball to centralized object storage according to the following rules:
- If the
DEIS_OUTSIDE_STORAGE
environment variable exists, saves to the S3 API compatible server at https://$DEIS_OUTSIDE_STORAGE
- Starts a new Kubernetes Pod to build the code, according to the following rules:
- If a
Dockerfile
is present in the codebase, starts a dockerbuilder
pod, configured to download the code to build from the URL computed in the previous step.
- Otherwise, starts a
slugbuilder
pod, configured to download the code to build from the URL computed in the previous step.
Development
The Deis project welcomes contributions from all developers. The high level process for development matches many other open source projects. See below for an outline.
- Fork this repository
- Make your changes
- Submit a pull request (PR) to this repository with your changes, and unit tests whenever possible
- If your PR fixes any issues, make sure you write
Fixes #1234
in your PR description (where #1234
is the number of the issue you're closing)
- The Deis core contributors will review your code. After each of them sign off on your code, they'll label your PR with
LGTM1
and LGTM2
(respectively). Once that happens, a contributor will merge it
Docker Based Development Environment
The preferred environment for development uses the go-dev
Docker image. The tools described in this section are used to build, test, package and release each version of Deis.
To use it yourself, you must have make installed and Docker installed and running on your local development machine.
If you don't have Docker installed, please go to https://www.docker.com/ to install it.
After you have those dependencies, grab Go dependencies with make bootstrap
, build your code with make build
and execute unit tests with make test
.
Native Go Development Environment
You can also use the standard go
toolchain to build and test if you prefer. To do so, you'll need glide 0.9 or above and Go 1.6 or above installed.
After you have those dependencies, you can build and unit-test your code with go build
and go test $(glide nv)
, respectively.
Note that you will not be able to build or push Docker images using this method of development.
Testing
The Deis project requires that as much code as possible is unit tested, but the core contributors also recognize that some code must be tested at a higher level (functional or integration tests, for example).
The end-to-end tests repository has our integration tests. Additionally, the core contributors and members of the community also regularly dogfood the platform. Since this particular component is at the center of much of the Deis platform, we find it especially important to dogfood it.
Running End-to-End Tests
Please see README.md on the end-to-end tests reposotory for instructions on how to set up your testing environment and run the tests.
Dogfooding
Please follow the instructions on the official Deis docs to install and configure your Deis cluster and all related tools, and deploy and configure an app on Deis.
License
Copyright 2013, 2014, 2015, 2016 Engine Yard, Inc.
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.