i was constantly restarting that job and the failures seemed to almost always be purely environmental to travis so there was that problem too in general. thanks for the reminder as to why we had it in the first place. i think that sounds right.
On Thu, Jan 28, 2021 at 3:42 AM <[email protected]> wrote: > I think the purpose of the docker build in Travis was to find build > problems in the docker build automatically. I vaguely remember that the > docker build was broken once and we didn't notice it as we didn't execute > that automatically in Travis. > But since the build seems to introduce more problems than it solves, so > I'm also OK with removing it. > > -----Ursprüngliche Nachricht----- > Von: Stephen Mallette <[email protected]> > Gesendet: Mittwoch, 27. Januar 2021 17:54 > An: [email protected] > Betreff: [DISCUSS] travis docker build > > At some point we started doing a docker build in travis. I'm not sure what > purpose that served exactly as it doesn't seem to do any additional options > beyond those we already build directly in other jobs. As it stands, docker > builds are failing with what looks like a need to pass dockerhub > credentials as part of the job. I guess that could be figured out, but I > wonder if it's worth it. > > Given changes in docker rate limiting and travis seeming to tighten up on > the free build tier, perhaps it would be best to just kill the docker build > job out. Any objections or better ideas? > >
