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
After deploying a project that uses marklogic-unit-test, there is nothing in MarkLogic that indicates what version of marklogic-unit-test was deployed. In scenarios where an environment is not updated for an extended period, that would be useful information.
There's probably a reasonably simple way to include a .txt file with the version number in the packaged artifacts, which would end up in the modules database of a project that uses the framework. Even better -- could it be injected into default.xqy to display in the UI?
The text was updated successfully, but these errors were encountered:
Would you want the version to be in some response from the REST extension, or possibly from a new REST extension that only returns the version (and possibly other metadata in the future)?
Added to setup.xqy to be part of server-side display build.
Added to an API that setup.xqy's client-side JS could call and display (which would also allow other ways of getting the info)
.\gradlew.bat mlUnitTest --version. This could be useful when running tests in pipelines.
I think having it visible in the UI and through a gradle task would be great. If I had to pick one, I'd lean toward the UI based on how I use the framework, but others might feel differently.
After deploying a project that uses marklogic-unit-test, there is nothing in MarkLogic that indicates what version of marklogic-unit-test was deployed. In scenarios where an environment is not updated for an extended period, that would be useful information.
There's probably a reasonably simple way to include a .txt file with the version number in the packaged artifacts, which would end up in the modules database of a project that uses the framework. Even better -- could it be injected into
default.xqy
to display in the UI?The text was updated successfully, but these errors were encountered: