Skip to content

Add user.email to the CI Visibility pipeline attributes.#253

Merged
drodriguezhdez merged 1 commit into
masterfrom
drodriguezhdez/add_user_email_triggered_pipeline
Oct 25, 2021
Merged

Add user.email to the CI Visibility pipeline attributes.#253
drodriguezhdez merged 1 commit into
masterfrom
drodriguezhdez/add_user_email_triggered_pipeline

Conversation

@drodriguezhdez

Copy link
Copy Markdown
Collaborator

Requirements for Contributing to this repository

  • Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
  • The pull request must only fix one issue at the time.
  • The pull request must update the test suite to demonstrate the changed functionality.
  • After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.

What does this PR do?

This PR adds the user.email tag to the pipeline attributes if we can obtain it.

Description of the Change

Alternate Designs

Possible Drawbacks

Verification Process

Additional Notes

Release Notes

Review checklist (to be filled by reviewers)

  • Feature or bug fix MUST have appropriate tests (unit, integration, etc...)
  • PR title must be written as a CHANGELOG entry (see why)
  • Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
  • PR must have one changelog/ label attached. If applicable it should have the backward-incompatible label attached.
  • PR should not have do-not-merge/ label attached.
  • If Applicable, issue must have kind/ and severity/ labels attached at least.

@drodriguezhdez
drodriguezhdez requested a review from edrevo October 25, 2021 10:40
Comment on lines +124 to +126
if(StringUtils.isNotEmpty(buildData.getUserEmail(""))){
buildSpan.putMeta(CITags.USER_EMAIL, buildData.getUserEmail(""));
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: I do not know what the Java convention is but would it not be better to store the value of buildData.getUserEmail("") instead of calling it twice?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's OK to invoke multiple times to a getter.

@drodriguezhdez
drodriguezhdez merged commit 4cc12f7 into master Oct 25, 2021
@drodriguezhdez
drodriguezhdez deleted the drodriguezhdez/add_user_email_triggered_pipeline branch October 25, 2021 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants