Master:

Development:

Jumpscale is a cloud automation product and a branch from what used to be Pylabs. About 9 years ago Pylabs was the basis of a cloud automation product which was acquired by SUN Microsystems from Q-Layer. In the mean time we are 4 versions further and we have rebranded it to Jumpscale.

• Jumpscale
  • About Jumpscale
  • Installing Jumpscale
  • Usage
  • Tutorials
  • Collaboration Conventions

Some tools available in jumpscale

• Config Manager The config manager is a secure way to manage configuration instances. Anything saved to the file system is NACL encrypted and only decrypted on the fly when accessed.

• Executors Jumpscale comes with its own executors that abstract working locally or remotely. Of these executors:

  • SSH Executor (for remote execution)
  • Local Executor (for local execution)
  • Docker Executor (for executing on dockers)

• Builders Builder tools is a set of tools to perform the common tasks in your builder (e.g read a file , write to a file, execute bash commands and many other handy methods that you will probably need in your builder)
  To create a builder see [documentation](docs/howto/Create\ a\ new\ Builder.md)

See documentation

• The jsshell in your terminal, type js_shell

• Kosmos in your terminal, type kosmos

• In Python

  python3 -c 'from Jumpscale import j;print(j.application.getMemoryUsage())'

  the default mem usage < 23 MB and lazy loading of the modules.

To run unittests you can execute the following command

source /sandbox/env.sh; pytest /sandbox/code/github/threefoldtech/jumpscaleX/

You can also run Integration tests by running the command

source /sandbox/env.sh; pytest  --integration /sandbox/code/github/threefoldtech/jumpscaleX/

To annotate the one of your tests is an itegeration test rather than a unittests, you can add the following docorator to the test

@pytest.mark.integration
def test_main(self)

Check Documentation

check conventions