Skip to content

Improve artifact end-to-end traceability #72

@algattik

Description

@algattik

Configuration management best practices demand there should be full traceability end-to-end from source code, build, release (model building & model deployment), as well as artifacts (model, container, pipeline runs etc.)

At this time there are gaps in achieving this, especially if concurrent builds are run, e.g.:

  • the model deployment pipeline picks up the latest build
  • the evaluate_model.py script assumes as described a comment: "Get most recently registered model, we assume that is the model in production"
  • When traceability is possible, things are quite buried and require a lot of scripting to surface

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions