Google Git
Sign in
coral / releases / cf4bb41ab943306bb2d74453cb4ed41bac67ad9f
commitcf4bb41ab943306bb2d74453cb4ed41bac67ad9f[log] [tgz]
authorJune Tate-Gans <jtgans@google.com>Fri Jul 24 08:58:42 2020 -0500
committerJune Tate-Gans <jtgans@google.com>Fri Jul 24 09:04:17 2020 -0500
tree45a18077edc0ad1b470d689885fc3939a36f5239
parent776084a0338099a3af8fd03a6017bf8c3037166e [diff]
release: Add in the eagle 5.0 release manifest and readme

This will allow us to generate reproducible builds using manifests generated by
Jenkins as we go.

Change-Id: Iaa2e219e25ae73907799ce448572e5c195b4592e
2 files changed
tree: 45a18077edc0ad1b470d689885fc3939a36f5239
  1. enterprise/
  2. README.md
README.md

Release Manifests

What is this?

This directory contains the repo manifests used to build a particular Mendel release. Each time an image is made from Jenkins, the resulting manifest snapshot is placed here to allow for reproducing the build on another machine.

How do I use this?

To make an earlier build with these manifests, simply copy the manifest you need out of this tree into your $ROOTDIR/.repo/manifest.xml and call repo sync to bring your tree up to date with those commits.

The general format of the paths are $BOARDNAME/$RELEASENAME-$RELEASEVER.xml, so to find the eagle 5.0 release for enterprise, you'd want to use the enterprise/eagle-5.0.xml release.