If you work with subversion, how can you organize that developers can easily checkout the last working build and work on this one, instead of working on a potentially broken HEAD?
The idea behind the question is as follows. When a lot of developers work simultaneously on a project, it can happen that someone breaks the build or some tests. Continuous integration helps to find these things early, but it does not prevent that the HEAD release is temporarily broken. So I want to give everyone the ability to easily check out and work on the latest revision known to be working, and only update to HEAD when necessary for a commit. Creating a tag with SVN seems not to be the appropriate way to do this, since in SVN a tag is essentialy a new branch and can hardle be moved after each successful build. How would you do this?
If your CI server notifies all developers, i.e. not just those who broke the build when a build breaks, your developers can avoid fetching a broken head by watching for a failed build email and holding off until the ‘build fixed’ email goes out. If a developer crucially needs to update (perhaps after a vacation), they can go back to the last good revision. Most CI software supports this. I know for a fact Jenkins provides a ‘last successful build’ link. If you wanted a web page to show this, like @forsvarir suggested, you could easily scrape this page.