Name: deisrel
Owner: Deis
Description: A releaser tool for Deis
Forked from: arschles/deisrel
Created: 2016-04-29 16:29:22.0
Updated: 2017-10-27 18:09:17.0
Pushed: 2017-05-10 20:50:09.0
Homepage: null
Size: 175
Language: Go
GitHub Committers
| User | Most Recent Commit | # Commits |
|---|
Other Committers
| User | Most Recent Commit | # Commits |
|---|
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 the 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.
deisrel is a utility tool for assisting with Deis product releases. It makes is easy to check what components need to be released before making a workflow release.
You can install the latest version of deisrel from the following links:
Alternatively, you can compile this project from source using Go 1.6+:
$ git clone https://github.com/deis/deisrel
$ cd deisrel
$ make bootstrap build
$ ./deisrel
Once done, you can then move the client binary anywhere on your PATH:
$ mv deisrel /usr/local/bin/
deisrel requires two files, the requirements.lock file from a Kubernetes Helm Workflow chart,
and a repository mapping file, allowing deisrel to map between a repository and chart name.
You may fetch the requirements.lock file from a given chart in the following manner:
$ helm repo add deis https://charts.deis.com/workflow
$ helm fetch --untar deis/workflow --version v2.9.0
$ cat workflow/requirements.lock
As the Workflow component list has stabilized, the repository mapping file (map.json) at the root of this project may be used. (However, it will need to be updated when/if the list changes.) The key is the repository name, and the value is the chart name, as found in the requirements.lock file.
With these two files, you can use deisrel to generate a report:
isrel path/to/requirements.lock path/to/repomapping.json
der v2.6.1 -> v2.7.1 (dirty)
builder has unreleased changes. See https://github.com/deis/builder/compare/v2.7.1...master
roller v2.10.0 -> v2.11.0 (dirty)
controller has unreleased changes. See https://github.com/deis/controller/compare/v2.11.0...master
base v2.5.0 -> v2.5.1 (clean)
erbuilder v2.5.2 -> v2.6.0 (clean)
ntd v2.6.0 -> v2.6.1 (clean)
er v2.4.1 -> v2.4.2 (clean)
o v2.3.4 -> v2.3.5 (clean)
tor v2.7.0 -> v2.7.1 (clean)
v2.2.5 -> v2.2.6 (clean)
s v2.2.4 -> v2.2.5 (clean)
stry v2.3.2 -> v2.3.3 (clean)
stry-proxy v1.1.1 -> v1.1.1 (dirty)
registry-proxy has unreleased changes. See https://github.com/deis/registry-proxy/compare/v1.1.1...master
stry-token-refresher v1.1.0 -> v1.1.1 (clean)
er v2.8.1 -> v2.9.0 (clean)
builder v2.4.8 -> v2.4.9 (clean)
runner v2.2.4 -> v2.2.4 (dirty)
slugrunner has unreleased changes. See https://github.com/deis/slugrunner/compare/v2.2.4...master
flow-manager v2.4.4 -> v2.4.5 (clean)
It's also possible to output the report in json using the -o json argument for easier machine parsing.
Github has a very low ratelimit for unauthenticated api requests. A “personal access token” can be used to bypass this restriction. Create a GitHub token with “repo” permission and set it to $GITHUB_ACCESS_TOKEN. deisrel will
use it when making requests.
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.
Fixes #1234 in your PR description (where #1234 is the number of the issue you're closing)LGTM1 and LGTM2 (respectively). Once that happens, a contributor will merge itCopyright 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.