Uploaded image for project: 'PUBLIC - Liferay Sync'
  1. PUBLIC - Liferay Sync
  2. SYNC-1453

SyncDLObject table is not populated on first upgrade/deployment

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Connector-3.0.0
    • Fix Version/s: Connector-3.0.1
    • Component/s: Upgrade
    • Labels:
      None

      Description

      The current plugin upgrade mechanism is flawed. It assumes that not having a build number is the same as a new deployment. In one case, we want to run all the upgrades and in another, none of them (just verify to populate data).

      EXPECTED
      New deployment From sync 1 From beta/every other upgrade
      release = null release != null release != null
      set release.buildNumber = 101 set release.buildNumber = 0 N/A
      upgrades: none upgrades: 100, 101 upgrades: 101
      #1: release.info.build.number=101, release.info.previous.build.number=0
      New deployment From sync 1 From beta/every other upgrade
      release = null release = null release != null
      set release.buildNumber = 0 set release.buildNumber = 0 N/A
      upgrades: 100, 101 upgrades: 100, 101 upgrades: 101
      #2: release.info.build.number=101, release.info.previous.build.number=100
      New deployment From sync 1 From beta/every other upgrade
      release = null release = null release != null
      set release.buildNumber = 100 set release.buildNumber = 100 N/A
      upgrades: 101 upgrades: 101 upgrades: 101
      #3: release.info.build.number=101, release.info.previous.build.number=101
      New deployment From sync 1 From beta/every other upgrade
      release = null release = null release != null
      set release.buildNumber = 101 set release.buildNumber = 101 N/A
      upgrades: none upgrades: none upgrades: 101

        Attachments

          Activity

            People

            • Assignee:
              shinn.lok Shinn Lok
              Reporter:
              shinn.lok Shinn Lok
              Participants of an Issue:
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 23 weeks ago