Problem/Motivation

Looking at the new GitLab jobs for testing Core I see

declare -x GITLAB_USER_EMAIL="[actual_email_address_I_registered_with_on_drupal_dot_org]"
declare -x GITLAB_USER_ID="39382"
declare -x GITLAB_USER_LOGIN="Spokje"
declare -x GITLAB_USER_NAME="Spokje"

This also works in MRs I have not created, where the email address of its creator is also publicly visible.

Can we use the same anonymize-magic we do on the rest of drupal.org?
I'm not really happy (slight understatement) to have my email address out there without any (at least know to me) way to turn that off.

Tentatively putting a "Major" priority on this, due to GDPR/privacy concerns.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Issue fork drupal-3387916

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

Spokje created an issue. See original summary.

fjgarlin’s picture

fjgarlin commented

Removing the export command should do it.

fjgarlin opened merge request !4808

fjgarlin’s picture

fjgarlin commented
Status: Active » Needs review

I've removed the lines, which were there mostly for debugging purposes.

Pipeline for this MR is running: https://git.drupalcode.org/issue/drupal-3387916/-/pipelines/20997
MR to review: https://git.drupalcode.org/project/drupal/-/merge_requests/4808

spokje’s picture

spokje
Primary language Dutch
commented
Status: Needs review » Reviewed & tested by the community

Unsure if we want to remove all of the export, since there might be useful stuff in there, but at least it doesn't expose the email address any more.

RTBC for me.

Thanks for the (very) quick turnaround!

poker10’s picture

poker10 commented
Parent issue: » #3387107: [meta] GitLab CI feature parity with DrupalCI

  • catch committed 60b86d58 on 10.1.x 
    Issue #3387916 by fjgarlin, Spokje: Each GitLab job exposes user email...

  • catch committed 9bc5e07a on 11.x 
    Issue #3387916 by fjgarlin, Spokje: Each GitLab job exposes user email
catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Fine to remove all I think, they create noise in pipelines and we can always add back to debug.

Committed/pushed to 11.x and cherry-picked to 10.1.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.