apigee / apigee/apigeetool-node
running remotetests takes a looong time
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
The deploy proxy in remotetests steps takes about 50-60 seconds and sometimes timing out
Proposal
1 - use a simpler proxy with just express - there is no need to include node_modules if its just express, so the bundle size could become significantly smaller and deployment faster
2 - for non-nodejs test, we could use a simpler proxy that does not have nodejs resources - might fasten the tests
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the deploy proxy used in the remotetests steps and inspect how its bundle includes node_modules and Node.js resources. Compare the current deployment time and timeout behavior with simpler Express and non-Node.js proxy variants; done means remotetests deploy faster without timing out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript, nodejs
- Domain
- devops, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100