Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • I iapi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • 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
  • immerda
  • Immerda Apps
  • iapi
  • Issues
  • #6

Closed
Open
Created Jun 15, 2020 by o@oOwner

how can we run the test in CI

just wanted to start a discussion on how we will run the tests in CI, because to me it is not clear how, when and where.

Here are some issues that we need to resolve:

  1. the tests depend on iapi-hack and there is no pinning of the iapi-hack version needed
  2. iapi-hack needs containers to be started
  3. the tests depend on the socket client from https://code.immerda.ch/immerda/ibox/puppet-modules/-/tree/master/ib_iapi/files, again no pinning

for 1 and 3, my solution would be to hard-code a commit hash in .gitlab-ci.yaml, I find that simpler and better for this usecase than submodules or such.

but 2 I am not sure how to deal with... I guess we could use the container config of iapi in iapi-hack as the base, then start a postgres container as service, then have a modified setup.rb which just fills in the db and creates the config for the iapi, then we can start iapi and run the tests. is there an easier/cleaner way which does not require yet another mode of setting up the environment?

Assignee
Assign to
Time tracking