Pipeline Authoring 18.5 Planning issue
Pipeline Authoring Issue Boards
Current/Upcoming Security issues
Goals for the milestone
- Bug burndown
- Get rid of remaining severity2 issues, likely some of them coming in from Pipeline Execution
- Afterwards focus on infradev and security issues with lower severity, overdue ones first
- Work towards successful delivery of Read inputs from a file (gitlab-org/gitlab#415636)
- Proceed with interlock projects
- Allow interpolation to use local context data needs to be ready for development, ideally we can start implementation this milestone
- Dynamic Input Selection and Job Inputs should start taking shape; both are due in Q1FY27 – but ideally I'd like us to deliver Dynamic Input Selection in Q4FY26 already so there is fewer things at the same time.
- Preparing for future interlock items
- We thought about Pipeline Creation Performance for Q2FY27, but I'll probably put it up for Q3FY27 instead, so we can do JSON schema for validation in Q2FY27 first. It's a good prerequisite and complex enough on its own.
- We haven't progressed the Interlock - Support .com components in a Self M... (gitlab-org&15224) topic, but we still want to do it as a future interlock item. We need to get it into "interlock shape", which will require planning work.
- Onboarding Sahil :)
Active UX Research Efforts
- Currently none planned
Capacity
- Verify:Pipeline Authoring Google Calendar
- Rajendra coming back and recovering from Co-Create/Travel
- Sahil onboarding with Laura as onboarding buddy
- Furkan on conference; PTO in second half of milestone
Dynamic view of work in the milestone
---
title: Work that is "Ready for development" or further along
display: table
fields: title, epic, weight, labels("missed::*", "type::*", "frontend", "backend") AS "Labels", assignee
limit: 40
sort: created desc
---
label = ("group::pipeline authoring") AND label in ("workflow::ready for development", "workflow::in dev", "workflow::in review", "workflow::ready for review", "workflow::verification", "workflow::blocked") AND group = "gitlab-org" AND state = opened AND milestone = "18.5"
---
title: Work that is not ready for development yet
display: table
fields: title, epic, labels("workflow::*") AS "Workflow", labels("missed::*", "type::*", "frontend", "backend") AS "Labels", assignee
limit: 40
sort: created desc
---
label = ("group::pipeline authoring") AND label != ("workflow::ready for development", "workflow::in dev", "workflow::in review", "workflow::ready for review", "workflow::verification", "workflow::blocked", "type::ignore") AND group = "gitlab-org" AND state = opened AND milestone = "18.5"
---
title: Completed work
display: table
fields: title, epic, weight, labels("workflow::*") AS "Workflow", labels("missed::*", "type::*", "frontend", "backend") AS "Labels", assignee
limit: 40
sort: created desc
---
label = ("group::pipeline authoring") AND label != ("type::ignore") AND group = "gitlab-org" AND state = closed AND milestone = "18.5"
/cc @gitlab-com/pipeline-authoring-group
Edited by Manuel Grabowski