Permissions for publishing parent-pom of build-monitor plugin

[rsomas...@netflix.com]

Hi!

The build-monitor plugin used to publish the HPI file to repo.jenkins-ci.org with group: org.jenkinsci-plugins and artifactId: build-monitor-plugin.

The pom it published referenced a parent-pom with group: org.jenkinsci-plugins and artifactId: build-monitor.

The parent-pom was never published. This caused problems for anyone resolving the artifact using maven or gradle.

I submitted a fix to the repo - https://github.com/jan-molak/jenkins-build-monitor-plugin/pull/522

We're now getting a 403 trying to publish the parent-pom.

What would be the correct way to resolve it? 1. Should the parent have a different coordinate? 2. Can the credential used by that plugin be given permission to publish the parent-pom?

Thanks!

Rahul

[Gavin Mogan]

All artifactory permissions are managed via https://github.com/jenkins-infra/repository-permissions-updater

if your publishing a new repo, you'll probably want a new file, or at least paths added to your existing yml file

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ed17ec65-7e70-4e17-916e-479bb7b45befn%40googlegroups.com.

[rsomas...@netflix.com]

Thanks!
I've created a PR - https://github.com/jenkins-infra/repository-permissions-updater/pull/2221