Tag Info

New answers tagged

1

If I understand your question correctly, the only reason you want a "clean master" at all times is so that you can "react fast if something is broken". I believe this is best served by doing hotfixes on release branches, rather than moving all non-hotfix tasks to non-master branches. Basically, you do all development work on master as usual, then when the ...


0

It is possible to build from two repos in one Bamboo plan. Build plans allow multiple repositories. The first and default task in a plan is a source code checkout for the repo. You can then add another source code checkout task for the second repo (with an optional checkout directory) The other option is to have a build plan for your web interfaces that ...


0

Never mind the current deployment, if you (or your customers) run a previous version you may need to get a snapshot of that version going to reproduce an issue for an incident or compare current undesirable behaviour to a previous build. That includes not just the application, but test data, and test details as well.


0

"Once it's deployed and working, why would you ever want to go back to a previous version ?" The key words here being "and working". In a perfect world, every new version would be thoroughly tested and completely accurate before it is deployed. But in real life, that doesn't always happen. What if you discover a critical bug that was introduced, not in the ...


1

Being able to rollback to the current version is a different way of saying "rollback to the previous version", now to do that you have 2 ways of doing this: You can simply make a copy of the current version before deployment, and if anything goes wrong, just replace the new version with the backup copy. You can create a system where you can deploy any ...


8

In short: Since you don't know whether a build contains a critical bug at the time of deployment, you may need to roll back more than one version when you're deploying at a relatively high frequency. If your setup doesn't allow you to do so, your only alternative is to roll forward as quickly as you can. As soon as you have an application that has 3rd ...


4

Fabric is a deployment tool, not a CI server. Jenkins is and its awesome. Its basically a glorified script-runner that's integrated into your SCM (with lots of extras), so it looks at your SCM and runs scripts when commits are made. One of those scripts will be to deploy automatically. A CI server is basically an automated way of performing half the tasks ...



Top 50 recent answers are included