Setting up driver tests to run against previous versions of lua libs through jenkins pipeline

[aleclorimer]

Moving to testing PR commits against current and legacy versions of SmartThingsEdgeDrivers. This change moves away from using Github workflows to run the tests and instead kicks off a set of Jenkins jobs when provided a version and commit. Upon completion of testing, the Jenkins job(s) will report back a passing or failing status to the PR for each version tested against.

[varzac]

I think we should keep the run against the latest uploaded artifact in addition to the jenkins version matrix testing. This gives us 1) rich test results directly in PR, and 2) a fallback of test status if the jenkins connection is unavailable for some reason.

[aleclorimer]

I think we should keep the run against the latest uploaded artifact in addition to the jenkins version matrix testing. This gives us 1) rich test results directly in PR, and 2) a fallback of test status if the jenkins connection is unavailable for some reason.

Done. I added back the latest GH route. Moved the jenkins script to its own file and lastly removed the Artifactory route from GH run-tests.yml because this has not worked in some time and does not sound like a route we will be pursuing going forward.

This flow should be replicated and can be seen in a development/test PR

[cjswedes]

What will we expand this to and when can we do that?

[aleclorimer]

Question mainly for @varzac. Chats about maybe going back to 52, but for sure looking to go to 59 at least. Currently working on a script that makes it easier to backport the tagging of tests to earlier versions of lua-libs.