Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Story Points:20
-
Epic Link:
-
Team:SQuaRE
Description
Motivated by the deviation seen from build 156 to 157 in https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package), and other deviations seen later as well, we want to show the list of packages that changed in the current build with respect to the previous build and link to the the git commit URLs to easily identify what caused that deviation.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Status | To Do [ 10001 ] | In Progress [ 3 ] |
Story Points | 2 | 4 |
Description | Motivated from the deviation seen from build 156 to 157 in https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package) we can show the list of packages that changed in the current build with respect to the previous build by comparing the git commit shas and return a list of tuples with the package name and git url. | Motivated by the deviation seen from build 156 to 157 in https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package) and other deviations seen later as well, we want to show the list of packages that changed in the current build with respect to the previous build by comparing the git commit shas and return a list of tuples with the package name and git url. |
Description | Motivated by the deviation seen from build 156 to 157 in https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package) and other deviations seen later as well, we want to show the list of packages that changed in the current build with respect to the previous build by comparing the git commit shas and return a list of tuples with the package name and git url. | Motivated by the deviation seen from build 156 to 157 in https://squash.lsst.codes/AM1 (caused by a commit in meas_algorithms package), and other deviations seen later as well, we want to show the list of packages that changed in the current build with respect to the previous build and link to the the git commit URLs to easily identify what caused that deviation. |
Attachment | screenshot-1.png [ 28569 ] |
Story Points | 4 | 10 |
Attachment | screenshot-1.png [ 28569 ] |
Attachment | Screen Shot 2016-10-27 at 7.58.55 PM.png [ 28584 ] |
Story Points | 10 | 14 |
Attachment | Screen Shot 2016-11-06 at 7.04.24 AM.png [ 28598 ] |
Attachment | Screen Shot 2016-10-27 at 7.58.55 PM.png [ 28584 ] |
Story Points | 14 | 20 |
Resolution | Done [ 10000 ] | |
Status | In Progress [ 3 ] | Done [ 10002 ] |
Summary | Show the list of packages that changed from build to build linked to the git url of the latest commit | List the code changes from job to job and link the package names with the corresponding git url |
Another motivation to work on this issue now is that the jobs api endpoint returns the whole list of packages for each build.
http://sqr-009.lsst.io/en/latest/#the-dashboard-api
Instead, we should have another API endpoint to retrieve just the necessary data to feed the metrics app. Example:
api/measurements (return required information for all measurements)
The api/jobs?ci_dataset filter should be implemented in this new endpoint as well. Example:
api/measurements/?ci_dataset='chft' (return required information only for cfht data set measurements)
In addition each result will include only the packages in the current build that differs from the packages in the previous build for comparison, reducing the information retrieved.
The git_url, the git_commit and the git_branch will also be returned.
Expected results:
Note that api/jobs still will be used to ingest data from validate_drp.