Use a function instead of find to delete all job's config.xml

Find recurse into all the directories under the jenkins home to
find the jobs/XXXX/config.xml files. Instead, a method recursing only
into jobs folder let us skip all other directories (builds,
configurations, etc...). This slowness was not discovered on staging
because staging has less way build that the prod instance.

Tested for speed on the jenkins master without deleting the files
(just echoing)

Tested for correctness by deploying to staging.

Change-Id: Ife41c7dcb035c967eda6c3f33b01b8d66bbc8ec5
1 file changed
tree: bd7adfae74080ae0b1a4881710b6d834b06272a6
  1. base/
  2. docs/
  3. gce/
  4. gcr/
  5. gerrit-github-sync/
  6. jenkins/
  7. mac/
  8. templating/
  9. .gitignore
  10. AUTHORS
  11. CONTRIBUTING.md
  12. CONTRIBUTORS
  13. LICENSE.txt
  14. README.md
  15. WORKSPACE
README.md

Bazel continous integration setup

This workspace contains the setup for the continuous integration system of Bazel. This setup is based on docker images built by bazel.

Make sure you have a Bazel installed with a recent enough version of it. Also make sure gcloud and docker are correctly configured on your machine. Only docker version 1.10 or later is supported.

More documentation:

  • init.sh: initializes the whole CI platform. This may delete VMs and do other irreversible changes, so handle with care.
  • vm.sh: lets you control the machines (e.g. start/stop them, create/delete/reimage them), including the Jenkins controller and the executor nodes.
  • workflow: explains the CI workflow, and how you can test local changes with jenkins-staging
  • jobs: explains what jobs are running on the CI