netlify: document ownership

[philips]

Currently @philips, @caniszczyk and @lucperkins all have access to netlify used on etcd.io. We should document this here and give access to any other maintainers who need it.

[philips]

@jberkus @lucperkins can you please document netlify ownership for etcd.io? There were caching issues getting the blog post out and I didn't really know who to bug.

[lucperkins]

@philips For future reference, that wasn’t a caching issue. The issue was that there was a specific time of day specified in the post’s front matter, which caused Hugo to consider the post as “future” and thus not create it. This can be avoided by specifying only month, day, and year.

[philips]

@lucperkins yea, I guessed that was the reason after I sent the email.

Is there any public way to see build issues?

[lucperkins]

@philips If the build fails, you see a big red X in the PR and are provided with a link to the build output. If it succeeds, you get a green check mark and a link to the deploy preview.

[philips]

Where? Like what happens if something breaks in master after a PR is merged?

…

On Thu, Jan 30, 2020 at 9:45 AM Luc Perkins ***@***.***> wrote: @philips <https://github.com/philips> If the build fails, you see a big red X and are provided with a link to the build output. If it succeeds, you get a green check mark and a link to the deploy preview. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=AAAIGCDA67VWGHUTYVSD44LRAMGZ7A5CNFSM4HQHNPIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKL4MSY#issuecomment-580372043>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIGCHOLM7N5V2JH6ZZF3LRAMGZ7ANCNFSM4HQHNPIA> .

[lucperkins]

@philips These are the log for all deploys: https://app.netlify.com/sites/etcd/deploys

There’s also output for each PR.

[philips]

Can we make that publicly viewable? I don't think I have rights.

…

On Thu, Jan 30, 2020 at 4:18 PM Luc Perkins ***@***.***> wrote: @philips <https://github.com/philips> https://app.netlify.com/sites/etcd/deploys — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=AAAIGCEBN6KK7Y5NYACRZV3RANU43A5CNFSM4HQHNPIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNBJXA#issuecomment-580523228>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIGCCJ2XAKKLHDQ2IUNZTRANU43ANCNFSM4HQHNPIA> .

[lucperkins]

@philips I'm looking around and I don't think there's a way to make the entire log viewable. Only the PR-specific log is public.

In terms of concerns about something breaking in master after a PR is merged, the website works just like "normal" CI-driven things. If there's a build failure, this is made clear in the PR and you cannot merge.

[philips]

OK, in that case we will have to document who to contact if things aren't deploying :-/

…

On Thu, Jan 30, 2020 at 4:58 PM Luc Perkins ***@***.***> wrote: @philips <https://github.com/philips> I'm looking around and I don't think there's a way to make the entire log viewable. Only the PR-specific log is public. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#11?email_source=notifications&email_token=AAAIGCF46QMY2S27DHWZHIDRANZRVA5CNFSM4HQHNPIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNDSKI#issuecomment-580532521>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAIGCD3MBP4PQTNJAOG57TRANZRVANCNFSM4HQHNPIA> .

[lucperkins]

@philips If things aren't deploying, whoever created the PR will be able to see why in the CI error output. If people can't interpret that error output, they would indeed need to @ one of the site maintainers. But that's how all CI workflows work; it's not fundamentally different from, say, how the etcd code works.

You appear to object to this system. Could you possibly clarify your objection?