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
Dear Jenkins Community,
I am aware that we can generate dynamic stages using groovy scripts.
Question is, can we also do this from the standard output of a script?
For example, I have a script written in Nodejs that I execute with "sh node
script.js" and that It can produce standard output
Dear Jenkins Community.
I have a script written in NodeJS that I execute from Jenkins using the
shell. I would like to know if it possible to derive stages from its
standard output without parsing the output and generating the stages from
groovy.
I am aware that we can generate dynamic
Perhaps. I'll have to give it a try to see what its limitations are.
When you have 5-10 artifacts per job, it takes a lot of time saving
them, so they can be attached to a Jira ticket.
Jenkins doesn't provide a way to save those files. You need to view
each one, copy it's contents into an editor,
Could the run selector plugin help?
https://github.com/jenkinsci/run-selector-plugin
Martin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
Have a look at
https://github.com/jenkinsci/run-selector-plugin/blob/master/README.md
Martin
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
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
