Our customers make the software that powers warfighting
Providing a suite of development and management services for the Defense Intelligence Information Enterprise that enables users to build valued software faster and more securely
Our list of software development and deployment tools is always growing.
Where do you want to start?
-
Jira
Issue Tracking, Agile Planning, Helpdesk Operations, and Agile Development
-
Confluence
Wiki, Documentation, Designs, Reports, Policies, and Procedures.
-
Bitbucket
Distributed, efficient Git source control and versioning
-
Jenkins
Automate software builds, tests, and deployments
-
Nexus
Store and cache artifacts, software dependencies, and binaries
-
Sonarqube
Catch bugs and vulnerabilities in your apps
-
Fortify
Identify exploitable vulnerabilities in source code (Team License Required)
-
TestRail
Integrated test case management
-
Discourse
Modern Q&A and forum software for your community
-
Filesender
Securely and easily send arbitrarily large files
-
Storefront
A registry of reusable applications, services, and components
DI2E has revolutionized how we do business. I’ve got an all-star lineup of engineers we painstakingly found one by one, but for all that brainpower we really struggled to find documentation and code distribution mechanisms. Our IA counterparts balked at the idea of leaving it on GitHub and Sharepoint documentation made everyone consider looking down the wrong end of a shotgun. We have over 100 completely disparate sites we have to take care of with monthly releases and being able to point everyone to DI2E has been a complete gamechanger for us... It’s programs like this that make working in a DoD environment as a software engineer tolerable and make it possible to actually operate at the speed we should be operating at.
- Grant Curell, DoD software developer
I have multiple projects at our base setup with DI2E right now and more and more interest from other projects every day. This is definitely THE BEST development IDE the DoD/Government has ever provided. It's a one stop shop for developers and even in-service projects!
- Jenny Matheney, NSWC
I want to thank you and your team for getting the MDA project stood up in DI2E. Danford, Dana, David, Amanda, and Bobbie did an amazing job of getting it set up quickly and helping this non-technial PM work through a couple issues that were beyond my technical depth. You’ve got a great team, and they did a great job setting up the project. Thanks to you all.
- Brion Thomas, USN PEO C4I
First, I just wanted to offer my thanks for setting up and maintaining this service. The resources you have here are very valuable to my prototyping team and ensuring that we are getting the latest and greatest technologies in the hands of our warfighters. Thank you for your help.
- Steve Plassman, USAF AFRL
I am loving Jenkins and everything you guys do some awesome work keep it up!!!!!!
- Steven Gaddis, AMRDEC
Thank you for offering such a wonderful service. Thank you also for providing a docker registry for us to use.
- Zhao Li
We're excited here to have our project really taking off. We've got our first 4 sprint scheduled and can start tracking progress. DI2E is a great tool suite.
- William Pickl
Multiple Environments. Cross Domain.
US Only
Our flagship environment, operational since 2012, serves thousands of US users and projects across the DoD and Intelligence Community.
Suitable for projects that require ITAR, CUI, and FOUO protections.
Coalition
A collaborative software development environment serving the multinational/coalition community.
Secret
DI2E DevTools are also available on SIPRNet at www.di2e.smil.mil.
Frequently Asked Questions
General
-
What are the "DI2E DevTools"?
The DI2E Developer Tools provide an open development environment for the defense and intelligence community, offering a full suite of popular, widely used development tools. Project teams are able to establish cross-team efforts to support development, integration, and test needs. The tools support software development life-cycle activities by providing:
- Issue tracking
- Project collaboration
- Documentation and design artifact hosting
Aligning with Office of Acquisition, Technology, and Logistics (AT&L) Open Systems Architecture guidance, the DI2E Developer Tools provide ready access and accessibility to government-owned capabilities. It has the following immediate benefits:
- Reduce routine procurement of closed development environments on a costly contract-by-contract basis; infrastructure avoidance
- Cross-program developer coordination; start to reduce stove-pipes
- Promote development in the open, vice in a closed ecosystem
- Government developed code on government resources
-
Is there a cost or fee for using the DevTools or having an account?
- The DI2E DevTools are available at no cost to any Intel-related project in the DoD or IC.
-
Who uses DI2E?
- Every major command, service, and agency in DoD and the Intelligence Community. We support thousands of software development and project management groups. Some are actively conducting agile software development, while some are less agile. Many teams use DI2E because their work involves many different organizations and it is impossible/impractical for them to allow distributed access; DI2E enables this collaboration.
-
How does DI2E provide continuous integration support?
Here is an example of how DI2E tools provide continuous integration using the general flow of Plan → Code → Build → Test → Deploy (repeat):
- Plan: We have the Atlassian tool suite with includes JIRA for issue tracking and management. Confluence hosts project wikis for communication and documentation. These project spaces are not open to the internet.
- Code: We don't provide a cloud-based IDE, but we do provide source code management – Bitbucket is our most popular SCM tool as it provides Git functionality and we also have a subversion server
- Build: We provide a Jenkins server to perform builds on. We have multiple managed build agents that perform builds for the majority of projects and can also run builds inside of docker containers if needed (example for this would be if you wanted to build with specific versions of OS tools or libraries you can create/specify a docker image for Jenkins to use and that will make sure that your build environment is consistent and portable from your developer workstations to our managed build nodes)
- Test: In addition to any unit tests inside of your code we provide a SonarQube server that can identify issues and show test coverage regression.We host a Fortify SSC (Software Security Center) server. Customers can upload fortify scans to this server for reporting purposes. To make use of that your project would need to purchase a Fortify license.
- Deploy: We offer artifact deployment servers, Sonatype Nexus 2 and Nexus 3 for projects to deploy their artifacts to. This includes development and released versions ranging from maven jars to nodejs packages, yum, and docker images.
-
On which network fabrics can I find DI2E DevTools?
- The US-Only DI2E DevTools and Coalition DevTools are currently available on the open Internet. The Secret DevTools is available on SIPRNet and a similar environment is offered by our parent organization on JWICS.
-
Can DI2E host my application and/or can my project use DI2E's cloud services for hosting?
- DI2E does not provide PaaS or IaaS services that allow projects to host their services or applications. The DevTools suite does allows projects to store build artifacts and binaries but does not allow any run-time hosting of them.
DI2E Projects
-
What is a DI2E Project?
- DI2E uses a concept of 'projects' to determine resource and permissions separation within our hosted tools. Generally a project is directly related to a program of record although programs can have many different DI2E projects depending on their use-cases and needs. Each project within DI2E has a unique project key. The project key is used throughout all of the tools and also for specifying permissions.
-
What kinds of projects are allowed?
- DI2E DevTools provides Hosted Projects that will be used either for development, sustainment, or support for a Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) capability by a DoD or Intelligence Community organization.
-
Are all DI2E projects visible and shareable?
A key goal of the DI2E Framework is to provide an open and public environment in order to promote collaboration and interaction which may result in reuse and shared best practices with other DI2E users. DI2E users have the ability to control privacy and access to their tools and content. However, by default, all projects are setup to be open/shareable to the DI2E community. DI2E helps projects move toward being more open and visible, and encourages all programs to promote the DI2E ideals of open architecture, open development, sharing and reuse, starting as early in the development life cycle as possible. However, each DI2E project can set its own visibility / sharing / permissions in each DevTool.
All DI2E users have the ability to read general information about any project's name, description, and points of contact. This permits DI2E users to reach out and collaborate where it makes sense.
-
How can I request a DI2E project?
-
We use Jira to receive and process new project requests. Please consider these choices carefully when requesting your team project:
- Project Name/Description. These are the most important sections which are typically not filled completely or clearly. Spell out acronyms and write a Project Name and Description that anyone or most can understand. All projects, whether public or private, are visible to entire community. Everyone can view basic information (e.g., project name, description, and POCs), so clear titles and descriptions are helpful.
- Hosted Project Access. This field indicates the level of access for other DI2E users. The three options are the following:
- "All DI2E Account Holders." This is fully accessible by all DI2E users and is the default setting. Requesting to be private is by exception.
- "Some Project Information is shared with all DI2E account holders." The intent for this option is some information is public and some areas are private. The areas that are private could include new individuals who request access via the project owner.
- "Private." Project is not accessible to other DI2E users. However, like option two above, a DI2E user can still contact the project approver and request access or to engage in general collaboration.
With these choices in mind users NEW to DI2E, can request a new project here: Submit a Project Request
An existing DI2E user can request a new project here: Create a Project Request
DI2E Accounts
-
Who can get a DI2E user account?
- DI2E supports three primary environments:
- US Only: In adherence with International Traffic in Arms Regulations (ITAR) restrictions, all users of the US-Only DI2E DevTools are required to have US citizenship. This requirement is necessary for both the user access to the DevTools as well as the access DI2E-hosted Jenkins build nodes.
- Coalition: The Coalition DI2E DevTools environment allows users from the United States, Australia, Canada, Great Britain, and New Zealand.
- Secret: All users of the SIPRNet DI2E DevTools environment are required to have US citizenship.
-
How can I get a DI2E account?
All users of the US-Only DI2E DevTools are required to have US citizenship. We can immediately validate your citizenship electronically if you hold a DoD Common Access Card (CAC) or DoD External Certificate Authority (ECA) certificate. Cleared DoD employees and contractors can pass their citizenship information to us electronically using JPAS. Users with access to JWICS email can provide electronic proof of citizenship via JWICS. Finally, we accept appointments for users that need to validate their citizenship using government-issued documents. Choose the first possible option:
If you have a DoD Common Access Card (CAC) or ECA certificate click here to create an account automatically.
If you hold a DoD clearance, click here for instructions on passing your citizenship information via JPAS.
If you have access to SIPRNet or JWICS email, click here for instructions on passing your citizenship information via JWICS email.
If you have a passport or US birth certificate, click here for instructions re: scheduling an appointment.
Contact DI2E Support
DI2E Dev Tools support is available during business hours (8am-5pm), U.S. East Coast time. Response and resolution times are based on the availability of support staff.
Please contact us for support:
- Customer Support Portal: https://helpdesk.di2e.net (DI2E Login Required)
- Email: helpdesk@di2e.net
- Telephone: 571-357-DI2E (3423)
Instructions for sending your citizenship information through JPAS
You MUST be in JPAS to select this option.
If you aren't sure, please ASK YOUR Facility Security Officer (FSO)!Requesting an account and validating your US citizenship is a two-step process that must happen in this order to proceed smoothly:
- Submit a new account request in DI2E JIRA Select "JPAS" as your "Source of citizenship".
- Ask your security office to pass your U.S. Citizenship information to us via JPAS using the information below. Please make certain your security officer submits your request as an individual request (not part of a group request) and that the purpose is "DI2E Framework Access".
- SMO CODE: 4ZTT65
- Destination: Volant Associates
- Address:15049 Conference Center Dr. STE 230 Chantilly, VA 20151
- POC: David Treat
- Purpose:DI2E Framework access
- Security POC: Matt Robles (703-652-9227 / matt.robles@volantco.com)
Instructions for sending your citizenship information through SIPRNet or JWICS email
Requesting an account and validating your US citizenship is a two-step process that must happen in this order to proceed smoothly:
- Submit a new account request in DI2E JIRA Select "IC/DoD PKI" as your "Source of citizenship".
- Choose one of the options below:
- From JWICS: Using your Intelligence Community (IC) PKI certificate, send a digitally signed email to DI2E-Accounts@nro.ic.gov - Please note that this email address is not reachable from any unclassified network.
- From SIPRNet Using your SIPRNet PKI certificate, send a digitally signed email to DI2E-Accounts@nro.smil.mil – Please note that this email address is not reachable from an unclassified network.
Note: In your email, please state you are requesting an unclassified DI2E account. Please provide your full name and the unclassified email account you used in the DI2E account request (step 1, above).
Note: Outlook and Webmail may not automatically sign your email for you. You must explicitly choose to digitally sign the message with your PKI certificate.
Instructions for validating your citizenship in person
** For cleared and uncleared individuals **
Requesting an account and validating your US citizenship is a two-step process that must happen in this order to proceed smoothly:
- Submit a new account request in DI2E JIRA Select "In-Person" as your "Source of citizenship".
- Reserve an appointment slot. There are two In-Person appointment slots per day:
Time Slots Monday - Friday (daily) at 10 am
Monday - Friday (daily) at 2 pmLocation Volant Associates
15049 Conference Center Dr.
Suite 230
Chantilly, VA 20151Reservations Please call/email ahead of time to confirm your appointment slot and to make sure that Matt Robles will be available when you plan to arrive. (703-652-9227 / matt.robles@volantco.com) Required Documents Recommended: Passport & Government issued Drivers License
Two forms of photo identification:
Proof of Citizenship for U.S. Citizens AND Second Form of Photo Identification Must have one of the following Current photo ID issued by a federal, state, or local government OR Secondary Photo ID - Current, valid U.S. Passport (also qualifies as one of the required photo IDs)
- Birth certificate issued by a government entity within the US or its territories
- Certificate of Naturalization
- FS-240 Consular Report
- DS-1350 Certification of Report of Birth.
- Certificate of Citizenship
Examples- This list is not exhaustive. You may use any current photo ID issued by a federal state, or local government. - Current, valid driver’s license (U.S. only)
- Government-issued photo identity card or badge (U.S. only)
- U.S. DOD Common Access Card (CAC)
Non-Exhaustive List of Examples: - Valid or expired passport (U.S. only)
- Valid or expired driver’s license (U.S. only)
- Government-issued photo identity card or badge (U.S. only)
- Student photo ID
- Official photo identity card or badge from your company or institution
- Credit card (with photo)
Questions Contact Matt Robles (703-652-9227 / matt.robles@volantco.com)
Production Workloads (Virtual Machines)
-
Does DI2E provide infrastructure for hosting websites or applications?
- Not at this time. DI2E provides virtual machines (Jenkins build nodes) that can be used to build and test software, but does not provide general purpose virtual machines or other hosting capabilities that would allow projects to deploy a website or application that external users could reach. Project teams need to acquire their own production hosting solutions.
Controlled Unclassified Information (CUI) / International Traffic in Arms Regulations (ITAR)
-
How do the DI2E DevTools meet the technical safeguards outlined in the DoD Instructions and NRO Directives to handle Controlled Unclassified Information (CUI) or subject to International Traffic in Arms Regulations (ITAR) information?
- Answer: see this page.
-
How can DI2E user teams properly mark and protect information that may be Controlled Unclassified Information (CUI) or subject to International Traffic in Arms Regulations (ITAR) policies?
- Answer: see this page.
Security / Accreditation
-
Are the DI2E DevTools Accredited?
- Yes, DI2E DevTools is accredited by a US government organization. Our accreditation documentation, including our signed authorization letter may be found here (DI2E login/account required). Please contact DI2E Security.
Programmatic Support
-
I have additional programmatic questions. Who should I contact?
- Please contact Greg (GM) Contreras.
Technical Support
-
How can I reach DI2E technical support?
DI2E Dev Tools support is available during business hours (8am-5pm), U.S. East Coast time. Response and resolution times are based on the availability of support staff.
US-only DevTools
- Email: helpdesk@di2e.net
- Telephone: 703-755-0072
Coalition DevTools
- Email: helpdesk-coalition@di2e.net
- Telephone: 703-828-1570
Contact Us
Interested in learning more? Start the conversation by emailing us at info@di2e.net.
Email UsNeed technical support? DevTools support is available during business hours (8am-5pm), U.S. East Coast time. Response and resolution times are based on the availability of support staff.
703-755-0072
Consent to Monitor
All information, including classified information, processed, stored, or disseminated via any system owned or managed by the United States Government (USG) IS THE PROPERTY OF THE USG. USG systems and access accounts are provided to users only for official USG purposes. Users of all USG systems and infrastructure have NO EXPECTATION OF PRIVACY in any data transmitted, processed, or stored by these systems.
All USG systems are subject to monitoring for maintenance, testing, security, counterintelligence, management, and other lawful purposes. Monitoring may include network analysis, automated intrusion, and misuse-detection systems, access, audits, logging, keystroke monitoring, and full-text review of files and electronic mail messages for all lawful purposes, to include ensuring the availability, integrity, and confidentiality of government information. Authorized officials may examine, record, copy, and appropriately disseminate any information discovered in the course of lawful monitoring activities.
Accessing a USG system or communicating across USG system infrastructure signifies your consent to such monitoring and your agreement to use information resources only for authorized purposes. System officials may provide evidence of intrusion, misuse, misconduct, criminal activity, or other malicious acts to the appropriate law enforcement or other authorities for appropriate action, which may include criminal investigation and administrative disciplinary enforcement.
Rules of Behavior
The following rules of behavior apply to all users of DI2E Systems:
- DI2E systems are for official purposes only.
- No unauthorized access. Passwords and access will not be shared.
- Pornographic or other offensive content is strictly prohibited Software copyrights and Licenses will be adhered to.
- All content subject to controls such as Controlled Unclassified Information (CUI), For Official Use Only (FOUO), and other special handling caveats will be properly labeled.
- Classified information will not be stored or processed.
- All non-compliance activities (e.g. spillages) must be reported to the DI2E support staff within four (4) hours of the inappropriate activity occurring.
These terms shall remain in effect while members use DI2E services and DI2E may terminate a member’s use or participation at any time for violation of these terms.
Approved Use
DI2E offers resources for software development and content creation, including communications tools, source code version control, project management tools, online forums, and personalized content.
- You maintain and administer project membership permissions. You are responsible for determining whether your Content is shared within the DI2E Community or if that Content is to remain private and shared only among project members. You are responsible for ensuring the correct permissions are applied to your Content to ensure Content that is private within a DI2E project is not exposed to the DI2E Community unless authorized by you.
- You are responsible for appropriately labeling and documenting any content that you submit, post or display; subject to controls such as Controlled Unclassified Information (CUI), For Official Use Only (FOUO), and other special handling caveats.
- All non-compliance activities (e.g. spillages) must be reported to the DI2E within four (4) hours of the non-compliance activity occurring.
- Links to third party web sites are provided solely as a convenience to the user consistent with the stated purpose of DI2E. The appearance of hyperlinks within DI2E does not constitute endorsement of linked web sites or the information, products or services contained therein. DI2E does not endorse or make any representations about the third party sites, or any information, services, or products found on the sites. If a user decides to access any of the linked sites, the user does so at their own risk.
These terms shall remain in effect while you use DI2E services and DI2E may terminate your use or participation at any time for violation of these terms or laws, or to protect the integrity of the services.