Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

(Journey) SJ3: Deploy a New Instance #25

Closed
5 tasks
grayside opened this issue May 25, 2021 · 0 comments
Closed
5 tasks

(Journey) SJ3: Deploy a New Instance #25

grayside opened this issue May 25, 2021 · 0 comments
Assignees
@grayside @dinagraves
Labels
component: delivery Related to automation, testing, deployment of the application. component: telemetry Related to metrics & usage data collection for project maintenance. persona: developer Developer, deployer, and incident manager of the app. priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: epic An Epic represents a collection of business requirements.
Milestone
v0.6.0

Comments

@grayside
Copy link
Collaborator

grayside commented May 25, 2021 •
edited by rogerthatdev
Loading

Description

As a technical practitioner, in order to experiment with the Emblem app, I want to easily and quickly deploy it using my own account. This should be completed within 15 minutes and set a clear expectation of wait time.

Note: 15 minutes is a ceiling and we should expect drop-off of completion or follow-up exploration beyond 5 minutes.

Phase 1 Requirements (v0.3.0)

  • Requiring only an empty project, a single script can be executed to bootstrap the project.
  • Deployment completes within 15 minutes, prefer 5-10 minutes to ensure we have space in the future

Phase 2 Requirements

  • Deploy with Cloud Shell makes a push-button option available
  • Deployment completion provides clear prompts to next steps, such as directing to filtered log views or launching a NEOS tutorial
  • We have deployment telemetry indicating how many unique deployed instances have been launched

Related Decision Records

<This section will be filled out as this journey's tasks pass through design>

Possible Future Enhancements

  • TBD
@grayside grayside added priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: epic An Epic represents a collection of business requirements. persona: developer Developer, deployer, and incident manager of the app. component: delivery Related to automation, testing, deployment of the application. component: telemetry Related to metrics & usage data collection for project maintenance. labels May 25, 2021
@grayside grayside changed the title (Journey) UJ1: Journey Title (Journey) SJ3: Deploy a New Instance May 25, 2021
@grayside grayside added this to the roadmap-2021Q2 milestone May 26, 2021
This was referenced May 27, 2021
Closed
Closed
@grayside grayside modified the milestones: roadmap-2021Q2, v0.3.0 Jun 10, 2021
This was referenced Jun 17, 2021
Closed
Closed
@dinagraves dinagraves modified the milestones: v0.3.0, v0.4.0 Jun 28, 2021
@grayside grayside modified the milestones: v0.4.0, v0.5.0 Jul 12, 2021
@grayside grayside mentioned this issue Jul 19, 2021
Closed
@grayside grayside mentioned this issue Sep 28, 2021
Closed
@grayside grayside modified the milestones: v0.5.0, v0.6.0 Dec 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@grayside grayside

@dinagraves dinagraves

Labels
component: delivery Related to automation, testing, deployment of the application. component: telemetry Related to metrics & usage data collection for project maintenance. persona: developer Developer, deployer, and incident manager of the app. priority: p0 Highest priority. Critical issue. P0 implies highest priority. type: epic An Epic represents a collection of business requirements.
Projects
None yet
Milestone
v0.6.0
Development

No branches or pull requests
2 participants
@grayside @dinagraves