Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.devtools bob.devtools
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.devtoolsbob.devtools
  • Issues
  • #18
Closed
Open
Issue created Mar 01, 2019 by André Anjos@andre.anjos💬Owner

Should encapsulate scripts/ci better

There are a few things we could do to make the CI scripts better to test and functionality more re-usable:

  1. It would be good that every environment variable required inside those commands is read from the command-line interface. That would give the chance for a user to test these recipes on their local installation before pushing changes
  2. The deployment of artefacts (conda packages and documentation) could be better encapsulated into functions that are more re-usable. Then, apply DRY where it matters!
Assignee
Assign to
Time tracking