1
65%
master: 61%

Ran 10 Dec 2018 07:57AM UTC

Files 249

Run time 35s

Badge

Embed ▾

Committed 10 Dec 2018 07:17AM UTC coverage: 65.206% (+0.02%) from 65.191%

Job # UTTEST=true

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

[Cherry-pick]Fix unable to use Notary after updating to v1.6.0  (#6496)

* Fix unable to use Notary after updating to v1.6.0

This commit is to fix the issue on notary migrations from mysql to pgsql.
1, alter sequence for the primary key of changeseed, this is missed in v1.6.0 migrator.
2, alter table owners from postgres to notarysigner and notaryserver.

Issue:
https://github.com/goharbor/harbor/issues/6465

Workaround:
https://github.com/goharbor/harbor/issues/6465#issuecomment-445162616

Impacted upgrade path:
1, Upgrade from version older then v1.6.0 with migrator:v1.6.0, and migrates the notarty DB.

No impacted upgrade path:
1, Upgrade from version older than v1.6.0 with migrator:v1.6.0, but without migrates the notarty DB.

Notes：
After merge this fix, we need to provide an new migrator with an new tag, like v1.6.1, and
deprecated the v1.6.0. For those who was impacted by migrator v1.6.0, will open an new PR to build
the workaround into the migrator and expose an specical command for hot-fix.

Signed-off-by: wang yan <wangyan@vmware.com>

* fix per comments, add if not exists to create pqsql sequence

Signed-off-by: wang yan <wangyan@vmware.com>

Run Details

13272 of 20354 relevant lines covered (65.21%)

8.72 hits per line

goharbor / harbor / 9915 / 1
65%
master: 61%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 9915.1 (UTTEST=true)

goharbor / harbor / 9915 / 1 65% master: 61%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 9915.1 (UTTEST=true)

goharbor / harbor / 9915 / 1
65%
master: 61%

README BADGES
x