jenkinsci / jenkinsci/support-core-plugin
[JENKINS-63825] Durations in the support bundle are affected by the locale
- Dominant language
- Java
- Stars
- 19
- Forks
- 77
- Avg merge
- 17h 53m
- Merged PRs (30d)
- 3
Description
Jenkins started with the following system properties:
```
- arg[3]: `-Dfile.encoding=SJIS`
- arg[4]: `-Dsun.jnu.encoding=SJIS`
- arg[5]: `-Duser.language=ja`
- arg[6]: `-Duser.timezone=Asia/Tokyo`
```
this results in duration printed like this:
```
* Process uptime: 17 日
```
As far as I understand, the bundle is produced in UTC and non-localized to minimize variability and enable at least partial automatic processing. Hence durations should be localized.
---
Originally reported by
duemir, imported from: Durations in the support bundle are affected by the locale
escoem
Raw content of original issue
Jenkins started with the following system properties:
- arg[3]: `-Dfile.encoding=SJIS`
- arg[4]: `-Dsun.jnu.encoding=SJIS`
- arg[5]: `-Duser.language=ja`
- arg[6]: `-Duser.timezone=Asia/Tokyo`this results in duration printed like this:
* Process uptime: 17 日As far as I understand, the bundle is produced in UTC and non-localized to minimize variability and enable at least partial automatic processing. Hence durations should be localized.
- environment:
* support-core:2.56 'Support Core Plugin'
Contributor guide
Research direction
The issue identifies the support-core plugin's support bundle and the affected Process uptime duration, but names no source file, test, or entry point. Start by locating where the support bundle formats Process uptime, then reproduce the Japanese-locale output and inspect existing tests. Done means duration output is stable and non-localized under the reported locale settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100