Bugzilla – Full Text Bug Listing
| Summary: | Need Buckminster 3.7 Builders | ||
|---|---|---|---|
| Product: | Community | Reporter: | Thomas Hallgren <thomas> |
| Component: | CI-Jenkins | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Thomas Hallgren
Ok, so you want me to copy the /shared/common/buckminster-3.6 directories to /shared/common/buckminster-3.7 and add that to hudson. Is that right? -M. Yes, that'll be a good start. Once that's done, I think I can take it from there. Ok, I've copied the buckminster3.6 to 3.7 and added it to Hudson. I"ve also removed the 'headless' from the 3.6 definition. Currently our 3.6 Integration is auto installed so I copied that to 3.7, will we need to update the plugin to be able to select 3.7 from the version drop box? -M. (In reply to comment #3) > Currently our 3.6 Integration is auto installed so I copied that to 3.7, will > we need to update the plugin to be able to select 3.7 from the version drop > box? > Yes, I believe so. I think most of the information regarding the plugin configuration is here: http://wiki.hudson-ci.org/display/HUDSON/Buckminster+PlugIn I'd be happy to help if you can trust me with the needed credentials. Oh, and could you please do a chown -R g+w /shared/common/buckminster-3.7 I intend to replace some of the content but it's owned by mruzika with a 755 permissions. I've changed the ownership. The buckminster plugin update will have to wait at least until after Eclipsecon. I'll look at installing it on the sandbox in the next day or two. -M. (In reply to comment #6) > The buckminster plugin update will have to wait at least until after > Eclipsecon. I'll look at installing it on the sandbox in the next day or two. > No problem. Thanks for fixing this thus far. Sorry about the delay on this. I've updated our sandbox instance to Hudson 1.391(compatible with the Buckminster plugin update) and have also updated the plugin. The catch is I'm not seeing Buckminster 3.7 in the drop list of installable versions. Am I missing something? -M. (In reply to comment #8) > The catch is I'm not seeing Buckminster 3.7 in the drop list of installable > versions. > I see it (and I use it), and I also see "Buckminster 3.7 Integration". I'm a bit curious how the latter is configured though. It's supposed to update itself with the latest from our 3.7 sites and that requires some work. Did you look at how the "Buckminster 3.6 Integration" was set up? Just so we're on the same page: we're both looking at hudson.eclipse.org/sandbox correct? I don't see 3.7 as an option in the buckminster area under hudsons configure page, or the per job config page. We did add 3.7 to the 'live' hudson instance(by hand) and the 3.7 Integration just calls buckminster 3.6. I was trying to verify that the 'new' buckminster plugin would allow us to include the 'real' 3.7 buckminster integration. Or an I missing something? -M. (In reply to comment #10) > Just so we're on the same page: we're both looking at > hudson.eclipse.org/sandbox correct? > No, I'm using the 'real' Hudson so that explains the difference. > I don't see 3.7 as an option in the buckminster area under hudsons configure > page, or the per job config page. > > We did add 3.7 to the 'live' hudson instance(by hand) and the 3.7 Integration > just calls buckminster 3.6. > That's the one I mean. Today we have Buckminster 3.6 -> Uses /shared/common/buckminster-3.6 Buckminster 3.7 -> Uses /shared/common/buckminster-3.7 Those two are OK and I can control them since I have the needed permissions for the two directories. But then we also have: Buckminster 3.6 Integration -> Uses ??? Buckminster 3.7 Integration -> Uses ??? I don't know where the configuration for those reside and I don't think I have any permissions to modify them. Hence my question if the 3.7 Integration now is a copy of the 3.6 Integration. The new buckminster plug-in would be great to have because it has some new features that are needed but it's not strictly necessary to make the above work. (In reply to comment #11) > Hence my question if the 3.7 Integration now is > a copy of the 3.6 Integration. Yes it is. > The new buckminster plug-in would be great to have because it has some new > features that are needed but it's not strictly necessary to make the above > work. Ok, I thought it was 'required' to actually make Buckminster 3.7 available from the 'install auto-magically' list box(currently only 3.5 and 3.6 are listed) -M. I maintain the "Buckminster 3.7" so that part is OK, but where does the "Buckminster 3.7 integration" reside? How do I get to it? 3.7 Integration is set to 'install automatically'(but seems to be pointing at vesion 3.6). Should it be removed? -M. No, it should ideally be maintained but I don't have access. There should also be a "Eclipse 4.2 Integration" set up. (In reply to comment #15) Ok, I'm a little lost here. Right now we have: Buckminster 3.7 Buckminster 3.7 integration As part of the available options in Hudson. The Buckminster 3.7 option points at an installed copy on /opt/public/common . However the integration version isn't 'installed' it's set to 'Install automatically' from Eclipse and Cloudsmith and is currently using 3.6 as the version tag to install. So I'm not sure what 'access' your looking for to maintain the 3.7 integration version? If you want to install it in /opt/public/common and have me point Hudson at it that's fine. Also I don't see any options in Hudson that would allow me to specify an Eclipse install, or are you asking for something else with 'Eclipse 4.2 Integration'? -M. I'm talking about the 'buckminster.json' file, see link in comment #4. The specific text on the wiki page that I'm referring to is the one listed under how extended buckminsters are installed, item 4. 4. place a 'buckminster.json' file under HUDSON_HOME/userContent/buckminster to override the default installer configuration. The file must list all available buckminster versions, the URL to the p2 director application, the IU of the product to be provisioned as well as the p2 repositories and the features to install from these repositories. The file structure is defined as following: etc. It's this json file that I want to be able to access and manage. Ok I've created the json file and linked it to build:/opt/public/common/buckminster.json (which you own). Please note: if something bad happens to Hudson and Buckminster I will so point the angry mob in your direction. Also make sure there aren't any passwords in this file, since it's publicly available. -M. |