-
Improvement
-
Resolution: Fixed
-
Minor
-
-
Evergreen - Milestone 2
In the storage.ts class, our code to remove plugins (exploded directories and files) is using old-school unlink and remove with callbacks and the likes.
We should "promisify" it to make it more readable and consistent with the rest of the codebase using Promises.
See:
- the class to modify https://github.com/jenkins-infra/evergreen/blob/master/distribution/client/src/lib/storage.ts
Main pointers about NodeJS's util.promisify:
- blocks
-
JENKINS-54207 Update delete plugin flow to error out for anything other than file not found
-
- Closed
-
- links to
[JENKINS-54545] Promisify the plugin deletion
Labels | Original: evergreen technical-debt | New: evergreen newbie-friendly technical-debt |
Description |
Original:
In the storage.ts class, our code to remove plugins (exploded directories and files) is using old-school {{unlink}} and {{remove}} with callbacks and the likes. We should "promisify" it to make it more readable and consistent with the rest of the codebase using Promises. See: * http://2ality.com/2017/05/util-promisify.html * http://2ality.com/2017/05/util-promisify.html |
New:
In the storage.ts class, our code to remove plugins (exploded directories and files) is using old-school {{unlink}} and {{remove}} with callbacks and the likes. We should "promisify" it to make it more readable and consistent with the rest of the codebase using Promises. See: * the class to modify https://github.com/jenkins-infra/evergreen/blob/master/distribution/client/src/lib/storage.ts Main pointers about NodeJS's {{util.promisify}}: * http://2ality.com/2017/05/util-promisify.html * http://2ality.com/2017/05/util-promisify.html |
Link |
New:
This issue blocks |
Assignee | New: Jen Lijó [ jennyfive ] |
Assignee | Original: Jen Lijó [ jennyfive ] | New: Baptiste Mathus [ batmat ] |
Assignee | Original: Baptiste Mathus [ batmat ] |
Assignee | New: Jen Lijó [ jennyfive ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Hi batmat! I would like to give a try to this particular one. I have a year of experience developing in Java / Node and have roughly used Jenkins to run e2e tests, I'd like to get more familiar with the whole Jenkins ecosystem, so I thought contributing would be a good idea
Is Evergreen a good point to start for a beginner? Cheers!