Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.7.0
-
None
-
None
Description
This is a top level JIRA to track effort required to jumpstart a full blown CI infra on http://builds.apache.org. The plan basically consists of:
- having testpatch-like functionality
- having a build
- running unit tests and publishing results (mvn test)
- collecting code coverage stats from the previous step
- publish the source tarball artifact (exact same tarball as gets released today)
- publish Maven artifacts to repostiroy.a.o
- publish a binary artifact (see bellow)
The only tricky bit here is the binary artifact. Today Ambari generates RPMs, but the tools to do that may not be available on b.a.o infrastructure. Thus we may need to reframe our expectations on what would be the ideal binary convenience artifact to publish.
Attachments
Issue Links
- depends upon
-
AMBARI-7209 Build a test patch Jenkins job on builds.a.o.
- Resolved