150 likes | 272 Views
In the pursuit of optimizing our Agile infrastructure, we must critically assess the effectiveness of our current tools like GitWeb, JIRA, Crucible, Jenkins, and GitLab. Are our workflows efficient and well-integrated? This discussion highlights the importance of collaboration within our tools, and whether they contribute to a smooth workflow. We examine various version control options and continuous integration systems, aiming to identify gaps and improvement areas. Your input is vital in making technology work for us, leading to a more productive Agile environment.
E N D
Current tools Gitweb JIRA Crucible Jenkins pilot (!!) GitLab (Q3/Q4?)
Workflow Tools Do we feel that our workflow is easy enough? Is there too much work in our workflow?* Is there enough flow in our workflow?* How integrated are these systems? How well can we collaborate? * Apologies for the horrible jokes.
I am not here to make a decision I am here to make a point
Version Control Choice An example
Version Control Email patches to each other Perforce CVS SVN Bazaar Mercurial Git
Continuous Integration Bamboo (Java/Atlassian) BuildBot (Python/FOSS) CruiseControl (Java/FOSS) Jenkins/Hudson (Java/FOSS) TeamCity (Java/JetBrains) Tinderbox (Perl/FOSS) Travis CI (Ruby/FOSS) (Hosted Recommended)
Documentation • ServiceNow (??) • Sphinx (Python/rST) • DocBook (Java/XML) • Gollum (Git/Many) • Microsoft Word • LaTeX (Many/LaTeX)
Problems • Do It Yourself • Maintainability • Outsourcing • Commercial • Open Source • Hosted • Self-Hosted • Man Hours
Solutions • Discussion • Evaluation • http://www.mediawiki.org/wiki/Git/Gerrit_evaluation • Make compromises • Software sucks • Implementation Agnosticism
Aims Few Man Hours Few Man Hours No Man Hours No Man Hours No Man Hours