The help of the agent availability (retention strategy) is hard coded into Jenkins as html files. This has 2 drawbacks:
- Not all translated pages have translations for all possible availability options (partially translation is there but only as comment in html), the description is then missing.
- Additional retention strategies provided by plugins can't provide their help
The proposal is to have the help generated in the same way is it is done for the launcher, so that each strategy can define it's own help files including translations.
This would also show english as fallback, in case a translation is not available.
Originally reported by mawinter69, imported from: Make Agent availability help more flexible
- assignee: mawinter69
- status: Closed
- priority: Minor
- component(s): core
- resolution: Fixed
- resolved: 2022-04-12T13:57:25+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
The help of the agent availability (retention strategy) is hard coded into Jenkins as html files. This has 2 drawbacks:
- Not all translated pages have translations for all possible availability options (partially translation is there but only as comment in html), the description is then missing.
- Additional retention strategies provided by plugins can't provide their help
The proposal is to have the help generated in the same way is it is done for the launcher, so that each strategy can define it's own help files including translations.
This would also show english as fallback, in case a translation is not available.
- environment:
Jenkins all version
The help of the agent availability (retention strategy) is hard coded into Jenkins as html files. This has 2 drawbacks:
The proposal is to have the help generated in the same way is it is done for the launcher, so that each strategy can define it's own help files including translations.
This would also show english as fallback, in case a translation is not available.
Originally reported by mawinter69, imported from: Make Agent availability help more flexible
Raw content of original issue
The proposal is to have the help generated in the same way is it is done for the launcher, so that each strategy can define it's own help files including translations.
This would also show english as fallback, in case a translation is not available.
Jenkins all version