From c9d4f2c8d87115fe6cd48f586de82b252a357c45 Mon Sep 17 00:00:00 2001 From: Sam Thursfield Date: Fri, 30 Jan 2015 15:05:38 +0000 Subject: Remove all mention of Mason from trove-setup The Mason referred to here is the 1st version of the Mason continuous delivery tool. There have been no instances of this for two years. We have made two subsequent Mason implementations since then which don't require coupling in Trove in order to work. As well as removing unneeded configuration, this will fix the misleading warning that users see on Git pushes: remote: [git.baserock.org] Notifying Mason of changes... remote: [git.baserock.org] Notification failed somehow --- ansible/roles/trove-setup/tasks/gitano-mason-setup.yml | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100644 ansible/roles/trove-setup/tasks/gitano-mason-setup.yml (limited to 'ansible/roles/trove-setup/tasks/gitano-mason-setup.yml') diff --git a/ansible/roles/trove-setup/tasks/gitano-mason-setup.yml b/ansible/roles/trove-setup/tasks/gitano-mason-setup.yml deleted file mode 100644 index 8439078..0000000 --- a/ansible/roles/trove-setup/tasks/gitano-mason-setup.yml +++ /dev/null @@ -1,16 +0,0 @@ -# Depends on: -# - gitano-setup.yml ---- -- name: Check if mason has a sshkey configured in gitano (This task can fail) - shell: su git -c 'ssh git@localhost as mason sshkey' 2>&1 | grep WARNING - register: gitano_mason_key - changed_when: False - ignore_errors: True - -# If distbuild user doesn't have an sshkey configured -- file: path=/home/git/keys state=directory owner=git group=git - when: gitano_mason_key|success -- copy: src={{ MASON_SSH_PUBKEY }} dest=/home/git/keys/mason.key.pub mode=0644 - when: gitano_mason_key|success -- shell: su git -c 'ssh git@localhost as mason sshkey add trove < /home/git/keys/mason.key.pub' - when: gitano_mason_key|success -- cgit v1.2.1