3 ms·
>> For the first month or so I take a very humble listening position .. and then - Everything in source control - CI - Static code analysis - Artifact
by pards 8y ago
>> For the first month or so I take a very humble listening position
.. and then
- Everything in source control
- CI
- Static code analysis
- Artifact repository
- Automated deployments, incl database and configs
- Branching strategy & pull requests
- Standalone dev env per developer
- chatmasta 8y agoWhat do you use for an artifact repository? I’m assuming you mean the cached artifacts of builds, but also vendor artifacts/cache like npm_modules or docker containers? This sort of vendor dependency management is a problem I haven’t found a great solution for yet. I’m actually thinking about creating a product that’s implemented as a proxy and supports multiple package managers, including docker, and caches all downloads keyed by branch. This way in the event of some catastrophic dependency failure you have a place to find the last working set of vendor dependencies that didn’t break the build. Would anyone be interested in this? What is current best practice for this workflow?
- jzl 8y agoOne popular option: https://jfrog.com/artifactory/ https://jfrog.com/artifactory/