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

[META] RPM, Deb and Windows integration testing lacks jenkins automation #2994

Closed
5 of 18 tasks
gaiksaya opened this issue Dec 12, 2022 · 15 comments · Fixed by #4368
Closed
5 of 18 tasks

[META] RPM, Deb and Windows integration testing lacks jenkins automation #2994

gaiksaya opened this issue Dec 12, 2022 · 15 comments · Fixed by #4368
Assignees
Labels
feature New feature technical-debt Additional rework required to improve the existing code untriaged Issues that have not yet been triaged

Comments

@gaiksaya
Copy link
Member

gaiksaya commented Dec 12, 2022

Describe the bug

Currently, we are running integration tests manually on windows and other distributions since the process is not automated yet.
Looks like the test workflow already has the required support for them but needs to be automated in terms of CI or Jenkins.

To reproduce

Need to create a VM and then run IT on that for all components. It is much more complicated for OSD

Expected behavior

The integration testing should be automated to save human hours.

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

No response

Sub tasks

Acceptance Criteria

  • Integration tests should run via test_workflow (python framework) with jenkins as a wrapper
  • Integration tests should run on all supported platforms (eg: tar, rpm and deb running on linux)
  • The workflow should run independently on any workflow. Distribution workflow should not be blocked just because integration testing is taking a long time.
  • Integration test failures should create GH issues on respective GH repos similar to build failure issue
@gaiksaya gaiksaya added bug Something isn't working untriaged Issues that have not yet been triaged labels Dec 12, 2022
@peterzhuamazon
Copy link
Member

@peterzhuamazon
Copy link
Member

I would rename this issue to Jenkins automation, as they both have the Python code automation completed, tho with bugs.

Thanks.

@gaiksaya
Copy link
Member Author

Sure. Do you know the bugs @peterzhuamazon ?

@gaiksaya gaiksaya changed the title [Bug]: RPM and Windows integration testing lacks automation [Bug]: RPM and Windows integration testing lacks jenkins automation Dec 13, 2022
@gaiksaya gaiksaya removed the untriaged Issues that have not yet been triaged label Dec 15, 2022
@gaiksaya gaiksaya assigned gaiksaya and unassigned gaiksaya Dec 19, 2022
@bbarani bbarani added the technical-debt Additional rework required to improve the existing code label Jan 10, 2023
@bbarani
Copy link
Member

bbarani commented Jan 10, 2023

@gaiksaya @peterzhuamazon Lets make sure we close the gap for Debian distribution as well.

@bbarani bbarani changed the title [Bug]: RPM and Windows integration testing lacks jenkins automation [Bug]: RPM, Deb and Windows integration testing lacks jenkins automation Jan 10, 2023
@bbarani bbarani removed the bug Something isn't working label Jan 30, 2023
@bbarani bbarani changed the title [Bug]: RPM, Deb and Windows integration testing lacks jenkins automation [Enhancement]: RPM, Deb and Windows integration testing lacks jenkins automation Jan 30, 2023
@peterzhuamazon
Copy link
Member

@bbarani
Copy link
Member

bbarani commented Feb 2, 2023

@peterzhuamazon Referencing #2144 to execute parallel integ tests for OpenSearch Dashboards

@peterzhuamazon peterzhuamazon self-assigned this Feb 2, 2023
@bbarani bbarani added technical-debt Additional rework required to improve the existing code feature New feature and removed technical-debt Additional rework required to improve the existing code labels Feb 10, 2023
@bbarani bbarani changed the title [Enhancement]: RPM, Deb and Windows integration testing lacks jenkins automation [META]: RPM, Deb and Windows integration testing lacks jenkins automation Feb 10, 2023
@bbarani bbarani changed the title [META]: RPM, Deb and Windows integration testing lacks jenkins automation [META] RPM, Deb and Windows integration testing lacks jenkins automation Feb 10, 2023
@peterzhuamazon
Copy link
Member

@peterzhuamazon
Copy link
Member

peterzhuamazon commented Apr 26, 2023

Hi,

More issues:

  1. windows integTest automation: [Bug]: Fix OS integration tests for Windows platform #3196
  2. distribution osd send wrong link to integTest: [Bug]: Incorrect URL of OS build manifest passed into OSD integ test parameter  #3432
  3. osd integTest on deb/rpm have path errors which exit the test: [BUG] NPM not found when running integTest OSD through su <> opensearch-build-libraries#197
  4. osd integTest parallel issues due to functional test repo script have TEST_TYPE=default vs manifest: Updated integ-tests implementation to run all the OSD plugins.  #3316 (comment) (Need to add entry in test_finder.sh and integtest.sh to make TEST_TYPE=default for Jenkins run so that components can be called individually)

Thanks.

@bbarani
Copy link
Member

bbarani commented Jul 22, 2023

@zelinh Can you provide an update here?

@peterzhuamazon
Copy link
Member

@peterzhuamazon
Copy link
Member

This means RPM/DEB/Windows all have integration Test today.

@peterzhuamazon
Copy link
Member

Close this issue now as it will be handled in the above issue for Windows.

@gaiksaya gaiksaya reopened this Jan 24, 2024
@github-actions github-actions bot added the untriaged Issues that have not yet been triaged label Jan 24, 2024
@gaiksaya
Copy link
Member Author

I think this issue was more for automation related part. This PR should add it now.#4368

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature technical-debt Additional rework required to improve the existing code untriaged Issues that have not yet been triaged
Projects
Development

Successfully merging a pull request may close this issue.

4 participants