Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • BridgeDB BridgeDB
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • BridgeDBBridgeDB
  • Issues
  • #15464

Closed
Open
Created 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.

Assignee
Assign to
Time tracking