-
Notifications
You must be signed in to change notification settings - Fork 58
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
Conditional reporting #11
Open
lillysGame
wants to merge
208
commits into
maplesteve:master
Choose a base branch
from
jenkinsci:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use javax.json to create a JSON payload that escapes the content that is sent to Jira. This fixes 400 Bad request responses from Jira whenever the test failure message has a double quote. This also reformats the data sent to Jira so that it's formatted a bit more nicely.
This fixes a crash when attempting to save a job that uses this plugin and the job has been run on a slave: "Can't send a remote FilePath to a different remote channel".
Fix escaping of JSON payload.
Mark the workspace field as transient.
If there are no test results (e.g. if the build fails before the tests run) then build.getAction(AbstractTestResultAction.class) returns null. Add a check for this case.
Add the URL for the job that caused the test failure to the Jira ticket.
Fix a NullPointerException when there are no test results.
Add job URL to the Jira ticket.
fix for Jenkins 1.577+.
JENKINS-33898: Auto resolve issue created by jiratestresultreporter p…
Bump BOM fo fix JUnit issues
…rkflow chore: use jenkins infra maven cd reusable workflow
Bumps [io.jenkins.tools.incrementals:git-changelist-maven-extension](https://github.com/jenkinsci/incrementals-tools) from 1.2 to 1.8. - [Release notes](https://github.com/jenkinsci/incrementals-tools/releases) - [Commits](jenkinsci/incrementals-tools@parent-1.2...parent-1.8) --- updated-dependencies: - dependency-name: io.jenkins.tools.incrementals:git-changelist-maven-extension dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Refresh plugin for September 2024
….apache.httpcomponents.DefaultHttpClientFactory (#158) - corrected some typos in README.md - removed unneeded imports
NPE fix from `JiraTestDataPublisher.getJobName`
Co-authored-by: Basil Crow <[email protected]>
…on-deprecated equivalents (#179)
….version 2.452.4 (#184)
- added code markdown for command line calls - added description for images
Updated docu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to be able to limit what gets reported to jira. as it works now, my tests will fail and skip the rest, but also creates jira tickets for the skipped tests, maybe add a conditional to every field configuration - my main focus is if the specific field is going to be blank, don't report the ticket