FYI, if JIRA is not available, we can’t push any patch, as the commit hook to validate the Issue-ID within the patch is failing. Example:
remote: Resolving deltas: 100% (26/26) remote: Processing changes: refs: 1, done remote: Non-existing issue ids referenced in commit message remote: The issue-ids remote: * SDNC-471 remote: are referenced in the commit message of remote: db13f4ddbd4a66ab9d66b1820279514137543eff, remote: but do not exist in its-jira Issue-Tracker So, Gerrit is impacted as well, in the sense that new patch can’t be submitted. Alexis > On Oct 4, 2018, at 5:20 PM, jwagant...@linuxfoundation.org wrote: > > What: The Linux Foundation will be performing a JIRA migration to AWS > > When: Thursday Oct 04 at 6:00pm Pacific > > Why: To improve the performance of JIRA and helping generating reports faster. > > Impact: only JIRA will be unavailable during this time > > Thanks so much! > Jess > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3837): https://lists.onap.org/g/onap-tsc/message/3837 Mute This Topic: https://lists.onap.org/mt/26796413/21656 Group Owner: onap-tsc+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
