Opened 4 years ago

Closed 4 years ago

#15464 closed enhancement (fixed)

BridgeDB's continuous integration setup steps should be separate scripts

Reported by: isis Owned by: isis
Priority: Medium Milestone:
Component: Circumvention/BridgeDB Version:
Severity: Keywords: bridgedb-ci, jenkins, bridgedb-0.3.2
Cc: isis, sysrqb, weasel Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

…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.

Child Tickets

Change History (1)

comment:1 Changed 4 years ago by isis

Cc: weasel added
Keywords: bridgedb-0.3.2 added
Resolution: fixed
Status: newclosed

This is fixed in my fix/15464-ci-directives_r1 branch, which is merged for bridgedb-0.3.2.

CCing weasel so that he knows I did the thing that he suggested I do. :)

Note: See TracTickets for help on using tickets.