Skip to content
Permalink
Browse files

Add AUTHORS, update install for release builds

  • Loading branch information...
dnsmichi committed Aug 17, 2014
1 parent 4665360 commit a078f1d16e3e3be3f70f047d632107317c497dc4
Showing with 45 additions and 0 deletions.
  1. +5 −0 .mailmap
  2. +2 −0 AUTHORS
  3. +1 −0 README.md
  4. +37 −0 doc/installation.md
@@ -0,0 +1,5 @@
<gunnar.beutner@netways.de> <gunnar@beutner.name>
<gunnar.beutner@netways.de> <gunnar@blade9.beutner.name>
Gunnar Beutner <gunnar.beutner@netways.de> <icinga@net-icinga2.adm.netways.de>
<michael.friedrich@netways.de> <michael.friedrich@gmail.com>
<michael.friedrich@netways.de> <Michael.Friedrich@netways.de>
@@ -0,0 +1,2 @@
Michael Friedrich <michael.friedrich@netways.de>
Valentino Gagliardi <valentino.g@servermanaged.it>
@@ -3,6 +3,7 @@
### What is an Ansible role?

Ansible roles are pre-packaged units of automation. Once downloaded, roles can be dropped into Ansible PlayBooks and immediately applied to servers.
For details checks [doc/about.md](doc/about.md).

## Documentation

@@ -0,0 +1,37 @@
# Installing Icinga 2 Ansible Roles

Put them into your roles directory and refresh the configuration.

## Building Release Tarballs

In order to build a release tarball you should first check out the Git repository
in a new directory. If you're using an existing check-out you should make sure
that there are no local modifications:

$ git status

Here's a short check-list for releases:

* Update the .mailmap and AUTHORS files
$ git log --use-mailmap | grep ^Author: | cut -f2- -d' ' | sort | uniq > AUTHORS
* Bump the version.
* Update the ChangeLog and doc/about.md files.
* Commit these changes to the "master" branch and create a signed tag (tags/v<VERSION>).
$ git commit -v -a -m "Release version <VERSION>"
$ git tag -u EE8E0720 -m "Version <VERSION>" v<VERSION>
$ git push --tags
* Merge the "master" branch into the "support/2.0" branch (using --ff-only).
$ git checkout support/2.0
$ git merge --ff-only master
$ git push origin support/2.0
* Bump the version to "v<NEXT-VERSION>-dev" and commit this change to the "master" branch.

Use "git archive" to build the release tarball:

$ VERSION=2.0.0
$ git archive --format=tar --prefix=icinga2-ansible-$VERSION/ tags/v$VERSION | gzip >icinga2-ansible-$VERSION.tar.gz

Finally you should verify that the tarball only contains the files it should contain:

$ VERSION=2.0.0
$ tar ztf icinga2-ansible-$VERSION.tar.gz | less

0 comments on commit a078f1d

Please sign in to comment.
You can’t perform that action at this time.