Enable CD permission for plugin-jetbrains-space

[Kiryushin-Andrey]

Link to GitHub repository

https://github.com/JetBrains/space-jenkins-plugin

When modifying release permission

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

• @username1
• @username2

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)

Edit tasklist title

Beta Give feedback Tasklist Release permission checklist (for submitters), more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. 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](https://accounts.jenkins.io/).

   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.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. All users added have logged in to [Artifactory](https://repo.jenkins-ci.org/) and [Jira](https://issues.jenkins.io/) once.

   All users added have logged in to Artifactory and Jira once.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. I have mentioned an [existing team member](https://github.com/orgs/jenkinsci/teams) of the plugin or component team to approve this request.

   I have mentioned an existing team member of the plugin or component team to approve this request.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to Release permission checklist (for submitters)

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

jenkinsci/jetbrains-space-plugin#7

CD checklist (for submitters)

Edit tasklist title

Beta Give feedback Tasklist CD checklist (for submitters), more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

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

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

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to CD checklist (for submitters)

Reviewer checklist

Edit tasklist title

Beta Give feedback Tasklist Reviewer checklist, more options

• Rename
• Copy markdown
• Delete tasklist

Delete tasklist

Delete tasklist block?

Are you sure? All relationships in this tasklist will be removed.

Cancel Delete

1. Check that the `$pluginId Developers` team has `Admin` permissions while granting the access.

   Check that the $pluginId Developers team has Admin permissions while granting the access.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
2. In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.

   In the case of plugin adoption, ensure that the Jenkins Jira default assignee is either removed or changed to the new maintainer.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove
3. 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.

   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.
   Options

   • Convert to issue
   • Toggle completion
   • Rename
   • Remove

Add item to Reviewer checklist

There are IRC Bot commands for it.

[NotMyFault]

Looks good so far, but be aware that cd will not work if your build doesn't pass all checks on ci.Jenkins.io

[Kiryushin-Andrey]

Looks good so far, but be aware that cd will not work if your build doesn't pass all checks on ci.Jenkins.io

Ok, then I have a question about those checks :) They fail to fetch org.jetbrains:space-sdk-jvm dependency - Could not find artifact org.jetbrains:space-sdk-jvm:jar:2024.2-178074 in aws-proxy (https://repo.aws.jenkins.io/public/). But this dependency comes from https://maven.pkg.jetbrains.space/public/p/space/maven that is mentioned in the pom.xml file. Seems that the build on ci.jenkins.io for some reason ignores the repository referenced in the pom.xml and tried to fetch the dependency from this aws-proxy repo. So how can I either get the build to fetch the dependency from the right repo, or get this dependency published into the https://repo.aws.jenkins.io/public ?

I guess adding useArtifactCachingProxy: false to Jenkinsfile will help, but maybe I can use proxying for all the dependencies except this one?

[NotMyFault]

I guess adding useArtifactCachingProxy: false to Jenkinsfile will help, but maybe I can use proxying for all the dependencies except this one?

I've exempted it in jenkins-infra/jenkins-infra#3314

[NotMyFault]

For documentation purposes: jenkins-infra/helpdesk#3973