Bugzilla – Full Text Bug Listing
| Summary: | Requesting a Job for EMF Compare | ||
|---|---|---|---|
| Product: | Community | Reporter: | Cedric Brun <cedric.brun> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d_a_carver, Kenn.Hussey, michal.ruza, nboldt, sbouchet, thomas |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Cedric Brun
I have a few questions regarding the naming of the job, I don't really care about the buckminster, cbi or any other prefix if it is useful for anybody though I don't think it's useful to me and - from my perspective - I'd like to be able to find the build jobs corresponding to any project just knowing about the project (and not the build technology it is using). To do so starting by the name looks easier to me but I guess we should then have something like modeling-emf-compare.. the "nightly" is not making a lot of sense to me neither, whether it is launched nightly or not is subject to change, once the 1.1 version is released we'll probably move from a nightly schedule to a manually triggered one (or a "poll from SCM only" one). And what should I do once the 1.1 stream enters maintenance mode and I need to start a 1.2 stream, what kind of name should I pick then ? Adding helios, ganymede or any other simultaneous release name in the job is not nice neither as the 1.1 stream of emf compare for instance might be built upon the 3.3, 3.4, 3.5 and 3.6 platforms. Is there a specific intention in changing the "emf-compare-1.1" name I gave into "buckminster-emf-compare-nightly" or is that just an overlook ? My personal opinion is that the build technology used for the build is irrelevant and should not be part of the name. Buckminster has a job called 'buckminster-nightly', a name is motivated by the simple fact that it actually builds buckminster. The build name comes from the following page: http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson Particularly the following sentence: generally, name is build_system-project_name-version-qualifier, where qualifier could be "nightly", "release", or the Eclipse version used Please open a separate bug if the community wishes to come up with some other convention. From a Hudson Admin standpoint, it helps us to narrow down the type of build technology that is being used if it is part of the name. In general I don't care what the name is. I'll rename the job to: emf-compare-1.1 (In reply to comment #3) > My personal opinion is that the build technology used for the build is > irrelevant and should not be part of the name. > > Buckminster has a job called 'buckminster-nightly', a name is motivated by the > simple fact that it actually builds buckminster. If you use the ${buildTechPrefix}- when naming jobs, you can very easily see who's using what tech on the server. Why would you care? Well, consider the build panel @ EclipseCon where I was able to point to the 60+ projects using Athena, compared to the 1 dozen using Bucky or the handful using Tycho. Stats are useful. :) (In reply to comment #5) > Stats are useful. :) Hmm, perhaps you should change form 'cbi' to 'athena' to get them on top of the list :) (In reply to comment #6) > (In reply to comment #5) > > Stats are useful. :) > > Hmm, perhaps you should change form 'cbi' to 'athena' to get them on top of the > list :) It's not about alpha order, it's about # of adopters. :) closing, EMF Compare is using buckminster. I can attach the build to a specific view for stats if required. |