CONTROLLED DATA
Leidos Proprietary - US Citizens ONLY
The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.
This article provides a high-level description of what to expect if you are planning to migrate projects into Secure DevOps (SDO).
Be prepared to answer these questions
- Please familiarize yourself with our sites and services
- SDO Service Desk - https://helpdesk.sdo.leidos.com/servicedesk/customer/portal/4?src=sidebar
- SDO Knowledge Base - https://confluence.sdo.leidos.com/display/SDOKB
- SDO Engineering Community - https://confluence.sdo.leidos.com/display/SDOEC/SDO+Engineering+Community
- User Management
- All users must be US-US
- All users must have a Leidos account (yes, your subcontractors Leidos sponsored accounts will work)
- All users must be on Leidos Network (VPN using OTP or direct)
- Jira
- Current version of your source system
- Add-ons in your source system that are not present in SDO (Verify the add-ons here)
- Customization
- Workflows
- Custom Fields
- Screens
- Schemes
- Portfolio plans do not migrate automatically and must be recreated by the project after migration
- Confluence
- Add-ons in your source system
- Calendars and fully qualified links will not be migrated.
- Please read these article about best practices to assist with migration. They apply to page links and attachment links
Step-by-step guide
Use the SDO Service Desk request and follow directions at Migrate Project to Secure DevOps. Complete the form. Include in the description much information as possible. For example, any customization, add-ons, current version of the applications to be migrated.
- SDO Engineering reviews the request and schedule an engineering meeting to be certain all pertinent information has been provided for a smooth migration which includes.
- Your current version
- Any customization (fields, screens, workflows, etc.)
- Any add-ons not installed in SDO
- Exported files from source are shared with SDO Engineering and dry runs are executed in the DEV environment.
- Source projects with customization require an add-on “Project Configurator” be added to the source for exporting configurations in a single step.
- May require that SDO Engineering stand up a temporary version of the application that matches the source (if the source cannot be upgraded to match the target) This is why the Project Configuration add-on (a) is necessary – in most cases it alleviates this step (b) and allows export/import on disparate versions
- May take multiple iterations during the dry run in DEV as the biggest hurdle tends to be migrating users..
- Allow project to test and verify the integrity of the migration in DEV.
- Schedule a cut-off date and migrate to the production target
- Export the source data
- Import the source data
- Test and verify the integrity of the migration
Mini migration can occur in our DEV environment before attempting a migration in the PROD environment at any time provided SDO Engineering has the information from #1 above.