Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Test commander core commands #3516

Closed
18 tasks done
ManuGowda opened this issue May 6, 2019 · 4 comments
Closed
18 tasks done

Test commander core commands #3516

ManuGowda opened this issue May 6, 2019 · 4 comments
Assignees

Comments

@ManuGowda
Copy link
Contributor

ManuGowda commented May 6, 2019

Expected behavior

Should be able to install commander on Linux and MacOS (Fresh machines)

Note: Try all the possible options for each command

Linux

  • lisk core --help
  • lisk core:install
  • lisk core:start
  • lisk core:stop
    - [ ] lisk core:upgrade
  • lisk core:logs
  • lisk core:uninstall

NPM

  • lisk core --help
  • lisk core:install
  • lisk core:start
  • lisk core:stop
    - [ ] lisk core:upgrade
  • lisk core:logs
  • lisk core:uninstall

MacOS

  • lisk core --help
  • lisk core:install
  • lisk core:start
  • lisk core:stop
    - [ ] lisk core:upgrade
  • lisk core:logs
  • lisk core:uninstall

Note: Upgrade command cannot be used as the commander supports upgrade for Lisk Core version > 2.0.0

@michielmulders
Copy link
Contributor

Screenshot 2019-05-16 at 11 01 17

@michielmulders
Copy link
Contributor

Screenshot 2019-05-21 at 13 52 44
When using lisk core:stop mainnet-03, I checked the logs and found the following output. @ManuGowda

@michielmulders
Copy link
Contributor

michielmulders commented May 21, 2019

Tested for Lisk Commander .tar build on Linux:

  • Try uninstall non-existing NAME -> ✅
  • Install with below command for mainnet and testnet using snapshot -> ✅
  • --no-snapshot option -> ✅
  • Don't stop Lisk Core instance but uninstall directly -> ✅(Commander first stops and then cleans up)
  • --no-start option -> ✅ @ManuGowda Commander shows that it is downloading the snapshot and starting the app, but then, when finishing, it shows only one line that Lisk Core was installed (and not started). Might be confusing verbose output.

Note: If you cancel during installation, the output directory will be created. When trying to rerun the installation for the same name, it will tell you that Lisk Core with that specific name is already installed. So, best to do is cleanup with lisk core:uninstall NAME and reinstall.

Tested 2.0.0-alpha.9 version with lisk core:install --network=testnet --release-url=https://localhost/lisk-core/lisk-2.0.0-alpha.9-5ed4cbe-Linux-x86_64.tar.gz testnet-01

@michielmulders
Copy link
Contributor

Tested for Lisk Commander npm from our repository:

  • All checks completed ✅

Tested on Mac with Darwin build:

  • All checks completed ✅

DO droplet destroyed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants