FY24-Q2 - Ops Hackathon - Pitches
This issue will represent a collection of pitches that everyone is suggesting to work on during the Hackathon week amongst folks who work in the section!
WHEN: 2023-05-22 to 2023-05-30 (F&F Day on 05/26
DETAILS: FY24-Q2 - Ops Hackathon Week (&8712 - closed)
💡
Wanting to pitch an idea? - What is the problem to solve and why it's important
❓ - What expertise/skillset is needed (e.g. As specific as
1 UX, 1 BE, 1 FE
or as general asanyone who wants to reorganize our docs in this area!
)💻 🎨 🗞 - Effort expected (or how you intend to timebox the effort to 1 week)
⏲
Upon completion of the hackathon, link to the artifact(s) to showcase your work (ideally a recorded demo would be great so that we can share them asynchronously!)
**Problem to Solve**
There's a number of CI templates that have gone untested, and we end up fixing them ad-hoc as users request it.
I'd like to collaborate with a few other interested individuals to:
1. Validate that they still run on a test project
2. Create an MR to fix the ones that do not work (e.g. pointing to an out of date image)
**Why this is important?**
We want to drive adoption of CI, much of which starts with a new user trying out a template.
This can become cumbersome for each of our users to stumble upon errors, then have to create a bug
only when they get a failed pipeline.
**Requested expertise**
Anyone who enjoys debugging and fixing broken builds built from syntax in our CI templates! :)
**Effort expected**
Likely 2-3 days of dedicated effort, depending on the number of individual interested in joining this effort
**Artifacts to be produced**
Record a short walkthrough of the changes made, with links to MRs.
Sign-up (TBD)
Similar to last time, we will move the pitched ideas to a spreadsheet for easier reference and voting (during the week of 2023-05-15).
Previous FY23 Hackathon Pitches
Looking for inspiration?
- FY23 - Verify Hackathon - Pitches (#203 - closed)
- FY23 Hackathon ideas that were voted on: see spreadsheet
Potential Hackathon ideas (carryover from FY23-Q3):
This is a list of carryover that did not have an associated Slack or any votes towards them in the previous Hackathon. If you'd like to pitch it again, please re-add it to this issue!
Pitched by | Description |
---|---|
Arran Walker | Bring the Ruby code for CI config validation and GitLab-Runner job definition rendering to WASM. |
James Heimbuck | I want to run concurrent runners per executor but only one per project - Taken from gitlab#15325 |
James Heimbuck | after_script is not working for cancelled or timed out pipelines making it difficult to get data from those jobs. |
Elliot Rushton | Reverse Hack-a-thon! Spend the week solely focused on resolving, moving forward, closing out, merging, fixing, completing as many outstanding community contributions as possible. |
Frédéric Caplette | Build a mechanism where any BE engineer can flag a certain CI yaml keyword as being deprecated, and have it automatically show warnings in UI |
Grzegorz Bizon | Build automation to convert JSON Schema for .gitlab-ci.yml to Cue |
Eduardo Bonet | Add an API endpoint that takes a job definition and adds to the runner queue - gitlab#328489 |
Elliot Rushton | Allow user to specify a Dockerfile in CI yaml config (it's either pulled from a registry or builds a new one and caches it) |
Dov Hershkovitch | Build automation to auto-create a JSON Schema for .gitlab-ci.yml |
Elliot Rushton | Create CI sample environments to reproduce customer issues |
Arran Walker | Create new renderer for job logs |