eik-ci-approaches.md

Publishing from CI, 2 approaches

Approach 1. [current approach] (where the cli controls the version)

• eik package
  • calculates hashes of a local build and compares with what is available on the server
    • if hashes are the same, abort
  • calculates the next version number to publish
    • for a patch 1.0.1 goes to 1.0.2
    • for a minor 1.0.1 goes to 1.1.0
  • publish returns new version and sha file hashes
  • version field is updated in .eikrc (to be changed to assets.json)
• app reads version from .eikrc (to be assets.json) and builds URLs

a deploy script for CI looks something like:

eik login -k change_me -s https://assets.finn.no
eik package
git add assets.json
git commit -m "update assets version [skip ci]"
git push origin master

Approach 2. (where user controls the version, same as npm)

• A separate command/script is written (eik version??)
  • calculates hashes of a local build and compares with what is available on the server
    • if hashes are the same, abort
  • calculates the next version number to publish
    • for a patch 1.0.1 goes to 1.0.2
    • for a minor 1.0.1 goes to 1.1.0
  • writes the new version to assets.json version field
• eik package
  • reads version from assets.json file
  • creates a bundle and publishes
  • publish returns sha file hashes
  • file hashes are updated in assets.json file
• commit assets.json back to github
• app reads version from .eikrc (to be assets.json) and builds URLs

a deploy script for CI might look something like:

eik login -k change_me -s https://assets.finn.no
eik version patch
eik package
git add assets.json
git commit -m "update assets version [skip ci]"
git push origin master