reuse TEITechnicalCouncil user at GitHub as DockerHub build bot

Peter Stadler

6 May 2020 6 May '20

6:29 p.m.

Dear all, you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense … So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me. Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot? If I do not receive any objections I will proceed in that direction. Best Peter

Attachments:

signature.asc (application/pgp-signature — 488 bytes)

Show replies by date

Hugh Cayless

6 May 6 May

6:34 p.m.

New subject: reuse TEITechnicalCouncil user at GitHub as DockerHub build bot

I believe Raff created that user for the SourceForge migration, and that it's only ever been used for that, so downgrading its capabilities and repurposing it should be just fine. Hugh On Wed, May 6, 2020 at 12:30 PM Peter Stadler wrote:

...

Dear all,

you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense …

So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me.

Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot?

If I do not receive any objections I will proceed in that direction.

Best Peter _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

Martin Holmes

8:36 p.m.

New subject: reuse TEITechnicalCouncil user at GitHub as DockerHub build bot

I don't remember that user being intended for anything specific, so I can't think of any objections. I wonder if that was a user created by Raff when he was importing issues from SourceForge, so that existing comments could be attributed to a specific user? Cheers, Martin On 2020-05-06 9:29 a.m., Peter Stadler wrote:

...

Dear all,

you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense …

So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me.

Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot?

If I do not receive any objections I will proceed in that direction.

Best Peter

_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca

Peter Stadler

7 May 7 May

4:08 p.m.

New subject: reuse TEITechnicalCouncil user at GitHub as DockerHub build bot

Thanks everybody for the quick replies. I now went ahead and degraded the TEITechnicalCouncil to the member role (for out TEIC group at GitHub) and added a new group „build“ (to which that user got added). This group needs admin(!) access to all repos that want to have automated builds enabled at DockerHub. The current list can be seen at https://github.com/orgs/TEIC/teams/build/repositories. With the help of Raffaele (who knows the password) and James (who receives the 2auth codes on his phone) I already setup the new DockerHub builds for OJS. So it’s working :) Cheers Peter

...

Am 06.05.2020 um 20:36 schrieb Martin Holmes :

I don't remember that user being intended for anything specific, so I can't think of any objections.

I wonder if that was a user created by Raff when he was importing issues from SourceForge, so that existing comments could be attributed to a specific user?

Cheers, Martin

On 2020-05-06 9:29 a.m., Peter Stadler wrote:

...
Dear all, you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense … So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me. Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot? If I do not receive any objections I will proceed in that direction. Best Peter _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

James Cummings

6:07 p.m.

New subject: reuse TEITechnicalCouncil user at GitHub as DockerHub build bot

Just for history, this was the user that was created when first setting up the TEI-C organisation on GitHub...which is why he was in the owners lists... but now is downgraded just to a lowly member. It all seems to have gone smoothly. Many thanks, James -- Dr James Cummings, James.Cummings@newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council on behalf of Peter Stadler Sent: 07 May 2020 15:08 To: TEI Council Subject: Re: [Tei-council] reuse TEITechnicalCouncil user at GitHub as DockerHub build bot ⚠ External sender. Take care when opening links or attachments. Do not provide your login details. Thanks everybody for the quick replies. I now went ahead and degraded the TEITechnicalCouncil to the member role (for out TEIC group at GitHub) and added a new group „build“ (to which that user got added). This group needs admin(!) access to all repos that want to have automated builds enabled at DockerHub. The current list can be seen at https://github.com/orgs/TEIC/teams/build/repositories. With the help of Raffaele (who knows the password) and James (who receives the 2auth codes on his phone) I already setup the new DockerHub builds for OJS. So it’s working :) Cheers Peter

...

Am 06.05.2020 um 20:36 schrieb Martin Holmes :

I don't remember that user being intended for anything specific, so I can't think of any objections.

I wonder if that was a user created by Raff when he was importing issues from SourceForge, so that existing comments could be attributed to a specific user?

Cheers, Martin

On 2020-05-06 9:29 a.m., Peter Stadler wrote:

...
Dear all, you might have received a notification from GitHub that I added the docker-pkp-ojs repo to the TEIC realm at GitHub. Next, I wanted to integrate with DockerHub for automated builds but DockerHub changed something (already some time ago) in that step that makes it necessary to re-connect a GitHub account with DockerHub. They recommend to use a dedicated service user for that rather than using an individuals account because otherwise the whole TEI group/organization at DockerHub would get access to that individuals repositories. Makes sense … So, I’m now looking for a service account I could use and found the existing user TEITechnicalCouncil – which is not really needed, methinks? The only caveat I see is that this user is currently in the group „owners“ and has admin access to all repositories. We should downgrade that user but that might have side effects? If I was to create a new account at GitHub I’d need an email-address that is not already registered with GitHub. So, it'd probably result in two new accounts which seems a bit messy to me. Any objections to downgrading the TEITechnicalCouncil user and turning that into a bot? If I do not receive any objections I will proceed in that direction. Best Peter _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

-- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes@uvic.ca _______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1652

Age (days ago)

1653

Last active (days ago)

List overview

Download

4 comments

4 participants

participants (4)

Hugh Cayless
James Cummings
Martin Holmes
Peter Stadler