letsencrypt / pebble / 1126 / 1
0%
master: 8%

LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran
Files 1
Run time 0s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 0.0%. First build
GO111MODULE=on

push

travis-ci

jsha 
Configure AppVeyor to deliver native Windows containers of Pebble and Challtestsrv (#213)

Fixes #208. As a prerequisite, #212 must be merged before.

This PR configure an AppVeyor pipeline to build and publish native Windows
containers of Pebble and Challtestsrv on Docker Hub. This pipeline execute
the same logic that his Linux counterpart on Travis CI: go build, go
test using chisel2 and `acme` module from Certbot, then docker build +
docker push.

The CI part (build + test) is executed for every commit on every branch
(including pull requests). The CD part (docker deploy) is executed
only for tags pushed on Pebble repository. When triggered, the CD will
publish two native Windows dockers on the `letsencrypt/pebble` and
`letsencrypt/pebble-challtestsrv` Docker Hub projects: * the pinned
release tag `X.X.X-nanoserver-sac2016`, that corresponds to the tag
released on the GIT repository (Linux counterpart is `X.X.X`) * the
rolling release tag `nanoserver-sac2016` that is the latest pinned release
(Linux counterpart is `latest`)

Aside AppVeyor configuration, I also modified chisel2 to be runnable on
both Python 2.x and Python 3.x, because Certbot needs to run on Python
3.x on Windows. I also made some lights corrections on the Travis CI
pipeline to make it live nicely with AppVeyor.

Once this PR have been merged, one thing will need to be done from
the Pebble maintainers that I cannot do myself. Indeed, two secured
environment variables are required by this pipeline: `DOCKER_USER` and
`DOCKER_PASS` that are the Docker Hub credentials used to push the image
triggered by a GIT tag push, to trigger a release.

These credentials need to be set with the login/password
of a user authorized to push to `letsencrypt/pebble` and
`letsencrypt/pebble-challtestsrv` Docker Hub projects. To do so, go to
the AppVeyor Pebble project > Settings > Environment, and add the two
environment variables (name + value) in the "Environment varia... (continued)

0 of 54 relevant lines covered (0.0%)

0.0 hits per line

Source Files on job 1126.1 (GO111MODULE=on)