From 5b2c06b3da44dfb503413aa7cc9469c4d0e77f4f Mon Sep 17 00:00:00 2001 From: Major Hayden Date: Tue, 9 Jun 2020 16:30:00 -0500 Subject: [PATCH] Use environment variables to control Ansible Ansible configuration can be managed by an `ansible.cfg` ini file, but setting up that file and ensuring it's always in the same place is difficult. Configure Ansible via environment variables instead. Signed-off-by: Major Hayden --- schutzbot/Jenkinsfile | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/schutzbot/Jenkinsfile b/schutzbot/Jenkinsfile index 3cf09330b..526d65800 100644 --- a/schutzbot/Jenkinsfile +++ b/schutzbot/Jenkinsfile @@ -4,6 +4,18 @@ pipeline { environment { AWS_REGION = "us-east-2" AWS_BUCKET = "imagebuilder-jenkins-testing-use2" + // Colorful Ansible always looks nicer. + ANSIBLE_FORCE_COLOR="True" + // Time each task and display stdout as YAML (easier to read). + ANSIBLE_LOAD_CALLBACK_PLUGINS="True" + ANSIBLE_CALLBACK_WHITELIST="profile_tasks" + ANSIBLE_STDOUT_CALLBACK="yaml" + // Don't display those ugly purple deprecation warnings. + ANSIBLE_DEPRECATION_WARNINGS="False" + // Our host keys are constantly changing. + ANSIBLE_HOST_KEY_CHECKING="False" + // Enable ssh pipelining for faster deployments to remote nodes. + ANSIBLE_PIPELINING="True" } options {