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.
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
Investigate using the DSL of jenkins-client-plugin #146
Comments
As far as I remember we started with this, but changed to |
@tjaeschke Ah! As far as I understand the DSL allows to fallback to "raw" commands for such cases. |
@michaelsauter This would be good. Hm, for experimenting locally with Jenkinsfiles I often use https://github.com/jenkinsci/jenkinsfile-runner since @ungerts recommended it to me a few months ago. |
@tjaeschke Awesome! I will definitely check this out. Maybe we can use this for tests as well? |
@michaelsauter I think so. On my agenda is also to take a look at https://github.com/jenkinsci/JenkinsPipelineUnit |
@tjaeschke @michaelsauter we've successfully implemented roughly 200 unit tests for the MRO shared lib using just Spock. Why? Because when looking at frameworks targeted at pipeline unit testing, they had their fair share of limitations and had no major benefits over going with a solid general testing framework. Also, it would be beneficial to settle on one approach for a type of tests. @tjaeschke know of a good framework for running integration tests against a live Jenkins instance? |
@metmajer I'm with you using Spock for unit testing. Unfortunately I didn't find any good framework for integration tests, that satisfied me, yet. |
oc patch was one thing. And having a complete mixture of DSL and raw things, we decided for one solution. |
Everything has been moved into |
Add UTC timestamps prefix to log lines in Pipelinesteps.echo command
Instead of shelling out to the
oc
binary we might be better of using the DSL of https://github.com/openshift/jenkins-client-plugin. This plugin is already installed in the Jenkins master.Thanks @oalyman for the suggestion.
One downside of using that plugin is that it is harder to try out changes - instead of being able to play with commands in the terminal, right now I don't see a way other than running a pipeline to experiment with the DSL.
The text was updated successfully, but these errors were encountered: