| Summary: | EPP jobs for Indigo | ||
|---|---|---|---|
| Product: | Community | Reporter: | Markus Knauer <mknauer> |
| Component: | CI-Jenkins | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | david_williams, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Markus Knauer
I just saw the names of the other (helios|indigo) build jobs. Maybe it would be better to name the EPP jobs according to their naming scheme: * indigo.epp-repository-build and * indigo.epp-package-build (In reply to comment #1) > I just saw the names of the other (helios|indigo) build jobs. Maybe it would be > better to name the EPP jobs according to their naming scheme: > > * indigo.epp-repository-build and > * indigo.epp-package-build I should be able to set these up (copy existing) ones on build.eclipse.org. I'll assume you'll want the indigo prefix (I usually recommend names go from "most general" part, to most specific part (as package names do) ... but, not sure if it's clear if whole release (indigo vs. helios) is the most general or most specific part :/ I assume the "new" hudson isn't ready/mandatory yet? Done. I did just literally copy them. So they started up automatically, I assume building "helios". I'll let them run, unless I hear otherwise, but you'll need to change everything (even comments) over to 'indigo'. Thanks, |