CI/CD Support Pod

Purpose

Discuss CI/CD related tickets/issues, learn about CI/CD features and improve related documentation.

Scope

Topics in this pod will ideally align with these product groups:

• Pipeline Authoring
• Pipeline Execution
• Pipeline Security

In the context of “CI/CD” it can be hard to pinpoint where exactly a problem fits in. This list is not meant to discourage anyone from seeking help in the pod – when in doubt, ask away! The worst that could happen is that someone suggest a better place for the question.

Current objectives

• Keep regular meetings going
• Stay updated on all things CI/CD
• Help each other with CI/CD tickets!

Support Pod members

• Lead: Manuel Grabowski (@manuelgrabowski) (Interested in co-leading? Let me know!)
• Cleveland Bledsoe Jr (@cleveland)
• Ryan Kelly (@rkelly)
• Elif Munn (@e_munn)
• Edward Hilgendorf IV (@edwardhilgendorf)
• Duncan Harris (@duncan_harris)
• Alejandro Guerrero de Alba (@alejguer)
• Segolene Bouly (@sbouly)
• Charl Marais (@cmarais)

How to get involved

1. Talk with your manager.
2. Add CI to your knowledge areas in the Support Team data. If it already exists, adjust your level accordingly.
3. Let your teammates and groupmates know about your new focus area.
4. Join the #spt_pod_cicd Slack channel.
5. Add yourself to this page.
6. Attend CI/CD pairing sessions if we can ever figure out how to work a calendar. See Regular meetings and check the GitLab Support calendar for up to date meeting times

Regular meetings

• CI/CD Pod pairing session:
  • Mondays, 15:30 CET (13:30 / 14:30 UTC depending on DST, check the GitLab Support calendar)
  • Thursdays, 15:30 CET (13:30 / 14:30 UTC depending on DST, check the GitLab Support calendar)

Collaboration channels

• Slack channel: #spt_pod_cicd

Set up a CI/CD View in Zendesk

It’s recommended to set up a personal view for all CI/CD related tickets.

1. Go to Manage Views
2. Click Add View
3. Set up a view with the following parameters:
   • Title: CI/CD Pod
   • Conditions:
     • Tickets must meet all of these conditions to appear in the view:
       • Status is not Closed
       • Status is not Solved
       • Status is not pending
     • Tickets can meet any of these conditions to appear in the view:
       • Tags contains at least one of the following:
         • Add all support_cicd_* tags
         • Add support_category_cicd
   • Columns (Recommended but you can choose what you’d like):
     • Next SLA breach
     • Subject
     • Requester
     • Request date
     • Assignee
     • Priority
     • Organization
   • Order by:
     • Next SLA breach - Ascending

View page source - Edit this page - please contribute.