Skip to content

what would be required to transform this into an open source 'product'? #364

@samsmithnz

Description

@samsmithnz
  • Add more monitoring
  • Make it more secure - move secrets (pat tokens) from table storage to key vault
  • Add setup/installation scripting, with options
  • Add administration/setup functionality, to make it user friendly to add a new repo/build/etc
  • Add Why/When/Where/How do I use it - add documentation
  • Add more DevOps around the project, optimized testing, L0-L3 testing etc.
  • Improve resiliency - especially when interacting with the external dependencies and random failures that can happen - ensure there is a retry process built in and transparency around theses issues/data that flows in.
  • Do we need an upgrade process? or at least embed a version?
  • Release/announce

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions