OLMIS-4117 Add git to dev image
|Participant||Role||Time Spent||Comments||Latest Comment|
|Author||39m||5||I agree, created OLMIS-4146. From my understanding of th...|
|Reviewer - 0% reviewed||33m||2||Separation of jobs might help to some extent, but the Jav...|
|Reviewer - 93% reviewed||37m||4||Nick Reid brought up package-lock.json files. We don't ha...|
|Reviewer - Complete||20m||2||You have good points. This seems to be one of the main dr...|
|Reviewer - Complete||4m||3||Sebastian Brudziński I fixed the problem|
We have started seeing problems with local and Jenkins build. I've investigated this briefly and I'm 90% sure the reason is renamed repo for one of our transitive dependencies - https://www.npmjs.com/package/drange (from discontinuous-range). The same repo was also renamed on GitHub, although using an old URL redirects to the new one and git clones still work properly (https://github.com/fent/discontinuous-range). It seems that upon failure to find the package on npm repo, it falls back to git and then fails, since we don't have git in our dev tools.
Are we fine adding Git to dev image?
If we are fine with this, I'll also release v4 and update all our services.
Branches in review
Issues Raised From Comments