-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Testcase reports with a url attribute will now properly write this to… #1874
Conversation
Just triggering a rerun of travis with the close/open routine |
Thanks! According to the junit-plugin schema this is valid on Jenkins, but could you explain your use case better? Do you have custom hooks that add that attribute to test reports? |
I do! We're using this to point to where our test artifacts are, so that when you see a failure in phabricator, you can be linked directly to the artifacts in jenkins |
@fushi I see, thanks. This seems like a new feature (albeit small), so perhaps this should go into the Also I wonder how to better document that. |
I agree this should go to |
@fushi could you change the target of this PR to |
Apparently we can change the target ourselves using the edit button at the top of the page :-) |
Thanks for submitting a PR, your contribution is really appreciated!
Here's a quick checklist that should be present in PRs:
master
; for new features, targetfeatures
;AUTHORS
;CHANGELOG.rst
CHANGELOG
, so please add a thank note to yourself ("Thanks @user for the PR") and a link to your GitHub profile. It may sound weird thanking yourself, but otherwise a maintainer would have to do it manually before or after merging instead of just using GitHub's merge button. This makes it easier on the maintainers to merge PRs.… junitxml