4 Commits (87eff997b093e585cf9ee137a8ea893e2992c9d9)

Author	SHA1	Message	Date
Victor Seva	87eff997b0	TT#43813 properly do steps for POOL_SIZE ... Change-Id: I6a67c23c2ebbcc0c4b26d41190b150b69641733e	5 years ago
Victor Seva	9ef5a238a3	TT#43813 support changes on build_deps in the middle of a release ... * added mr8.1.2 and data to test it * don't add project as failed for piuparts job with FAILURE status Change-Id: I95a8bdbf5a73b4f353d99bc172f879a90870e1f0	5 years ago
Victor Seva	f138c5f067	TT#43813 build: improvements ... * smart build release reading per release metadata file provided by sipwise-repos-scripts-data package * build release will trigger settings.RELEASE_JOBS jobs first * old build process hidden at /release_panel/old/ as a fallback just in case * some examples of config/<release>.yml files just for test * style changes by black pre-commit plugin to unify code style * rework panel.js to support both views /release/ and /release_uuid/ via $.release.uuid value * cosmetic improvements Change-Id: I5f581100e6c297a1cc0abc4bb1ddf978870b6936	5 years ago
Victor Seva	2cf5b8da53	TT#15305 build release REST API ... * using https://github.com/manosim/django-rest-framework-api-key for Permissions. Will generate an Auth KEY for jenkins to be able to trigger build from there using build REST API * store the info needed to trigger builds for a set of projects for a release - build is a list of projects to be built with branch or tag as orig and release as destination for a debian distribution * added release_uuid to JenkinsJobInfo model - release_uuid is the way to group project builds for a release - tag works for group of jobs for a project Change-Id: Iebeaa54308c3e569a167f55d98c184b52248af8a	8 years ago