Managing the lifecycle of notebooks and scripts

After you have created and tested your notebooks or scripts, you can move them to deployment spaces to run in jobs. Notebooks can be added to pipelines, published to a catalog so that other catalog members can use the notebook in their projects, or shared outside of Watson Studio so that people who aren't collaborators in your Watson Studio projects can see and use them.

Alternatively, after you have created and tested your notebooks in a project, you can promote them to deployment spaces to run in a production environment, add them to pipelines, publish them to a catalog so that other catalog members can use the notebook in their projects, or share read-only copies outside of Watson Studio so that people who aren't collaborators in your Watson Studio projects can see and use them.

You can use any of these methods for notebooks:

For scripts, you can automate the lifecycle.

Parent topic: Notebooks and scripts