allure-framework / allure-framework/allure3
Single Executable Build
- Dominant language
- HTML
- Stars
- 401
- Forks
- 58
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
Previously i was using allurectl in my CI to upload reports - and it was easy but resource intensive.
Now we switched to plugin-testops and it works great for environments that already have nodejs.
In cases where i don't have nodejs in the image it becomes quiet a challenge because it:
1. Requires you to install nodejs
2. Need time to resolve and download packages for allure (quite a lot)
3. Base image size grows
Solution:
Use same technique as allurectl and create Single Executable build so i can download it and use directly without additional node/npm
Contributor guide
Research direction
The issue names allurectl and plugin-testops but no source files or tests. Start by locating allurectl’s existing single-executable build and the plugin-testops packaging workflow; define the required artifact and verify it runs in a Node-free CI or container image without installing node, npm, or packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100