Project

General

Profile

Bug #9090

Create production instances of Klever locally if necessary

Added by Evgeny Novikov about 2 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Urgent
Category:
Deployment
Target version:
Start date:
07/11/2018
Due date:
% Done:

0%

Estimated time:
Detected in build:
svn
Platform:
Published in build:

Description

At the moment scripts use several related interfaces incorrectly as they expect a Boolean flag (development or not development) while they pass a mode that is a string and that is always true. Welcome dynamic typing!


Related issues

Related to Klever - Bug #9064: Klever developer instances are not developer onesClosed07/05/2018

Actions

History

#1

Updated by Evgeny Novikov about 2 years ago

  • Related to Bug #9064: Klever developer instances are not developer ones added
#2

Updated by Evgeny Novikov about 2 years ago

  • Status changed from New to Resolved

I fixed the issue in branch deploy-fixes-and-improvements. Indeed, there was a mixture of development and non-development stuff, namely, scripts installed production Klever Bridge but development Native Scheduler and its workers.

#3

Updated by Evgeny Novikov about 2 years ago

  • Status changed from Resolved to Closed

Tests passed, so, I merged the branch to master in b33a51eb.

Also available in: Atom PDF