Build

1
Build Release Best Practices Steps to Ensure
Reliability, Repeatability, Performance
2
Agenda

• Todays Development Build Challenges
• Hidden Cost of Build and Release Problems
• Best Practices from Industry Leaders
• How BuildForge Supports Best Practices System
  Overview
• Questions and Answers

3
Todays Build Release Challenges
Current Conditions
Business Impact

• Manual, error-prone build processes
• Proprietary, internally-developed build systems
• Inconsistent processes for different products and
  platforms

• Unpredictable product release cycles
• Costly systems to support maintain with
  knowledge held by few
• More work requires more people limited
  repeatability or portability for new projects and
  platforms

4
Todays Build Release Challenges, Contd
Current Conditions
Business Impact

• Dependence on the build team for execution,
  status, and troubleshooting
• Differences between developer environments and
  production systems
• Multiple tools in the product lifecycle

• Burdens staff and requires increased headcount to
  take on new projects
• Unreliable nightly and production builds
• Product lifecycle tracking and versioning - audit
  trail - non-existent

5
Hidden Development Costs Broken Build Processes
Examples

• Resources wasted in execution of builds and
  manual detection of build-related errors
• Scrapping of undocumented, proprietary systems
  when key personnel are lost
• Engineer headcount added to satisfy build-related
  work
• Developer productivity losses due to build delays
• Lost revenue due to delayed product releases
• Burden on staff to meet compliance regulations

6
Best Practices from Industry Leaders
7
What Customers Told Us
Five Build Release Best Practices

• Automate build and release process
• Connect essential systems source, build, test,
  deploy
• Establish an automated way to share information
• Integrate early and often continuous integration
• Establish audit trail for compliance and measure
  improvements

1
2
3
4
5
8
Best Practice Automate Build and Release
Automate the build and release process
1

• Create automated handoffs at each phase (close
  stitch points)
• Common interface for all processes
• Developer self-service in a predictable environ
• Automatic error-detection

Critical issues to consider

• Portability of processes to support future
  workflows
• Provide access without compromising security

9
Automation Decreases Build Time
After Push button, unattended Negligible
developer time 3 hour build, 1 person 3 hour
build
Before 12 hour weekly process2 hrs per
developer/wk 16 hour build, 2 people 60 hour
build
10
Self-Service Creates Efficiencies

• After
• 20 increased productivity
• Product teams can view and execute builds
  on-demand
• Immediate results reduce troubleshooting time
• Integrated system across all platforms
• Payback in lt 6 months

11
Best Practice Connect Essential Systems

• Connect essential systems

2

• Establish a one-stop view of project status
  across all tools and systems
• Incorporate automated tests into the build
  process

Critical issues to consider

• Be flexible enough not to constrain development
  tasks
• Consistent versioning through product lifecycle

12
Adobes Architecture The Matrix
13
Best Practice Connect Essential Systems
An effective build and release system requires a
tight integration with the source environment

• Create a seamless link between source and build
  activity
• Execute builds based on source activity
• Answer the question what changed? for each
  build
• Understand who built what, when
• Understand trends in source activity by build
  over time

14
Best Practice - Communicate

• Establish an automated way to share information

3

• Self-service, real-time status on build progress
• Reduce developer wait time
• Unattended notification of errors
• Take administrative tasks off your plate

15
Communicate the Entire Development View
A real-time, consolidated view of code, build,
test, and defectinformation for a
product/release.
16
Best Practice Continuous Integration

• Integrate early and often

4

• The longer you wait to build, the more painful it
  will be
• Provides teams with valuable feedback
• Daily cycles now becoming hourly or continuous
• Automation is an essential prerequisite

17
Continuous Integration Increases Quality
Weve had a 20X improvement in our ability to
execute builds for the organization. With our
first product, we were able to improve from 18
builds per week to over 360 builds per week!
Across 50 other projects, that will save us 75
Million annually!
Bob SetterboSenior Computer ScientistAdobe
18
Best Practice Audit Trail and Metrics
Establish audit trail and measure improvement
5
The right build environment creates an audit
trail tosupport regulatory compliance initiatives

• Traces back to the only reliable record the
  executable providing accurate details about
  release contents
• End-to-end bill-of-materials including source
  changes, tests performed, and defects resolved
• Self-documenting record provides a continuous
  audit trail
• Enforcement of development standards processes

19
Best Practice Audit Trail and Metrics

• Measure improvements

Collect quantifiable before after data

• Short-Term
• Total build time
• development cycles
• New project set-up time
• Time to make project changes
• errors per build
• Hardware utilization
• Deployment time

• Long-Term
• Process scalability
• Developer productivity
• CM team productivity
• On-time product schedules
• Development cycle time
• Reduced staff training time
• Audit preparation time

20
How BuildForge Supports Best Practices
21
The Value Best Practices BuildForge Bring

• Reduced cost of software delivery
• By increasing productivity and automating
  processes
• Increased quality of product delivered
• By increasing the number of code cycles
• Decreased overall time to market
• By removing life cycle stitch points
• Decision Support
• By providing critical information about your
  build and release life cycle

22
World-Class Customers
Corporate Development
Corporate Development and IT
23
BuildForge Simplifies the Complexity
24
Architecture
25
End -to-End Automation
1
26
Connect Essential Systems ClearCase
2
27
View Change Lists for Each Build
28
View Diffs for Troubleshooting
29
Communicating Step-by-Step Results
3
30
Notify Teams with Detailed Information
31
Configure for Continuous Integration
4
32
Establish an Audit Trail
5
33
Measure Improvements
34
Understand Server Utilization
35
Analyze Source Activity by Build
36
Questions and Answers
37

• Thank You!
• To learn more
• Visit us at the ALM Expo virtual trade show!
• Webcast Achieving Build and Deployment
  Excellence
• White paper Agile CM for Large
  Organizationswww.buildforge.com/agile

www.almexpo.com