[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [mdt-papyrus.dev] Gerrit authorisation
|
Hi
OCL is easy for me because my ssh: Remote just works. The only secret to
learn is the refs/for/master that appears nowhere in the UI help.
For Papyrus, if I am foolish enough to follow the Vogella tutorial I
would start by installing command line Java tooling; totally unnecessary
and very off putting.
Since the Papyrus guide has no screen shots and three broken file links
it is confusing. How is refs/for/master spelled? It appears to echo as
HEAD:refs/for/master in my dialog. Anyway, I still do not know what the
Gerrit REMOTE config should look like, but pushing the ordinary config
gives a config selection, so that I see something where I can select
from "master" to "refs/for/master". After three requests for
username/password it reports unauthorized. I can use the select
branch-to-delete box to see many branches so it would appear that the
URI is at least a Papyrus path, although perhaps not a refs/for/master
pushable one. It would have saved and still save a lot of time if the
author of the guide had put in a screenshot of a correct push dialog.
So either the "r/p" URI is wrong, it certainly seems really wierd to me,
or my username/password are wrong. I use the my normal
ed_at_willink.me.uk and Eclipse Foundation password that had its six
monthly update a couple of weeks go. These work on the Gerrit web interface.
Another possibility is enforcement of the bug name + commit id + signed
off. Perhaps I did it wrong; the links in the guide are broken and the
words say it is easy; not that hard but I'd never used them before.
Again a screen shot of a correct commit would save a lot of time.
Regards
Ed Willink
On 22/01/2015 07:10, SCHNEKENBURGER Remi 211865 wrote:
Hi Ed,
No, there is absolutely no rule against committers from other projects or given people ;-)
We have for example many commits from Michael Golubev, who is a committer on GMF-tooling, and some of us are also committers on other projects.
However, I am curious to know why it could be simpler in OCL than Papyrus. We did not ask for particular configuration or settings AFAIK.
Regards
Rémi
-------------------------------------------------------
Rémi SCHNEKENBURGER
+33 (0)1 69 08 48 48
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
www.eclipse.org/papyrus
-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Ed Willink
Envoyé : mercredi 21 janvier 2015 23:43
À : Papyrus Project list
Objet : [mdt-papyrus.dev] Gerrit authorisation
Hi
Is Papyrus Gerrit blocked to arbitrary users or is it just confused by
non-Papyrus Eclipse committers?
I get unauthorised repeatedly for Papyrus Gerrit, yet OCL Gerrit is easy.
Regards
Ed Willink
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5645 / Virus Database: 4260/8972 - Release Date: 01/21/15