Skip to content

Releasing Core Plans

Nell Shamrell-Harrington edited this page Oct 20, 2017 · 20 revisions
  • Open a Pull Request with your changes

  • Before you merge, run these checks on your core plan (in the following examples it is the go plan) from the core-plans root. If it flags errors, correct them.

    $ shellcheck --shell=bash --exclude=SC1090,SC1091,SC2034,SC2039,SC2148,SC2153,SC2154,SC2140 go/hooks/*
    $ pre-commit run --files go/*
    
  • Request a review of your Pull Request, once approved, merge the Pull Request

  • Head to https://bldr.habitat.sh/#/origins/core/packages and find your plan

  • Watch the build

  • If the build is successful, do any vetting you need to do.

  • If all looks good - promote the build to stable

    $ hab pkg promote core/your_package/version/release stable
  • Any reverse dependencies in the core origin should rebuild automatically. However, we still need to promote them manually.

  • Check out the builder output for the most recent build for your package on https://bldr.habitat.sh/#/origins/core/packages

  • Look for this line (the number will vary)

      hab-studio: Exported: HAB_BLDR_CHANNEL=bldr-832040326113607680
  • Copy the number after "bldr-" - this is your job group id

  • Head back to your terminal and run this command:

    $ hab bldr job promote <job_group_id> stable
  • And you should be done!