Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "ALF/Build Use Cases"
(→Build with IT Compliance Audit) |
(→Build a Change Request) |
||
| Line 1: | Line 1: | ||
| + | = Assumptions = | ||
| + | These Build Use Cases assume that an SCM tool or another process has populated the build area and source code locations with the appropriate files to be involed in the build. To keep inline with the ALF Service Flow process the Build portion of the Service Flow will be notified to start running. The pre and post processing will be handled by the complete Service Flow which is constructed by the End Users. | ||
| + | |||
| + | * Best Practice Build Service Flow needed. | ||
| + | |||
== Build a Change Request == | == Build a Change Request == | ||
The problem management tool would provide the change request info which would execute a check out of the corresponding code from the SCM tool. The SCM tool would request an incremental build of only the changes or request a full build. The build results upon success would be checked back into SCM tool via an ALF notification. On failure, the problem management tool and development team would be notified. | The problem management tool would provide the change request info which would execute a check out of the corresponding code from the SCM tool. The SCM tool would request an incremental build of only the changes or request a full build. The build results upon success would be checked back into SCM tool via an ALF notification. On failure, the problem management tool and development team would be notified. | ||
| − | |||
== Build a Requirement == | == Build a Requirement == | ||
Revision as of 13:36, 19 June 2006
Contents
Assumptions
These Build Use Cases assume that an SCM tool or another process has populated the build area and source code locations with the appropriate files to be involed in the build. To keep inline with the ALF Service Flow process the Build portion of the Service Flow will be notified to start running. The pre and post processing will be handled by the complete Service Flow which is constructed by the End Users.
- Best Practice Build Service Flow needed.
Build a Change Request
The problem management tool would provide the change request info which would execute a check out of the corresponding code from the SCM tool. The SCM tool would request an incremental build of only the changes or request a full build. The build results upon success would be checked back into SCM tool via an ALF notification. On failure, the problem management tool and development team would be notified.
Build a Requirement
The requirement tool would provide the enhancement request info which would execute a check out of the corresponding code from the SCM tool. The SCM tool would request an incremental build of only the changes or request a full build. The build results upon success would be checked back into SCM tool via an ALF notification. On failure, the requirements tool and development team would be notified.
Change Request Impact Analysis
The change request tool would provide the change request info which would execute a check out of the corresponding code from the SCM tool. The SCM tool would request an impact analysis report and return he information to the Change Request tool.
Audit Build for Non-approved components
The SCM tool would request a build that displays all components not managed within the SCM repository. The build would execute with dependency gathering, listing all components that were used in the build, but not managed within the SCM repository and return he report to the SCM tool.
Build with IT Compliance Audit
The SCM tool would request a build that created a audit trail showing all components used in the compile/link process and create a footprint validating matching source to executables. The footprint would be embedded in the executables and the executables would be checked back into the SCM tool.
Reproduce Build
The SCM tool would request a build of source used in a previous (historical) build. A build label or timestamp would be used to determine which files are to be included in the build.