Skip to content

CI pipeline rework - using stages and inheritance

Stanislav Židek requested to merge ep69/gnutls:ci-rework into master

Separating CI/CD pipeline into stages - fails can be spotted earlier and provides useful groundwork for splitting longer tests later. Using inheritance to decrease code duplication.

@dueno Daiki, could you have a look? Does it make sense from your point of view?

Checklist

  • Commits have Signed-off-by: with name/author being identical to the commit author
  • Code modified for feature
  • Test suite updated with functionality tests
  • Test suite updated with negative tests
  • Documentation updated / NEWS entry present (for non-trivial changes)
  • CI timeout is 2h or higher (see Settings/CICD/General pipelines/Timeout)

Reviewer's checklist:

  • Any issues marked for closing are addressed
  • There is a test suite reasonably covering new functionality or modifications
  • Function naming, parameters, return values, types, etc., are consistent and according to CONTRIBUTION.md
  • This feature/change has adequate documentation added
  • No obvious mistakes in the code
Edited by Daiki Ueno

Merge request reports