| Summary: | CI build results of Tycho 0.14.0-SNAPSHOT are not available | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Tobias Oberlies <t-oberlies> |
| Component: | Tycho | Assignee: | Project Inbox <tycho-inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jan.sievers |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Tobias Oberlies
(In reply to comment #0) > Currently, there is no CI build for Tycho. This means that whoever wants to use > Tycho 0.14.0-SNAPSHOT has to build Tycho from source. > > Bug 360628 would fix this problem. this is not exactly true: we have CI build jobs for tycho and tycho-its https://hudson.eclipse.org/hudson/job/tycho-nightly/ https://hudson.eclipse.org/hudson/job/tycho-its-linux-nightly/ https://hudson.eclipse.org/hudson/job/tycho-its-win-nightly/ All that's missing is a maven repo to deploy to from these jobs. So why do we need a separate bug for this? Good point: renamed to "CI build results of Tycho 0.14.0-SNAPSHOT are not available". I created this issue because I couldn't find bug 360628 within five attempts, and I wasn't sure if I can rename the bug because it seemed to have one particular solution in mind. (In reply to comment #2) > Good point: renamed to "CI build results of Tycho 0.14.0-SNAPSHOT are not > available". I created this issue because I couldn't find bug 360628 within five > attempts, and I wasn't sure if I can rename the bug because it seemed to have > one particular solution in mind. so what's the alternative solution other than deploying build results to a maven repository? None - but the intend of bug 360628 seemed to specifically about deploying to maven.eclipse.org. If this was just a misunderstanding, we can close this bug as duplicate, and make the title of bug 360628 more general. *** This bug has been marked as a duplicate of bug 360628 *** |