Hello,
I'm trying to publish my new plugin, but I get a 
"jenkinsci/plugin-pom.git/<pluginid> 
is not a valid repository name" error. I do not understand why it is trying 
to publish under plugin-pom.git. Nowhere in my sources I refer to a 
plugin-pom repo!

Here is the exact error message:

[INFO] 
    [INFO] --- maven-install-plugin:3.0.0-M1:install (default-install) @ 
castecho ---
    [INFO] Installing 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin\target\castecho.hpi 
to 
C:\Users\TPO\.m2\repository\io\jenkins\plugins\castecho\1.0.0\castecho-1.0.0.hpi
    [INFO] Installing 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin\pom.xml to 
C:\Users\TPO\.m2\repository\io\jenkins\plugins\castecho\1.0.0\castecho-1.0.0.pom
    [INFO] Installing 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin\target\castecho.jar 
to 
C:\Users\TPO\.m2\repository\io\jenkins\plugins\castecho\1.0.0\castecho-1.0.0.jar
    [INFO] 
------------------------------------------------------------------------
    [INFO] BUILD SUCCESS
    [INFO] 
------------------------------------------------------------------------
    [INFO] Total time: 01:17 min
    [INFO] Finished at: 2019-06-11T11:28:11+02:00
    [INFO] Final Memory: 85M/1650M
    [INFO] 
------------------------------------------------------------------------
Checking in modified POMs...
Executing: cmd.exe /X /C "git add -- pom.xml"
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
Executing: cmd.exe /X /C "git status --porcelain ."
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
Ignoring unrecognized line: ?? .gitignore
Ignoring unrecognized line: ?? pom.xml.releaseBackup
Ignoring unrecognized line: ?? release.properties
Executing: cmd.exe /X /C "git commit --verbose -F 
C:\Users\TPO\AppData\Local\Temp\maven-scm-1728998852.commit pom.xml"
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
Executing: cmd.exe /X /C "git symbolic-ref HEAD"
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
*Executing: cmd.exe /X /C "git push 
ssh:********@github.com/jenkinsci/plugin-pom.git/castecho 
refs/heads/master:refs/heads/master"*
Working directory: 
C:\Sources\Jenkins_plugins\Jenkins-plugins\castecho-plugin
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 01:35 min
Finished at: 2019-06-11T11:28:14+02:00
Final Memory: 23M/289M
------------------------------------------------------------------------Failed 
to execute goal org.apache.maven.plugins: maven-release-plugin: 2.5.3: 
prepare (default-cli) on project castecho: Unable to commit files
Provider message:
The git-push command failed.
Command output:
warning: CRLF will be replaced by LF in pom.xml.
The file will have its original line in your working directory.
*fatal: remote error:*
*  jenkinsci / plugin-pom.git / castecho is not a valid repository name*


-> [Help 1]

To see the full stack of errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.


However I followed what was asked here: 
https://jenkins.io/doc/developer/publishing/releasing/
And my git repo is ready for tag at this location: 
https://github.com/jenkinsci/castecho-plugin

Any help would be welcome to get me out of this mess. :-)

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0b3fbd42-e577-4b95-9b3a-7c77f98dbdde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: release.properties
Description: Binary data

Attachment: pom.xml
Description: XML document

Reply via email to