Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support external tests run without docker #2026

Open
sophia-guo opened this issue Oct 22, 2020 · 1 comment
Open

Support external tests run without docker #2026

sophia-guo opened this issue Oct 22, 2020 · 1 comment
Labels
enhancement type:external 3rd party application tests (invoked by the make target 'external')

Comments

@sophia-guo
Copy link
Contributor

sophia-guo commented Oct 22, 2020

Current external tests are supposed to run with dockers, which lets people focus on setting up test running rather than correctly configuring machines.

There is an increasing requirement to run the tests on local or native environment without docker installed.
For example:

  • running tests on mac or windows.
  • running directly against pre-build jdk (no docker image available) , could use EXTRA_DOCKER_ARGS to set jdk as default java. Need to double check if it still work.
@karianna karianna added the bug label Oct 23, 2020
@llxia llxia added enhancement type:external 3rd party application tests (invoked by the make target 'external') and removed bug labels Mar 29, 2022
@judovana
Copy link
Contributor

This is just top level idea on top of "Global image for external #5553 " #5553
Durign the impl of ^ unless it will get much changed, quite straightforward option how to implement the "run on localhost" occured:

  • the EXTERNAL_AQA_IMAGE may get value of local/os:version where os:version is optional, and can be usually (but not straightforwardly) detected.
  • once it is set, a small call in external.sh will be diverge existing run from dockerfile and run to direct call to test.sh in selected test
    -- maybe soem bigger preparation will be needed (maven home, ant home.. - those will just egt extracted from dockerfiel generation to reusable calls), some copying)
  • in 5553 I had implemneted multi-os properties (different names of pkgs over oses (including optional versions) withotu necessary duplications
    -- this will be used to verify installed packages. If all found, then ok to go, otherwise error and exit (maaybe dgradable to warning)
    -- side idea - if EXTERNAL_AQA_SUDO is set, then instead of dying, it willt ry to install the deps

wdyt?
J.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement type:external 3rd party application tests (invoked by the make target 'external')
Projects
Status: Todo
Development

No branches or pull requests

4 participants