elastic / elastic/logstash

Trigger gem update GHA periodically

Open
#19,151 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
1d 4h
Merged PRs (30d)
88

Description

Instead of concentrating gem dep updates right before release, we should set up a trigger to update active branches (perhaps weekly). This will help us get more soak time for new gem deps and reduce change set right before release. We can still do a manual run on FF to make sure we are getting the latest, but having gem updates happening at a regular cadence should reduce that change set. This can likely be accomplished by setting up a workflow dispatch for a schedule. Ideally we can automatically determine the streams to be actively managed. If there is a manual step there we should include updating that schedule in the minor release ticket template.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the existing gem update workflow and the minor release ticket template. Determine how active branches or streams are identified, then define the scheduled workflow and any manual step needed; done means active branches receive periodic gem updates without relying on pre-release runs.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, ruby
Domain
ci-cd, devops, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.