New answers tagged

1

Don't ever leave code on just one box. Hard drives fail. People get sick. Accounts get locked out. Buildings catch on fire. And sometimes other people just need to see what you've been up to. Use a separate branch. Commit often. Keep it in sync. Don't commit broken code without SAYING that it's broken and HOW it's broken. It's so much easier to back ...


3

If you're using git, you should be doing your work in a branch. Create as many commits as you like on this branch, but don't check them into your CI server. The CI build should be kept clean. You don't want other developers accidentally getting your broken code. Once you are finished your work (or at least have a compilable chunk of code), you can ...


1

Some CI software can quarantine test failures (quarantine is the word that atlassian use for this, other CI tools may be different). It will record the test failure, but it won't fail the build. However, the way that I would approach this is to create a bugfix branch, write the test on this bugfix branch so that the branch fails to build. When the bug is ...



Top 50 recent answers are included