Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 481301

Summary: [Papyrus] Permissions setup and folder creation
Product: Community Reporter: Francois Le Fevre <francois.le-fevre>
Component: CI-JenkinsAssignee: CI Admin Inbox <ci.admin-inbox>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: benoit.maggi, cletavernier, francois.le-fevre, mikael.barbero, rschnekenburger, sebastien.gerard, webmaster
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Francois Le Fevre CLA 2015-11-03 05:29:30 EST
Dear Hudson managers,

We are trying to split our Papyrus in several components (a component has its own git repository, a dedicated component in bugzilla and a view for its jobs in Hudson)

We would to allow to promote/publish the component update site build in Hudson to downloads.eclipse.org in a specific folder by using the option described [0]
We have followed the discussion at CBI mailing list [1]
We have made a publish script based upon the one of GEF4: [2]

We would like to give write permissions of genie.papyrus on the following folder /home/data/httpd/download.eclipse.org/modeling/mdt/papyrus/components/

with the following rights: 
drwxrwxr-x 2 genie.papyrus modeling.mdt.papyrus components

We will also use the security script /shared/common/gerrit-utils/authorizeGerritBuild.sh $GERRIT_PROJECT $BUILD_URL $GERRIT_PATCHSET_UPLOADER_EMAIL mentionned here [3] 

Any remarks will be appreciate.

Thanks a lot for your help.

Francois

[0]: https://wiki.eclipse.org/Hudson#HIPP
[1]: https://dev.eclipse.org/mhonarc/lists/cbi-dev/msg01515.html
[2]: https://git.eclipse.org/r/#/c/59473/
[3]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=375350#c42
Comment 1 Mikaël Barbero CLA 2015-11-04 05:48:00 EST
You've done your homework very well ;) I've no comments to make on what you said.

I've created the "components" folder and set the proper permissions for your HIPP.
Comment 2 Francois Le Fevre CLA 2015-11-09 05:30:02 EST
Hello Mickael,
thanks to the tasks done.
however when I have tried to call the /shared/common/gerrit-utils/authorizeGerritBuild.sh $GERRIT_PROJECT $BUILD_URL from my hudson job

it is failing: https://hudson.eclipse.org/papyrus/view/Sysml/job/papyrus-sysml-gerrit/400/

because the $GERRIT_PROJECT is linking to papyrus/org.eclipse.papyrus-sysml

and we do not have any folder in /shared/${project}/contributor_whitelist.txt

Could we have also a folder /shared/papyrus/ as mylyn etc... ?

Thanks again.

Francois
Comment 3 Mikaël Barbero CLA 2015-11-09 11:03:12 EST
You should use your own existing folder /shared/modeling/mdt/papyrus. Mylyn is a top level project, that's the reason why they have a folder right under /shared.
Comment 4 Francois Le Fevre CLA 2015-11-16 04:53:57 EST
Mikael,
I do agree with you when saying papyrus is not a top level project.
but it seems to be linked to /shared/modeling/papyrus (no mdt folder?)

Even if, we cannot use the default CBI /shared/common/gerrit-utils/authorizeGerritBuild.sh $GERRIT_PROJECT $BUILD_URL $GERRIT_PATCHSET_UPLOADER_EMAIL

because $GERRIT_PROJECT return for instance papyrus/org.eclipse.papyrus-sysml
and not /shared/modeling/papyrus 

so the CBI script is working for top level project and low level project.

So do you agree we will need to customize the CBI script?
Comment 5 Francois Le Fevre CLA 2015-11-16 04:56:38 EST
An additional element, in the script they use the following url
${GERRIT_ACCESS_URL}${project}

>>this url exists
https://git.eclipse.org/r/access/?project=modeling/papyrus/org.eclipse.papyrus-sysml

>>this one does not exist
https://git.eclipse.org/r/access/?project=papyrus/org.eclipse.papyrus-sysml
Comment 6 Mikaël Barbero CLA 2015-11-16 05:12:53 EST
Francois, you're right. I've overlooked at how we match gerrit's project names and project paths under /shared. 

I am thinking of creating a subfolder in shared (e.g. /shared/gerrit_whitelists) where all projects will put their whitelist files because I don't want to create a duplicate project right under /shared without this top folder. 

I will check with mylyn if they are ok with that and will come back to you shortly.
Comment 7 Mikaël Barbero CLA 2015-11-16 05:18:03 EST
See bug 375350 comment 43
Comment 8 Mikaël Barbero CLA 2015-11-17 06:07:34 EST
/shared/gerrit-contributor-whitelists/papyrus has been created and you should now be able to add contributor_whitelist.txt files into it. Note that you have to add them in proper subfolders depending on the gerrit project name, e.g. 

/shared/gerrit-contributor-whitelists/papyrus/org.eclipse.papyrus or
/shared/gerrit-contributor-whitelists/papyrus/org.eclipse.papyrus-sysml 

The symlinks work so I suggest you create a top level file 

/shared/gerrit-contributor-whitelists/papyrus/contributor_whitelist.txt 

and create symlinks to it from subfolder.

Please reopen if you face issues.
Comment 9 Francois Le Fevre CLA 2015-11-20 10:15:35 EST
Thanks
I have done the test with the follwoing patch
https://git.eclipse.org/r/#/c/60911/

First pass, I was not member of the white list, so it was refused
Secund pass Camille add me to the white list, so it was accepted !

So now I continue in oder to test the promote/publish of the p2

Thanks