2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.
If you were registered and logged in, you could join this project.
NOTE: Sin is not hosted on tigris.org's CVS server.
To obtain a working copy, you must use Subversion and check out the
source code from svn://sin.eudicon.com/sin/trunk. Looking for
pre-packaged distributions? Try the
File sharing area.
What is Sin?
Sin is a framework for implementing Continuous Integration
on top of the Subversion version control system. Read a short introduction to Sin
here and take a guided tour of Sin.
Why use Sin?
- Stable codebase
Sin ensures that your codebase is stable at all times. Here, stable is defined as the codebase obeying all rules you set up in your Sin system (codebase must build, all tests must pass, etc.).
- Sin saves your time
Developers will never be bothered with the consequences of incorrect changes that cause broken builds. Sin automatically reverts (undoes) any change that violates one or more rules and notifies the developer who checked in the change, of the problem.
- Sin is easy to set up and use
Use the graphical setup application to set up your Sin system in minutes. Once set up, developers hardly know Sin is there until they check in a change that breaks the build - in which case Sin might just have saved the developer from public humiliation.
- Easy reviewing
Sin can send checked in changes in color-coded html by email for easy reviewing by other developers.
- Use your existing build system
No change to your existing build system is needed as long as your system can be built from the command line.
- Sin is scalable
Sin is a distributed system based on open standards like SOAP webservices and is easy to expand to handle new loads.