Algorithm
- Developer Pulls Code from central repository to local repository
- Developer Makes Changes to Code in local repository
- Developer Pushes local Changes to Code to central repository
- Git post-commit hook send Changes to Code to Jenkins
- Jenkins build step does 'X' - in this case 'X' is 'put files on s3' or 'push files to NFS server'
- if its s3, then PublicN needs to pull from s3 (how does it know when to pull?)
- if its NFS, it operates more like local changes ... no push or poll required
- PublicN gets Changes to Code (changes are live) ← this is the hard step ... do we have:
- Jenkins build step runs script over ssh on PublicN to pull changes, OR
- Jenkins build step publishes to sns topic, lambda subscribed to that topic uses ssm to push light module changes to PublicN
- A custom whitelisted magnolia command over commands rest api endpoint tells publicN when new versions of light modules are ready (polling)
- if this one, then we don't even need Jenkins! Jump out after step 3
CLI
Demo
{"serverDuration": 82, "requestCorrelationId": "7078886a9e26deca"}
4 Comments
Bradley Andersen
was: Light Development turn around
Bradley Andersen
https://documentation.magnolia-cms.com/display/DOCS57/Sharing+light+modules+-+advanced+topics#Sharinglightmodules-advancedtopics-Testing
Bradley Andersen
https://docs.google.com/document/d/13-2_zbrDd0HC3KCkedKMs8cu0UoUpn7fGcqSxM-KXSo/edit?usp=sharing
Bradley Andersen