Use vuex to store the otaConfig, now the history configurations can be
reused in the job detail page. Also the targetBuilds, incrementalSources
are not stored in vuex as well. Once the targetBuilds are chosen, it
will not lose the states when switching the tab between singleOTA,
batchOTA and chainOTA.
Test: npm run test:unit
Change-Id: I563ac0c79fd0cedd5e71e8722b956545f6624551
The extra space in args['extra'] may cause the ota generation fail.
Test: python test_ota_interface.py -v
Change-Id: Iac6d06a89c52ab7554e54c08e5e04496b3da730a
Add test to two classes: BuildInfo and TargetLib. BuildInfo is a
dataclass which can store and parse Android Build informations from an
OTA package. TargetLib is a database interface which can be used to
store and extract BuildInfo.
Please refer to this CL for more details of these two classes:
https://android-review.googlesource.com/c/platform/development/+/1735315
Test: python test_target_lib.py -v
Change-Id: I3b2143af7f3708207b6c53744d903d3dcee92d55
The ProcessManagement helps initiate OTA generation processes and
monitor those processes. Add some test and comments to this class.
Please refer to:
https://android-review.googlesource.com/c/platform/development/+/1736940
for more details.
Test: python test_ota_interface.py -v
Change-Id: Ib22fca4c5a670f8b55db8a4175fef16d92eaceaf
Add testcases for ota_interface.JobInfo, which is used as object to
store task information and serve/read data to/from database.
Refer to:
https://android-review.googlesource.com/c/platform/development/+/1736940
for more details.
Test: python test_ota_interface.py -v
Change-Id: I74dcb16390078bd9258da490e21cb2b73dd78e81
The os.path.join() will bring in an unwanted backslash.
Test: Tested by starting a new OTA generation process by calling
ota_interface.ota_generate directly.
Test: python test_ota_interface.py -v
Change-Id: I8449eea79303f5aff5188176538eca1291101dff
Jest is a JavaScript test framework. Test-utils is used to test vue
components.
No-Typo-Check: auto-generated artifacts
Test: npm run test.
Change-Id: I2466687120b96a3a393299d127c6d7e1f15204e7
In a single page application, the url sometimes does not correspond to
the actual resources on the server. Thus, it might cause 404 when users
refresh the page. By redirecting this kind of url back to the homepage,
the proper page can be rendered. If the url does not exist, the front
end will redirect to a Not Found page.
Test: mannual tested.
Change-Id: I36beff436a450ae7fcabe9172df9c7cc217d7305
Previously, when multiple extra flags are set, the subprocess.run
can start generation properly. Now this is fixed.
Test: mannual tested.
Change-Id: Iab7275b9058a088d1fafd8c445c7f0775626c1ba
To upgrade from the Android version A to Android version D, one could
directly generate an OTA package from A to D. But chances are (a) this
OTA package can be large and unstable (b) there are multiple other
devices are on version B or C. So generation of chain OTA packages
(A-->B-->C-->D) can help life easier.
Users will be able to select and sort the Android build in
`ChainOTAOptions.vue` component, and submit multiple jobs at the same
time using a OTAConfiguration from `JobSubmission.js`.
Test: Mannual tested.
Change-Id: I9f16f981af80900c18a571162146ce218ea96387
Batch generation of OTA packages is a important feature
requested by googler and partners: please refer to go/ota-dashboard-doc.
Given n incremental source builds and m target builds,
batch generation will generate n x m OTA packages in total.
If n=0, full OTA package will be generated.
The front end will be taking in the source/target lists and send the
request to backend one-by-one.
Test: mannual tested.
Change-Id: I769359ee69c7aa8c71704c4e119c374635554dfb
Following part has been modified:
1. Add tabs for selection between single generation and batch
generation. (src/components/JobConfigure.vue)
2. Change the data structure of OTAConfiguration, now it only records
the flags. The source/target build will be provided when submit jobs.
(src/services/JobSubmission.js)
3. Seperate the OTAOptions as a single component, which only takes in
the flags for backend. The selection of source/target build will be in a
seperate component. (src/components/OTAOptions.vue,
src/components/SingleOTAOptions.vue).
4. Now the partition selection can takes in more than one build, but
only show the partition list of first one. Later on, this will be able
to show the intersection of the partition lists from all given builds.
(src/components/PartialCheckbox.vue)
Point 1 enables the possibility of the dynamical loading of single/batch
ota generation pages. Point 2,3,4 allow the OTAOptions components to
be reused for batch generation.
Test: Mannual tested.
Change-Id: I1a29fa7c605596d717d19da25d31b81ce5b8fcba
A variable name was mispelled and it could lead to jobs unable to be
started.
Test: Mannual tested.
Change-Id: I4067e2ae243428cb190463f55122b88d471f45f7
A complete set of flags for the CLI tool can be found in this script:
https://source.corp.google.com/android/build/make/tools/releasetools/ota_from_target_files.py
Now most of the flags are being added to the front end. However, there
are several TODOs:
1. flags that require extra arguements or file operations are not
supported yet.
2. the flags can depend or exclude on other flags. Dependency is
included in file 'JobSubmissions.js'-'OTAExtraFlags'. But the function
is not implemented yet.
Test: Mannual tested.
Change-Id: I3b6b76d48861cff81bfad86b549ff53f6536933b
Previously, the newly uploaded file cannot be shown immediately in the
datatable, unless refresh the page. Now the bug is fixed.
Similar bug is also fixed in OTAJobTable.vue.
Test: mannual tested.
Change-Id: Ia0531db884a7e1675b2cf51aeb8ca0847694c63c
Previously, the front end will generate a string for '--partial' flag.
Now the front end will only record the partial partitions that are going
to be updated as an array, and the backend will convert the array into a
string for CLI tool.
The output now is also calculated in the backend,
Test: mannual tested.
Change-Id: Ib5604e52b0c0d0cdd2bf85c71479b3133479da74
The original code for OTA configuration in the frontend is tightly
coupled and hard to maintain. This CL decoupled the job configuration
component (OTAOptions.vue), build library (BuildLibrary.vue) and job
submission (JobSubmission.js).
The BuildLibrary.vue will present the
target build list and take selections. Selections will be sent to
OTAOptions.vue, where flags are set. Once the setting is complete, an
OTAOption object defined by JobSubmission.js will be sent to the
backend. This design can be viewed in go/ota-dashboard-doc : detailed
design - TASK CONFIGURATION.
This has several benefits: (a) easier for
future maintainence. (b) The original code cannot easily be reused for
batch OTA package generation. Now, only the OTAOptions.vue has to be
modified for this purpose.
Test: Mannual tested. Unit tests will be added in following CLs.
Change-Id: I846d0c242cd6ed51478dd4d1a3e4c5fb8878aba1
Currently, users cannot choose build from the datatable directly, but
the datatable will give options to sort the builds uploaded and then
select from the sorted list.
Test: mannual tested.
Change-Id: If4e8ff7210a19170f7a7e6f77f03d21f6a10e6ac
1. The ordering in OTAJobTable was incorrect. Now fixed.
2. The JobDisplay card in JobList wasn't rendered correctly.
Test: Mannual tested.
Change-Id: I53d861fb60a623552487f957b42f4cd7404e654e
1. Changed the layout using material design ui in vuetify.
2. Changed the file upload to drag-and-drop style.
Test: Mannual tested.
Change-Id: I8b34a405ae3783d6806946f0adc5fc5ac9c30a49
The default entry point is /analyseOTA in production enviroment. This is
for the deployment on android.github.io/.
Test: Mannual tested.
Change-Id: Ic77277024b34b67b9964be8cf4f1592cebf5c5e8
Now the OTA_analysis is able to do statistics over how many blocks
are being operated by different types of COW merge operations.
Also refactor part of payload.js.
Test: Mannual tested.
Change-Id: Icd24f2c0aa42f968438965378b05a7021bafb88c
Now update_metadata.js will be able to parse COW merge operations in the
OTA packages. Please refer to change 1736935 for more details.
No-Typo-Check: auto-generated artifacts
Test: Mannual tested.
Change-Id: Ie18125524b991173b0599704eca51004fd0c0243
Now both OTA configuration and OTA analysis page support select/unselect
all partitions.
Test: Mannual tested.
Change-Id: I684912886f3d3da259aeafea6aea1e53ae4a1c9a
echarts_data.js will take the raw data and convert it into vue-echarts
readable option. PieChart.vue take this option and render it into a
pie chart.
Test: Mannual tested.
Change-Id: I54af3603031f0e23afa743ffc420d240a1b07bb2
payload_composition.js defines functions that could parse the
manifest of payload and do statistical analysis based on different
metrics. Currently, there are two functions:
1. Number of blocks (in target build) that are being operated,
categorized by the installation operations.
2. Disk usage of the payload.bin, categorized by the installation
operations.
The output is currently a list of pairs: (Operation, Number), which
can be later turned into input of visualized element.
Test: Mannual Tested.
Change-Id: I07defc23f6f04616656d8c9d3a7ecd05026bbbff
payload.js defines a Class that could parse the OTA metadata from
an OTA package(.zip). PackageAnalysis.vue enable users to upload
their own OTA package for analysis. PayloadDetail.vue and
OperationDetail will display the metadata in a human-readable way.
The whole analysis process is done on frontend and no communication
with server is involved after loading the page.
Test: Mannual tested.
Change-Id: I3becba872f6564ec9e44edad3a6cc19eb0714ed6
Use protobufjs to compile the update_metadata.proto
into update_metadata_pb.js
No-Typo-Check: auto-generated artifacts
Test: Mannual tested.
Change-Id: Ia0fefa57154f68809c8775ead9fa5e24d4804013
Add functions:
- Now the ota package generate history is stored in a database.
- Job status page will show some basic info of the jobs.
- Job detail page will show a detailed configuration.
Test: Mannual tested.
Change-Id: Ia98763e783e8d9c903ac8f5c137719df8527d204
New functions:
- The uploaded target files will be stored into a database.
- The detailed info of target files can be shown in the target library.
- Add support for generating partial OTA.
Test: Mannual tested.
Change-Id: Idf715994fe51b9ab6addbfe72792be890243702d
New functions:
- Can upload target file.
- Can select target file from the uploaded ones.
- Can download the generated OTA file.
- Can monitor the stdout during OTA package generation.
Also decoupled the job running function with the web server code.
Test: Mannual tested.
Change-Id: Ic525ef3997f048d73b21ad1d9475d54b1f8d112c
