Request permissions to release configurationslicing

[guysoft]

Hey,

Description

I Have recently adopted the plugin, I have a new version ready to release but I am getting:

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project configurationslicing: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:configurationslicing:hpi:1.50 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Transfer failed for https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/configurationslicing/1.50/configurationslicing-1.50.hpi 401 Unauthorized -> [Help 1]

Submitter checklist for changing permissions

Always

• Add link to plugin/component Git repository in description above
  https://plugins.jenkins.io/configurationslicing/

For a newly hosted plugin only

• Add link to resolved HOSTING issue in description above

For a new permissions file only

• Make sure the file is created in permissions/ directory
• artifactId (pom.xml) is used for name (permissions YAML file).
• groupId / artifactId (pom.xml) are correctly represented in path (permissions YAML file)
• Check that the file is named plugin-${artifactId}.yml for plugins

When adding new uploaders (this includes newly created permissions files)

@guysoft

• Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
• Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
  (Account from https://accounts.jenkins.io/)
• Make sure to @mention the users being added so their GitHub account names are known if they require GitHub merge access (see below).
• All newly added users have logged in to Artifactory at least once

Reviewer checklist (not for requesters!)

• Check this if newly added person also needs to be given merge permission to the GitHub repo (please @ the people/person with their GitHub username in this issue as well). If needed, it can be done using an IRC Bot command
• 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 @daniel-beck) in this pull request. If an email contact is changed, wait for approval from the security officer.

There are IRC Bot commands for it

[halkeye]

[2020-05-23T13:53:05.930Z] Exception in thread "main" java.lang.IllegalStateException: User name not known to Artifactory: guysoft

Have you logged into artifactory yet?

[guysoft]

Yes, Just making sure this means I am in right?

Also I can see my username here: https://reports.jenkins.io/artifactory-ldap-users-report.json

[halkeye]

Yep, it syncs the list of people logged in every 15 minutes (believe), so it probably hadn't syned yet by the time the CI ran.

I don't have permissions to re-run it, if you have the ability to close, wait a few seconds and reopen this, it should re-run.

Otherwise wait for those with access

[guysoft]

Closing, see #1539

[halkeye]

oh okay, close and reopen just meant click the button twice type thing, but that totally works :)

[guysoft]

Ah, ok, I thought you need a whole new PR.
Done, should build and work since the other PR did.

[guysoft]

@halkeye Hey, its passing - is there anything else you need?

[halkeye]

Oh I just randomly help with reviews. I don't have approval access.

[halkeye]

I'll nudge though