Don't make persistent changes to the build environment in jobs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 19
- Forks
- 18
- Avg merge
- 1d 53m
- Merged PRs (30d)
- 1
Description
Several jobs make persistent changes to the build environment, e.g. https://github.com/openmicroscopy/devspace/blob/0.10.0/home/jobs/BIOFORMATS-push/config.xml#L78 which installs scc outside of a sandboxed virtualenv.
Either these dependencies should be in the Dockerfile, or in a dedicated virtualenv. Moving all builds to docker would also solve this problem.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with home/jobs/BIOFORMATS-push/config.xml around line 78 and inspect the other job definitions for dependencies installed outside virtual environments. Review the relevant Dockerfile options, then verify that job dependencies no longer persist in the build environment and remain available to the jobs that need them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, ci-cd, devops
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100