Skip to content

GitLab Next

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

Merged
Opened Jan 26, 2017 by Seweryn Zeman@seweryn.zemanContributor3 of 4 tasks completed3/4 tasks

Added post_build_script to call scripts after user-defined build scripts

  • Overview 4
  • Commits 1
  • Pipelines 1
  • Changes 5

What does this MR do?

This MR adds possibility to define post_build_script that can be defined in config.toml just like pre_build_script but which is launched after user-specified build scripts were launched.

Why was this MR needed?

It is found useful to make administrative meta-tagging for deployed projects.

Are there points in the code the reviewer needs to double check?

Not really.

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Closes #2077 (closed)

Assignee
Assign to
Reviewer
Request review from
v1.11
Milestone
v1.11 (Past due)
Assign milestone
Time tracking
Reference: gitlab-org/gitlab-runner!460
Source branch: features/post-build-script

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.