Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • ensembl
  • Merge requests
  • !443

Gitlab CI: enable triggering of dependent builds on Travis

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marek Szuba requested to merge gitlabci_dependents_on_travis into master Nov 13, 2019
  • Overview 3
  • Commits 6
  • Pipelines 1
  • Changes 1

Created by: mkszuba

Description

Extend .gitlab-ci.yml so that ensembl pipelines on EBI GitLab can trigger dependent builds in projects still using Travis.

Use case

The switch from to GitLab CI is to take place on a per-team basis so there will be dependent projects on Travis.

Benefits

Ensure CI compatibility of Core projects on EBI GitLab with dependent projects still on Travis.

Possible Drawbacks

In order for all dependent builds to be triggered successfully the user whose API token is used to authenticate with Travis REST API must have write access to all dependent repositories, which will have to be set up manually (in case of all-Travis runs there is implicit organisation-wide trust).

Testing

Have you added/modified unit tests to test the changes?

No.

If so, do the tests pass/fail?

N/A

Have you run the entire test suite and no regression was detected?

N/A, changes only affect the running of tests on EBI GitLab.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: gitlabci_dependents_on_travis