Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #15464

Closed (moved)
Open
Opened Mar 26, 2015 by Isis Lovecruft@isis

BridgeDB's continuous integration setup steps should be separate scripts

…or Makefile directives.

weasel requested this at the Valencia developer meeting, in order to make it easier to get BridgeDB's test builds running on Jenkins (if we should ever wish to do so).

Currently, BridgeDB's CI uses Travis. The builds can be viewed here. The script which controls the setup and testing procedure for these builds is BridgeDB's .travis.yml file, which is basically a lot like Tor Browser's gitian descriptors, it's YAML with one command per line, organised into various sections (which in this case, are called in the order they happen to be in in the .travis.yml file). So pretty simple to convert.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#15464