The goal of this issue is that every week we want our 40+ projects CI builds to be green with as little pain and effort as possible. Having green builds across the board will increase quality of our work in general, increase developer happiness and help prevent us from deploying broken code.
Scope: this issue covers builds for our official Piwik Plugins (VisitorGenerator, CustomAlerts, etc.) and components and all Piwik PRO plugins.
Proposed steps For The Win
<a class='mention' href='https://github.com/deprecated'>@deprecated</a>or not tagged with
<a class='mention' href='https://github.com/api'>@api</a>#6539
What we already have today
What else can we do to help us achieve green builds every week on 40+ repositories?
And we discussed "Detect automatically when plugins use code tagged with
<a class='mention' href='https://github.com/deprecated'>@deprecated</a>"?
it's starting to look pretty green on CI status! 5 builds failing out of 45 builds
CI Status: 9 builds failing out of 50 builds.
after the automatic Sunday Builds refresh we have: 12 builds failing out of 50 builds.
CI Status: 9 builds failing out of 49 builds.
we're almost there! Ci Status: 6 builds failing out of 49 builds.
This is getting really exciting!
Summary: 2 builds failing out of 47 builds.
Yesterday, 10 builds failing. Today 4 builds failing.
This new feature in ci-status will get rid of 2 failed builds: https://github.com/piwik/ci-status/issues/20
When following issues are closed we can close this issue:
The next step will be:
maybe someone from the team will volunteer to "own this" (eg. for a few months), or maybe a person rotating each week or month?
Created follow up issue: Decide who is responsible to fix the builds so that they are green each monday #7453
Well done to us, for the huge progress made in this area in the last few months... :+1: