1. Forge.mil
Overview

2. Agenda
Forge.mil Background
RACE Overview
Continuous Integration
Next Steps – How do I participate?

3. Forge.mil FORGE.mil TODAY TODAY Agile development and testing
Developer
Tester
User
Certifier
Shared Test & Development Tools/Services/Environments
Shared Asset
Libraries & Repositories
FORGE.mil
Agile development and testing
Cross-program sharing: software and services
Early and continuous collaboration
Integrated approach to development life cycle
Extensible platform to support delivery of partner capabilities
TODAY
Siloed development environments
Expensive and time consuming start-up
Limited exposure, sharing, or re-use
Duplication of effort
TODAY
Siloed development environments
Expensive and time consuming start-up
Limited exposure, sharing, or re-use
Duplication of effort
Forge.mil Vision
Enable the rapid development, test, certification, deployment and acceptance of new products and services on the GIG
by providing policies, processes, tools and a federated development and test infrastructure.
Why Forge.mil?
The Department recognized a need for a collaborative environment for developers, testers, Warfighters and other stakeholders for the rapid development, testing, certification and deployment of software.
Current Statistics 3

4. Policy and Guidance
HR 2647, National Defense Authorization Act for Fiscal Year 2010, Sec. 804.
“The Secretary of Defense shall develop and implement a new acquisition process for information technology systems. The acquisition process developed and implemented pursuant to this subsection shall, to the extent determined appropriate by the Secretary —
. . . be based on the recommendations in chapter 6 of the March 2009 report of the Defense Science Board Task Force on Department of Defense Policies and Procedures for the Acquisition of Information Technology; and
. . . be designed to include —
early and continual involvement of the user;
multiple, rapidly executed increments or releases of capability;
early, successive prototyping to support an evolutionary approach; and
a modular, open-systems approach.”
H.R National Defense Authorization Act for Fiscal Year 4

5. Application lifecycle management (ALM) for the DoD Enterprise
Requirements management
Source code management
Discussion forums
Project wiki
Document management
Project management for distributed development teams
Tasking & alerts
Release management
Real-time reporting
Software development services
Bug, Issue Tracking
Share software, best practices, information
Current Forge Product is built on CollabNet Team Forge.
Current Capabilities of Software Forge and Project Forge include a set of Project Management Tools
Task Management, Requirements Management via a tracking tool and Reporting
A set of Developer Tools
Source Code Management (Subversion repository), Bug and Requirements Tracking, Release and Configuration Management,
And a set of Collaboration tools
Discussion forums, Project wiki pages and Document Management
Continuous Integration
Extending the toolset
. . . 5

6. Forge.mil Services Access to Forge.mil
Free, collaborative development environment for open-source and DoD community source software
On-demand, fee-for-service, development environment for individual programs and projects
Access to Forge.mil
DoD Civilian, Military, DoD contractors
PKI User Authentication
CAC or ECA Certificate
Open source or DoD Community Source projects
Enable Re-use of common functionality
Enable cross-DoD collaboration
Primary differences between SoftwareForge and ProjectForge – Access (more fine grained permissions) and Cost (SoftwareForge is free, ProjectForge is fee for service)
SoftwareForge is used for the Development and Distribution of:
Open Source and Public Domain Software
DoD Community Source
Distribution to DoD employees and contractors for official US Government use
Enables reuse of software when Government has acquired Unlimited Rights or Government Purpose Rights (DFARS)
Open Source licensing is used for existing OSS software that someone in DoD is modifying and storing on Software Forge for internal DoD use DoD Community Source is for DoD initiated code (or even things like SharePoint Web Parts) that needs to be shareable within the Department
When to choose ProjectForge
When you need greater access control
SoftwareForge operates as an open community where every member has visibility into project artifacts
ProjectForge provides customizable, role-based access controls
When you don’t have the intellectual property rights necessary to share your software with the entire DoD community
SoftwareForge supports open-source and community-source (Government Purpose Rights or Unlimited Rights) software projects
ProjectForge can be used to support the development of proprietary/limited rights software projects
When you want greater control over the core platform functionality
Site branding, project specific templates, custom extensions, product configuration
Multi-Tenant Environment
Isolated project spaces for each customer
Shared infrastructure
Private Environment
Full environment dedicated to your program 6

