Page History

Algorithm

1. Developer Pulls Code from central repository to local repository
2. Developer Makes Changes to Code in local repository
3. Developer Pushes local Changes to Code to central repository
4. Git post-commit hook send Changes to Code to Jenkins
5. Jenkins build step does 'X' - in this case 'X' is 'put files on s3' or 'push files to NFS server'
   1. if its s3, then PublicN needs to pull from s3 (how does it know when to pull?)
   2. if its NFS, it operates more like local changes ... no push or poll required
6. PublicN gets Changes to Code (changes are live) ← this is the hard step ... do we have:
   
   1. Jenkins build step runs script over ssh on PublicN to pull changes, OR
      
   2. Jenkins build step publishes to sns topic, lambda subscribed to that topic uses ssm to push light module changes to PublicN
   3. A custom whitelisted magnolia command over commands rest api endpoint tells publicN when new versions of light modules are ready (polling)
      1. if this one, then we don't even need Jenkins! Jump out after step 3
         

CLI

Demo