Verify jenkins.war with sha256 instead of sha1

Jenkins provides a sha256 digest to verify the war file against [1] - we
should be using this instead of the sha1 we generate locally.

[1] https://get.jenkins.io/war-stable/2.222.4/

Bug: Issue 16464
Change-Id: Iecf430c110bbadecda73d98ee9b12d6f24379536
2 files changed
tree: f34c7847495e3c1146c1427c979e2d78f0592c1f
  1. jenkins/
  2. jenkins-docker/
  3. vars/
  4. worker/
  5. .gitignore
  6. Jenkinsfile
  7. README.md
  8. yamllint-config.yaml
README.md

Gerrit CI scripts

Providing jobs

This project uses Jenkins Jobs Builder [1] to generate jobs from yaml descriptor files.

To add new jobs reuse existing templates, defaults etc. as much as possible. E.g. adding a job to build an additional branch of a project may be as easy as adding the name of the branch to an existing project.

To ensure well readable yaml-files, use yamllint [2] to lint the yaml-files. Yamllint can be downloaded using Python Pip:

pip3 install yamllint

To run the linter, execute this command from the project's root directory:

yamllint -c yamllint-config.yaml jenkins/**/*.yaml

Yamllint will not fix detected issues itself.

[1] https://docs.openstack.org/infra/jenkins-job-builder/index.html [2] https://pypi.org/project/yamllint/