This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
CollabNet is a leading provider of Enterprise Cloud Development and Agile ALM products and services for software-driven organizations. With more than 10,000 global customers, the company provides a suite of platforms and services to address three major trends disrupting the software industry: Agile, DevOps and hybrid cloud development. The CollabNet TeamForge® ALM platform can be deployed on-premise or in the cloud. CollabNet complements its technical offerings with industry leading consulting and training services for Agile and cloud development transformations. Many CollabNet customers improve productivity by as much as 70 percent, while reducing costs by 80 percent.
For more information, please visit www.collab.net.
Carahsoft Technology Corp. is the trusted Government IT solutions provider. As a top-ranked GSA Schedule Contract holder, Carahsoft serves as the master government aggregator for many of its best-of-breed vendors, supporting an extensive ecosystem of software manufacturers, resellers, and consulting partners committed to helping government agencies select and implement the best solution at the best possible value. Carahsoft is consistently recognized by its partners as a top revenue producer, and is listed annually among the industry's fastest growing firms by VAR500, CRN, Inc., Washington Technology, Washington Business Journal, and SmartCEO.
For more information, please visit www.carahsoft.com.
• 19 years working in and across software and IT disciplines
• Experience with 100’s of developers and development teams
• Focused on distributing knowledge and solving unique problems within software development organizations
• Key Client Accounts include;
At CollabNet, I am an Enterprise Transformation Manager. I work with large and small software development organizations to improve the Application Lifecycle Management (ALM) process through the use of TeamForge, OSS, and best practices.
Prior to CollabNet, I spent 12 years in software development. Much of that was spent at Sony Computer Entertainment including work as the Director of Tools and Technology, overseeing the development and deployment of a worldwide collaboration portal, and managing tools and process adoption and standardization.
① Ops, DB, and App Developers implement user stories from TeamForge and commit changes to SVN/GIT, the user stories and code changes are associated.
② A CI build job runs, executing unit tests, code analysis, etc, a TeamForge Build Artifact is created, change notes are generated and associated.
③ Every 15 minutes or on-demand a snapshot build is published to the Nexus Repository. The snapshot build is deployed to the Development servers by Automic.
④ The Project Manager reviews the Change Notes and Release Folder in TeamForge and using the data decides to promote a build as a Release Candidate, she creates a Release Manager Artifact (RMA) and set it to “Ready to Release.”
⑤ A Jenkins Release Candidate Promotion job runs executing the application builds, publishing the artifacts to Nexus and populating Automic with the release meta-data.
⑥ An Automic package references the Nexus release holding the release candidate to be deployed.
⑦ Operations, QA and/or Change Management promote and deploy the release candidate using Automic Workflows.
⑧ At each promotion and deployment step the TeamForge Release Artifact is updated from Automic and team members receive email notifications.
⑨ The Release Dashboard in TeamForge provides up-to-date pipeline Activity Reports and Release Notes.
⑩ Dev, QA, Ops and Management can view the Release Dashboard inTeamForge to track acitivy and make informed decisions.
• In a DevOps organization, developers, testers, and operations teams share goal• Support clear and constant communication
Development based on operational input, operational plan on development input
• Developers understand how their software is going to be deployed• Operations understands what is being deployed• All stakeholders know when it is being deployed
Take a trust but verify approach to governance
• Enable developer to act rapidly• Capture all activities• Implement strong checks where needed, eliminate where the are not
Automation is a must
• Repeatability is critical to risk reduction and traceability
CollabNet is a leading provider of Enterprise Cloud Development. With more than 10,000 global customers, the company provides a development platform and services to address three major trends disrupting the software industry: Agile, DevOps and hybrid cloud development. CollabNet TeamForge® ALM, ScrumWorks® Pro Agile project management and Subversion Edge and Enterprise Git source code management can be deployed separately or together, in the cloud or on-premise. CloudForge ® enables cloud development through a flexible platform that is team friendly, enterprise ready and integrated to support TeamForge and leading third party tools. CollabNet complements its technical offerings with industry leading consulting and training services for Agile and cloud development transformations. Many CollabNet customers improve productivity by as much as 70 percent, while reducing costs by 80 percent.
For more information, please visit www.collab.net.
This report compares multiple versions (may be in separate projects) and displays the “Kill Rate” (time to close an artifact) – with the Cycle time for that Version to be deployed into Production.
This kind of metric is unique to CollabNet. Traditional Agile Burn Up / Burn Down charts (also available in CTF) do not show any connection to an actual deployment environment
① Ops, DB, and App Developers implement user stories from TeamForge and commit changes to SVN/GIT, the user stories and code changes are associated.
② A CI build job runs, executing unit tests, code analysis, etc, a TeamForge Build Artifact is created, change notes are generated and associated.
③ Every 15 minutes or on-demand a snapshot build is published to the Nexus Repository. The snapshot build is deployed to the Development servers by Automic.
④ The Project Manager reviews the Change Notes and Release Folder in TeamForge and using the data decides to promote a build as a Release Candidate, she creates a Release Manager Artifact (RMA) and set it to “Ready to Release.”
⑤ A Jenkins Release Candidate Promotion job runs executing the application builds, publishing the artifacts to Nexus and populating Automic with the release meta-data.
⑥ An Automic package references the Nexus release holding the release candidate to be deployed.
⑦ Operations, QA and/or Change Management promote and deploy the release candidate using Automic Workflows.
⑧ At each promotion and deployment step the TeamForge Release Artifact is updated from Automic and team members receive email notifications.
⑨ The Release Dashboard in TeamForge provides up-to-date pipeline Activity Reports and Release Notes.
⑩ Dev, QA, Ops and Management can view the Release Dashboard inTeamForge to track acitivy and make informed decisions.