Community
Participate
Working Groups
I lost hudson CI control for https://hudson.eclipse.org/releng/ after merge of platform sub projects. https://hudson.eclipse.org/releng/ used to be under platform releng project. Since we have merged them now we need to move this hipp to platform project
In the security settings, you are listed with your email address and given all permissions, so I don't know why you lost access. Are you able to login? Are you just missing admin permissions? I have replaced the permissions for platform releng project with the platform project.
(In reply to Frederic Gurr from comment #1) > In the security settings, you are listed with your email address and given > all permissions, so I don't know why you lost access. > > Are you able to login? Are you just missing admin permissions? > > I have replaced the permissions for platform releng project with the > platform project. I can login to the hipp. This hipp is not listed anymore in my committers portal. I am not able to restart the hipp.
I'm willing to bet the recent amalgamation of the Eclipse projects has led to stale entries in the ProjectServices table. I am looking into it.
I've updated the eclipse.platform.releng jipp to now be owned by the eclipse.platform project. This change does break the 1:1 rule of "1 jipp per project", so the results may be unpredictable. What is this CI instance used for? Can its functionality be combined into the eclipse.platform project?
(In reply to Denis Roy from comment #4) > What is this CI instance used for? Can its functionality be combined into > the eclipse.platform project? I do not think it can be combined. See for example bug 509219 for some history and use cases. In short, it is used for the platform release engineer to do things to "platform" and to "equinox". [This is all "as far as I know" -- I am out of touch with recent day to day work, so there is a small chance something has changed.]
(In reply to Denis Roy from comment #4) > I've updated the eclipse.platform.releng jipp to now be owned by the > eclipse.platform project. This change does break the 1:1 rule of "1 jipp > per project", so the results may be unpredictable. > > What is this CI instance used for? Can its functionality be combined into > the eclipse.platform project? Looks like this CI instance is completely down now. Raised bug 521967 for the same This particular instance is used for building platform and Equinox and do release engineering activities. I would like keep only a small section of platform users to have access to this. I prefer to keep both separate. eclipse.platform hipp is used for day to day activities like gerrit builds, tests etc. releng hipp is used for regular builds and promotion of milestones, promotion to Maven central etc.
Same for me. When Platform Releng was not merged, I saw the HIPP on https://projects.eclipse.org/projects/eclipse.platform.releng and could restart it. This is now gone. Can we somehow get a link to restart the Releng and Platform HIPPs? NOTE: I would prefer if only a restricted set of people (Eclipse Platform release engineers, webmasters and myself) can do this and not all Eclipse Platform committers.
You should see it again on the control panel. Could you please have a look?
(In reply to Mikaël Barbero from comment #8) > You should see it again on the control panel. Could you please have a look? Sorry, you won't have access to the link. Denis, Matt We will need to add a new column to ProjectServices to store the "true" project ID to which the HIPP/JIPP is attached. We should add a field "ServiceName" that will be the project short name by default, and change the usage of ProjectID. It will become the association of a HIPP/JIPP to a given project, without the assumption that it is the only service for this project. This way, will have two entries with ProjectID = "eclipse.platform", one with ServiceName = "platform" and one with ServiceName = "releng". It requires a lot of changes in a lot of scripts (from jipp/hipp creations / backup, to puppet modules, along with some drupal and eclipse.org-common php script). Another solution is to move this releng HIPP to a foundation-internal project, and give access to a restricted number of committers. WDYT?
(In reply to Mikaël Barbero from comment #9) > (In reply to Mikaël Barbero from comment #8) > > Another solution is to move this releng HIPP to a foundation-internal > project, and give access to a restricted number of committers. I'd rather we be consistent and stick to the 'one CI per project' and merge the releng hipp into the platform hipp. We don't really have the time right now to re-wire things to support 'phantom' projects, and the platform build isn't really 'internal' to the Foundation. I realise that this position also means we should fold the perftests instance into the platform instance as well. -M.
*** Bug 531954 has been marked as a duplicate of this bug. ***
What's the status here?
Since we are moving to our new clustered infrastructure, the CI control widget will not longer be supported. It will probably replaced with something else.
