| Summary: | Nighlty Build Job for org.eclipse.fmc | ||
|---|---|---|---|
| Product: | Community | Reporter: | Benjamin Schmeling <Benjamin.Schmeling> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | thanh.ha, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Benjamin Schmeling
Do you have a preference on what the job should be called? Also who should be given access to manage/modify the job? It is only me who needs access, thanks. You could name it org.eclipse.fmc-nightlybuild, for example, or is there another naming pattern? I created the job org.eclipse.fmc-nightlybuild and assigned the permissions to you, we can always rename it later if you change your mind.
https://hudson.eclipse.org/hudson/job/org.eclipse.fmc-nightlybuild
The job name is up to you. Most projects either tag the job name with the branch they are building for example:
- fmc-master
- fmc-maintenance-1.x
or another way I've seen is name the job by the build schedule such as:
- fmc-nightly
- fmc-integration
|