在中找不到org.jenkins ci.plugins:plugin:pom:2.11https://repo.maven.apache.org/maven2

我正在尝试编译一个maven项目，它被设计成一个Jenkins插件。当运行“mvnpackage”命令时，我得到下面列出的错误。如何解决这个问题

短暂性脑缺血发作

看到这个, 并去掉了将Maven插件定义为“父级”的部分，将其改为“依赖项”

然后我开始出现错误，比如：“未知包装：hpi@line 12，column 13”

然后我看到了以下情况： 上面写着=>“另外，将详细信息添加到.m2/settings.xml中，如本教程顶部所示，以允许使用短名称“hpi”

更改settings.xml后（根据链接），仍然会出现“未知打包…”错误

然后我返回到包附带的原始pom.xml文件

pom.xml文件如下所示：

这一次，在使用它之后，似乎所有与Jenkins相关的jar文件都被下载了（这需要一些时间）。“hpi”错误已消失，但已替换为新错误

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running InjectedTest
Tests run: 18, Failures: 3, Errors: 12, Skipped: 0, Time elapsed: 60.722 sec <<< FAILURE! - in InjectedTest
edu\utah\med\ped\WaveMakerDeployer\config.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.338 sec  <<< FAILURE!
java.lang.AssertionError: <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/edu/utah/med/ped/WaveMakerDeployer/config.jelly
        at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108)

edu\utah\med\ped\WaveMakerDeployer\global.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.086 sec  <<< FAILURE!
java.lang.AssertionError: <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/edu/utah/med/ped/WaveMakerDeployer/global.jelly
        at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108)

index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.019 sec  <<< FAILURE!
java.lang.AssertionError: <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/index.jelly
        at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:108)

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No tests found matching Method index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) from org.junit.internal.requests.ClassRequest@450f78c9

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No tests found matching Method edu\utah\med\ped\WaveMakerDeployer\config.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) from org.junit.internal.requests.ClassRequest@4877102b

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0.001 sec  <<< ERROR!
java.lang.Exception: No tests found matching Method edu\utah\med\ped\WaveMakerDeployer\global.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck) from org.junit.internal.requests.ClassRequest@c69c38

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0.001 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0.001 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0.001 sec  <<< ERROR!
java.lang.Exception: No runnable methods

initializationError(org.junit.runner.manipulation.Filter)  Time elapsed: 0.001 sec  <<< ERROR!
java.lang.Exception: No runnable methods


Results :

Failed tests:
  JellyTestSuiteBuilder$JellyCheck.runTest:108 <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/edu/utah/med/ped/WaveMakerDeployer/config.jelly
  JellyTestSuiteBuilder$JellyCheck.runTest:108 <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/edu/utah/med/ped/WaveMakerDeployer/global.jelly
  JellyTestSuiteBuilder$JellyCheck.runTest:108 <?jelly escape-by-default='true'?> is missing in file:/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/index.jelly
