1406132 - Build config busted for releases for win32

Status: RESOLVED WONTFIX

(Testing :: geckodriver, enhancement)

Description

[Henrik Skupin [:whimboo][⌚️UTC+2]]

Originally reported as: https://github.com/mozilla/geckodriver/issues/951

Due to an outdated docker image which is using non-existing sources for apt, necessary packages can no longer be installed. As result we can no longer produce win32 release builds for win32.

We already got a couple of reports on the github repository that people are missing those builds. We should try to get the docker image updated, or removed at all if it is not needed anymore.

I haven't worked with docker yet, so where is the image actually built? Does it have to be uploaded to the hub? Or how is Travis handling that?

Andreas, can you give some insights here please?

Comment 1

[Andreas Tolfsen ❲:ato❳]

(In reply to Henrik Skupin (:whimboo) from comment #0)

> We already got a couple of reports on the github repository that
> people are missing those builds. We should try to get the docker
> image updated, or removed at all if it is not needed anymore.

To get a build out the door quickly, it is possible\ to upload a
cross compiled binary done locally.

I’m not sure, however, it is the best use of time to get cross
compilation working on Travis as we will want to make releases to
GitHub directly from TaskCluster in the future.  Perhaps it would be
a better investment to get the Windows builds working there.

> I haven't worked with docker yet, so where is the image actually
> built? Does it have to be uploaded to the hub? Or how is Travis
> handling that?

Docker uses the configuration in
testing/geckodriver/i686-trusty/Dockerfile to automatically build an
image.  Documentation on this is available here:

	https://docs.docker.com/engine/reference/builder/

Comment 2

[Andreas Tolfsen ❲:ato❳]

I’m inclined to say that we should spend our time on setting up
TaskCluster so we can release directly from there instead of
spending time on this.