Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On 04/03/18 21:39, Michael Stapelberg wrote: > Ah! Runs will automatically be triggered as soon as a gitlab-ci.yml file > is found. You can retry any run with the “retry” button next at the top > right. See for > example https://salsa.debian.org/go-team/packages/ethflux/-/jobs/8312 > > Does that

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Sun, Mar 4, 2018 at 6:29 PM, Martín Ferrari wrote: > Hi, > > Thanks for all the info, now it is a lot more clear! > Great! I updated ci.html with the link as discussed. > > > On 04/03/18 08:48, Michael Stapelberg wrote: > > * What kind of control do we have over it?

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Hi, Thanks for all the info, now it is a lot more clear! On 04/03/18 08:48, Michael Stapelberg wrote: > * What kind of control do we have over it? > Not sure I follow. Can you make this question more specific? Wondering about if it is posible to manually trigger runs, re-tries, etc. --

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Thu, Mar 1, 2018 at 2:41 PM, Martín Ferrari wrote: > On 01/03/18 07:58, Michael Stapelberg wrote: > > I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html > > already. If not, start there. > > I had read it, but it was good to read it again. > > > Instead of

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On 01/03/18 07:58, Michael Stapelberg wrote: > I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html > already. If not, start there. I had read it, but it was good to read it again. > Instead of sharing the knowledge only on mailing list posts, I would > strongly prefer to extend

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

I’m assuming you have read https://pkg-go.alioth.debian.org/ci.html already. If not, start there. Instead of sharing the knowledge only on mailing list posts, I would strongly prefer to extend ci.html such that it makes sense to everyone and is easily discoverable. Could you pose a few specific

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Michael, On 25/02/18 22:43, Michael Stapelberg wrote: > I ran this yesterday and had it do a CI run for all of our repositories. > There were 3 failures, all of which because the repository in question > has a debian/changelog entry whose version git-buildpackage cannot find > as a tag: This

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Status update: I have updated the ci setup tool to create/update debian/gitlab-ci.yml: https://salsa.debian.org/go-team/ci/commits/master I ran this yesterday and had it do a CI run for all of our repositories. There were 3 failures, all of which because the repository in question has a

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On 20/02/18 12:20, Michael Stapelberg wrote: > I’m only aware of one package (jacobsa/crypto) which has a > Debian-specific patch that requires the use of an architecture-specific > build tag. My proposed solution for this is to either specify the > architectures (as opposed to custom pointer

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Tue, Feb 20, 2018 at 12:06 PM, Martín Ferrari wrote: > Hi, > > On 19/02/18 17:13, Michael Stapelberg wrote: > > > I see the role of the CI setup as complementary: I expect that people > > will still build packages locally as they work on the packages. That > > path will

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Hi, On 19/02/18 17:13, Michael Stapelberg wrote: > I see the role of the CI setup as complementary: I expect that people > will still build packages locally as they work on the packages. That > path will continue to cover the debian/* part of the package. The > remainder (fit into the archive)

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Thanks for taking a look. I see the role of the CI setup as complementary: I expect that people will still build packages locally as they work on the packages. That path will continue to cover the debian/* part of the package. The remainder (fit into the archive) will be covered by the CI. In the

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Michael, On 19/02/18 09:25, Michael Stapelberg wrote: > I have spent the last two weeks on a different approach to our CI setup, > published the current version of the tools just now and added a document > to our website (not linked from the main page yet until I have some > feedback). This is a

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

I have spent the last two weeks on a different approach to our CI setup, published the current version of the tools just now and added a document to our website (not linked from the main page yet until I have some feedback). Please have a look at https://pkg-go.alioth.debian.org/ci.html,

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

Status update: I now ran ci.go, i.e. all of our repositories should now be configured. The next step is to bulk-commit debian/gitlab-ci.yml. I’ll let you know more details once I start working on that. On Tue, Jan 30, 2018 at 2:38 PM, Michael Stapelberg wrote: > > > On

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Tue, Jan 30, 2018 at 2:17 AM, Alexandre Viau wrote: > This is great! Good job. > Thanks for the feedback :) > > > Aside from the GitLab-side, we also need a .gitlab-ci.yml file > > in the repository itself. I can bulk-commit these, along with > >

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

This is great! Good job. > 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. Please do. (it

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

The tool to configure our repositories now lives at https://salsa.debian.org/pkg-go-team/ci/blob/master/cmd/ci/ci.go. I’ll run this tomorrow unless there are any objections. For the time being, the tool only touches the runner configuration and CI config path. In other words, I will not yet place

Re: [pkg-go] GitLab CI: git-buildpackage and ratt

On Sat, Jan 27, 2018 at 11:21 PM, Michael Stapelberg 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

[pkg-go] GitLab CI: git-buildpackage and ratt

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