Re: [gemini-dev] Hudson job naming convention for

[Mike Keith <michael.keith@xxxxxxxxxx>]

Thanks for bringing this up, Juergen.
It would be nice to have a consistent naming scheme across the Gemini 
projects (and it seems a little odd for the Gemini Web job to have 
"virgo" in the name).

I'm not personally too fussed about what format the name is in, although 
if a project is planning on having multiple builds then it might make 
sense to make sure we include the version.  I have seen underscores for 
readability used as well:

gemini_web_2.0_snapshot
gemini_management_1.0_snapshot
etc.?

-Mike

On 7/7/2011 5:03 AM, Kissner, Juergen wrote:
> Hi,
>
> I was going to apply for an Eclipse Hudson job and found the following information:
> http://wiki.eclipse.org/Common_Build_Infrastructure/Getting_Started/Build_In_Hudson
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=276270
>
> There does not seem to be a unique and general naming convention for the Hudson jobs, but it would be nice if the Gemini subprojects could try head towards a common naming convention.
>
> So far, the Eclipse Hudson host the following Gemini jobs:
> - virgo.gemini-web-container.snapshot
> - gemini-management
>
> The web-container is a special case...
> According to the link above, a suggestion convention could look like:
>
> build_system-project_name-version-qualifier
> possible suggestions:
>
>   1) gemini-dbaccess.snapshot
>   2) gemini.dbaccess.snapshot
>   3) rt.gemini.dbaccess.snapshot
>
> Should the version be include? For a version 1.1.x that could look like
>
> gemini-dbaccess.11.snapshot
>
> Or rather:
> gemini-dbaccess.snapshot which goes to gemini-dbaccess.11 after its release.
> Any suggestions, thoughts?
> -- Juergen
>
>
>
>
>
> _______________________________________________
> gemini-dev mailing list
> gemini-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gemini-dev