[tor-bugs] #29173 [Internal Services/Service - jenkins]: Add meek-server in jenkins-ci

[Tor Bug Tracker & Wiki]

#29173: Add meek-server in jenkins-ci
-------------------------------------------------+-------------------------
 Reporter:  sysrqb                               |          Owner:  weasel
     Type:  enhancement                          |         Status:  closed
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Service - jenkins  |        Version:
 Severity:  Normal                               |     Resolution:  invalid
 Keywords:                                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by sysrqb):

 * status:  new => closed
 * resolution:   => invalid


Comment:

 Replying to [comment:1 gk]:
 > #29171 is the context here. So we should be sure to have the right Go
 version and make sure we deploy the result later on the BridgeDB side (for
 Moat).

 Yes, but it seems like our jenkins doesn't support downloading the build
 artifacts, so adding a meek-server job wouldn't be very useful for this
 right now.

 In some glorious future, it would be nice if we had a build system where
 we could get the most recent version of a program (meek-server, in this
 instance) and then we can deploy it onto the correct server. (The "deploy"
 step is another challenge in this scenario, but there are different tools
 for that, too). And maybe both stages run on the same server, but the
 "build" and "deploy" stages are automated.

 I'll close this, but we should have a discussion about how we can maintain
 the custom applications we are running on the servers.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29173#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online