On Sat, Jan 27, 2018 at 11:21 PM, Michael Stapelberg <stapelb...@debian.org> wrote:
> Hey, > > Have a look at https://salsa.debian.org/stapelberg/toxiproxy/-/jobs/5260 > — I just got a GitLab CI runner and job working which builds the package > using git-buildpackage, then looks for failures in reverse-dependencies > using https://github.com/Debian/ratt. > > I intend to write a tool to programmatically bulk-update CI settings on > GitLab, so that we can enable this feature for all of our repositories. > > Aside from the GitLab-side, we also need a .gitlab-ci.yml file in the > repository itself. I can bulk-commit these, along with adding them to > Files-Excluded in debian/copyright so that upstream copies are discarded. > I just saw that one can customize the path to .gitlab-ci.yml: https://docs.gitlab.com/ee/user/project/pipelines/settings.html#custom-ci-config-path I suggest setting this path to “debian/gitlab-ci.yml” for our repositories, so that we don’t need to mangle upstream’s .gitlab-ci.yml and have all relevant files within the debian/ directory. > > With this feature place, the next step I’d like to implement is a > speculative package auto-updater: upon noticing the Debian and upstream > version have diverged, we could import the new version, send a Merge > Request, have the CI check for breakages and (manually) merge and upload if > no breakages are introduced. > > Let me know if you have any thoughts, > > -- > Best regards, > Michael > -- Best regards, Michael
_______________________________________________ Pkg-go-maintainers mailing list Pkg-go-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers