Opened 9 months ago

Closed 9 months ago

#29173 closed enhancement (invalid)

Add meek-server in jenkins-ci

Reported by: sysrqb Owned by: weasel
Priority: Medium Milestone:
Component: Internal Services/Service - jenkins Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi!

Can we have meek-server builds included in jenkins-ci? I see there are build instruction here: https://gitweb.torproject.org/pluggable-transports/meek.git/tree/meek-server/README

It seems relatively simple (assuming go-lang is installed)

	cd meek-server
	go build

https://git.torproject.org/pluggable-transports/meek.git

Child Tickets

Change History (2)

comment:1 Changed 9 months ago by 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).

comment:2 in reply to:  1 Changed 9 months ago by sysrqb

Resolution: invalid
Status: newclosed

Replying to 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.

Note: See TracTickets for help on using tickets.