Community
Participate
Working Groups
Hello! I am going to publish MDT OCL builds. Could you please a) enable full SSH access to dev.eclipse.org for me b) add me to the callisto-dev and signers groups Thanks in advance, Alex.
I've done everything but the callisto-dev group. David, can you please +1? -M.
Nick and Matt, sorry for the newbie's question. Is it obligatory to be in callisto-dev to run builds and publish them? If yes, I need it the sooner the better.
Sorry Matt, this sort of slipped by me ... but I agree with Alex :) his second comment. Shouldn't me callisto-dev ... there is probably some 'modeling-admin' group for their download area?
David: you are correct. Since most people asking for callisto-dev access are looking to build for Galileo I pass them along for approval. Aleksandr: Where on build.eclipse.org do you need access? I'm presuming it's /opt/public/modeling, in which case Kenn will need to +1 you(since it's a different group). The good news is that you have access to the MDT.OCL downloads area. -M.
+1 for giving Alex whatever rights he needs, as the new component lead for MDT OCL, in order to publish OCL builds.
Ok, Aleksandr you should be all set to build. Let me know if anything is missing. -M.
(In reply to comment #4) > Aleksandr: Where on build.eclipse.org do you need access? I'm presuming it's > /opt/public/modeling, in which case Kenn will need to +1 you(since it's a No one needs access to /opt/public/modeling except the people maintaining the releng system for Modeling (ie., me). Please remove him. Aleksandr needs the following: 1. callisto-dev group - access to write changes into *.build files for Galileo contributions 2. mdtadmin - used by all MDT committers to create shared update site Additionally, Aleksandr should be removed from this group, since he doesn't need it: 1. modelingadmin (used only for /cvsroot/modeling/releng-common, IIRC). These groups have already been added to Aleksandr's list. 1. signers group - signing access in /home/data/httpd/download-staging.priv/modeling/<project>/ 2. modeling-home group - www.eclipse.org/modeling/ website [already done] 3. modeling.mdt.ocl group - source code 4. modeling.mdt.ocl-releng group - releng source code
Ok I've made the listed changes. I still need a +1 from David for the callisto-dev access. -M.
(In reply to comment #8) Ok ... I'm sure Nick is correct, but I'd like to hear (read) Alex say he plans to check in changes to .build file ... since he only mentioned "publish MDT OCL builds". I'm sure it's obvious to others ... but not me ... who's been checking them in up to now? Should someone be removed? And, once he does ... +1 :)
(In reply to comment #9) > Ok ... I'm sure Nick is correct, but I'd like to hear (read) Alex say he plans > to check in changes to .build file ... since he only mentioned "publish MDT OCL > builds". I'm sure it's obvious to others ... but not me ... who's been checking > them in up to now? The history of the mdt-ocl.build file suggests it's been changed by Rich, then Christian, then me. Once we have all the ducks lined up, the build system will be switched over to do these automated commits using Alex's id. > Should someone be removed? I dare ya to take my callisto-dev rights away. Ya feel lucky, punk? Well, do ya? :P
Well, I am not quite sure whether I actually need callisto-dev participation since I am not yet acquainted with the nuts and bolts of releng:)) On one hand, I do not want to have extra access rights, on the other - I do not want to get stuck with anything unexpected while making the release. However, I feel I need at least the same rights as Christian had. Nick, are you sure I will need participation in callisto-dev?
(In reply to comment #11) > Well, I am not quite sure whether I actually need callisto-dev participation > since I am not yet acquainted with the nuts and bolts of releng:)) You do. > On one hand, I do not want to have extra access rights, on the other - I do not > want to get stuck with anything unexpected while making the release. > However, I feel I need at least the same rights as Christian had. Christian, as project lead for OCL, ran the build using his ID (logically) and therefore needed callisto-dev access to be able to generate changes to the Galileo .build files. > Nick, are you sure I will need participation in callisto-dev? Yes. Make it so, Number One.
In case there's any doubt, I'm fine with this. Now that Alex understands that even if it is a "automatic" build provided by someone else, if his contributions break the Galileo build, then _he_ is responsible to fix it (or getting it fixed, keeping us all informed, etc). I'm glad I asked. :)
(In reply to comment #13) > In case there's any doubt, I'm fine with this. > > Now that Alex understands that even if it is a "automatic" build provided by > someone else, if his contributions break the Galileo build, then _he_ is > responsible to fix it (or getting it fixed, keeping us all informed, etc). I'm > glad I asked. :) > Tempting... But if there is no other way, then let it be... I just wonder - other components must have had similar concerns but they hadn't, had they? =))
(In reply to comment #14) > (In reply to comment #13) > > Tempting... > But if there is no other way, then let it be... > > I just wonder - other components must have had similar concerns but they > hadn't, had they? =)) > Alex, if I'm reading this right, you recently became lead of OCL, taking over from Christian, and when Christian was PL, he also did the "releases" (the releng part of releases, to be exact). Sounds like no one told you that before you committed, eh? :) As PL, it is up to you to decide how to do this ... for example, you could find someone else to do it for your sub-project. So, if you want to go that route, let us know ... but, honest, we're much more helpful in practice than we have been in this bugzilla exchange, so if you do take over the releng tasks, help will always be nearby.
(In reply to comment #15) > (In reply to comment #14) > > (In reply to comment #13) > > > > Tempting... > > But if there is no other way, then let it be... > > > > I just wonder - other components must have had similar concerns but they > > hadn't, had they? =)) > > > > Alex, if I'm reading this right, you recently became lead of OCL, taking over > from Christian, and when Christian was PL, he also did the "releases" (the > releng part of releases, to be exact). Sounds like no one told you that before > you committed, eh? :) > It seems I couldn't make myself understood. Sorry, I didn't mean to offend anyone. What I wanted to say is that for me the procedure of permitting someone to make and publish builds and releases seems a standard routine. For instance, UML2Tools committers also do the releases, consequently, they must have faced the same problem of being included into callisto-dev. But from the discussion above I concluded that this problem hasn't been faced before. So my question was why MDT OCL should be exceptional in this and differ from UML2Tools, for instance. > As PL, it is up to you to decide how to do this ... for example, you could find > someone else to do it for your sub-project. So, if you want to go that route, > let us know ... but, honest, we're much more helpful in practice than we have > been in this bugzilla exchange, so if you do take over the releng tasks, help > will always be nearby. > Thanks, David! I am going to do the releases by myself. In case other OCL team members wish to join me - that would be great too. Once again, sorry for being unclear. Foreign speakers sometimes say things which are opposite to the ones they intended to say=))
FYI, you can set multiple email contacts in your /www/modeling/mdt/ocl/build/_common.php file so that the "blame emails" that the Galileo buckybuilder send will go to multiple recipients. I'm not sure if you can set a mailing list address (mdt-ocl-dev@eclipse.org), but at least you can spam multiple committers at once. However, the build can only be run as a single committer, which is generally either the project lead or the releng person. Or me, when there's no one else for it to fall upon. Alex, you should make sure you update the Galileo wiki to list your name in place of Christian: http://wiki.eclipse.org/Galileo#Projects
(In reply to comment #17) > FYI, you can set multiple email contacts in your > /www/modeling/mdt/ocl/build/_common.php file so that the "blame emails" that > the Galileo buckybuilder send will go to multiple recipients. I'm not sure if > you can set a mailing list address (mdt-ocl-dev@eclipse.org), but at least you > can spam multiple committers at once. > > However, the build can only be run as a single committer, which is generally > either the project lead or the releng person. Or me, when there's no one else > for it to fall upon. I see, thx. > > Alex, you should make sure you update the Galileo wiki to list your name in > place of Christian: > > http://wiki.eclipse.org/Galileo#Projects > Done.
I've added Aleksandr to the callisto-dev group. I'm going to close this bug as 'fixed' and hope that it stays that way ;) -M.
