Details
-
Improvement
-
Resolution: Outdated
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
Description
As presented at the 1st Open Mic session. Potentially helps with the following scenarios:
- light dev wants a custom webapp without getting involved with Maven
- marketplace should generate instances on the fly so people can test modules
- cloud instances should start Magnolia much faster by having the installation pre-done for them
- etc.
Flow
User initiates the new command, for instance:
$ mgnl jumpstart -s 6.2 --build // 6.2-SNAPSHOT
$ mgnl jumpstart --build // latest stable, 6.1.4 at time of writing
$ mgnl jumpstart -m 6.1.3 -d info.magnolia.abtesting:magnolia-abtesting:1.0-SNAPSHOT,info.magnolia.abtesting:magnolia-abtesting:1.0-SNAPSHOT // 6.1.3, --build is assumed
But what is the difference between jumpstart & jumpstart --build when no dependencies are specified?
- this option will require LDAP credentials to connect to Jenkins, so not available to all
- but, it will preinstall the webapp on Jenkins by default, which means it'll start much faster, especially if on a slow machine
Rely on the available webapps listed in the CLI
? What Magnolia would you like to install?
1) magnolia-empty-webapp
2) magnolia-community-webapp
3) magnolia-community-demo-webapp
4) magnolia-dx-core-webapp
5) magnolia-dx-core-demo-webapp
Answer:
Then the script runs its course (triggers job, waits for end of build, download the artifact once ready)
Then jumpstart will resume its normal course (fetch/install Tomcat, light dev. tweaks, etc.)
Then the user can run it with:
$ mgnl start
A note on downloadJars
This new feature is competing with the downloadJars custom option. We will keep that one for now but the documentation will be updated to reflect that if you have LDAP credentials, then you should get your webapp built.
Checklists
Attachments
Issue Links
- mentioned in
-
Page Loading...