Gaia/Build/NewBuildSystem: Difference between revisions

Jump to navigation Jump to search
Line 24: Line 24:
** New re-run step: in 2nd make, new build will check the change files and ENV to decide whether to regenerate all.mk or not, and then execute it.
** New re-run step: in 2nd make, new build will check the change files and ENV to decide whether to regenerate all.mk or not, and then execute it.
** Refactoring webapp-shared.js and copyToStage: based on new build system architecture, we'll refactor webapp-shared module and copyToStage into config and execute task in order to save time when re-run make and check if any possible risk before Milestone 2 (refactoring all build modules and app/build.js).
** Refactoring webapp-shared.js and copyToStage: based on new build system architecture, we'll refactor webapp-shared module and copyToStage into config and execute task in order to save time when re-run make and check if any possible risk before Milestone 2 (refactoring all build modules and app/build.js).
<bugzilla>
{
  "id": "1154582, 1154583, 1154585",
  "include_fields": "id, summary, assigned_to, status, resolution"
}
</bugzilla>


== Milestone 2 ==
== Milestone 2 ==
Line 34: Line 41:
** Refactoring all modules and app/build.js into small tasks and split each module into configuring + building steps.
** Refactoring all modules and app/build.js into small tasks and split each module into configuring + building steps.
** Implement config.status which will introduce DAG structure to configure step.
** Implement config.status which will introduce DAG structure to configure step.
<bugzilla>
{
  "id": "1154586, 1154587",
  "include_fields": "id, summary, assigned_to, status, resolution"
}
</bugzilla>


== Milestone 3 ==
== Milestone 3 ==
Confirmed users
429

edits

Navigation menu