Option to replace previous job on addjob about testswarm

[Krinkle]

The main purpose of testswarm is to distribute and automate continuous unit testing. What's the point in removing the old jobs, then you will no longer be able to track when a particular test broke.

When submitting a job the url given should be a static one, not a dynamic one. ie. http://example.org/mootools-checkouts/r12345/tests/index.html

Reason being that tests run asynchronous, so basically do svn checkout into a directory and submit the job with tests, rather than svn update and re-submit the same urls.

Suggesting wontfix.

[Krinkle]

I think you might have confused projects with jobs. A job is to run all tests for a project in a specific state. A project (or "user") is a collection of jobs (usually organized by revision id of their version control repository).

So whenever a new commit for MooTools comes into their trunk you create a new job. This is also important due to the asynchronous nature of TestSwarm. If a job is added for revision 1234 and half-way you change the job to revision 1235 (i.e. by running svn update or git pull), then some of the results of that job will be for one revision and some for another. Instead it should do a separate checkout in another directory and submit a new job.

If you no longer need a certain job you can just let it be, ignore it. Or delete it if you really want to, but in general it is useful to have historical data and a timeline to spot when things broke for a certain browser.

Closing issue for those reasons.