document how users should not edit Jenkins directly

Signed-off-by: Alfredo Deza <adeza@redhat.com>

diff --git a/README.rst b/README.rst
index 1a596645082ce0b0b2fdbb17c81c98a007f747c5..40cd1fcb35b44ec503abd860c072ee965f2b1243 100644 (file)
--- 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::