7. Benefits of Using Forge.mil
FOR DEVELOPERS
FOR MANAGERS
FOR EXECUTIVES
Access a full featured development platform over the web or directly from your IDE
Have fewer meetings and less administration when collaboration is part of everyday development
Link to continuous integration servers and provision build and test servers in the cloud
Speed new project startup
Secure access to project assets
Enhance team productivity and collaboration
Improve visibility into project status
Reduce management and administrative overhead
Access critical team assets via the web
Consolidate and centralize to reduce administration, licensing, and infrastructure costs
Establish governance and compliance
Improve predictability of the development organization
Integrate easily into existing systems to extend return on investments
DISA’s goal is to reduce the subscriber cost of ProjectForge with each fiscal year customer renewal term. This is possible by aggregating the growing number of ProjectForge users across projects, services, and agencies to reduce infrastructure and operational costs. 7

8. Community Victories Sample Hosted Projects Army Navy Air Force
Apps 4 Army: Innovation challenge to develop new ‘mashup’s of Army data
SOSCOE: System of Systems Common Operating Environment - tactical middleware
Navy
Gargoyle: a network activity monitoring and analysis system
NEP-O: Naval Enterprise Portal Oceanography – Agile process used heavily
Vulnerator: Aggregation of security readiness findings for systems
Air Force
AF EIM: code supporting Air Force’s Enterprise Information Management
AF IIB: Air Force Initial Infrastructure Build
Marine Corps
DCGS-MC: Distributed Common Ground/Surface System – Marine Corps
MAGTF C2: Marine Air Ground Task Force Command and Control
Joint Organizations
NSLDSS: National Senior Leader Decision Support Service
DIB: Distributed Common Ground/Surface System (DCGS) Integration Backbone
JAIWG: JFCOM led Joint Architecture Integration WG
TILT: Three-dimensional Imaging Lidar Toolkit
As of 2 July 2010:
1300 software releases available
30,000 software downloaded
14,000 bugs/requirements tracked
11,000 code commits
2000 discussion posts 8

9. Rapid Access Computing Environment
RACE Overview
Rapid Access Computing Environment 9

10. Rapid Access Computing Environment1
Need 2
Log into portal 3
Drop down menu with catalog of services
Server Image: Operating Systems:
1-4 CPU, 1-8 GB RAM, Red Hat 4.6, /64 bit
60 GB Storage Windows 2003/8, 32/64 bit
1 TB optional storage available (per server) 4
Choice of services 5
Funds transferred (MIPR/gov’t credit card) 6
Services provisioned and customized
Use Cases:
STRATCOM – ISPAN validation
ARMY – Applications for the Army 7
Software provisioned and customized 8
Warfighter uses services 10
Purchase in 7 minutes ~ Ready for Use < 24 hours

11. Application Accreditation in RACE
Path-to-Production Execution Process
Streamlined and automated IA C&A
Standard process for customer
Accreditation time reduced from 80+ days to 40 days
End state objective of 7 days for C&A
eMASS: Enterprise Mission Assurance Support System (eMASS)
Automates the creation of select DIACAP artifacts
Populates DISA’s inherited controls into the workflow process
Provides customer an advanced, dynamic workflow management tool
Test &
Development
Promote
to Production

12. The Pathway To Production offers RACE Customers a T&D migration path to production, and an accelerated C&A process
Virtual Operating Environment Migration
Accelerated C&A Process Execution
The Path-to-Production allows users to migrate their Development (Zone B) environments to Limited User Testing (Zone A) environments
When Limited User Testing is completed, the customers are able to seamlessly transition to a DECC production environment
Inheritance of the RACE cloud and DECC facility is leveraged to implement IA controls in the VOEs
Virtual Operating Environments that are purchased from RACE are pre-hardened, and Developer Friendly
Tools that facilitate automation and workflow management of the C&A process such as eMASS are implemented
Virtualized Production Zone
RACE Compute Cloud
Zone A
Zone B
Environment Promotion to Production
NIPRNet / GIG
Environment Promotion to Test

13. Current RACE White List
.COM
.MIL

14. Entrance Criteria define a set of standards that provide the framework of the streamlined Path-to-Production C&A process
Customers who wish to benefit from the streamlined approach to development and test must adhere to the following RACE standards
RACE customers who are unable to meet the entrance criteria will be ushered to their CME representative for implementation assistance.
Environment Criteria
C&A Criteria
eMASS & VMS must be used as the C&A automation tools to enable promotion to Test and Production environments
An IATT, IATO, or ATO is required in Test
Test plan must not exceed 30-days duration without approval of RACE IAM
An IATO or ATO is required to move in to Production (no IATT)
An IATT only allows limited user testing. Testing limitations are enforced via the duration specified in the Customers test plan
RACE is NIPRNET only
Development and Test is completed in a virtualized environment
Start with provisioned VOEs provided by RACE (Windows/Red Hat)
Customers must begin in either Development or Test prior to moving to Production
Adhere to the RACE standard set of ports and protocols for Test and Production
Customer must relinquish ROOT authority when moving to Production

