background preloader



List of revision control software This is a list of notable software for revision control. Local data model[edit] In the local-only approach, all developers must use the same computer system. These software often manage single files individually and are largely replaced or embedded within newer software. Open source[edit] Client-server model[edit] In the client-server model, developers use a shared single repository. Open source[edit] Proprietary[edit] Distributed model[edit] In the distributed approach, each developer works directly with his or her own local repository, and changes are shared between repositories as a separate step. Open source[edit] Proprietary[edit] BitKeeper – was used in Linux kernel development (2002 – April 2005)Code Co-op – peer-to-peer version control system (can use e-mail for synchronization)Sun WorkShop TeamWare – designed by Larry McVoy, creator of BitKeeperPlastic SCM – by Codice Software, Inc Notes[edit] See also[edit] External links[edit]

Trac KB Article: Useful Queries for TRACK2SQL There are several ways to track various server problems using TRACK2SQL, and this article discusses some of the most common queries you might use. Times returned by these queries are in milliseconds. Process IO Consumption The following SQL statement returns user, command and "IO used", to show which processes consumed the most IO. SELECT user,cmd,SUM(pagesIn+pagesOut) as io FROM tableUse JOIN process USING ( processKey) GROUP BY tableUse.processKey ORDER BY io DESC LIMIT 25; Example Output from this SQL statement: Longest Compute Phase The following SQL statement returns a list of users, commands, and the length of the compute phase to show which processes had the longest compute phase: SELECT user,cmd, MAX(readHeld+writeHeld)-MAX(readWait+writeWait) as compute FROM tableUse JOIN process USING (processKey) GROUP BY tableUse.processKey ORDER BY compute DESC LIMIT 25; Example output from the SQL statement. Average Wait Time SELECT AVG(readWait+writeWait) as wait FROM tableUse; Read/Write Percentage

Flying Meat: FlyStash FlyStash & Boomerang FlyStash is a lightweight cgi script written in python that acts as a very simple wiki. While it doesn't support nearly as many features as most wikis, it does have a couple of redeeming qualities. It's very simple to install and use, and it works with Boomerang as a document store. Boomerang is a Mac desktop application which connects to FlyStash servers to retrieve, edit, and synchronize pages. You would use Boomerang to edit pages when you are in situations where you can't connect to the internet, or just because it's a nicer experience than editing in a web browser. FlyStash and Boomerang are very much alpha products. So whatever you do don't rely on these applications to store important information. Requirements: Mac OS X 10.3 or later. Download: Boomerang beta 1. How to install FlyStash on Mac OS X: Ok, so with that out of the way open up the Terminal and past in these commands to install FlyStash: Advanced Stuff Want another space on your FlyStash instance?

Git Workflows and Tutorials | Atlassian Git Tutorial The array of possible workflows can make it hard to know where to begin when implementing Git in the workplace. This page provides a starting point by surveying the most common Git workflows for enterprise teams. As you read through, remember that these workflows are designed to be guidelines rather than concrete rules. We want to show you what’s possible, so you can mix and match aspects from different workflows to suit your individual needs. Centralized Workflow Transitioning to a distributed version control system may seem like a daunting task, but you don’t have to change your existing workflow to take advantage of Git. However, using Git to power your development workflow presents a few advantages over SVN. Second, it gives you access to Git’s robust branching and merging model. How It Works Like Subversion, the Centralized Workflow uses a central repository to serve as the single point-of-entry for all changes to the project. Developers start by cloning the central repository.

Painless Bug Tracking Painless Bug Tracking by Joel Spolsky Wednesday, November 08, 2000 TRS-80 Level-I BASIC could only store two string variables, A$ and B$. Keeping a database of bugs is one of the hallmarks of a good software team. If I can bend your ear a moment, I'd like to explain a pretty painless way to do bug tracking, in the spirit of my previous articles on painless schedules and painless specs. First of all, you need a real database. Let's follow a bug around, for the purpose of illustration, from the moment it's born until someone finally puts it out of its misery. Here's what happened. Mikey the Programmer is hacking away on the new FTP client feature of his groovy Macintosh software. Bad things happen when you don't reuse code, Mikey. Later that week, Jill the Very, Very Good Tester is banging away at the code, rolling her forehead back and forth on the keyboard or some equally cruel test. Jill squints at the list of repro steps. Jill enters the new bug in the bug tracking database. Part three.

git - petit guide - no deep shit! git - petit guide juste un petit guide pour bien démarrer avec git. no deep shit ;) par Roger Dudler (translation by KokaKiwi) Remerciements à @tfnico, @fhd, Namics this guide in english, deutsch, español, indonesian, italiano, nederlands, polski, português, русский, türkçe, မြန်မာ, 日本語, 中文, 한국어 installation Télécharger git pour Mac OSX Télécharger git pour Windows Télécharger git pour Linux créer un nouveau dépôt créez un nouveau dossier, ouvrez le et exécutez la commande git init pour créer un nouveau dépôt. cloner un dépôt créez une copie de votre dépôt local en exécutant la commande git clone /path/to/repository si vous utilisez un serveur distant, cette commande sera git clone username@host:/path/to/repository arbres ajouter & valider Vous pouvez proposer un changement (l'ajouter à l'Index) en exécutant les commandes git add <filename> git add * C'est la première étape dans un workflow git basique. envoyer des changements branches mettre à jour & fusionner tags remplacer les changements locaux

TagCloud Keep your build artifacts in the repository – James Fisher – Medium After your CI server builds your product, what does it do with the build artifacts? In my experience, it stores them on a disk somewhere, using some ad-hoc version scheme to distinguish between different builds. It might also publish them to some artifact server, which again uses some ad-hoc version scheme to allow users and developers to download different versions. I suggest that the CI server should instead use a repository for versioning and distribution of build artifacts. Check out source: git checkout e3125fa.Run build system: . The advantages of this approach are several: Easy checkout of builds. (Really, I’m just re-hashing the advantages of git, but applied to build artifacts rather than build sources. ‘I was told not to commit build artifacts!’ Yeah. What I’m suggesting is only a slight variant of this scheme, but it does not suffer from the problems associated with it. ‘But my artifact is just a big binary blob!’ No it isn’t. Tracking multiple builds per commit Thoughts?

Consistency “Consistency, thou art a jewel.” —popular saying “Consistency, from Sciral, does one thing and does it well. Its interface is pleasant, original, and crystal clear. It's utterly simple to use. ... In short, this is my kind of program.” “What an app! “Thanks for writing this application. “Love it! Now $10 for Desktop Editions and only $1.99 for iOS! What's New? Available for iPhone, Mac and Windows! Click here! Check out the version history for information on the latest updates. What is Sciral Consistency? Calendars are great for keeping track of tasks where you need to coordinate with others by setting fixed times and intervals. To-do lists are great for keeping track of tasks that you will do once, and that you need to keep in order by priority. But there's another class of activities for which neither traditional calendars nor to-do lists are optimal. The kinds of activities or tasks you use Sciral Consistency for share a number of attributes: What are some examples of appropriate tasks?