Browse Source

Get rid of references to Jenkins slaves

Update documents.

We also don't have a long-lived proposal node anymore, so the special
instructions there no longer apply.

Change-Id: I68ddfaff82fb71d35bddac5dc565b2569458ca6e
changes/48/529148/2
Monty Taylor 5 years ago committed by Andreas Jaeger
parent
commit
1a40e14379
  1. 13
      README.rst
  2. 19
      REVIEWING.rst

13
README.rst

@ -57,9 +57,9 @@ nodepool
========
This dir contains the nodepool scripts and nodepool disk image builder
elements that are used to build the images we boot slave nodes off of.
Edit these files if you need to modify the base images that Jenkins jobs
run on.
elements that are used to build the images we boot build nodes off of.
Edit these files if you need to modify the base images that Nodepool creates
for Zuul to run content on.
`Nodepool Documentation <http://docs.openstack.org/infra/system-config/nodepool.html>`_
@ -75,10 +75,9 @@ site.
zuul
====
This dir contains the zuul layout.yaml file and its python functions file(s).
These files determine what jobs are run on Gerrit events for each project.
Edit these files if you need to change the jobs that your project runs or
attributes of those jobs (voting, slave node type, etc).
This dir contains the zuul main.yaml file which defines the Zuul tenants
and the system-variables.yaml file which contains some global variables.
Edit these files to add, remove or rename a project from Zuul.
`Zuul Documentation <http://docs.openstack.org/infra/system-config/zuul.html>`_

19
REVIEWING.rst

@ -48,25 +48,6 @@ only enabled for projects that are in the Big Tent (mentioned in
governance repository). Similary, translation workflow is also only
enabled for Big Tent projects.
Proposal jobs
=============
Proposal jobs run on the long running proposal slave that has access
to the credentials that the jobs need to access Zanata and gerrit.
Jobs running there are the exception and need to be carefully reviewed
before approving them.
Here are some points to look at:
* First response should be: How else can we achieve this?
* Jobs can publish artifacts also to specific places, like
static.openstack.org or tarballs.openstack.org, and use these from
other jobs.
* Proposal jobs should not run arbitrary scripts from other
repositories or install untrusted packages.
Removing check-requirements job
===============================

Loading…
Cancel
Save