New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Example test showing usage of JenkinsPipelineUsage #3

Open

mkobit opened this issue Nov 29, 2017 · 1 comment

Owner

mkobit commented Nov 29, 2017

Sort of depends on one of:

Related to jenkinsci/JenkinsPipelineUnit#70

Owner Author

mkobit commented Dec 11, 2017

Codegen in plugin might be a better option for now until the issue is released in JenkinsPipelineUnit

a com.lesfurets.jenkins.unit.global.lib.SourceRetriever (like from https://github.com/SAP/jenkins-library/blob/master/test/groovy/ProjectSource.groovy) could be implemented as part of the codegen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment