% IMPORTANT: The following is UTF-8 encoded. This means that in the presence
% of non-ASCII characters, it will not work with BibTeX 0.99 or older.
% Instead, you should use an up-to-date BibTeX implementation like “bibtex8” or
% “biber”.
@INPROCEEDINGS{Caspart:1049168,
author = {Caspart, René and Speck, Robert and Mesiti, Michele},
title = {{RSEHPC}@{ISC}25: {T}ools and {T}echniques
for {C}ontinuous {I}ntegration and {B}enchmarking},
volume = {16091},
address = {Cham},
publisher = {Springer Nature Switzerland},
reportid = {FZJ-2025-05251},
isbn = {978-3-032-07611-3 (print)},
series = {Lecture Notes in Computer Science},
pages = {683 - 692},
year = {2026},
comment = {High Performance Computing},
booktitle = {High Performance Computing},
abstract = {This summary paper presents the outcomes of the RSEHPC
workshop at ISC25, which convened experts from the Research
Software Engineering and High-Performance Computing
communities to examine the integration of Continuous
Integration and Continuous Benchmarking (CI/CB) throughout
the HPC system life cycle. Through keynote and lightning
talks as well as through lively discussions, participants
explored the use of CI/CB from system design and procurement
to deployment and production use. The paper highlights three
case studies: KIT’s CI/CB services in production for
flexible HPC benchmarking; JSC’s deployment of exaCB for
system-wide benchmarking during the JUPITER exascale system
preparations; and RIKEN R-CCS’s integration of CI/CB in
the early design phase of the FugakuNEXT project. User
perspectives from software developers of projects like
OpenFOAM, PIConGPU, and libNEGF underscore both the growing
importance and the practical challenges of implementing
CI/CB in diverse and complex HPC environments. A recurring
theme is the tension between the need for customized
solutions and the drawbacks of fragmentation, which hinder
reproducibility, portability, and collaboration. The paper
concludes with a call to action for the HPC community to
establish common standards for CI/CB workflows and data
formats. By making benchmarking practices more FAIR
(Findable, Accessible, Interoperable, Reproducible), the
community can enhance software sustainability and
operational excellence in HPC ecosystems.},
month = {Jun},
date = {2025-06-22},
organization = {ISC High Performance 2025, Hamburg
(Germany), 22 Jun 2025 - 26 Jun 2025},
cin = {JSC},
cid = {I:(DE-Juel1)JSC-20090406},
pnm = {5112 - Cross-Domain Algorithms, Tools, Methods Labs (ATMLs)
and Research Groups (POF4-511) / HiRSE - Helmholtz Platform
for Research Software Engineering (HiRSE-20250220) / RGRSE -
RG Research Software Engineering for HPC (RG RSE) (RG-RSE)},
pid = {G:(DE-HGF)POF4-5112 / G:(DE-Juel-1)HiRSE-20250220 /
G:(DE-Juel-1)RG-RSE},
typ = {PUB:(DE-HGF)8 / PUB:(DE-HGF)7},
doi = {10.1007/978-3-032-07612-0_54},
url = {https://juser.fz-juelich.de/record/1049168},
}