[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #15464 [BridgeDB]: BridgeDB's continuous integration setup steps should be separate scripts
#15464: BridgeDB's continuous integration setup steps should be separate scripts
----------------------------------+----------------------
Reporter: isis | Owner: isis
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: BridgeDB | Version:
Keywords: bridgedb-ci, jenkins | Actual Points:
Parent ID: | Points:
----------------------------------+----------------------
â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 [https
://travis-ci.org/isislovecruft/bridgedb/builds here]. The script which
controls the setup and testing procedure for these builds is BridgeDB's
[https://gitweb.torproject.org/bridgedb.git/tree/.travis.yml?h=develop
.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.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15464>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs