[INTDIST-51] No way to automatically find test tools belonging to a particular ODL release Created: 03/Feb/16  Updated: 20/Oct/17  Resolved: 19/Nov/16

Status: Resolved
Project: integration-distribution
Component/s: Scripts
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Jozef Behran Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5206

 Description   

Suppose that a test needs the "testtool" testing tool to do its work. How it can automatically determine where it is located in the Nexus?

For Lithium releases it is needed to pull from "org/opendaylight/netconf/netconf-testtool/1.0.0-SNAPSHOT" (I am not sure about this one to be exact). For Beryllium releases it is also needed to pull from "org/opendaylight/netconf/netconf-testtool/1.0.0-SNAPSHOT" But for Boron releases is is needed to pull from "org/opendaylight/netconf/netconf-testtool/1.1.0-SNAPSHOT".

The particularly troublesome part of the path to the test tool is the "1.0.0-SNAPSHOT"/"1.1.0-SNAPSHOT". There is no automatic way to figure this one out. Currently the test tools deployment code needs to harbor a large dictionary

It is not particularly safe to use e.g. Boron test tools to test Lithium. For example now this won't work because Lithium/Beryllium require Java 7 while Boron test tools require Java 8.

 Comments   
Comment by Vratko Polak [ 10/Feb/16 ]

This seem to work for Beryllium, both snapshots and autorelease, since Change 34149 was merged.
Setting to FIXED.
Official release and Boron snapshots are not tested thoroughly, reopen when necessary.

Generated at Wed Feb 07 20:02:39 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.