Skip to content
Snippets Groups Projects

Heptapod CI: (too) simple triggering of heptapod-tests

Merged Georges Racinet requested to merge topic/heptapod/trigger-heptapod-tests into branch/heptapod

Instead of trying a programmatic conversion of branch names, (not clear whether that would apply to fill in the triggered pipeline branch), we're defining two jobs, using branch rules.

The drawback of this approach is that we're writing to the 'heptapod:testing' image over and over. With the current low traffic on Omnibus Heptapod, this should still be ok.

A followup could be to create Docker tags based on the Node id, and then trigger the functional tests by passing the Docker tag…

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
Please register or sign in to reply
Loading