[gnutls-devel] GnuTLS | CI pipeline rework - using stages and inheritance (!1366)

[Read-only notification of GnuTLS library development activities]

Stanislav Židek created a merge request: https://gitlab.com/gnutls/gnutls/-/merge_requests/1366

Project:Branches: ep69/gnutls:ci-rework to gnutls/gnutls:master
Author:    Stanislav Židek
Assignee: Daiki Ueno


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
 * [x] 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

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1366
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20201201/4c9b2466/attachment-0001.html>