# [Blueline] Py2F infrastructure: CI/CD on alps/balfrin, muli-process runs, update ICON

Continuation of this: https://hackmd.io/Sim7d9JXSs-oYSSlmUrI3g
<!-- Add the tag for the current cycle number in the top bar -->

- Shaped by: Christoph, Sam, Daniel
- Appetite (FTEs, weeks): 1 cycle
- Developers: <!-- Filled in at the betting table unless someone is specifically required here -->

## Problem

Currently missing:
* Building icon-exclaim with the granule in one step (scripts, spack recipe)
* jenkins/(gitlab?) CI/CD on balfrin/santis based on venv
* successful verification of diffusion granule with multiple GPU for all relevant experiments

## Appetite
1 cycle

## Solution
<!-- The core elements we came up with, presented in a form that’s easy for people to immediately understand -->

- Build recipe based on uvenv
- non-spack based first
- spack based TBD
- jenkins CI/CD on balfrin
- verification mode (compare granule at every execution to Fortran)
- substitution mode (only execute icon4py granule, probtest)
- gitlab on santis?
- Switch from mch_ch_r04b09 to small production experiments of MCH (icon1, icon2, kenda1)
- successfully verify diffusion granule for multiple GPUs (MCH production and aquaplanet) (merge Abishek's PR https://github.com/C2SM/icon-exclaim/pull/275)
- Test the (ITIR -> dace) backend instead of (ITIR -> gtfn)
- Update to newest icon-nwp

## Rabbit holes
<!-- Details about the solution worth calling out to avoid problems -->
Do not try to replicate any workflow and data processing platform. Keep it simple.

## No-gos

No performance optimizations yet.
## Progress
<!-- Don't fill during shaping. This area is for collecting TODOs during building. As first task during building add a preliminary list of coarse-grained tasks for the project and refine them with finer-grained items when it makes sense as you work on them. -->

- [ ] building icon-exclaim with granules
- [x] Without spack
- [ ] With spack