Hello community friends
Does anyone have recommendations on how to do continuous integration and deployment with dnn?
We have many modules which coexist on same site, it consumes a lot of time to build and deploy and we want to find at way to automate this process. We are currently using Subversion, either continuing using this or port it to like say git.
Do you have any idears and recommendations from own expericence on how to start up this process, what kind of program is suiteable to DNN, eventually consultance company that can help remote setup (living in Denmark).
Thanks so much.
Kind regards,
Danny
The first step is going to be setting up continuous integration, where a source code push triggers an install package being built. Most of the common module templates will create a package when you build in Release mode. You can then trigger your CI server to run this build, and keep the install package as an artifact of the build. You can do this with your existing SVN repo, and integrate it with TeamCity, Azure DevOps Pipelines, or some other CI provider.
For deployment, I would suggest looking at Cantarus PolyDeploy. You will install the module on your DNN site, and then you can use the command line client to connect to the site and run module installations as part of a CD process. If you're using Azure DevOps Pipelines, I maintain a PolyDeploy task you can use.
You may also want to look at the DNN Pipeline Tasks from Iown Computer Gurus (Mitchel Sellers) and Andrew Hoefling's DNN CI/CD post.
Posted By Brian Dukes on 25 Jun 2019 09:00 AM For deployment, I would suggest looking at Cantarus PolyDeploy. You will install the module on your DNN site, and then you can use the command line client to connect to the site and run module installations as part of a CD process. If you're using Azure DevOps Pipelines, I maintain a PolyDeploy task you can use.
Woah that's cool
Well that link didn't work.
My DNN Azure Pipelines Blog Post
I noticed Andrew Hoefling post has a lot of missing images. Just FYI.
Posted By Cameron K on 27 Nov 2019 05:17 PM I am also wondering what you guys do when you need to update the sql scripts (sql data provider folder)? Do you manage that manually and leave the version numbers separate from the auto build?
If you're using a process that utilizes the actual DNN installer, then you don't have to worry about this. For example, PolyDeploy does this, and then DNN reads the manifest file (*.dnn) to know if there are scripts and when to install them. As long as the scripts are tested, properly wired up in the manifest, and are present in the correct place in the package, they'll execute for the extension version(s) as necessary.
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.