Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • OpenTAP OpenTAP
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 132
    • Issues 132
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 54
    • Merge requests 54
  • 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
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenTAP
  • OpenTAPOpenTAP
  • Issues
  • #490
Closed
Open
Issue created Jan 05, 2021 by Asger Iversen@asgerOwner

Track package installation count

To allow package developers to follow the adoption of their package. We should add a ping from an OpenTAP installation back to the package repository with anonymous info about which packages are installed (probably their IPackageIdentifier).

  • Package names (or the entire identifier) should be cryptographically hashed so only package names already in the repository will be identifiable.

  • This ping should also serve as an update check, and the repository should respond with any packages that could be updated. This is already implemented on the server-side, and an interface already exists here.

  • To distinguish (and be able to count) installations, each ping should contain an anonymous ID representing the installation.

  • An engine setting (browsable false) should be added to allow users to opt-out of the tracking-ping/update check.

Eventually (not part of this issue), we can visualize this info in the package repo frontend on packages.opentap.io.

Edited Jan 05, 2021 by Asger Iversen
Assignee
Assign to
Time tracking