Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [recommenders-dev] Simplified Workspace and IDE Setup

I’ve just added and preconfigured Mylyn Builds, Reviews and Bugzilla Connector to the master configuration.

With that version you should have three queries (Bugs, Help Wanted, and Reviews) as well as the build plans for our gerrit and regular builds in your IDE. Pretty neat I think. See the screenshot below how this looks like.

Best,
Marcel


Am 28.03.2014 um 12:03 schrieb Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>:

Forwarding Eike and Ed’s reply:


Hi Marcel,

finally I've had the time to test OOMPH, here are my results:
Hi Patrick,

Ed Merks and I have carefully studied all your comments and the log files you've attached. We appreciate a lot that you've taken the time to explain your concrete problems and your general feelings about Oomph. Please find our detailed comments below...


Fresh OS Installation / no SSH server keys stored (which was luckily the case):
A UnknownHostKey SSH error occurs (see unknownSshHost.log attached). Actually no big surprise, seems like OOMPH can't handle this.
This *could* be noteworthy for new CoRe developers, as they shouldn't have the Eclipse host SSH key.
We have tried hard to reproduce this problem but for us the "Unknown host" prompt comes up as expected. Then we've analyzed the respective JGit and JSch code:

        if (credentialsProvider != null
                && (!hc.isBatchMode() || !credentialsProvider.isInteractive())) {
            session.setUserInfo(new CredentialsProviderUserInfo(session,
                    credentialsProvider));
        }

For us there is a credentialsProvider and it is always interactive. The batch mode of the host configuration (hc) is false. We see two possible explanations for your problem:

1) Your credentialsProvider could be null because the EGit bundle hasn't been started yet. We've recently (March 25) added code to start the EGit bundle early, so this likely isn't the root cause, unless you have an older version of Oomph.

2) The host configuration appears to be populated from a ${user.home}/.ssh/config file. This file does not exist on our Windows machines, but if it existed it could configure the batch mode to be true. Do you have such a file and if so what does it look like?

Marcel has already submitted a bugzilla to track this issue:

    [Bug 431429] [Oomph] Git checkout fails due to unknown SSH host
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=431429


'demo-master' selection from the OOMPH installer menu:
Auth failure for the org.eclipse.recommenders.examples.git repository (see demoMasterFail.log attached)
In your log it appears that you specified "pgottschmmer" as your git/gerrit user ID rather than "anonymous". But the "xxxxxxxx..." in the log confuses us. You can't have specified an email address as the user ID because that would have resulted in an "UnknownHostException: xxxxxx@xxxxxxxxxxxxxxx". Why did you obfuscate the log?

Did you upload a public key to your "pgottschmmer" account on Gerrit?
If so, what's the name of your private key file?

When you do these Git/Gerrit things manually, how does that work out?


Several crashes during installation
I've needed 3 attempts until Oomph went through the installation without any critical crashes.
Are two of these three the above two problem that you've described in detail? If so, what was the third problem?

Unfortunately, Oomph didn't provide me any error logs, it just froze.
What task was it performing when it just froze?

Please note that Oomph writes a setup.log file in the branch folder (e.g., recommenders/master/setup.log), which sometimes has a little bit more detail.

In any case, are there clues in the Error Log (i.e., recommenders/master/ws/.metadata/.log)?


Besides these, I had no critical errors after installing the oomph distribution (setting the target platform for recommenders 'master' in the first way crashed, but that could have been a connection failure by me)
However, for me Oomph isn't an suitable alternative to a 'classical' Eclipse setup due to the following reasons:
  • Long installation time:
    When downloading the bundles, Oomph creeped forward with something about 200 KB/s, internet connection and Eclipse servers went fine when downloading manually.
We agree with you in that using p2 to download individual artifacts is slower than just downloading a single, large zip file. However, Oomph uses a global p2 bundle pool, so once you've downloaded the artifacts once you'll never download those same artifacts again. Because of this installing a complete IDE along with dozens of additional features can take as little as 20 seconds. Of course the first time you won't see that benefit.

  • Sadly, you can't leave it alone since it needs some 'Accept here!'
For legal reasons we must prompt for license agreement, just as you see in the "Install New Software..." dialog. But Oomph can remember accepted licenses to not prompt again for each and every installable unit that you might install or update later. So this is another first-time issue. Nevertheless, to make that even better, we've submitted this enhancement request:

    431432: [Oomph] Provide support for pre-approval of licenses used at Eclipse
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=431432

  • and 'Click there!' moments, ofc.
Please explain the 'Click there!' moments. Perhaps you're referring to Oomph's variable prompt dialog? Those choices are also remembered, so this is again another first-time issue.

  • Forcing to Eclipse Luna 4.4 M6:
    I don't mind testing new Eclipse Milestone builds on a regular basis, but I prefer a stable release for productive use.
    Even Eclipse Milestone builds have their rough edges from time to time, at least speaking on my own experiences.
The Oomph installer dialog gives you a choice of Eclipse versions, with the latest version (currently Luna / 4.4) being the default.

  • Throwing eclipse installation, workspace and Git repository to the same location on the same hard drive:
    I'd like to have them separated, allowing cross-work between them (e.g. for Livedoc incubators development, I usually have both Git Repos (Livedoc and Recommenders Core) imported in my workspace. )
Are you suggesting you want to share Git clones across workspaces? That seems like an exceedingly bad idea for many reasons. However, if the setup model for Code Recommenders used a variable in the GitCloneTask's location attribute you could easily have redirected it anywhere you want via a variable override task in your user preferences model.

All in all, these aren't critical reasons against an usage of Oomph imo, but it didn't saved me any time or configuration effort, due to the reasons above.

How much time do you normally spend to set up a completely fresh development environment?

So the advantages doesn't take over (at least for me :) ).

Certainly if you didn't encounter the communications problems and didn't repeatedly face the first-time issues you could expect to finish a completely fresh installation unattended in less than four minutes.

I didn't take the time and make an Oomph setup for Livedoc, but from my users point of view, Yoxos does basically the same. (Not that I am a fan of Yoxos)

However, there are clearly benefits for eclipse beginners, as there are no needs of eclipse configuration, plugin installing etc.

Being an expert doesn't make the manual tasks significantly faster or less tedious, but granted, the expert is less likely to make errors. We know from experience with existing expert users that the tedious manual task of installing a completely fresh IDE can be reduced from hours to minutes, depending mostly on the size of the source code repositories.

At least for Recommenders core development, doesn't fit for Livedoc Incubator atm, due to the separated Git repo's

So that's not a real issue; see above.

and the different target platforms.

What exactly is the "different target platforms" issue?

Cheers
/Eike

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


Back to the top