Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #20564

Closed (moved)
(moved)
Open
Created Nov 04, 2016 by Karsten Loesing@karsten

Add Jenkins configuration for running metrics-lib's unit tests and producing a .jar file

We should start using Jenkins for metrics builds, and ideally we should start with something simple. Let's have it run CollecTor's unit tests as a start. Step two would be to run Checkstyle or Cobertura, but those require .jar files that are not in Debian Stable. So, step one for now.

weasel suggests these two Git repositories:

git clone git@git-rw.torproject.org:project/jenkins/tools
git clone git@git-rw.torproject.org:project/jenkins/jobs

In particular, tools/slaves/linux/tb-manual and the corresponding settings in the jobs repository might serve as template for us.

The CollecTor repository is here:

https://gitweb.torproject.org/collector.git/

Build requirements can be derived from the .jar files listed here:

https://gitweb.torproject.org/collector.git/tree/build.xml

Just came to mind: we might have to package metrics-lib first, because Jenkins jobs cannot download anything from the network.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking