From ed57f2eb8232e383ea4b8e7389e5c635f9816c94 Mon Sep 17 00:00:00 2001 From: Juan Antonio Osorio Robles Date: Thu, 28 Feb 2019 15:01:29 +0200 Subject: [PATCH] (queens only) Fix identation in README so we can do a release The following command was failing: python3 setup.py check --restructuredtext --strict This was preventing us from releasing for queens. This also adds a couple of jobs to our zuul layout... since none were matching. Change-Id: Ic830d22de4bed08d782a3f5c49163bb122016361 --- README.md | 1 + zuul.d/layout.yaml | 1 + 2 files changed, 2 insertions(+) diff --git a/README.md b/README.md index b42dd1ede..51487b153 100644 --- a/README.md +++ b/README.md @@ -62,6 +62,7 @@ We have five places we can do configuration in TripleO: Our current heuristic for deciding where to do any particular configuration step: + - per user config should be done from the outside via APIs, even for users like 'admin' that we know we'll have. Note that service accounts are different - they are a form of inter-node configuration. diff --git a/zuul.d/layout.yaml b/zuul.d/layout.yaml index 976f9a169..fc2b33d2f 100644 --- a/zuul.d/layout.yaml +++ b/zuul.d/layout.yaml @@ -4,6 +4,7 @@ - tripleo-multinode-baremetal-minimal - tripleo-multinode-container-minimal - release-notes-jobs + - release-notes-jobs-python3 post: jobs: - publish-openstack-python-branch-tarball