Continuous Integration plan for Telligent 11?

We don't generally have CI specific recommendations as that can vary by company/developer.  We provide some basic guidance on setting up projects etc which then can be used to infer a CI setup appropriate for your environment.   The widget issue can be worked around using custom providers, if they are new, if they are just tweaks to existing widgets then it can be overkill and make upgrading more involved from a merge perspective.

https://community.telligent.com/community/11/w/developer-training/65128/setting-up-your-development-environment
https://community.telligent.com/community/11/w/developer-training/65068/managing-widget-source-and-distribution

Thank you

Hi Chris.

How did you get on setting up CI?

We're new to this, but so far this is how we've set things up..

• We created Factory Default Providers for widgets + automations.
• Developers working on local installs of Telligent will create new widgets/automations in the above providers.. publishing staged changes will save the files to disk (defaultwidgets/OURGUID, defaultautomations/OURGUID), at which point we can check them into Git.
• At this point we can trigger a process to push the files from those folders onto the development server. That's running in devmode, so will pick up the changes when it's restarted (or we clear the caches).
• Similar for the plugins.. but involves building the DLLs.
• When we do a deployment to Staging/Prod, we intend to export all the widgets/automations and import them on during the release. 

Haven't yet looked at the theme, so not 100% how we're going to handle that.

Hi Chris.

How did you get on setting up CI?

We're new to this, but so far this is how we've set things up..

• We created Factory Default Providers for widgets + automations.
• Developers working on local installs of Telligent will create new widgets/automations in the above providers.. publishing staged changes will save the files to disk (defaultwidgets/OURGUID, defaultautomations/OURGUID), at which point we can check them into Git.
• At this point we can trigger a process to push the files from those folders onto the development server. That's running in devmode, so will pick up the changes when it's restarted (or we clear the caches).
• Similar for the plugins.. but involves building the DLLs.
• When we do a deployment to Staging/Prod, we intend to export all the widgets/automations and import them on during the release. 

Haven't yet looked at the theme, so not 100% how we're going to handle that.