New answers tagged continuous-integration
Some inspiration of what is possible can be found on these existing Performance Dashboards. Unfortunately, not all of them are free software, and neither of them seems to be ready-to-use by others: https://datazilla.mozilla.org/ http://goperfd.appspot.com/perf http://speed.pypy.org/ https://chromeperf.appspot.com/
What is the best way to get a grip on intended and unintended performance changes in such a setup? I don't know anything about your benchmark suite, but as far as I understand the question, this can be implemented as an automatic test (I assume you have already a test suite with integration or acceptance tests in place). What you need is a ...
I believe that the best approach for your case is using Jenkins with the Performance Plugin. It has nice graphs and can be used both with JMeter and SoapUI. Also test performance is important. According to Martin Fowler it is better to run fast unit tests for every commit and slow integration and performance tests every few hours.
I have a limited amount of experience with Jenkins. One thing I really liked about it was the dashboard display that had been set up by my colleagues, using plugins for Jira, Subversion, and Clover (code coverage). Jenkins supports quite a number of plugins and you can develop them yourself. I know that Hudson has a similar extensibility.
Yes. The newer Team Foundation Server versions support Git, so if you set up your TFS repository to use git, you can easily use TFStogether with the build-in git version control tools in Xcode.
You don't have to use TFS inside Visual Studio, though Microsoft seems to prefer this "buy one, get one for full price plus SQLServer and CALs" solution :) You can access TFS from an external source control. They have a Windows Explorer plugin that works much like TortoiseXXX products, allowing you to commit and update directly from the filesystem icons. ...
Doesn't seem so bad all in all. Ok, so you want feature branches in your repository workflow. Simple: Where it says 'release build', you need to make a tag with the appropriate version number and use that to build the releases. It allows you to respond to feedback from Integration and QA testing by applying changes to the tag (and passing the changes back ...
I'll try keep my answer focused on the How could we make this process more obvious? part of the question you asked. Simplifier processes do tend to get a "that's obvious" response from users, but are difficult to articulate and develop. Some things I don't see in the diagram or don't know if they exist in your documentation; How code changes flow ...
That's right - document tools that produce HTML should be put on a webserver. If you have many projects, just copy the html output into subdirectories and update a master index page that links to each one. You can put a link to each project's html 'start page' in a wiki for each project (if you use a project management site like redmine or trac). The point ...
Top 50 recent answers are included