Thanks Jan! I’ll try it out and see what I find.
Best,
Matt
On Aug 21, 2019, 6:51 AM -0700, Jan Monterrubio ,
wrote:
> I’ve found success debugging through the plug-ins by using a combination of:
>
> - the Jenkins Test harness
> - the plugin as a dependency
> - using the Jenkins rule to run a
I’ve found success debugging through the plug-ins by using a combination of:
- the Jenkins Test harness
- the plugin as a dependency
- using the Jenkins rule to run a job and hit the plugins breakpoint.
Here’s some resources that might help:
https://github.com/jenkinsci/jenkins-test-harness
Hi Ullrich,
Thanks for the suggestion! I tried that, and still saw the problem.
Speficially, I did this:
stage (“Unit tests”) {
sh “runtests.sh”
sh “cat build/pytest.xml”
junit testResults: “**/build/pytest.xml"
}
Are there instructions anywhere for how to setup a dev environment for
Shoudn’t the command use ’testResults’ as parameter name?
junit testResults: '**/build/pytest.xml'
> Am 18.08.2019 um 06:42 schrieb Matt Hollingsworth :
>
> Hi everyone,
>
> I ran into a weird issue that I thought you might be able to help
> troubleshoot. I'm using Jenkinsfile-based
Hi everyone,
I ran into a weird issue that I thought you might be able to help
troubleshoot. I'm using Jenkinsfile-based Pipelines with python, and I use
pytest to produce JUnit-compatible reports after the tests are run. The
problem is that I get an error when I try to parse the results with
