Make job submission system configurable
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 2.5k
- Forks
- 650
- Avg merge
- 6m
- Merged PRs (30d)
- 3
Description
I guess that parallel execution of build jobs is also supported by your software.
These jobs will be run by a local build environment so far. It can happen that the computing resources can become too limited for a challenging data processing application there.
I suggest to extend corresponding resources with capabilities from distributed systems. Some programming interfaces are available for such a purpose.
How do you think about to make it possible to choose from various job submission systems by configuration variables?
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 clarifying which job submission systems and configuration variables are intended, since the issue does not identify files, entry points, or a concrete interface. Survey the existing parallel build-job execution and local build environment before defining a bounded scope and success criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100