@kgrid/release-cli
CLI for building KGrid components and KOs via CircleCI
Last updated a year ago by farrisg .
ISC · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install @kgrid/release-cli 
SYNC missed versions from official npm registry.

KGrid Release CLI

CircleCI GitHub release npm version

This CLI will help you trigger a Release of the KGrid components.

Getting Started

  1. Get a Circle CI a personal api token
  2. npm install -g @kgrid/release-cli
  3. Run export CIRCLECI_TOKEN=#### && kgrid-release

Using the CLI

  1. Choose the component
  2. Adapter is sub module so if Adapter you have to say api or javascript otherwise just press enter
  3. The release version #.#.# for releases #.#.#-rc# for release candidates. This will used to tag the GitHub repository. For maven projects this sets the version
  4. The development version will be #.#.#-SNAPSHOT, used for maven projects can be innored for KO releases.
  5. If it is Pre Release type Y defaults to N

Review the additional [#note]

Will kick off Circle CI build.

  _  ______      _     _   ____      _                        ____ _     ___ 
 | |/ / ___|_ __(_) __| | |  _ \ ___| | ___  __ _ ___  ___   / ___| |   |_ _|
 | ' / |  _| '__| |/ _` | | |_) / _ \ |/ _ \/ _` / __|/ _ \ | |   | |    | | 
 | . \ |_| | |  | | (_| | |  _ <  __/ |  __/ (_| \__ \  __/ | |___| |___ | | 
 |_|\_\____|_|  |_|\__,_| |_| \_\___|_|\___|\__,_|___/\___|  \____|_____|___|
                                                                             
? What KGrid Component are you Releasing? (Use arrow keys)
❯ Activator 
  Adapter 
  Library 
  Play 
  Shelf 

Here is an example of final screen

  _  ______      _     _   ____      _                        ____ _     ___ 
 | |/ / ___|_ __(_) __| | |  _ \ ___| | ___  __ _ ___  ___   / ___| |   |_ _|
 | ' / |  _| '__| |/ _` | | |_) / _ \ |/ _ \/ _` / __|/ _ \ | |   | |    | | 
 | . \ |_| | |  | | (_| | |  _ <  __/ |  __/ (_| \__ \  __/ | |___| |___ | | 
 |_|\_\____|_|  |_|\__,_| |_| \_\___|_|\___|\__,_|___/\___|  \____|_____|___|
                                                                             
? What KGrid Component are you Releasing? Activator
? What branch (e.g. hotfix, feature or master)? master
? What is the Component Module (e.g. adapter-api or javascript-adapter or blank)? 
? What is the Release Version (e.g. 1.0.3)? 1.0.1-rc3
? What is the Development Version (e.g 1.0.4-SNAPSHOT)? 1.0.1-SNAPSHOT
? Is this PreRelease? Yes
Build has started
~/kgrid-config/release/cli $ 

Issues

  • Issues with executing kgrid-release once installed could be based on a few things
    • make sure it is global npm list -g --depth=0
    • run npm bin -g to global bin path.

Notes

  • Component Module is only need when releasing Adapters. The project consists of mmaven submodules and thus requires more information

  • The Demo components release process consists of updating the the GitHub pages. When releasing Demos you really only have to input a Release Version, it will be used to tag the repo.

Current Tags

  • 1.0.4                                ...           latest (a year ago)

4 Versions

  • 1.0.4                                ...           a year ago
  • 1.0.2                                ...           a year ago
  • 1.0.1                                ...           a year ago
  • 1.0.0                                ...           a year ago
Maintainers (2)
Downloads
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 1
Dependencies (9)
Dev Dependencies (0)
None
Dependents (0)
None

Copyright 2014 - 2016 © taobao.org |