sxa
commented
7 months ago You can run this over the logs to produce a summary of each type of entry failure from the log issues above (Number at the start of each line in the output is the issue number): jenkinslog-process.sh.txt
Creating this as an umbrella to tie all the jenkins activities together:
[ ] Ongoing - #lts updates
[ ] https://github.com/adoptium/infrastructure/issues/3214
[x] Improve management of jenkins "jobs" disk usage
[x] https://github.com/adoptium/infrastructure/issues/3379
[x] https://github.com/adoptium/infrastructure/issues/3384
[ ] https://github.com/adoptium/infrastructure/issues/3385
[ ] https://github.com/adoptium/infrastructure/issues/3400
[ ] https://github.com/adoptium/infrastructure/issues/3442
[ ] https://github.com/adoptium/infrastructure/issues/3491
[ ] https://github.com/adoptium/infrastructure/issues/3500
[ ] https://github.com/adoptium/infrastructure/issues/3409
[ ] https://github.com/adoptium/infrastructure/issues/3622
[ ] https://github.com/adoptium/infrastructure/issues/3645
[ ] https://github.com/adoptium/infrastructure/issues/3811
Log warnings (=Potential security issues)
[ ] https://github.com/adoptium/infrastructure/issues/2774
[x] https://github.com/adoptium/infrastructure/issues/3469
[x] https://github.com/adoptium/infrastructure/issues/3485
[x] https://github.com/adoptium/infrastructure/issues/3486
[ ] https://github.com/adoptium/infrastructure/issues/3487
[ ] https://github.com/adoptium/infrastructure/issues/3496
[ ] https://github.com/adoptium/infrastructure/issues/3514