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
Currently the intended development cycle for the Cryostat backend is to make edits to the sources, then run mvn verify to build the OCI image and run all relevant tests, then sh smoketest.sh to run that OCI image as a Podman container to test it manually with curl etc. This is a pretty long and slow process end-to-end. It can be sped up somewhat by doing mvn -DskipTests=true -Dcryostat.minimal=true package instead, to skip unit and integration tests and to not (re)build the web-client, but this is still fairly slow. It would be nice to have a devserver setup similar to what the web-client has, where changes cause automatic recompilation and redeploy, while the Cryostat backend webserver is running as a local JVM process on the development machine. There would be no sample apps available as in the smoketest.sh, and no ability to apply container resource limits, so it would not be a replacement for the existing development cycle. Rather it would be a nice-to-have when adding a new API handler or fixing a bug with an existing handler, for example, since changes could be much more rapidly made and verified using curl/httpie/wget.
The text was updated successfully, but these errors were encountered:
Currently the intended development cycle for the Cryostat backend is to make edits to the sources, then run
mvn verify
to build the OCI image and run all relevant tests, thensh smoketest.sh
to run that OCI image as a Podman container to test it manually withcurl
etc. This is a pretty long and slow process end-to-end. It can be sped up somewhat by doingmvn -DskipTests=true -Dcryostat.minimal=true package
instead, to skip unit and integration tests and to not (re)build the web-client, but this is still fairly slow. It would be nice to have a devserver setup similar to what theweb-client
has, where changes cause automatic recompilation and redeploy, while the Cryostat backend webserver is running as a local JVM process on the development machine. There would be no sample apps available as in thesmoketest.sh
, and no ability to apply container resource limits, so it would not be a replacement for the existing development cycle. Rather it would be a nice-to-have when adding a new API handler or fixing a bug with an existing handler, for example, since changes could be much more rapidly made and verified usingcurl
/httpie
/wget
.The text was updated successfully, but these errors were encountered: