Remove build retry attempt
- Dominant language
- Go
- Stars
- 927
- Forks
- 387
- Avg merge
- 15h 5m
- Merged PRs (30d)
- 36
Description
The build should just fail and report this information back to the user ASAP, there is no reason to retry a build that is going to likely fail again for the same reason. I guess when it was introduced it was because there was some maven build intermittent issue.
_Originally posted by @squakez in https://github.com/apache/camel-k/pull/6582#pullrequestreview-4152596200_
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no file, test, or entry point. Start by locating the build retry handling in the Apache Camel K build flow and review the Maven intermittent-failure context; done means a failing build reports promptly without retrying.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100