Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • P Pre Shipping
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 33
    • Issues 33
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • Pre Shipping
  • Issues
  • #51
Closed
Open
Issue created Sep 14, 2021 by etienne peysson@epeyssonMaintainer2 of 6 checklist items completed2/6 checklist items

ADR: E2E preshipment team A workflow bot

Status

  • Draft
  • Proposed
  • Trialing
  • Under Review
  • Approved
  • Retired

Context & Scope

Following the Preshipment validation dashboard :

preship-validation-scope

There are multiple manual steps to achieve in order to test each workflow. This seems to be error prone and time consuming.

This ADR focuses on the following steps :

- Authenticate to any CSP
- File uploading whenever required
- Trigger DAG
- Validate the workflow
- Generate a report
- Clean up

That work could be also be extended with the following :

- Bulk loading

Another ADR has been approved for maintaining Postman collections to be integrated for testing on DAGs and services endpoints end to end executions.

There might be some overlapping with the Postman Collection ADR.

Proposition

Implement a script/framework so we can test each use case independently from any computer but also a Gitlab pipeline (e2e tests).

  • Pros :

Get a clear report of the process so we can more easily provide feedbacks.

Have a common place with configuration templates to fill in for CSPs (another script could also help on that part).

Add other workflows using the existing framework.

Test using multiple source files.

Match the framework version with the releases so pipelines could be run in multiple test environments at the same time (as long as environments are available).

Easy onboarding for new developers.

  • Cons :

Maintenance of the configuration parameters (CSPs) should follow releases cadence.

Needs developers

Decision

Rationale

Consequences

  • Direct consequence on the Preshipment team A.

When to revisit

Tradeoff analysis - input to decision

Decision timeline

Edited Sep 14, 2021 by etienne peysson
Assignee
Assign to
Time tracking