Causam: Difference between revisions

Revision as of 14:55, 22 September 2016

DEPLOY A NEW RELEASE

use nop-util to set up the new version
- edit util.js to update the version search and replace strings - note that you want to go from a -SNAPSHOT to a release (no -SNAPSHOT)
- npm install -g

nop-util-sync updated version bump strings nu force-tag 4.0.0-2016Oct22-AmazingNewFeature # force a git tag of the stable old version on all repos nu set-scala-version # stamp the new scala version into all projects nu sync --major Stamping components with new 4.1.0 version

now use Jenkins to kick it all off - dependencies are all set, you just need to build pa-xi-monitor-requests-scala

COMMONS WORKFLOW (thanks greg and brandon!)

code away

sbt publishLocal (or via gpy - NOTE that only libraries have a gpy)

puts it in ~/.ivy2/local

(sbt will use that then)

(code is happy and pushed)

(once you push it to stash, it will be in artifactory)

ungpy (removes ivy/local AND cache - good to do ofen to avoid sbt confusion) (esp before coding)

(then it will reresolve next time)

"sbt uses ivy instaed of maven, doesn't know snapshots"

then either publishLocal again, or just carry on and it will use artifactory

(these just do a self-contained local build)

activator dist

activator compile

nop-client message flow

   EDGE                                CLIENT
   
                                       initial certificate provisioning
                                       
                                       olympicmachines < hello
                                       simplepointframe < heartbeat keepalives (as needed)
   EDGE becomes device-aware
   build config
   send to machine                     olympicmachines > polling config
                                       olympicmachines < polling config ACK
                                       
   start polling                       simplepointframe < data
                                       
                                       (dead) < (buffer until server becomes responsive)

ExpandSet up a Windows client to use Stash ssh key
Use git-for-windows exclusively, it doesn't need putty. Install Git for Windows, set it up to use its own ssh (not plink). Set up this folder with .ssh configuration C:\Users\##user##\.ssh\config Copy the .ssh folder from dropbox, the config looks like this: Host git.poweranalytics.io IdentityFile ~/.ssh/git.poweranalytics.io/id_rsa Now you should be able to pull: cd C:\Michael's Data\development\power_analytics\gec git clone ssh://git@git.poweranalytics.io:7999/gec/pa-pdp-xiagent-csharp.git

ExpandGEM provisioning

ExpandINSTALL AND COMPILE north-poller ON UBUNTU

ExpandINSTALL AND RUN north-poller BINARY ON PI

@@ Line 3: / Line 3: @@
 ** edit util.js to update the version search and replace strings - note that you want to go from a -SNAPSHOT to a release (no -SNAPSHOT)
 ** <code>npm install -g
-nop-util-sync updated version bump strings</code>
+nop-util-sync updated version bump strings
 nu force-tag 4.0.0-2016Oct22-AmazingNewFeature # force a git tag of the stable old version on all repos
 nu set-scala-version # stamp the new scala version into all projects