Eclipse Community Forums: Oomph » Accessing location of setup file during setup

Help

Home

Home » Eclipse Projects » Oomph » Accessing location of setup file during setup

Show: Today's Messages :: Show Polls :: Message Navigator

Accessing location of setup file during setup [message #1817250]

Tue, 19 November 2019 09:32

Victor Toni

Messages: 20
Registered: July 2009

Junior Member

We are using self-contained project repositories including configuration of CI/CD and for the future the Oomph setup file (allowing different configurations per branch if required).
The first thing to do is to clone the repository and then use the included setup file to install the IDE and import the projects.
Importing projects is automated insofar that the user has to provide the "correct" paths to the common root of the projetcs before all projects are imported automatically

The information about the repository could be deduced from the location of the setup file as it is part of the repository containing the projects to import.

I would prefer to not require the user to provide the location.
Is this information (path of setup file) accessible somehow?

Report message to a moderator

Re: Accessing location of setup file during setup [message #1817430 is a reply to message #1817250]

Fri, 22 November 2019 05:42

Eike Stepper

Messages: 6690
Registered: July 2009

Senior Member

Why don't you let Oomph clone the repository in the first place? That would be the common approach abd then the clone location would be know to Oomph and you could use it in subsequent tasks.

AFAIK the location of the physical setup models is not available to tasks at perform time.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator

Re: Accessing location of setup file during setup [message #1821730 is a reply to message #1817430]

Wed, 19 February 2020 09:04

Victor Toni

Messages: 20
Registered: July 2009

Junior Member

Sorry for the late response.

As said the Oomph setup is part of the repository so the repository comes first _always_.
There are multiple reasons for that:

The setup is versioned. Means if something has to be changed on a given branch all settings / plugins are available for setting up the IDE for this special branch.
This seems to work better than a central Oomph file since changes there seem to be reflected to all installations based on the file (which is good for most cases just not for us for the time being)
Cloning git with the tools Oomph / Eclipse provides is/was terrible slow and took hours (roughly 300-400 projects) whereas using command-line git seems to have been limited by bandwidth only and was magnitudes faster.
So everybody used CLI git to avoid hours of waiting. Since we cloned the repo manually the benefit of using Oomph for that was non-existent and adding the Oomph setup itself to the repo was logical (now we have IDE setup, CI/CD setup and code in the same repo and everything is matching all the time).
Some (main) branches need their own set / version of plugins (this seems like repeating 1) but is still different)

3) proved to be a bit more difficult because since it seems there is some kind of ID matching. So we actually needed two distinct configurations.
One with a fixed version of a given plugin and one free to install the latest version.

Report message to a moderator

Previous Topic:	Update to remove a feature
Next Topic:	Oomph provisioning Eclipse features

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Sep 19 19:01:39 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter