Skip to content
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

Branch And Updated column added to Web panel #52 #5

Open
wants to merge 77 commits into
base: master
Choose a base branch
from

Conversation

zwithsmile
Copy link

For triaging defects related check-ins in Gerrit, we want Branch and Updated field added to the Web Panel view.

Joe Hansche and others added 30 commits November 16, 2012 16:12
Some changes were inspired by PR #9 which was closed by author @treymarc.

This disables the ApprovalFunctionTest, because junit was failing
due to ClassNotFoundException looking for UserKeyStore. This will likely
require implementing some kind of compatibility layer due to the User
API changes between JIRA 5 and 6.

Some plugins and dependencies have also been updated to their latest versions.
update example user creation to reflect gerrit api v2.10
* Move dashboard link above the table header.
* Left align text and headers
* More readable link text for dashboard
In case of a misconfigured app-data file system level access permissions
it'll throw an unreadable exception stack trace to the browser screen.

This change makes it fail gracefully and add a meaningful message with
details to the log.
Treat and log exception when trying to add a Private Key.
Improve webpanel readability
Add support for viewing gerrit panel in JIRA Agile Details Panel
…to master

* 'master' of git://github.com/p00by/jira-gerrit-plugin:
  Adds support for jira 7

 Conflicts:
	pom.xml
	src/main/java/com/meetme/plugins/jira/gerrit/data/dto/GerritApproval.java
	src/main/java/com/meetme/plugins/jira/gerrit/tabpanel/GerritReviewsTabPanel.java
As of 3.0, the code now only supports JIRA 7+

This is because of a breaking API change in the JIRA 7 update.
Support for multiple issue keys (e.g. issues moved between projects)
torarnv and others added 11 commits March 27, 2020 14:31
The statuses can be extended via Gerrit plugins, in which case we
would throw an exception and fail to show any changes for the issue.

java.lang.IllegalArgumentException: No enum constant com.meetme.plugins.jira.gerrit.data.dto.GerritChange.Status.INTEGRATING
	at java.lang.Enum.valueOf(Enum.java:238)
	at com.meetme.plugins.jira.gerrit.data.dto.GerritChange$Status.valueOf(GerritChange.java:35)
	at com.meetme.plugins.jira.gerrit.data.dto.GerritChange.fromJson(GerritChange.java:90)
	at com.sonyericsson.hudson.plugins.gerrit.gerritevents.dto.attr.Change.<init>(Change.java:97)
	at com.meetme.plugins.jira.gerrit.data.dto.GerritChange.<init>(GerritChange.java:52)
	at com.meetme.plugins.jira.gerrit.data.IssueReviewsImpl.getReviewsFromGerrit(IssueRev

There's no need to hard-code these statuses as enums, as the rest
of the plugin operates on them as strings anyways.
This will enable caching in a clustered environment, such as Jira Data Center.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.