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.

  • Created by Unknown User (johnsonli), last modified on Apr 14, 2020

Use this article when you want to share your code with the Leidos developer community.  Before you begin, review the ECR CONOPS.


The high-level process for submitting code is shown below.

Figure 1. ECR Submit Code/Resource Workflow

ECR-SubmitWorkflow

Step-by-step guide

  1. Go to the SecDevOps Service Desk and open a request to Submit Reusable Code. You will need to provide an approver (Project Manager or Technical POC) and the Contract Record Number (CRN) or Charge Number that was used to develop this code. Your charge number is required to locate and identify your contract for the IP Legal review and will not be charged for setting up the ECR project. This information is required to initiate the process.

  2. The project will be created and permission will be granted to the requestor so that the code can be uploaded into the ECR git repository, artifacts can be uploaded to the Artifactory repository. No additional permissions for managing the code will be provided until the code has completed the review cycle.

    1. The requestor creates a repository and uploads the source code.
    2. Once the code has been uploaded, the requestor must respond to the original SecDevOps Service Desk request.
  3. Complete the ECR Governance Spreadsheet for the IP/Legal Review. It can be downloaded here.
    1. Upload the completed spreadsheet to the Submit Reusable Code service desk request.
    2. Once received, it will be forwarded to IP/Legal for an opinion
    3. Wait for approval
  4. Once the code has been approved for general use, the SecDevOps Engineering team will set the permissions on the repository to be accessible by the Leidos developer community (any Leidos US-US account). By default, cloning and branching will be allowed by the Leidos developer community.  The requestor has authority to manage the settings on the repository.
  5. The Requestor manages any merge requests on the code base.


If you are only requesting Artifactory repositories, you will still be given a Bitbucket project for the minimal documentation requirement.






The information contained herein is proprietary to Leidos, Inc. It may not be used, reproduced, disclosed, or exported without the written approval of Leidos.
CONTROLLED DATA