Hi Ian,
To access additional files, such as IT output files, you need to tell Jenkins
to save them as “artifacts”. This page tells how, if your project is using
Jenkinsfiles (which are highly recommended):
https://www.jenkins.io/doc/pipeline/tour/tests-and-artifacts/
Something similar can be done with the other Jenkins control configurations.
However, for the build#1 at the link you provided, don’t these test logs give
enough info?
https://builds.apache.org/blue/organizations/jenkins/maven-box%2Fmaven-dependency-plugin/detail/te/1/pipeline
Hope this helps,
—Matt
—————————
Open Source Technologies @
`This is not a contribution.`
On Aug 5, 2020, at 11:18 AM, Ian Lavallee <[email protected]> wrote:
Hi,
I'm trying to figure out why tests that pass locally are failing on
Jenkins. When I run the tests locally I can go target\it\test to see the
output, build log, etc. of each integration test but I can't figure out how
to do that on Jenkins. Does anyone know how to do this or how to get more
info than just the logs?
Build:
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/te/
Thanks,
Ian
