We've found that as the projects grow that having a weekly job to
refresh the JJB fails more often than it succeeds. As this can be done
as a manual process by the releng team it's better to just remove the
job than have it sit around failing.
Change-Id: I48d154d3cb459171f76526844ef6b64269982c42
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>
jobs:
- 'ci-management-verify-jjb'
- 'ci-management-merge'
- - 'ci-management-weekly'
project: 'ci-management'
- shell:
!include-raw-escape include-raw-jjb-update.sh
-- job-template:
- name: 'ci-management-weekly'
-
- # ci-management-weekly job to run JJB update weekly
- #
- # This job's purpose is to update all the JJB on a weekly (Sunday)
- # basis with --flush-cache enabled to ensure jobs are properly configured in Jenkins
-
- project-type: freestyle
- node: jjb
-
- logrotate:
- daysToKeep: 30
- numToKeep: 40
- artifactDaysToKeep: -1
- artifactNumToKeep: 5
-
- parameters:
- - project-parameter:
- project: '{project}'
-
- scm:
- - git-scm:
- credentials-id: '{ssh-credentials}'
- branch: 'master'
-
- wrappers:
- - ssh-agent-credentials:
- users:
- - '{ssh-credentials}'
-
- triggers:
- - timed: 'H H * * 0'
-
- builders:
- - shell: |
- jenkins-jobs --flush-cache update --recursive jjb/
-
-