Tests for pipeline includes

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

Pipeline includes are awesome, but as with any plugin system, there's potential for serious challenges. Jenkins plugins are a great example of how we don't want to do it. But modularized includes are clearly viable elsewhere. Ruby gems, npm, etc. are all good examples of people sharing code successfully. So how do we avoid plugin-hell? Well, one major difference is tests. Most published modules on rubygems or npm have a test suite. These tests allow developers to be confident that the module is still compatible as base versions change, and as new features are added. From what I can tell, most plugin systems don't have any kind of test suite, so you rely on manual testing, or no testing at all and just listen to bug reports.

So, thinking about GitLab CI/CD pipeline includes, are there tools and conventions we can create to help make sure that our community of pipeline fragment providers can release reliable benefits, which end-users can consume confidently?

Intended users

Further details

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Edited by 🤖 GitLab Bot 🤖