On Tue, Sep 05, 2023 at 07:22:46PM +0200, Gert Doering wrote: > Hi, > > On Tue, Sep 05, 2023 at 01:12:10PM +0000, flichtenheld (Code Review) wrote: > > GHA: do not trigger builds in openvpn-build anymore > > > > We do this via explicit PRs now, generated by renovate. > > This allows much better control over what state of the > > code gets built. > > Can you elaborate on this a bit more? I see lots of things flying by, > but do not understand any of it...
Sure. We have the renovate GHA at https://github.com/OpenVPN/openvpn-build/actions/workflows/renovate.yaml That runs regularly and checks whether all of the dependencies of openvpn-build can be updated. There are three primary inputs for renovate (its "state"): 1) The openvpn-build git repository 2) The PRs in the openvpn-build github repository 3) The "Dependency Dashboard" issue in openvpn-build github repository (https://github.com/OpenVPN/openvpn-build/issues/386) In 3) you can see a list of dependencies renovate has detected. >From 1) renovate will determine which dependencies are out-of-date. It will then check 2) whether it has already created a branch and PR to update this dependency. It respects closed PRs. So if it created a PR previously and the PR was closed without merging it, it will not be recreated. So for example if you push something into OpenVPN/openvpn, then renovate will determine on the next run that the src/openvpn submodule in openvpn-build is out of date and open a PR to fix that. renovate tracks both master and release/2.6 and through the information in the .gitmodules knows which branch of OpenVPN/openvpn to look at. So if you push into both master and release/2.6, it will create two PRs, against master and release/2.6 in openvpn-build, respectively. So as a result, we get PRs (and through that PR builds) for every push into any of the dependent repositories. That gives us a much more detailed picture than we had before, when we just inside the GHA updated all of the repositories to their latest state and hoped that they work together. Hope this helps, -- Frank Lichtenheld _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
