5 Commits (f153d0109d05fc8e530a663ca1fc6c78d0ab59bc)

Author	SHA1	Message	Date
Victor Seva	d2e6b1752a	TT#15305 build: provide end point to delete latest build of release-trunk-{distribution} ... * /build/release-trunk-{version}/ DELETE when we trigger the deletion of the repository, we should remove the non-finised instance of it, so we can later create another one Change-Id: Ie7e96aebfbe719dee4a9c6e1da25be08e6a38ab7	3 years ago
Victor Seva	1652418a6d	TT#121955 django.conf.urls.url() removed ... https://docs.djangoproject.com/en/3.2/internals/deprecation/#deprecation-removed-in-4-0 Change-Id: I6515688706f50422eb7751d305a8ed87ca0394e8	3 years ago
Victor Seva	44b0cdc640	TT#43813 fix RemovedInDjango20Warning issues ... This will help us when jumping to Django 2+ > /code/repoapi/urls.py:93: RemovedInDjango20Warning: Specifying a namespace in > django.conf.urls.include() without providing an app_name is deprecated. Set > the app_name attribute in the included module, or pass a 2-tuple containing the list of patterns > and app_name instead. > url(r"^build/", include("build.urls", namespace="build")), * py-test: set norecursedirs due to 'build' is in the default so build app was not included in the test * py-test: raise errors if warnings from Django are detected from repoapi Change-Id: Iab74024a435c1d7851cfe5a51f0ae54a044791a3	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