Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Deploy Builds into Emulators

< DSDP‎ | MTJ

Back to main DSDP-MTJ Use Cases


Short description:

A Java developer has a need to deploy builds into emulators to test the code during the application development. The deployment to emulators is done number of times, often hundreds of times during a project. The deployment configuration information should be reusable.

Priority:

Owner:

Status: Proposed, Outlined

Proposed:|Accepted: date_here
Identified|Described|Outlined|Detailed

Community Review: review_date_here


Use Case Specification: Deploy builds into emulators


1. Brief Description

A Java developer has a need to deploy builds into emulators to test the code during the application development. The deployment to emulators is done number of times, often hundreds of times during a project. The deployment configuration information should be reusable. All the extra phases from the deployment should be removed.

A Java developer creates builds for different phones and deploys them straight into emulators. The Java developer creates builds from all the software versions he wants and the system creates builds from them. The system passes the builds straight into right emulators.


2. Flow of events

2.1 Basic Flow

B1: The system defines the available emulators for each software version/phone group based on device database.
B2: The user defines which builds should be used in the emulators.
B3: The user chooses to open the builds in the emulators.
B4: The system opens up the builds in the emulators.
B5: The system stores the information about the emulator deployment for reuse.

2.2 Alternative flows

Alternative flow 1: Transfer signed builds into emulators.
Alternative flow 2: User chooses the emulators to be used with the builds.


3. Special Requirements


4. Preconditions

4.1 The builds exist
The user has made the builds.

4.2 The device database exists with emulator information
There exists a device database with information about which emulators best fit with each device. This information can be modified by the user or the information can be overridden with user defined information.

4.3 The emulators are available
The emulators are available and they are integrated into Eclipse.


5. Post Conditions

5.1 The builds are opened in emulators
The system opens up the emulators for each build. The system opens up either one or several emulators per each build.

5.2 The emulator deployment procedure is reusable
The system remembers all the choices made during the deployment process: which builds are used with which emulators. In order to redo the build procedure the user can start it with just one click. The user can also modify the signing configuration if he wants.


6. Extension Points



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top