Community Plugin SDK Experiences
We are considering automation around our development process and would be interested in any experiences, both good and bad, from anyone who uses the Community Plugin SDK on a regular basis to help us...
Forum Discussion
I also copy paste from Studio into an editor (Sublime Text w/Freemarker syntax, but want to move to IntelliJ). There's a Chrome extension that makes the Studio a lot better to work with: https://chrome.google.com/webstore/detail/lithium-studio-editor-enh/noiffnkgeldhkegbdldaeghijnoghapj?hl=en
It's still not ideal, but working in Studio is way faster. Going through the SDK, it takes over a minute to see any change posted (lithium push, refresh page, etc).
The node version has bugged me for a long time too. I have an open issue on the npm package warning about LTS (which is long since passed lol).
We have stage, preprod, and prod. All development happens in stage. Once work relating to a specific feature is done, I use lithium export to pull down the latest code.
We use Github. We have two branches main and stage. Work is completed in feature branches, so developers push up to their own branch, issue a Pull Request for review against stage.
When we want to release certain features, we cherry-pick, or straight up merge stage into main. From there, a Jenkins job is kicked off and basically runs the li studio publish to preprod. In preprod, I queue the version up, and go to Publishing in prod... etc.
This has worked for us, as it helps me mitigate what features go out to production, while enabling development work to continue without fear of releasing something by accident.
I hope that helps/makes sense. Happy to answer any questions or elaborate where needed.
