Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !5142

Add a download buttons for Build Artifacts

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Lin Jen-Shin requested to merge artifacts-from-ref-and-build-name into master Jul 07, 2016
  • Overview 287
  • Commits 117
  • Pipelines 1
  • Changes 34

What does this MR do?

This MR adds a download buttons for build artifacts of latest succesful pipeline in:

  • dashboard of project,
  • branches and tags views,
  • and tree viewer

Implement #4255 (closed)

What are the relevant issue numbers?

Closes #4255 (closed), Closes #14419 (closed)

Screenshots

Project main

Branches

Tags

Source Tree

Does this MR meet the acceptance criteria?

  • CHANGELOG entry added
  • Documentation created/updated
  • Download buttons
  • Models
  • Routes
  • Projects::ArtifactsController
  • API
  • Tests
    • Rails
      • Project#builds_for
      • branch name with slashes
      • only success builds
      • only latest builds
      • feature tests for download buttons
    • API
      • branch name with slashes
      • only success builds
      • only latest builds
    • All builds are passing
  • Conform by the style guides
  • Branch has no merge conflicts with master (if you do - rebase it please)
  • Squashed related commits together
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: artifacts-from-ref-and-build-name