Age | Commit message (Collapse) | Author | Files | Lines |
|
an exception is no more caught and triggers an error
when running versions
Issue-ID: TEST-312
Signed-off-by: morganrol <morgan.richomme@orange.com>
Change-Id: Ib787e6bf6359abc6df2732c27ebd7ac7ab9389af
Signed-off-by: morganrol <morgan.richomme@orange.com>
|
|
Issue-ID: INT-1834
Signed-off-by: mrichomme <morgan.richomme@orange.com>
Change-Id: I032ad1234036c5671722456995d1059a8a493cfb
|
|
For Java 11 there are four ways of checking Java binary version:
* -version print product version to the error stream and exit
* -showversion print product version to the error stream and continue
* --version print product version to the output stream and exit
* --show-version print product version to the output stream and continue
For Java 8 only error stream options are available. There is no support
for output stream (double-hyphenated) options.
This patch extends list of executed commands for binary version
detection. Java 8 presence will now be shown in results instead of
being reported as an error.
Issue-ID: INT-1601
Change-Id: I1b538bc1f0826f6000fedb08860d12c15fe2fc14
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|
|
This patch adds utility to check versions of binaries available in
Docker containers run on Kubernetes cluster. It has been contributed by:
kkkk-k <kkkk.k@samsung.com>
Several minor changes were made to comply with ONAP CI linter rules.
Issue-ID: INT-1571
Change-Id: Id0e4b557212dec1bf8d2bac580968d69e2cf5595
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
|