You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recent release notes for CDash look excellent, and we'd love to test the latest version! However, I am struggling to upgrade from CDash 3.1.0.
We run CDash with docker, and we use the kitware/cdash images available on DockerHub. We run the container on AWS, on a VM in a private network, behind a public load balancer which serves as the TLS endpoint. Therefore, we don't need or want CDash to handle TLS.
This was possible with CDash 3.1.0, but I can't achieve the same with CDash 3.2.0 or 3.3.0. Am I missing something?
There seems to be a way via DEVELOPMENT_BUILD, but I don't like the look of it 😅
Additional Information
For what it's worth, our systemd unit file to run CDash 3.1.0 looks like this:
The exact situation you describe is a known pain point that we're working to address. The changes related to that are currently scheduled for CDash 3.5, which we hope to release sometime in July. As a temporary workaround, you could modify the conf files to use port 80 instead of 443, and get rid of any SSL certificate stuff. You could alternatively use the development image and set APP_ENV to production.
Hi there,
The recent release notes for CDash look excellent, and we'd love to test the latest version! However, I am struggling to upgrade from CDash 3.1.0.
We run CDash with docker, and we use the
kitware/cdash
images available on DockerHub. We run the container on AWS, on a VM in a private network, behind a public load balancer which serves as the TLS endpoint. Therefore, we don't need or want CDash to handle TLS.This was possible with CDash 3.1.0, but I can't achieve the same with CDash 3.2.0 or 3.3.0. Am I missing something?
There seems to be a way via
DEVELOPMENT_BUILD
, but I don't like the look of it 😅Additional Information
For what it's worth, our systemd unit file to run CDash 3.1.0 looks like this:
cdash.service
The text was updated successfully, but these errors were encountered: