939: Improve robustness and error reporting on invalid fixVersion

[rwestberg]

If a fixVersion isn't found, ensure that we refresh the cache and log a proper error message if it still isn't found.

---

Progress

• Change must not contain extraneous whitespace
• Change must be properly reviewed

Issue

• SKARA-939: Improve robustness and error reporting on invalid fixVersion

Reviewers

• Erik Helin (@edvbld - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/skara pull/1099/head:pull/1099
$ git checkout pull/1099

Update a local copy of the PR:
$ git checkout pull/1099
$ git pull https://git.openjdk.java.net/skara pull/1099/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1099

View PR using the GUI difftool:
$ git pr show -t 1099

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/skara/pull/1099.diff

[bridgekeeper]

👋 Welcome back rwestberg! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[edvbld]

Looks good!

[openjdk]

@rwestberg This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

🔍 One or more changes in this pull request modifies files in areas of the source code that often require two reviewers. Please consider if this is the case for this pull request, and if so, await a second reviewer to approve this pull request before you integrate it.

🌎 Applicable reviewers for one or more changes in this pull request are spread across multiple different time zones. Please consider waiting with integrating this pull request until it has been out for review for at least 24 hours to give all reviewers a chance to review the pull request.

After integration, the commit message for the final commit will be:

939: Improve robustness and error reporting on invalid fixVersion

Reviewed-by: ehelin

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 1 new commit pushed to the master branch:

• 3a40804: mlbridge: use nicer link for webrev commits

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[mlbridge]

Webrevs

• 00: Full (c41d9048)

[rwestberg]

/integrate

[openjdk]

@rwestberg Since your change was applied there has been 1 commit pushed to the master branch:

• 3a40804: mlbridge: use nicer link for webrev commits

Your commit was automatically rebased without conflicts.

Pushed as commit 2234a03.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.