15. To Acquire RACE Nodes 15

16. To Acquire RACE Nodes
Race Portal 16

17. Current Cost RACE Virtual Server Configuration Operating System
Cores
Memory
Base Storage
Monthly Rate
Windows 2003/2008 / Red Hat 4.X, 5.X
32-bit, 64 bit 1 60
$500 2
$862 3
$1,293 4
$1,724
$1,000
$2,000 8
$3,448
Additional SAN Storage - Up to 1TB in 10GB increments
$28.20/10GB

18. After Placing an Order For help configuring RACE to work with Forge:
Within 1 business day (from receipt of payment)
RACE node is provisioned
Administrator receives a confirmation & instructions:
need to set-up VPN client
configure node for use with Forge and CI (e.g. Hudson)
For help during order or configuration of RACE:
RACE Helpdesk, FAQ, Quick-start Guide
For help configuring RACE to work with Forge:
Forge.mil Continuous Integration Project at:

19. Continuous Integration
Improve the quality of your software and reduce the time taken to deliver it.

20. Continuous Integration
… the practice of frequently integrating the source code committed by the developers on a project
Regular build processes assurance that the code is always in a state that allows the application to be built successfully
Bugs/issues identified early in the development cycle
More efficient software delivery
After a successful build, the Continuous Integration engine can manage the execution of automated tests
Once the build is fully tested, the Continuous Integration engine can deploy the application into a test environment for continued review by the test team (e.g. functional testing)
Improved visibility and project transparency

21. Continuous Integration Environment
Informs
Manager
Commit
Watches
Uses
Version Control
(Forge.mil)
Build Integration
(Hudson)
Build Scripts
(Ant, Puppet, Bash,
PowerShell)
Developers
Automated Pull
Test 1
(Automated Regression Tests)
Compile/Tag Source
Run Unit Tests
Run Functional Tests
Run Test Coverage
Static Code Analysis
Build Database
Test
Tester
Nightly Pull
Test 2
(Manual & Migration Tests)
Inspect
On-Demand Pull
Stakeholder
Sandbox

22. Agile Information Assurance and Continuous Integration
Repeatable Builds
Frequent code integration
Functional regression and security testing
Static Analysis checks for
Coding conventions, Duplicate code,
Bad coding practices, Race conditions, …
Security Scans incorporated to check for
Cross-Site Scripting (XSS), Cross-Site Request Forgery (XSRF)
Injection/Input handling, Content issues, …
Functional test
Scripted test of software functionality
Regression testing

23. Continuous Integration and Automated Testing

25. Upcoming Capabilities: Full Application Life-cycle Support
Cloud Hosting Environment
Dashboard, Reporting & Monitoring
Development
Zone
Validation/
Pre-Production Zone
Production
Zone
Build Libraries & Code Repositories
IT & Data
Standards
Agile Software
Development
Static Code
Analysis
Unit, Integration &
Regression Testing
System
Testing IA
Certification
Release & Operations
Management
Today
Q4 10
Q2 11
Q4 11
Q4 12

26. Next Steps Get an account
Navigate to (requires a valid DoD CAC or ECA Certificate).
Under New Users, click on ‘Create an Account’.
Your account is active once your address is confirmed.
For info on how to obtain and install an ECA Certificate, see the FAQ – “How can I get access to Forge.mil” at
Use the resources on SoftwareForge to learn, explore and understand the capabilities
Learn and explore in the SoftwareForge TestProjects (Sandbox–1 and –2)
Join or create a Project and begin collaborating
Need to establish your own ProjectForge Project? Contact Forge.mil Business Office at
Still have questions – contact the Forge.mil Community Management Team at or
SoftwareForge Document ID – doc3808

27. Questions? Continuous Integration: gene.gotimer@coveros.com
Now open up to Q&A, please type your questions in the chat box on your screen
Continuous Integration:
Agile Development:

28. To Acquire RACE Nodes
Race Ordering Page 28

29. To Acquire RACE Nodes
Order Specifications 29

30. To Acquire RACE Nodes
Shopping Cart 30

31. To Acquire RACE Nodes
Completing the Order 31