Bugzilla – Full Text Bug Listing
| Summary: | Install Promoted Builds Simple and Copy Artifact Plugins | ||
|---|---|---|---|
| Product: | Community | Reporter: | Kenn Hussey <Kenn.Hussey> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | antoine, denis.roy, d_a_carver, michal.ruza, sbouchet |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=306854 | ||
| Whiteboard: | |||
|
Description
Kenn Hussey
(In reply to comment #0) > Would it be possible to install these plugins? > > http://wiki.hudson-ci.org//display/HUDSON/Promoted+Builds+Simple+Plugin > http://wiki.hudson-ci.org//display/HUDSON/Copy+Artifact+Plugin > > We're looking to simplify/automate "promotion" of builds from Hudson to > download.eclipse.org. Copy Artifact Plugin needs at least Hudson 1.355, and we are on Hudson 1.354 which we just upgraded too. The next scheduled upgrade is probably going to be after the RC candidates are done...So we are looking at the end of June or beginning of July. We already have the more advanced Hudson Promoted Builds plugin installed, but it was currently disabled. I've temporarily re-enabled it, and it should be available after the next restart. (In reply to comment #1) > Copy Artifact Plugin needs at least Hudson 1.355, and we are on Hudson 1.354 > which we just upgraded too. The next scheduled upgrade is probably going to be > after the RC candidates are done...So we are looking at the end of June or > beginning of July. OK, I guess we'll have to come up with an alternative in the meantime (perhaps invoking a custom script or ant task). > We already have the more advanced Hudson Promoted Builds plugin installed, but > it was currently disabled. I've temporarily re-enabled it, and it should be > available after the next restart. Thanks, I've taken a look and it seems like it will meet our needs. Does it support the notion of promotion "levels" (like the other one) or is it essentially binary? Can you comment on how it's more advanced, or tell me where I can find documentation on it? (In reply to comment #2) > (In reply to comment #1) > Thanks, I've taken a look and it seems like it will meet our needs. Does it > support the notion of promotion "levels" (like the other one) or is it > essentially binary? Can you comment on how it's more advanced, or tell me where > I can find documentation on it? The simple one was just a strict manual promotion process. The full version allows you to set conditions automatically for different promotion levels. Dave, we can't see the "force promotion" button in the Hudson web UI. Do users of our job (buckminster-emf-core-2.6-nightly) need to be explicitly authorized to do this? If so, could you help make that happen? (In reply to comment #4) > Dave, we can't see the "force promotion" button in the Hudson web UI. Do users > of our job (buckminster-emf-core-2.6-nightly) need to be explicitly authorized > to do this? If so, could you help make that happen? To get to the Force Promotion button, go to the build number you want to promote, then click on the Promotion Status. It will say the build has not been promoted. Over on the right hand side of the screen will be a "Force Promotion" button. (In reply to comment #5) > To get to the Force Promotion button, go to the build number you want to > promote, then click on the Promotion Status. It will say the build has not > been promoted. Over on the right hand side of the screen will be a "Force > Promotion" button. Yeah, I know that's where it's supposed to show up, but it doesn't appear for me. Do I need to be an administrator to see it? This makes me wonder: http://issues.hudson-ci.org/browse/HUDSON-3369 ... (In reply to comment #6) > (In reply to comment #5) > > To get to the Force Promotion button, go to the build number you want to > > promote, then click on the Promotion Status. It will say the build has not > > been promoted. Over on the right hand side of the screen will be a "Force > > Promotion" button. > > Yeah, I know that's where it's supposed to show up, but it doesn't appear for > me. Do I need to be an administrator to see it? This makes me wonder: > http://issues.hudson-ci.org/browse/HUDSON-3369 ... Yes, unfortunately it looks like you do need to be adminstrator. With that said, if you build and fix the plugin so that it doesn't require that, but looks at Job adminstrators instead, then you should be fine. You might also be interested in bug 306854 which asks for a eclipse specific plugin for Hudson to promote builds to download.eclipse.org. (In reply to comment #7) ... > Yes, unfortunately it looks like you do need to be adminstrator. I've tested it on our local instance of Hudson and found out that there is a new global privilege named "Promote" on the Hudson global configuration page in the "Project-based Matrix Authorization Strategy" table. Granting this privilege to a user gives him the "Force Promotion" button. Note that we run the latest version (1.7) of the plug-in on our local Hudson. Could you please set the privilege for us and/or if needed upgrade the plug-in in case the feature is not present in the version installed at build.eclipse.org? Where in the configuration is this option? I checked the Manage->System Configuration option and didn't see a global configuration for the Promoted Builds plugin. We are using 1.7. I also am hitting this problem. I want an automated way to go from a build to testing, with no scripts in the middle. (In reply to comment #10) > I also am hitting this problem. I want an automated way to go from a build to > testing, with no scripts in the middle. If you are talking about committer level testing, you can always have Hudson Archive your generated update site. The use the LastSuccessful or LastStable RESTful urls to get to it and use it. You may also be interested in: https://bugs.eclipse.org/bugs/show_bug.cgi?id=306854 Which asks for an Eclipse specific plugin to allow publishing on eclipse.org infrastructure. Another option for copying artifacts to download.eclipse.org automatically after a build is the SCP Plugin. http://wiki.hudson-ci.org//display/HUDSON/SCP+plugin This only uses a global configuration, so the plugin for Hudson would need to be enhanced so that it would allow for per job configuration of the userid and signon. Hi, there is no promote builds on the new hudson instance, but it was installed on the old hudson. could it be possible to install it or we should wait for another system to promote builds ? HIPP allows the project-owned Hudson user to be part of the project group, thus allowing direct write into the project download space (and Git repos). With HIPP these plugins are not needed. http://wiki.eclipse.org/Hudson#HIPP |