Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch CI jobs to Debian Buster/Python 3.7 #527

Closed
eloquence opened this issue Aug 7, 2019 · 3 comments · Fixed by #616
Closed

Switch CI jobs to Debian Buster/Python 3.7 #527

eloquence opened this issue Aug 7, 2019 · 3 comments · Fixed by #616
Labels

Comments

@eloquence
Copy link
Member

Since we will soon migrate to Debian Buster for all workstation VMs (freedomofpress/securedrop-workstation#306), we should update the CircleCI config in this repository. The test job currently specifies no OS version, which means it is already running on Buster; however, it is using a version of Python older than the one included with Buster (3.7).

$ docker run -it circleci/python:3.5 bash
circleci@94b1a95f6999:/$ cat /etc/debian_version 
10.0

The build job specifies Stretch.

We should update both jobs to Buster, and consider using upstream images instead of the re-tagged CircleCI versions. python:3.7-slim-buster seems like a good fit for both jobs, according to @conorsch.

Because we do not intend to use Stretch much longer and the workstation is in development, we do not need to retain parallel Stretch jobs; we can revisit that if we encounter major issues related to the switch.

@eloquence
Copy link
Member Author

Poked at this briefly just in case it's a simple change, but it's not, so leaving some notes for the implementer. WIP in ci-to-buster.

@eloquence
Copy link
Member Author

For the 11/6-11/20 sprint, we've committed to adding buster build jobs for all relevant repos, and to add a buster test job for the securedrop-export repo.

@kushaldas
Copy link
Contributor

Will push a pr after the evening.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants