Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,936
    • Issues 34,936
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,271
    • Merge Requests 1,271
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #239518

Closed
Open
Opened Aug 22, 2020 by Duncan Harris@duncan_harrisDeveloper10 of 11 tasks completed10/11 tasks

Always display build info for packages in the UI

Summary

Deploying the same package artifact with the same version from different branches and/or commits is accepted but:

  1. The package list shows the first deployment
  2. The package history only reflects the creation
  3. The details page shows the branch that created the package, not the most recent commit
  4. The details page shows duplicate files for each deployment

Steps to reproduce

  1. Set up repository that deploys package using CICD
  2. Use a branch to deploy the same package with the same version
  3. Check if the package details were updated to reflect the second deployment

Example Project

https://gitlab.com/duncan_harris/maven-package-test/ The test package

What is the current bug behavior?

Packages deployed multiple times with the same version do not reflect multiple deployments.

What is the expected correct behavior?

The package should show it's deployment history.

Relevant logs and/or screenshots

Output of checks

This bug happens on Gitlab.com on GitLab Enterprise Edition 13.3.0-pre 66a7f57b

Results of GitLab environment info

Results of GitLab application Check

Possible fixes

Implementation plan

  • Change package association with build_info to has_many, but create a method build_info that will return the first of build_infos to maintain existing behavior.
  • Remove unique index from database to allow for has_many.
  • Update each package type to create the build info anytime a package is published, not just when it is initially created.
  • Add package_file_build_infos to relate individual files to builds.
  • Add build info to packages that don't yet have it?
    • Conan
    • PyPI
    • NuGet
    • Composer (if applicable)
    • GoProxy ( if applicable)
  • Update the front end to be able to accept multiple pipelines for a package
Edited Dec 02, 2020 by Tim Rizzi
Assignee
Assign to
13.7
Milestone
13.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#239518