continuous delivery issue

Hi,

We are having issues with continuous delivery (CD) to a staging and cloud environment.

We have followed the documentation, and the continuous integration (CI) and continuous delivery (CD) processes do work. The issue arises when uploading the DLLs. We have multiple DLL files to push using the command-line interface (CLI) in the CD. The problem is that when one of the DLLs is not pushed in the correct order, the site crashes and the CD process stops uploading the DLLs, resulting in an automatic rollback.

This also applies to only using the CLI tool without continuous delivery. Our question is if there is a better way to publish the DLLs to a staging and a cloud environment.

Does anyone know a better way to upload the DLLs to the staging cloud environment?

https://doc.dynamicweb.dev/documentation/tutorials/extending/workflows/setting-up-ci-cd.html

With kind regards,

Duncan Janssen

Hi Duncan,

When you have a complex solution with dlls that interact and depend on each other, it can be hard to update them on the fly. That's why the CLI has the option to queue the dlls for installation without changing the running solution. Use the --queue flag to queue. That way the dlls are loaded when the solution recycles next time, which -- if you're following the guidelines in the article as you mention -- should happen as one of the last steps anyway. The article was updated a month or two ago to highlight the option to queue the installation.

Also note that you can queue as many assemblies as you want as many times as you want, but only the latest queued assembly per assembly is actually installed. E.G., if you have dll A.dll (1.0.0) and B.dll (1.0.0), you can queue them individually, I.E., installing A then B, and they will both be queued. If, however, you install A.dll (1.0.0) and then later before a recycle you install A.dll (1.0.1), version 1.0.1 is installed.

I hope this helps.

- Jeppe

Developer forum

continuous delivery issue

Replies