[NPMCLI-52] Download enterprise bundles with jumpstart Created: 20/Sep/16  Updated: 05/Sep/17  Resolved: 21/Nov/16

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.5

Type: Improvement Priority: Critical
Reporter: Christopher Zimmermann Assignee: Federico Grilli
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to NPMCLI-138 Add support for Now bundles Closed
dependency
depends upon MGNLEE-473 Provide a magnolia-enterprise-standar... Closed
relation
is related to NPMCLI-55 Release CLI 1.0 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Sprint: Basel 71
Story Points: 3

 Description   

The CLI should provide an easy way to jumpstart EE and Now local development.

To specify: how this manifests in CLI.

Possible solution
Enable more parameters on the jumpstart command to specify ee and Now bundles.

  • -n indicates the user wants to download the Magnolia Now Tomcat bundle for local development. (no further -d, -ees or -eep is required.)
  • -d (with travel demo)
  • -ees (ee standard)
  • -eep (ee pro)

Reason: As our company depends on selling EE licenses, we should support EE users and encourage its use everywhere possible.
And we should make it available for Magnolia Now users.

Must be able to deliver enterprise-standard bundle before releasing, bundle must be created. See linked ticket.



 Comments   
Comment by Christoph Meier [ 20/Sep/16 ]

Probably this is a "duplicate" of NPMCLI-50 - maybe we should merge them czimmermann?

Comment by Christopher Zimmermann [ 20/Sep/16 ]

Thanks. I link them for now - and would consider merging them after discussion.

Comment by Federico Grilli [ 23/Sep/16 ]

As to the implementation, this package looks interesting https://www.npmjs.com/package/prompt
Also worth reading https://developer.atlassian.com/blog/2015/11/scripting-with-node/ which shows how to combine commander.js and other libs to obtain a prompt-like feature to ask for username/password

Comment by Christoph Meier [ 01/Oct/16 ]

I felt free to slightly change the description.

I wanted to make sure that is also required for Magnolia Now local development

And i was slightly changing the new possible parameters for the jumpstart command.
I think it is important that the user has not to prompt Maven artifactId or groupId or even both; such arguments are un-handy and error prone.
Just one additional param for the Now bundle would be cool! :-p
I'm also unsure whether tree letter arguments make sense. All other arguments are one-letter-only.
To distinguish between other ee bundles i'm still unsure.

Comment by Viet Nguyen [ 27/Oct/16 ]

Vote for cmeier, also a small suggestion is that could we use provided bundle or existing downloaded bundle from our local machine instead of always download it from our nexus. In case a user is trying with 2 or more lightdev instances, his network could be overloaded with downloading the same 'bundle' now (actually I am now).
Imho adding 2 below options would be useful:
-mvn <version> to use existing maven bundle locally or remotely
-local <path> to use existing local bundle

Comment by Federico Grilli [ 17/Nov/16 ]

Blocked until dependent issues are solved. Functionality is complete and tested, only thing missing is bundles to download, except for the pro-demo one.

Comment by Federico Grilli [ 21/Nov/16 ]

Released 1.0.5 and updated docu

Generated at Mon Feb 12 04:46:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.