‘tree/<str:commit_hash>/full’ output is too big

[padovan]

For a linux-next branch test results, the size of the json file coming out of this API is about 4.6MB, however
only the testHistory bucket has 4.4MB and the bootHistory bucket 0.12MB. The data for the rest of the dict keys is quite small, so we could split this API endpoint into three endpoints:

• tree/<str:commit_hash>/status: It returns all the data returnedbyfull` except 'testHistory' and 'bootHistory' data
• tree/<str:commit_hash>/boot-history: It returns the Boot History dict
• tree/<str:commit_hash>/test-history: It returns the Test History dict

Edit:
Names have been updated to

tree/<commit>/summary
tree/<commit>/builds
tree/<commit>/boots
tree/<commit>/tests

The big tree/<hash>/full output is also causing a long delay in the Web Dashboard. With such a split we can quickly load all the status data and then take the time needed to download the history data and put it on the dashboard.

• create an endpoint for ‘tree/<str:commit_hash>/summary’ #719
• create an endpoint for tree/str:commit_hash/boots #720
• create an endpoint for tree/str:commit_hash/tests: #721
• tree/str:commit_hash/builds #722

[padovan]

time wget 'https://dashboard.kernelci.org/api/tree/d1486dca38afd08ca279ae94eb3a397f10737824/full?origin=maestro&git_branch=master&git_url=https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git'

real    0m6.700s
user    0m0.077s
sys    0m0.034s

This in the time it takes to get the data back. Of course there are db queries, but the download itself takes a few seconds.

[padovan]

Proposed names:

tree/<commit>/summary
tree/<commit>/builds
tree/<commit>/boots
tree/<commit>/tests

Also,

rename “TestHistory” -> “TestList”
rename “BootHistory -> “BootList”

[WilsonNet]

check if query parameters is viable