Skip to content
Snippets Groups Projects

Draft: [ci] Allow Contributors to Manually Trigger External Fork CI

Closed Ursa (9R) requested to merge ursa/ci into develop
1 unresolved thread

Contributor with push access to the main repo would just run make gitlab-trigger-ci and input the merge request number and follow the link to trigger the pipeline run - subsequent run on the authors PR should bypass the lint/smoke/regression jobs.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
1 #!/usr/bin/env bash
2
3 # prompt for gitlab merge request id
4 echo -n "Enter Gitlab Merge Request ID: "
5 read -r MR
  • Asmund THORSec approved this merge request

    approved this merge request

  • Asmund THORSec mentioned in merge request !3124 (closed)

    mentioned in merge request !3124 (closed)

  • Ursa (9R) mentioned in merge request !3133 (closed)

    mentioned in merge request !3133 (closed)

  • Ursa (9R) added 2 commits

    added 2 commits

    • bf22f9d9 - 1 commit from branch develop
    • b077cc16 - [ci] Allow Contributors to Manually Trigger External Fork CI

    Compare with previous version

  • Author Maintainer

    I opened !3135 (merged) as a replacement from a fork repo to show how this behaves in practice.

  • closed

  • Multipartite mentioned in merge request !3135 (merged)

    mentioned in merge request !3135 (merged)

  • Please register or sign in to reply
    Loading