Actions
Cleanup #45823
openFeature #40907: mgr/dashboard: REST API improvements
mgr/dashboard: pipeline Back-end API Tests
Status:
New
Priority:
Normal
Assignee:
-
Category:
General - Back-end
Target version:
-
% Done:
0%
Tags:
Backport:
nautilus, octopus
Reviewed:
Affected Versions:
Pull request ID:
Description
Currently, when a dashboard PR (or potentially in any other component,as now API tests are run in octopus for every PR) is run, the following CI checks happen in Github:
make check
(Jenkins job: https://github.com/ceph/ceph-build/blob/master/ceph-pull-requests/build/build), which basically ends up creating binaries and other artifacts from the Ceph sourcesdashboard back-end api tests
: they need a "vstart.sh" cluster, which can ran either with compiled sources or RPMs. In this case it always run from compiled sources. However, as there's no pipelining in place, the artifacts built in the make check, are not reused, so a new whole build happens in parallel with the "make check" one.
One chance of improvement would be to add pipelining in Jenkins jobs, so that the "dashboard back-end API tests" are launched AFTER the make check has built all the sources (not need to wait for it to finish, as after building the sources it spends 10 mins running unit-tests), and reusing those binaries.
Several approaches can be followed from this on:- Post-build action (or any other dependency-related plugin) + copy artifacts from make check
- Jenkins pipelines
Updated by Ernesto Puerta almost 4 years ago
- Subject changed from mgr/dashboard: pipeline backend API tests to mgr/dashboard: pipeline Back-end API Tests
Updated by Ernesto Puerta about 3 years ago
- Project changed from mgr to Dashboard
- Category changed from 146 to General - Back-end
Actions