Skip to content

GitLab

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

Closed
Open
Opened Apr 10, 2018 by David Haynes@dhaynes3🙆Owner
  • Report abuse
  • New issue
Report abuse New issue

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 admin enable hashed storage. More information
Assignee
Assign to
1.0 - MVP
Milestone
1.0 - MVP (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: srct/schedules#9