Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • MC Job Options MC Job Options
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 9
    • Merge requests 9
  • 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
  • atlas-physics
  • pmg
  • MC Job OptionsMC Job Options
  • Merge requests
  • !7

New triggers for skipping specific CI jobs and update of README

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Spyros Argyropoulos requested to merge check_common into master Jun 08, 2019
  • Overview 6
  • Commits 277
  • Pipelines 0
  • Changes 2

This job addresses two issues, as discussed in #6 (closed)

  1. Switching to new development model using branches instead of forks

Forks will not work since some CI jobs (logParser, athena) rely on hidden variables that are not transferred to forks. The only supported way of running those jobs would be to use branches. Since the master branch is protected (noone can push to it and only maintainers can merge) there is no risk for unwanted merges (everything has to be approved and merged by maintainers) so in principle we could give developer role to everyone

  1. Skipping specific jobs

I removed the option to skip the following jobs:

  • jO naming (check_jo_consistency)
  • unique physics short and have changed the trigger in order to be able to skip specific jobs
  • modified files can be skipped with [skip modfiles]
  • logParser check can be skipped with [skip logparser]
  1. README has been updated accordingly. Also added a description of the pipelines
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: check_common