We were using HPE-sync 12.53 and the HP-JIRA (built-in) adapter with JIRA Cloud and it stopped passing integrity checks last week, but still can run sync’s. What happened?

  • Questions
  • We were using HPE-sync 12.53 and the HP-JIRA (built-in) adapter with JIRA Cloud and it stopped passing integrity checks last week, but still can run sync's. What happened?
Question ID: 108184
1
0

We have a setup of HPE-Synchronizer 12.53 SP1 and were working happily with the HP built-in JIRA Adapter to connect and sync with defects/issues in JIRA Cloud (hosted by Atlassian). It was working fine for quite some time (over a year) and just the other day, after creating a new link, it would not pass integrity check. I tried integrity check on an existing/working link (one that passes it’s incremental and full sync tasks), and it fails.

ERROR (Integrity.General.Adapter2.JIRA.Bug) GenerateReport: Generation of report failed: server.general.PROGRAMMER_ERROR : Program flow error. Message: not a terminal state.

Any ideas?

Marked as spam
Posted by (Questions: 74, Answers: 4)
Asked on February 23, 2018 7:50 pm
5 views
Answers (1)
1
Private answer

Your Atlassian cloud JIRA was probably updated.

A few things to take note of:

1) HPE-Synchronizer and HP's built-in JIRA Adapter only support SPECIFIC versions of JIRA.
for instance HP-Sync 12.53 only supports Atlassian JIRA Adapter versions 6.x.x, 7.0.x, and 7.1.x.
Newer versions like 12.55 support JIRA 6.x.x, 7.0.x, and 7.1.x, 7.2.x, 7.3.x 7.4.x, 7.5.x and 7.6.x.

2) The Atlassian ''Cloud'' version of JIRA is usually updated on a regular basis to be the ''latest'' version.

3) If you look at the version information at the bottom of the JIRA login page, stand-alone (on-premise) load has a number like 7.6.1, but the ''Cloud'' version reports a different number like: ''1001.0.0-SNAPHSHOT''.

So, kinowing that ''Cloud'' version is usually the ''latest'' JIRA version, it may have automatically updated to a version beyond what is supported by the build-in JIRA adapter in HPE-sync12.53.

You should upgrade to the latest HPE-synchronizer version, 12.55-SP1 (SP1 just came out Feb 12, 2018), so it will support the newer version (for now). It supports from QC/ALM 12.55 down to QC/ALM 11.

As for why it sync'd but did not pass integrity check, it might have been ''different'' enough that it could work with simple sync tasks, but there must have been some additional version-related scrutiny with the integrity check.

Good Luck!

Marked as spam
Posted by (Questions: 0, Answers: 15)
Answered on February 23, 2018 8:51 pm