Menu

Continuum Analytics: Documentation

DOCUMENTATION
Search
Menu
  • Anaconda Platform
  • – Welcome
  • – Anaconda Distribution
  • – Anaconda Repository
    • User guide
    • Administrator guide
      • Install/Update/Uninstall Anaconda Repository
        • Quick links
        • Install Anaconda Repository
        • Install summary
        • 1. Install MongoDB 2.6
        • 2. Create the Anaconda Repository administrator account
        • 3. Install Miniconda
        • 4. Download and install Anaconda Repository enterprise packages
        • 5. Configure Anaconda Repository
        • 6. Start and log on to Anaconda server
        • 7. Set up automatic restart on reboot, fail or error
        • 8. Client configuration
        • 9. Install Anaconda Repository License file
        • 10. (Optional) Mirror installers for Anaconda and Miniconda
        • 11. (Optional) Adjust IPTables to accept requests on port 80
        • 12. Mirror Anaconda Cloud
        • Update Anaconda Repository
        • Uninstall Anaconda Repository
        • For additional help
        • Advanced topics
          • Advanced Installation Options
          • Troubleshooting your Anaconda repository installation
          • Maintenance and configuration concerns
          • User administration
          • Client configuration
          • Adding a PyPI or Anaconda Mirror
          • Recommended Workflow
            • Leveraging Channels for Workflow Separation
          • Anaconda repository requirements and verification
        • Did you find what you needed on this page?
      • Anaconda repository command line interface
      • Cross platform (“Noarch”) package support in Anaconda repository
      • Jupyter notebook support in Anaconda repository
      • Anaconda repository changelog
      • Configuration reference
      • Anaconda repository end user license agreement
    • What’s new in 2.23?
  • – Anaconda Accelerate
  • – Anaconda Adam
  • – Anaconda Enterprise Notebooks
  • – Anaconda Mosaic
  • – Anaconda Fusion
  • – Anaconda Scale
  • – Anaconda Cloud
  • Open source incubated projects
  • – Blaze
  • – Bokeh
  • – conda
  • – dask
  • – llvmlite
  • – PhosphorJS
  • – Numba

Recommended Workflow¶

One of the most useful features of Anaconda Repository is its ability to help you manage package development and deployment in a seamless fashion. Below you can find a write-up of the actual development process and channel usage employed by one of our internal teams.

Leveraging Channels for Workflow Separation¶

Using multiple channels allows your team to maintain separate package states and easily earmark and control the versions and states of packages that users can install. For example, your team might create the following channels:

  • master
  • staging
  • release

Master is created any time something is merged into our master branch. It’s considered the development build of all of the components that make up the software. Code that makes it to this should be stable and have been confirmed independently, but a full QA test has not been run on it yet.

Once we’re ready to start working on a release, we create a staging:X.Y.Z branch. This contains all code that’s going to go into a release. No new features should be introduced at this point, just any last minute bug fixes to existing code.

The staging channel gets culled so only the latest package is maintained in it – any alpha, beta, or dev packages are removed. After all testing is complete, all issues are resolved, and the channel contains only one version of each package, we copy that package into a release:X.Y.Z channel, then lock that channel.

We’ve used this through 4 release cycles and so far it’s worked out well for us.

  • Docs Home
  • Continuum Analytics Home
  • More Help & Support
Privacy Policy | EULA © 2016 Continuum Analytics, Inc. All Rights Reserved.