| Deploy with Buckminster [message #809477] |
Tue, 28 February 2012 18:10  |
Eclipse User |
|
|
|
Does anyone use Buckminster to deploy?
Currently I use Buckminster in eclipse, and headlessly in Jenkins.
Now I need to write a small p2 installer that gets a few properties from a wizard and installs and deploys the application.
So I'm wondering if this can all be done with buckminster?
If so, what is the best way? I have a few ideas but I don't know if I'm on the right track.
Method 1
1. Ship the installer with a non-deployed workspace
2. Copy the workspace to the machine (temp directory).
3. Get properties from wizard and deploy to the temp workspace.
4. Create a temp p2 from the temp workspace.
5 Finally, install the deployed product from the p2.
Method 2
1. Ship the installer with a non-deployed p2
2. Materialize a temp workspace from the p2 (temp directory).
3. Get properties from wizard and deploy to the temp workspace.
4. Create a temp deployed p2 from the workspace.
5 Finally, install the product from the temp deployed p2.
Am I on the right track?
Is there a better way to do it?
Thanks in advance
|
|
|
| Re: Deploy with Buckminster [message #809575 is a reply to message #809477] |
Tue, 28 February 2012 21:25  |
| Eclipse User |
|
|
|
Interested to hear about what functionality in Buckminster you are
interested in during the deploy.
There are other technologies that may be of interest.
- there is the EPP Wizard which basically generates a p2 repository
based on selections in the wizard (or pre existing p2 IUs IIRC). The
wizard has a UI obviously, but the resulting repository is just a p2
repository.
- the b3 aggregator project has an EMF model of p2 which makes it very
easy to write a repository publisher (suitable for headless).
- the b3 aggregator itself which can be used to
aggregate/mirror/compose/rewrite p2 repsoitories. (It can run headless)
- the way the marketplace works - not up to date exactly how it works,
but basically it is UI that enables selection of what to install. Has
more meta data than just "vanilla" p2.
Hope that gives you some ideas potentially reusable technology.
Regards
- henrik
On 2012-29-02 24:10, Philip Bedingfield wrote:
> Does anyone use Buckminster to deploy?
>
> Currently I use Buckminster in eclipse, and headlessly in Jenkins.
>
> Now I need to write a small p2 installer that gets a few properties from
> a wizard and installs and deploys the application.
> So I'm wondering if this can all be done with buckminster?
> If so, what is the best way? I have a few ideas but I don't know if I'm
> on the right track.
>
> Method 1
> 1. Ship the installer with a non-deployed workspace 2. Copy the
> workspace to the machine (temp directory).
> 3. Get properties from wizard and deploy to the temp workspace.
> 4. Create a temp p2 from the temp workspace.
> 5 Finally, install the deployed product from the p2.
>
> Method 2
> 1. Ship the installer with a non-deployed p2
> 2. Materialize a temp workspace from the p2 (temp directory).
> 3. Get properties from wizard and deploy to the temp workspace.
> 4. Create a temp deployed p2 from the workspace.
> 5 Finally, install the product from the temp deployed p2.
>
> Am I on the right track?
> Is there a better way to do it?
>
> Thanks in advance
|
|
|
Powered by
FUDForum. Page generated in 0.03003 seconds
Home