Bugzilla – Full Text Bug Listing
| Summary: | Deploy p2repo.analyzers to "permanent" download areas | ||
|---|---|---|---|
| Product: | [Technology] CBI | Reporter: | David Williams <david_williams> |
| Component: | p2 Repository Analyzers | Assignee: | David Williams <david_williams> |
| Status: | RESOLVED FIXED | QA Contact: | David Williams <david_williams> |
| Severity: | normal | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 487543 | ||
| Bug Blocks: | |||
This has been done, in the past few days (might have been a duplicate bug open?) The "dup" was actually a bug originally opened for other reasons, and ended up expanding its scope. See bug 507917 comment 8. In short, the repo for analyzers (aka "repo tests and reports") is at http://download.eclipse.org/cbi/updates/analyzers/4.6/ |
Another "todo" item is to decide and implement where to "permanently" put the output of the p2repo.analyzers build. Currently, in one place (Platform releng) we use simply use the "lastSuccessful" build *product* from the build. wget --no-proxy --no-cache -O "${TMP_DIR}/${tar_name}" https://hudson.eclipse.org/cbi/job/cbi.p2repo.analyzers.build/lastSuccessfulBuild/artifact/output/products/${tar_name} 2>&1 In another place (SimRel aggregation builds), I use the repository from a specific build and install it "into" a base platform using p2 director: https://hudson.eclipse.org/cbi/job/cbi.p2repo.analyzers.build/9/artifact/output/p2repo/ I would prefer to maintain only a "permanent" update site, but will have to determine if it easy enough to document "how to get the product" from that repository, if that is what users would prefer.