Plugins release automation

dLobatog · July 27, 2015, 4:17pm

Hi -dev,

The other day I spent some time writing a simple bash script to automate
foreman-docker releases so that the only input would be the version
number, name and email:

github.com

theforeman/foreman-docker/blob/master/release/rollout-release

#!/bin/bash

GITHUB_TOKEN=$(cat ~/.codereview)
RED='\e[31m';
BLUE='\e[44m';
GREEN='\e[32m';
PLUGIN_DIR=$(pwd)
DATE="$(date +'%a %b %d %Y')"

echo -e "${GREEN} foreman-docker releaser $1\033[0m"
echo -e "--------------------------"
echo -e "${BLUE} Part 1: Rubygems $1\033[0m"
echo -e "--------------------------"
echo -e "${GREEN} Current version: $(grep VERSION lib/foreman_docker/version.rb) $1\033[0m"
echo -e "${GREEN} -- Checking out branch master $1\033[0m"
hub checkout master --quiet
if [ $? -ne 0 ]; then
  echo -e "${RED} -- Error checking out master branch. Aborting... \033[0m"
  exit 1
fi

This file has been truncated. show original

All it does is:

Change version.rb and tag repo, submit to rubygems.org
Modify RPM spec and submit pull-request
Modify deb sources and submit pull-request

It has a lot of room for improvement, but I think it'd be possible for
other plugins (especially if they don't maintain 2 separate main
versions) to take it. Thoughts?

···

-- Daniel Lobato Garcia

@eLobatoss
blog.daniellobato.me
daniellobato.me

GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato

lzap · July 29, 2015, 9:55am

> It has a lot of room for improvement, but I think it'd be possible for
> other plugins (especially if they don't maintain 2 separate main
> versions) to take it. Thoughts?

Nice. But as long as there is no dry run, I would be too scared to try
it out.

···

-- Later, Lukas #lzap Zapletal