[tor-bugs] #20564 [Metrics]: Add Jenkins configuration for running metrics-lib's unit tests and producing a .jar file

[Tor Bug Tracker & Wiki]

#20564: Add Jenkins configuration for running metrics-lib's unit tests and
producing a .jar file
-------------------------+---------------------
 Reporter:  karsten      |          Owner:
     Type:  enhancement  |         Status:  new
 Priority:  Medium       |      Milestone:
Component:  Metrics      |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:               |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:
-------------------------+---------------------

Comment (by iwakeh):

 Replying to [comment:7 karsten]:
 > weasel suggests to add a second branch to metrics-lib, say, `release`,
 create two jobs `metrics-lib-master` and `metrics-lib-release`, and test
 applications against both.  Sounds good to me!

 That's really the best solution for supplying metrics-lib with the
 following assumptions:

 * check-ins on the respective branches trigger the jenkins jobs, i.e. the
 metrics-lib-release-job is only triggered when a new check-in occurs on
 this branch and after that the descriptor-<version>.jar is available for
 all other Metrics' jenkins jobs

 * The collector jenkins job on HEAD/master is triggered on check-in (in
 collector.git) and each time one of the two metrics-lib jenkins jobs ran
 (successfully).

 * Analogously with onionoo etc.

 It doesn't solve the non-debian stable library topic.  But, we can just
 start running the ant tasks in jenkins that don't require additional
 libraries.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20564#comment:8>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online