Press Ctrl / CMD + C to copy this to your clipboard.
This post will be reported to the moderators as potential spam to be looked at
Having a little issue with client dependency in production. I am using continuous integration for deployment (azure devops)
Looking at the notes on https://github.com/Shazwazza/ClientDependency/wiki/Versioning
Just wondering if you anybody had any further information in increasing the number for client dependency.
The javascript in the backend seems to lockup a bit after deployment - causing the backend not to work. Namely the angular controllers.
To resolve I have to
Hey Lori,
What CI/CD system are you using?
Nik
Azure Dev ops
Okay, so with azure Dev OPS, you can take advantage of your release pipeline to do variable substitution on the client dependency file and control the version number. Something I do is set it to the build id do it changes on every release.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.
Continue discussion
Client Dependency Versioning continuous integration - Umbraco Backend
Having a little issue with client dependency in production. I am using continuous integration for deployment (azure devops)
Looking at the notes on https://github.com/Shazwazza/ClientDependency/wiki/Versioning
Just wondering if you anybody had any further information in increasing the number for client dependency.
The javascript in the backend seems to lockup a bit after deployment - causing the backend not to work. Namely the angular controllers.
To resolve I have to
Hey Lori,
What CI/CD system are you using?
Nik
Azure Dev ops
Okay, so with azure Dev OPS, you can take advantage of your release pipeline to do variable substitution on the client dependency file and control the version number. Something I do is set it to the build id do it changes on every release.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.