Tests in error:
org.junit.runner.manipulation.Filter.initializationError(org.junit.runner.manipulation.Filter)
  Run 1: Filter.initializationError ▒  No tests found matching Method index.jelly(org.j...
  Run 2: Filter.initializationError ▒  No tests found matching Method edu\utah\med\ped\...
  Run 3: Filter.initializationError ▒  No tests found matching Method edu\utah\med\ped\...
  Run 4: Filter.initializationError ▒  No runnable methods
  Run 5: Filter.initializationError ▒  No runnable methods
  Run 6: Filter.initializationError ▒  No runnable methods
  Run 7: Filter.initializationError ▒  No runnable methods
  Run 8: Filter.initializationError ▒  No runnable methods
  Run 9: Filter.initializationError ▒  No runnable methods
  Run 10: Filter.initializationError ▒  No runnable methods
  Run 11: Filter.initializationError ▒  No runnable methods
  Run 12: Filter.initializationError ▒  No runnable methods

-------------------------------------------------------
T T S T S
-------------------------------------------------------
运行注入测试
测试运行：18次，失败：3次，错误：12次，跳过：0，运行时间：60.722秒在文件中丢失：/C:/WORK/Development/JENKINS/WaveMakerJenkinsDeployer/target/classes/edu/犹他州/med/ped/WaveMakerDeployer/global.jelly
JellyTestSuiteBuilder$JellyCheck.runTest:108在文件：/C:/WORK/Development/JENKINS/waveMakerjenkins部署器/target/classes/index.jelly中丢失
错误测试：
org.junit.runner.manipulation.Filter.initializationError（org.junit.runner.manipulation.Filter）
运行1:Filter.initializationError▒  没有找到匹配方法index.jelly（org.j。。。
运行2:Filter.initializationError▒  未找到与方法edu\犹他\med\ped\匹配的测试。。。
运行3:Filter.initializationError▒  未找到与方法edu\犹他\med\ped\匹配的测试。。。
运行4:Filter.initializationError▒  没有可运行的方法
运行5:Filter.initializationError▒  没有可运行的方法
运行6:Filter.initializationError▒  没有可运行的方法
运行7:Filter.initializationError▒  没有可运行的方法
运行8:Filter.initializationError▒  没有可运行的方法
运行9:Filter.initializationError▒  没有可运行的方法
运行10:Filter.initializationError▒  没有可运行的方法
运行11:Filter.initializationError▒  没有可运行的方法
运行12:Filter.initializationError▒  没有可运行的方法

问题：从这里可以走到哪里？这些“默认”注入测试有多重要

---

TIA

开发jenkins插件时，您需要配置maven从repo.jenkins-ci.org查找库。下面是一个示例

~/.m2/settings.xml

：

<settings>
  <pluginGroups>
    <pluginGroup>org.jenkins-ci.tools</pluginGroup>
  </pluginGroups>

  <profiles>
    <!-- Give access to Jenkins plugins -->
    <profile>
      <id>jenkins</id>
      <activation>
        <activeByDefault>true</activeByDefault> <!-- change this to false, if you don't like to have it on per default -->
      </activation>
      <repositories>
        <repository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/public/</url>
        </repository>
      </repositories>
      <pluginRepositories>
        <pluginRepository>
          <id>repo.jenkins-ci.org</id>
          <url>https://repo.jenkins-ci.org/public/</url>
        </pluginRepository>
      </pluginRepositories>
    </profile>
  </profiles>
  <mirrors>
    <mirror>
      <id>repo.jenkins-ci.org</id>
      <url>https://repo.jenkins-ci.org/public/</url>
      <mirrorOf>m.g.o-public</mirrorOf>
    </mirror>
  </mirrors>
</settings>

org.jenkins-ci.tools
詹金斯
。请注意，如果您使用的是nexus，您可以在那里找到nexus特定的替代说明。
burnettk的回答，除了我使用的是Gradle，所以对我来说是

repositories {
    maven {
        url('https://repo.jenkins-ci.org/public/')
    }
}

在Maven配置中，
子树可以被安全地省略，我想。
感谢您的响应。我在这里找到了一个旧线程：这与您所做的几乎相同。我相应地更改了settings.xml文件。java源文件似乎已经编译，但现在，似乎运行了默认注入测试（即使最初没有创建JUnit测试过程）。这些默认测试过程有多重要？是否仍可以尝试将此.hpi导入Jenkins？您可以使用插件连接Jenkins实例。您可能会很好地判断更改的可能性。您可以始终启动一个测试Jenkins实例（可能与docker一起），以确保您的插件sn不要点燃它。：）>>你可以用一个插件来点燃jenkins实例。LOL-这就是我所想的“你可以随时点燃一个测试jenkins实例——也许是docker——以确保你的插件不会点燃它”怎么做？什么是“docker”？另外，您是否了解这是什么：=>edu\犹他州\med\ped\WaveMakerDeployer\config.jelly（org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck）经过的时间：0.338秒