envoyproxy/envoy

Add (daily/weekly) CI for supported release branches

Open

#20,035 opened on Feb 18, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/buildarea/cienhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

description

A recurring issue we have is that there are some parts of CI that are not pinned, and are subject to change.

This can lead to bit-rot on release branches. Mostly these are just CI issues, but sometimes flag incompatibilities that should be addressed.

Currently this effects stable maintainers and backporters around the time of releases, who then have to figure what is breaking/broke to land their PRs

It would be very helpful if we were to add some CI that tests these branches regularly, and potentially alerts maintainers one way or another as issues arise.

Contributor guide

Research direction
Explore the existing CI configuration in the repository, especially in .github/workflows, and design a periodic workflow that runs daily or weekly on the supported release branches. Consider using workflow dispatch or schedule triggers.
Tech stack
cppgithub actions
Domain
ci cddevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitCI/CDGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60