# Deprecation/Removal: testeng-ci

**URL:** <https://discuss.openedx.org/t/deprecation-removal-testeng-ci/13000>\
**Category:** Deprecation\
**Created:** [May 14, 2024, 2:46pm UTC](https://discuss.openedx.org/t/deprecation-removal-testeng-ci/13000 "2024-05-14T14:46:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\
**Post date:** [May 14, 2024, 2:46pm UTC](https://discuss.openedx.org/t/deprecation-removal-testeng-ci/13000/1 "2024-05-14T14:46:13Z")

</div>

I’d like to archive the [testeng-ci](https://github.com/openedx/testeng-ci/issues/419) repository, a tiny collection of Python functions for interacting with GitHub’s API. If you rely on these function or know of a part of the Open edX project which relies on these functions, please speak up before May 28th, or the repository will be excluded from Redwood and future releases. Thanks!

> <https://github.com/openedx/testeng-ci/issues/419>
>
> \### Proposal Date
> 
> 2024-05-14
> 
> \### Target Ticket Acceptance Date
> 
> 2024-05-28
> 
> \##…# Earliest Open edX Named Release Without This Functionality
> 
> Redwood
> 
> \### Rationale
> 
> I believe this is only used by 2U's internal jenkins tooling. I did some searching around the openedx GitHub organization, and I couldn't find any remaining references to the \`testeng-ci\` repo or the \`jenkins\` Python package that it contains.
> 
> \### Removal
> 
> This repository will be archived and it will not be part of the Open edX named release, starting with Redwood.
> 
> (the repo contains a redwood.master branch, but it will not get redwood.1 tag if this is accepted in time)
> 
> \### Replacement
> 
> The various functions that Jenkins served at edX have been replaced in a community-friendly way by a mix of GitHub Actions workflows, scripts in app repos, and Tutor.
> 
> \### Deprecation
> 
> I'll put a notice in the README.
> 
> \### Migration
> 
> If 2U uses this, they may want to fork it back into the \`edx\` GitHub organization
> 
> \### Additional Info
> 
> N/A
> 
> \### Task List
> 
> \- \[\] Transfer this issue to public-engineering.
> \- \[\] Transfer this repo to openedx-unsupported and archive it.

---

<div class="post-metadata">

**Author:** ![Awais\_Qureshi](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/awais_qureshi/32/3040_2.png) [@Awais\_Qureshi](https://discuss.openedx.org/u/Awais_Qureshi)\
**Post date:** [May 15, 2024, 6:35am UTC](https://discuss.openedx.org/t/deprecation-removal-testeng-ci/13000/2 "2024-05-15T06:35:59Z")

</div>

Upgrade package job is using this [script](https://github.com/openedx/testeng-ci/blob/ed9083cd6f0a774d5de75cefd356ad69dd47b9bf/jenkins/github_helpers.py#L261) to identify the bumps versions.

sample [output](https://github.com/openedx/edx-platform/pull/34791#issuecomment-2109150724)

---

<div class="post-metadata">

**Author:** ![kmccormick](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/kmccormick/32/8982_2.png) [@kmccormick](https://discuss.openedx.org/u/kmccormick)\
**Post date:** [May 15, 2024, 4:52pm UTC](https://discuss.openedx.org/t/deprecation-removal-testeng-ci/13000/3 "2024-05-15T16:52:00Z")

</div>

Thanks @Awais_Qureshi . Looks like we could merge `pull_request_creator` into repo-tools pretty easily. I have a draft here: [feat: move pull\_request\_creator here from testeng-ci by kdmccormick · Pull Request #517 · openedx/repo-tools · GitHub](https://github.com/openedx/repo-tools/pull/517)

How does that sound?