From: Alfredo Deza Date: Fri, 5 Feb 2016 18:02:50 +0000 (-0500) Subject: document how users should not edit Jenkins directly X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=3bef7617c3a0207ba80522cca055a10d0c239001;p=ceph-build.git document how users should not edit Jenkins directly Signed-off-by: Alfredo Deza --- diff --git a/README.rst b/README.rst index 1a5966450..40cd1fcb3 100644 --- a/README.rst +++ b/README.rst @@ -32,7 +32,9 @@ Enforcement The rules and structure for the builds are *strictly* enforced. If the convention is not followed, the builds will not work. -Changing Jenkins jobs in Jenkins is **strongly** discouraged. +Changing Jenkins jobs in Jenkins is **strongly** discouraged. Changing +something in the Jenkins UI does not guarantee it will persist and will +probably be overwritten. By default, this is how a directory tree would look like for a build for a project called ``foo`` that uses every choice available::