Julio Biason
4 months ago
3 changed files with 44 additions and 17 deletions
@ -0,0 +1,20 @@
|
||||
- "Build stuff with Chris" |
||||
- What about the GPU builds? Are we going to have specialized pipelines for this? |
||||
- PR in scale (running pull requests validations) |
||||
- We don't need to do this right now |
||||
- We can disable branch discovery and leave only on "open PRs" |
||||
- Show & Tell about the new branching stuff |
||||
- Doing this after 4.2.1 |
||||
- Pick a "Guinea pig" to test this with us |
||||
- This sprint, focus more on this branch/PR thing |
||||
- Bitbucket may not support what we need (due the lack of blocking merges when the build fails) |
||||
- If we need harder restrictions, we have other options, like paying Bitbucket more or moving to something else |
||||
- Idea is to have larger tests happening 3 week before release, running 24/7 |
||||
- HelyxTest needs to go |
||||
- We need to help Emanuel remove his cases from helyxTest and have a specialized tool for image comparison |
||||
- Case database |
||||
- I don't think this is a devops job |
||||
- V&V Pipeline |
||||
- Work on it, we may need it in the future |
||||
- We are going to run larger cases in it too, which would require Slurm |
||||
- Run post build tests (validate distribution) |
@ -0,0 +1,10 @@
|
||||
- Generate images with RTPP |
||||
- Need to save those PNGs as artifacts |
||||
- Need to find something to compare images |
||||
- Artifacts are kept for 2 runs, so maybe we need to find some better place to keep them for a long time |
||||
- Run to completion |
||||
- Working on it with HelyxVerify |
||||
- Use a different repository for those tests |
||||
- Export Python scripts to Core scripts: Why? |
||||
- Join the Testing Meeting |
||||
- Cristian is there, so he can either pull me in the meeting or warn me about it. |
Loading…
Reference in new issue