refactor!: remove Jenkins CI scripts #31812
Conversation
These files were used to run tests on build.testeng.edx.org, a Jenkins server. All tests have sinced been moved over to GitHub Actions, and build.testeng.edx.org is decomissioned.
kdmccormick
changed the title
There was a problem hiding this comment.
pytest-xdist in general is still useful for local test runs in order to take advantage of all available CPU cores, but the scripts here were specifically for running tests on multiple remote machines. You could use them to trigger a test run locally and farm them out across EC2 workers (and we verified that this works), but I'm pretty sure nobody outside the former Tools team ever did that; the primary use case was reducing the overall duration of test runs on Jenkins.
|
Sounds good, thanks for the review and that context. |
|
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
|
EdX Release Notice: This PR has been deployed to the production environment. |
|
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production. |
Description
These files were used to run tests on
build.testeng.edx.org, a Jenkins server.
All tests have sinced been moved over to
GitHub Actions, and build.testeng.edx.org
is decommissioned.
Other information
This helps with:
by reducing the number of shell scripts I need get passing ShellCheck.
Question for reviewers
I deleted:
scripts/jenkins-*.sh: definitely Jenkins-specificscripts/Jenkinsfiles/*: definitely Jenkins-specificscripts/xdist/*: I think these are Jenkins-specific, but could someone with knowledge about edx-platform CI confirm this?