4 Commits (e9e2833f357ceed583cf27770209fd6e1236dfab)

Author	SHA1	Message	Date
Victor Seva	872af3822a	TT#43813 build: split settings per application ... Using https://django-appconf.readthedocs.io/en/latest/ helps us to keep configs per application Change-Id: I8b69f421bcafe5e93dd8029063496e0e32ef9595	6 years ago
Victor Seva	e6a6f46e26	TT#43813 build: support resume from panel ... * move build_resume logic to a task * move build_resume logic tests to test_task Change-Id: I6eafc2d0af14174cce7c96fa35998b63d6545f47	6 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	6 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	9 years ago