Releases: buda-base/asset-manager
Audit Tool v1.0 Beta Final
What's Changed
- Installation kits and documentation for v1.0 by @jimk-bdrc in #144
- Add -v and -h flags by @jimk-bdrc in #153
- Remove obsolete files by @jimk-bdrc in #154
- Organizing for v1.0 beta by @jimk-bdrc in #155
- Asset manager 152 by @jimk-bdrc in #157
- Support override of sequence length by @jimk-bdrc in #159
- Shrink long missing sequence reports by @jimk-bdrc in #160
- Asset manager 125 by @jimk-bdrc in #161
- Rename Work run logs when warnings by @jimk-bdrc in #163
- Add test for filename correctness by @jimk-bdrc in #167
- Support options by @jimk-bdrc in #168
- User designated test sets by @jimk-bdrc in #170
- Diagnostic logs by @jimk-bdrc in #172
- Put all logs under the --log_dir directory by @jimk-bdrc in #173
Full Changelog: v1.0-alpha...v1.0-beta
Asset Manager Native Installers
This release provides native installers for Windows, MacOS, and Debian systems. It also serves user documentation on Github pages: Asset Manager Github pages
Downloading
Please refer to Asset Manager Github pages for details.
Important Note BDRC is in the process of having Microsoft certify our installers as safe. While this is underway, you will have to override notifications from Edge Browser and Microsoft Safe Screen that the download file is a threat. You must validate the downloaded file's SHA512 checksum before doing this. (Checksum instructions are in Asset Manager Github pages )
SHA Checksums
File | SHA 512 checksum |
---|---|
Windows.10.audit-tool-1.0.exe | E5F4C2ADE29FF603C59D26AD5F2FF621C348120F9603B14A04C14478B2F5179ECF674657B2124E58F161786BFB3D91C0A8599DD70CB9CF405D36CF5B3AC27424 |
Debian.audit-v1_1.0-alpha-1_amd64.deb | 32e7c4eab4bee8c218a065995b978f8fb4fcb3ec8b4a2a9ab58432aaf80dfdda63865a498510a5d3d6e657063772d94ea3951dfbe651c5915ed7d1c9ca94f7d5 |
MacOS.audit-tool-1.0.dmg | a37b72ea1683c8e79188c8dd0267cd78b8ae419d4f7db99d8f5127cfbbfefd46b073e07a28b73cade5f57f9eeea4393a694d549b224dd593794778cb753c33ca |
Known issues:
#149 : Unhandled command line options throw exception
#148 : installation directory contains obsolete files.
** Important** the shell (.sh
) and PowerShell files that v0.9 and earlier used are no longer supported and are not required. Please refer to Asset Manager Github pages for updated installation and operation instructions.
#150 The Debian installation directory isn't the greatest.
#151 help message is confusing.
What's Changed
- Bump log4j-core from 2.14.0 to 2.17.0 in /audittool/audit-test-shell by @dependabot in #135
- Bump tmpl from 1.0.4 to 1.0.5 in /asset-manager-web by @dependabot in #131
- Bump tar from 4.4.13 to 4.4.19 in /asset-manager-web by @dependabot in #130
- Bump path-parse from 1.0.6 to 1.0.7 in /asset-manager-web by @dependabot in #129
- Bump ws from 7.2.5 to 7.4.6 in /asset-manager-web by @dependabot in #124
- Bump browserslist from 4.12.0 to 4.16.6 in /asset-manager-web by @dependabot in #123
- Asset manager 126 EXIF warnings dump pull Request by @jimk-bdrc in #138
- Bump log4j-core from 2.17.0 to 2.17.1 in /audittool/audit-test-shell by @dependabot in #137
- asset-manager-109 Update to Java 17 by @jimk-bdrc in #139
- Asset manager 84 by @jimk-bdrc in #140
- Asset manager 141 by @jimk-bdrc in #142
- Documentation updates by @jimk-bdrc in #143
Full Changelog: v0.9r6...v1.0-alpha
v0.9r6: Bump ini from 1.3.5 to 1.3.8 in /asset-manager-web (#99)
Changelog:
asset-manager-106 | Implement user profiles and command line overrides in audit tool |
asset-manager-104 | audit-tool-config.[sh|ps1] is updated to only ask for the runtime jar file (the test library is now bound into it) |
asset-manager-74 | Java util exception: Don't fail if the file size test directory is empty |
Tested:
- MacOS 11 (BigSur). java 11
- Debian 10, java 8
- Windows 10, java 8
0.9 Release 5
V0.9 Rel 4
This release adds 'WARNING' semantics to test outcomes. Several tests require the existence of well-known directory names which contain image groups. You can set these names in the shell.properties
files on a site-by-site basis.
With this release, if those directories aren't found, the test will hold the "Not run" outcome, and the logs will log the tests results as a WARN, instead of an Error.
The overall result of a batch of tests has new semantics as well. Formerly, a test run passed only if all tests passed. A WARNING result would have been determined to be the same as an ERROR. In this release, the overall run result is calculated:
- PASS only if every test passed
- WARN if some tests passed and some tests had WARN status
- FAIL if any test failed.
This result is captured in the output file name of the run result:{PASS|WARN|FAIL}-WorkRID={date}.csv
However, the return code of the audittool program is still
- 0 if no tests failed (some may have passed, some may have warned)
- 1 if any test failed
V0.9 Rel 3
Resolved issue #68, which always used the default maximum image file size of 400K, instead of using the value in the shell.properties
file.
V0.9 rel 2
Final 0.9 release
This is the code complete Audit tool release. Any future releases will implement new features and bug fixes. This release includes
#57
For current operating instructions, please see v0.9 Operation
Field Release to NT
This is the current supported release. Released 18 Dec 2019, which the field team is testing and documenting for deployment.
Patchup from windows port
Fixes up line endings and file modes which were messed up when editing on windows.