Skip to content

Add gbhat618 as developer to plugin-google-compute-engine.yml#4988

Open
gbhat618 wants to merge 3 commits intojenkins-infra:masterfrom
gbhat618:add-gbhat-to-gce-plugin-devs
Open

Add gbhat618 as developer to plugin-google-compute-engine.yml#4988
gbhat618 wants to merge 3 commits intojenkins-infra:masterfrom
gbhat618:add-gbhat-to-gce-plugin-devs

Conversation

@gbhat618
Copy link
Copy Markdown

Link to GitHub repository

https://github.com/jenkinsci/google-compute-engine-plugin

When modifying release permission

List the GitHub usernames of the users who should have commit permissions below:

This is needed in order to cut releases of the plugin or component.

If you are modifying the release permission of your plugin or component, fill out the following checklist:

Release permission checklist (for submitters)

  • The usernames of the users added to the "developers" section in the .yml file are the same the users use to log in to accounts.jenkins.io.
  • All users added have logged in to Artifactory and Jira once.
  • I have mentioned an existing team member of the plugin or component team to approve this request.

When enabling automated releases (cd: true)

Follow the documentation to ensure, your pull request is set up properly. Don't merge it yet.
In case of changes requested by the hosting team, an open PR facilitates future reviews, without derailing work across multiple PRs.

Link to the PR enabling CD in your plugin

CD checklist (for submitters)

  • I have provided a link to the pull request in my plugin, which enables CD according to the documentation.

Reviewer checklist

  • Check that the $pluginId Developers team has Admin permissions while granting the access.
  • In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
  • If security contacts are changed (this includes add/remove), ping the security officer (currently @Wadeck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it.

@gbhat618 gbhat618 requested a review from a team as a code owner March 25, 2026 07:46
@alecharp alecharp added the authorized unless rejected Authorized by the hosting team, but may be rejected by plugin maintainers later on label Mar 25, 2026
@alecharp
Copy link
Copy Markdown
Contributor

@gbhat618 please login to Jira.

@gbhat618
Copy link
Copy Markdown
Author

@gbhat618 please login to Jira.

ok, did that now. perhaps I need to push an empty-commit to re-trigger the build ?

@gbhat618
Copy link
Copy Markdown
Author

Failing with error

java.lang.IllegalStateException: User name not known to Jira: gbhat618

my github username (@gbhat618) and jenkins username (gbhat) are different; is it possible to make the build work as it is ? or perhaps need to create a new account in jenkins ?

Comment thread permissions/plugin-google-compute-engine.yml Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

authorized unless rejected Authorized by the hosting team, but may be rejected by plugin maintainers later on

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants