Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • MystiQ MystiQ
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • 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
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • swl-x
  • MystiQMystiQ
  • Issues
  • #8
Closed
Open
Issue created Nov 14, 2019 by swl-x@swl-xOwner

Use of travis-ci for CD/CI, packaging and releases.

Created by: stdevPavelmc

By using Travis-CI for Continuous Development and Continuous Integration we will be able to test the code ASAP and monitor any change/break point.

Also we can use travis for the release procedure and packaging (.deb/.exe) for different platforms.

I will contribute to that goal with code & test in my free time.

Assignee
Assign to
Time tracking