plugin-compat-tester is multimodule and CD publishing is not working

[jtnord]

only the cli has been published to releases recently. I have no access to the workflow for CD (github is having issues) but I am assuming as there are multiple files that antifactory has multiple different secrets, yet only one is available for use by them github action, causing all modules to fail.

was not the cause of the issue - however it may be required to fix the issue (not sure wrt publishing multi module repos in CD)

compare
https://repo.jenkins-ci.org/artifactory/releases/org/jenkins-ci/tests/plugins-compat-tester-cli/

and
https://repo.jenkins-ci.org/artifactory/releases/org/jenkins-ci/tests/plugins-compat-tester-model/

@jglick @raul-arabaolaza

Description

Submitter checklist for adding or changing permissions

Always

• Add link to plugin/component Git repository in description above

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)

• 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
• 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 @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

[jtnord]

may or may not be required for jenkinsci/plugin-compat-tester#381 (I am not fully clear on how multi-modul repos are supposed to work with cd here)

[jglick]

I am not fully clear on how multi-module repos are supposed to work with cd

I do not think anyone is. For historical reasons, the current logic does not handle multimodule repos well. The file structure needs to be reorganized (IMO) to be by repo rather than artifact. I have a full analysis of the code paths that just work by accident in some comment in some PR in this repo which I could search for if someone is interested. CC @daniel-beck