Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • schedules schedules
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • schedulesschedules
  • Issues
  • #9

Closed
Open
Created Apr 10, 2018 by David Haynes@dhaynes3🙆Owner

CI for running test, linting, and builds

Summary

Gitlab CI is a fairly full featured and built in approach for adopting CI into a project. Follow the templates from other SRCT projects and create a pipeline to be ran on every commit pushed up to ensure that things don't catch on fire without you knowing about it. Ask @dhaynes if you have any questions.

Helpful Links

  • https://git.gmu.edu/srct/whats-open/blob/master/.gitlab-ci.yml
  • https://docs.gitlab.com/ce/ci/examples/test-and-deploy-ruby-application-to-heroku.html
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking