Can't upload the hpi at end of build because repository is down

157 views

Skip to first unread message

Tal Yanai

unread,

Aug 17, 2016, 2:55:42 PM8/17/16

to Jenkins Developers

http://maven.jenkins-ci.org:8081/content/repositories/releases/ seems to be down. Was the server moved?

I'm getting Connect to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] failed: Connection refused: connect -> [Help 1]

Tried to update the parent POM to 2.6, and got the same problem again.

Thanks,

Daniel Beck

unread,

Aug 17, 2016, 3:15:19 PM8/17/16

to jenkin...@googlegroups.com

maven.j.o has been shut down, as it has only been a redirect to repo.j.o for years.

Do you explicitly specify maven.j.o in your POM or your settings.xml? Is uploading or downloading impacted?

> --
> 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/d4579b05-d450-4975-8036-2e4d76903c8a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Tal Yanai

unread,

Aug 17, 2016, 3:27:38 PM8/17/16

to Jenkins Developers, m...@beckweb.net

It's impacting my upload.

I used to specify it directly in distributionManagement. I now removed it, and updated to parent 2.6. I only use the global settings.xml and don;t have this url there. All I have there is:

<id>maven.jenkins-ci.org</id>

<privateKey>C:\Users\tyanai\.ssh\id_rsa</privateKey>

</server>

Is there a different url I should change for? A different id?

Daniel Beck

unread,

Aug 17, 2016, 3:51:08 PM8/17/16

to Tal Yanai, Jenkins Developers

> On 17.08.2016, at 21:27, Tal Yanai <t...@yanai.org.il> wrote:
>
> It's impacting my upload.
>
> I used to specify it directly in distributionManagement. I now removed it, and updated to parent 2.6. I only use the global settings.xml and don;t have this url there. All I have there is:
>
> <server>
> <id>maven.jenkins-ci.org</id>
> <privateKey>C:\Users\tyanai\.ssh\id_rsa</privateKey>
> <passphrase></passphrase>
> </server>
>
> Is there a different url I should change for? A different id?
>

The ID is fine, and the 2.6 plugins plugin should work:

https://github.com/jenkinsci/plugin-pom/blob/plugin-2.6/pom.xml#L750

What's the exact error message you're seeing?

Tal Yanai

unread,

Aug 17, 2016, 3:55:21 PM8/17/16

to Jenkins Developers, t...@yanai.org.il, m...@beckweb.net

I did release prepare & perform before changing any of this, where I had an explicit overwrite to maven.j.o. Now, seems that even after the change, whenever I'm doing release prepare, it still trying to access maven.j.o for uploading:

[INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ vmanager-plugin ---

Uploading: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/vmanager-plugin/2.1/vmanager-plugin-2.1.hpi

Uploading: http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/vmanager-plugin/2.1/vmanager-plugin-2.1.pom

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 01:17 min

[INFO] Finished at: 2016-08-17T22:48:42+03:00

[INFO] Final Memory: 46M/499M

[INFO] ------------------------------------------------------------------------

[WARNING] The requested profile "jenkins-release" could not be activated because it does not exist.

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project vmanager-plugin: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:vmanager-plugin:hpi:2.1 from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8081/content/repositories/releases/): Connect to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] failed: Connection refused: connect -> [Help 1]

[ERROR]

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR]

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Daniel Beck

unread,

Aug 17, 2016, 6:08:45 PM8/17/16

to jenkin...@googlegroups.com, t...@yanai.org.il

What's the output of the following?

mvn help:effective-pom

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/363c42a2-9844-40da-aab0-ced05b67f206%40googlegroups.com.

Tal Yanai

unread,

Aug 18, 2016, 2:12:56 AM8/18/16

to Jenkins Developers, t...@yanai.org.il, m...@beckweb.net

Effective POMs, after inheritance, interpolation, and profiles are applied:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/mav

<groupId>org.jenkins-ci.plugins</groupId>

<artifactId>plugin</artifactId>

</parent>

<groupId>org.jenkins-ci.plugins</groupId>

<artifactId>vmanager-plugin</artifactId>

<version>2.2-SNAPSHOT</version>

<name>Cadence vManager Plugin for Jenkins</name>

<description>Integrates Jenkins to Cadence vManager</description>

<url>http://wiki.jenkins-ci.org/display/JENKINS/Cadence+vManager+Plugin</url>

<name>Cadence</name>

<url>www.cadence.com</url>

</organization>

<name>MIT License</name>

<url>http://opensource.org/licenses/MIT</url>

</license>

</licenses>

<id>tyanai</id>

<name>Tal Yanai</name>

<email>tya...@cadence.com</email>

</developer>

</developers>

<scm>

<connection>scm:git:git://github.com/jenkinsci/vmanager-plugin.git</connection>

<developerConnection>scm:git:g...@github.com:jenkinsci/vmanager-plugin.git</developerConnection>

<url>http://github.com/jenkinsci/vmanager-plugin</url>

</scm>

<id>maven.jenkins-ci.org</id>

<url>https://repo.jenkins-ci.org/releases/</url>

</repository>

<id>maven.jenkins-ci.org</id>

<url>https://repo.jenkins-ci.org/snapshots/</url>

</snapshotRepository>

</distributionManagement>

<findbugs.failOnError>true</findbugs.failOnError>

<hpi-plugin.version>1.117</hpi-plugin.version>

<java.level>7</java.level>

<java.level.test>7</java.level.test>

<jenkins-test-harness.version>2.6</jenkins-test-harness.version>

<jenkins.version>1.625.3</jenkins.version>

<maven.test.redirectTestOutputToFile>true</maven.test.redirectTestOutputToFile>

<node.download.classifier>/x64</node.download.classifier>

<node.download.file>win-x64/node.exe</node.download.file>

<node.version>4.0.0</node.version>

<npm.loglevel />

<npm.version>2.13.1</npm.version>

<project.build.outputEncoding>UTF-8</project.build.outputEncoding>

<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>

<release.skipTests>true</release.skipTests>

<skip.node.lint />

<skip.node.tests />

<stapler-plugin.version>1.17</stapler-plugin.version>

<surefire.rerunFailingTestsCount>4</surefire.rerunFailingTestsCount>

</properties>

<groupId>com.google.code.findbugs</groupId>

<artifactId>annotations</artifactId>

</dependency>

<artifactId>jcip-annotations</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-core</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-war</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-war</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-test-harness</artifactId>

</dependency>

<groupId>org.jenkins-ci</groupId>

<artifactId>test-annotations</artifactId>

</dependency>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

<groupId>javax.servlet</groupId>

<artifactId>javax.servlet-api</artifactId>

</dependency>

<groupId>javax.servlet</groupId>

<artifactId>servlet-api</artifactId>

</dependency>

<groupId>org.codehaus.mojo</groupId>

<artifactId>animal-sniffer-annotations</artifactId>

</dependency>

<groupId>org.codehaus.mojo.signature</groupId>

<type>signature</type>

</dependency>

<groupId>org.codehaus.mojo.signature</groupId>

<type>signature</type>

</dependency>

<groupId>org.codehaus.mojo.signature</groupId>

<type>signature</type>

</dependency>

<groupId>commons-logging</groupId>

<artifactId>commons-logging</artifactId>

<scope>provided</scope>

</dependency>

<scope>provided</scope>

</dependency>

</dependencies>

</dependencyManagement>

<groupId>org.jenkins-ci.plugins</groupId>

<artifactId>dashboard-view</artifactId>

<scope>compile</scope>

</dependency>

<groupId>com.google.code.findbugs</groupId>

<artifactId>annotations</artifactId>

<scope>provided</scope>

</dependency>

<artifactId>jcip-annotations</artifactId>

<scope>provided</scope>

</dependency>

<groupId>org.codehaus.mojo</groupId>

<artifactId>animal-sniffer-annotations</artifactId>

<scope>provided</scope>

</dependency>

<groupId>javax.servlet</groupId>

<artifactId>javax.servlet-api</artifactId>

</dependency>

<groupId>javax.servlet</groupId>

<artifactId>servlet-api</artifactId>

<scope>provided</scope>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-core</artifactId>

<scope>provided</scope>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-war</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-war</artifactId>

</dependency>

<groupId>org.jenkins-ci.main</groupId>

<artifactId>jenkins-test-harness</artifactId>

<artifactId>junit-dep</artifactId>

<groupId>junit</groupId>

</exclusion>

</exclusions>

</dependency>

<groupId>org.jenkins-ci</groupId>

<artifactId>test-annotations</artifactId>

</dependency>

<groupId>junit</groupId>

<artifactId>junit</artifactId>

</dependency>

<scope>compile</scope>

</dependency>

</dependency>

</dependency>

</dependency>

</dependencies>

<id>repo.jenkins-ci.org</id>

<url>http://repo.jenkins-ci.org/public/</url>

</repository>

<enabled>false</enabled>

</snapshots>

<id>central</id>

<name>Central Repository</name>

<url>http://repo.maven.apache.org/maven2</url>

</repository>

</repositories>

<id>repo.jenkins-ci.org</id>

<url>http://repo.jenkins-ci.org/public/</url>

</pluginRepository>

<updatePolicy>never</updatePolicy>

</releases>

<enabled>false</enabled>

</snapshots>

<id>central</id>

<name>Central Repository</name>

<url>http://repo.maven.apache.org/maven2</url>

</pluginRepository>

</pluginRepositories>

<build>

<sourceDirectory>d:\work\dev\vmanager-plugin\src\main\java</sourceDirectory>

<scriptSourceDirectory>d:\work\dev\vmanager-plugin\src\main\scripts</scriptSourceDirectory>

<testSourceDirectory>d:\work\dev\vmanager-plugin\src\test\java</testSourceDirectory>

<outputDirectory>d:\work\dev\vmanager-plugin\target\classes</outputDirectory>

<testOutputDirectory>d:\work\dev\vmanager-plugin\target\test-classes</testOutputDirectory>

<directory>d:\work\dev\vmanager-plugin\src\main\resources</directory>

</resource>

</resources>

<directory>d:\work\dev\vmanager-plugin\src\test\resources</directory>

</testResource>

</testResources>

<directory>d:\work\dev\vmanager-plugin\target</directory>

<finalName>vmanager-plugin</finalName>

<artifactId>maven-antrun-plugin</artifactId>

</plugin>

<artifactId>maven-assembly-plugin</artifactId>

</plugin>

<artifactId>maven-clean-plugin</artifactId>

</plugin>

<artifactId>maven-compiler-plugin</artifactId>

</plugin>

<artifactId>maven-dependency-plugin</artifactId>

</plugin>

<artifactId>maven-jar-plugin</artifactId>

</plugin>

<artifactId>maven-resources-plugin</artifactId>

</plugin>

<artifactId>maven-surefire-plugin</artifactId>

</plugin>

<artifactId>maven-failsafe-plugin</artifactId>

</plugin>

<artifactId>maven-deploy-plugin</artifactId>

</plugin>

<artifactId>maven-enforcer-plugin</artifactId>

</plugin>

<artifactId>maven-install-plugin</artifactId>

</plugin>

<artifactId>maven-javadoc-plugin</artifactId>

</plugin>

<artifactId>maven-release-plugin</artifactId>

</plugin>

<artifactId>maven-site-plugin</artifactId>

</plugin>

<artifactId>maven-source-plugin</artifactId>

</plugin>

<artifactId>maven-war-plugin</artifactId>

</plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>findbugs-maven-plugin</artifactId>

</plugin>

<artifactId>maven-eclipse-plugin</artifactId>

<buildOutputDirectory>target/eclipse-classes</buildOutputDirectory>

<projectnature>org.eclipse.jdt.groovy.core.groovyNature</projectnature>

</additionalProjectnatures>

</configuration>

</plugin>

<groupId>org.codehaus.gmaven</groupId>

<artifactId>gmaven-plugin</artifactId>

<version>1.5-jenkins-3</version>

</plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>build-helper-maven-plugin</artifactId>

<id>add-source</id>

<phase>generate-sources</phase>

<goals>

<goal>add-source</goal>

</goals>

<source>d:\work\dev\vmanager-plugin\target/generated-sources/localizer</source>

</sources>

</configuration>

</execution>

</executions>

</plugin>

<groupId>org.jacoco</groupId>

<artifactId>jacoco-maven-plugin</artifactId>

</plugin>

<groupId>org.kohsuke.gmaven</groupId>

<artifactId>gmaven-plugin</artifactId>

<version>1.0-rc-5-patch-2</version>

</plugin>

<groupId>org.kohsuke.stapler</groupId>

<artifactId>maven-stapler-plugin</artifactId>

</plugin>

<groupId>org.jenkins-ci.tools</groupId>

<artifactId>maven-hpi-plugin</artifactId>

</plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>animal-sniffer-maven-plugin</artifactId>

</plugin>

<groupId>org.jvnet.localizer</groupId>

<artifactId>maven-localizer-plugin</artifactId>

</plugin>

<groupId>org.kohsuke</groupId>

<artifactId>access-modifier-checker</artifactId>

</plugin>

<groupId>com.cloudbees</groupId>

<artifactId>maven-license-plugin</artifactId>

</plugin>

<groupId>org.eclipse.m2e</groupId>

<artifactId>lifecycle-mapping</artifactId>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-enforcer-plugin</artifactId>

<goals>

<goal>display-info</goal>

</goals>

</pluginExecutionFilter>

</action>

</pluginExecution>

<groupId>org.codehaus.gmaven</groupId>

<artifactId>gmaven-plugin</artifactId>

<goals>

<goal>testCompile</goal>

<goal>generateTestStubs</goal>

</goals>

</pluginExecutionFilter>

</action>

</pluginExecution>

</pluginExecutions>

</lifecycleMappingMetadata>

</configuration>

</plugin>

</plugins>

</pluginManagement>

<artifactId>maven-enforcer-plugin</artifactId>

<id>display-info</id>

<phase>validate</phase>

<goals>

<goal>display-info</goal>

<goal>enforce</goal>

</goals>

<rules>

<message>Maven 3.0 through 3.0.3 inclusive do not pass correct settings.xml to Maven Release Plugin.</message>

</requireMavenVersion>

</ignoredScopes>

<exclude>org.jenkins-ci.main:jenkins-core</exclude>

<exclude>org.jenkins-ci.main:cli</exclude>

<exclude>org.jenkins-ci.main:jenkins-test-harness</exclude>

<exclude>com.google.code.findbugs:annotations</exclude>

</excludes>

</enforceBytecodeVersion>

<exclude>org.sonatype.sisu:sisu-guice</exclude>

<exclude>log4j:log4j:*:jar:compile</exclude>

<exclude>log4j:log4j:*:jar:runtime</exclude>

<exclude>commons-logging:commons-logging:*:jar:compile</exclude>

<exclude>commons-logging:commons-logging:*:jar:runtime</exclude>

</excludes>

</bannedDependencies>

</rules>

</configuration>

</execution>

</executions>

<groupId>org.codehaus.mojo</groupId>

<artifactId>extra-enforcer-rules</artifactId>

<scope>compile</scope>

</dependency>

</dependencies>

</plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>findbugs-maven-plugin</artifactId>

<id>findbugs</id>

<phase>verify</phase>

<goals>

<goal>check</goal>

</goals>

<findbugsXmlOutput>false</findbugsXmlOutput>

</configuration>

</execution>

</configuration>

</execution>

</executions>

</configuration>

</plugin>

<artifactId>maven-compiler-plugin</artifactId>

<id>default-testCompile</id>

<phase>test-compile</phase>

<goals>

<goal>testCompile</goal>

</goals>

</configuration>

</execution>

<id>default-compile</id>

<phase>compile</phase>

<goals>

<goal>compile</goal>

</goals>

</configuration>

</execution>

</executions>

</configuration>

</plugin>

<groupId>org.codehaus.mojo</groupId>

<artifactId>animal-sniffer-maven-plugin</artifactId>

<id>check</id>

<goals>

<goal>check</goal>

</goals>

<groupId>org.codehaus.mojo.signature</groupId>

</signature>

</configuration>

</execution>

</executions>

<groupId>org.codehaus.mojo.signature</groupId>

</signature>

</configuration>

</plugin>

<artifactId>maven-eclipse-plugin</artifactId>

<buildOutputDirectory>target/eclipse-classes</buildOutputDirectory>

<projectnature>org.eclipse.jdt.groovy.core.groovyNature</projectnature>

</additionalProjectnatures>

</configuration>

</plugin>

<groupId>org.jenkins-ci.tools</groupId>

<artifactId>maven-hpi-plugin</artifactId>

<id>default-test-hpl</id>

<phase>test-compile</phase>

<goals>

</goals>

<contextPath>/jenkins</contextPath>

</configuration>

</execution>

<id>default-resolve-test-dependencies</id>

<phase>test-compile</phase>

<goals>

<goal>resolve-test-dependencies</goal>

</goals>

<contextPath>/jenkins</contextPath>

</configuration>

</execution>

<id>default-hpi</id>

<phase>package</phase>

<goals>

</goals>

<contextPath>/jenkins</contextPath>

</configuration>

</execution>

<id>default-insert-test</id>

<phase>generate-test-sources</phase>

<goals>

<goal>insert-test</goal>

</goals>

<contextPath>/jenkins</contextPath>

</configuration>

</execution>

<id>default-validate</id>

<phase>validate</phase>

<goals>

<goal>validate</goal>

</goals>

<contextPath>/jenkins</contextPath>

</configuration>

</execution>

</executions>

<contextPath>/jenkins</contextPath>

</configuration>

</plugin>

<groupId>org.kohsuke.stapler</groupId>

<artifactId>maven-stapler-plugin</artifactId>

</plugin>

<artifactId>maven-release-plugin</artifactId>

<mavenExecutorId>forked-path</mavenExecutorId>

<useReleaseProfile>false</useReleaseProfile>

<preparationGoals>clean install</preparationGoals>

<goals>deploy</goals>

<releaseProfiles>jenkins-release,</releaseProfiles>

</configuration>

</plugin>

<groupId>org.jvnet.localizer</groupId>

<artifactId>maven-localizer-plugin</artifactId>

<goals>

<goal>generate</goal>

</goals>

<fileMask>Messages.properties</fileMask>

<outputDirectory>target/generated-sources/localizer</outputDirectory>

</configuration>

</execution>

</executions>

</plugin>

<artifactId>maven-javadoc-plugin</artifactId>

<phase>process-sources</phase>

<goals>

<goal>javadoc</goal>

</goals>

</execution>

</executions>

</plugin>

<groupId>org.kohsuke</groupId>

<artifactId>access-modifier-checker</artifactId>

<id>default-enforce</id>

<phase>process-classes</phase>

<goals>

<goal>enforce</goal>

</goals>

</execution>

</executions>

</plugin>

<groupId>org.codehaus.gmaven</groupId>

<artifactId>gmaven-plugin</artifactId>

<version>1.5-jenkins-3</version>

<id>test-in-groovy</id>

<goals>

<goal>generateTestStubs</goal>

<goal>testCompile</goal>

</goals>

</execution>

</executions>

<scope>compile</scope>

</dependency>

</dependencies>

</plugin>

<artifactId>maven-surefire-plugin</artifactId>

<id>default-test</id>

<goals>

</goals>

<name>hudson.udp</name>

</property>

</systemProperties>

</configuration>

</execution>

</executions>

<name>hudson.udp</name>

</property>

</systemProperties>

</configuration>

</plugin>

<groupId>com.cloudbees</groupId>

<artifactId>maven-license-plugin</artifactId>

<phase>prepare-package</phase>

<goals>

<goal>process</goal>

</goals>

<generateLicenseXml>target/vmanager-plugin/WEB-INF/licenses.xml</generateLicenseXml>

<inlineScript>filter {

def plugins = [] as Set

// collect all Jenkins plugins

models.entrySet().each { e ->

if (e.value.packaging=="hpi")

plugins.add(e.key.id)

}

// filter out dependencies that don't belong to this plugin

models.entrySet().removeAll(models.entrySet().findAll { e ->

def a = e.key;

if (a.dependencyTrail.size()>0 && plugins.contains(a.dependencyTrail[1]))

return true; // ignore transitive dependencies through other plugins

// if the dependency goes through jenkins core, we don't need to bundle it in the war

// because jenkins-core comes in the <provided> scope, I think this is a bug in Maven that it puts such

// dependencies into the artifact list.

if (a.dependencyTrail.find { trail -> trail.contains(":hudson-core:") || trail.contains(":jenkins-core:") })

return true;

return false;

})

}</inlineScript>

</configuration>

</execution>

</executions>

</plugin>

<artifactId>maven-clean-plugin</artifactId>

<id>default-clean</id>

<phase>clean</phase>

<goals>

<goal>clean</goal>

</goals>

</execution>

</executions>

</plugin>

<artifactId>maven-install-plugin</artifactId>

<id>default-install</id>

<phase>install</phase>

<goals>

<goal>install</goal>

</goals>

</execution>

</executions>

</plugin>

<artifactId>maven-resources-plugin</artifactId>

<id>default-resources</id>

<phase>process-resources</phase>

<goals>

<goal>resources</goal>

</goals>

</execution>

<id>default-testResources</id>

<phase>process-test-resources</phase>

<goals>

<goal>testResources</goal>

</goals>

</execution>

</executions>

</plugin>

<artifactId>maven-deploy-plugin</artifactId>

<id>default-deploy</id>

<phase>deploy</phase>

<goals>

<goal>deploy</goal>

</goals>

</execution>

</executions>

</plugin>

<artifactId>maven-site-plugin</artifactId>

<id>default-site</id>

<goals>

</goals>

<outputDirectory>d:\work\dev\vmanager-plugin\target\site</outputDirectory>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-project-info-reports-plugin</artifactId>

</reportPlugin>

</reportPlugins>

</configuration>

</execution>

<id>default-deploy</id>

<phase>site-deploy</phase>

<goals>

<goal>deploy</goal>

</goals>

<outputDirectory>d:\work\dev\vmanager-plugin\target\site</outputDirectory>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-project-info-reports-plugin</artifactId>

</reportPlugin>

</reportPlugins>

</configuration>

</execution>

</executions>

<outputDirectory>d:\work\dev\vmanager-plugin\target\site</outputDirectory>

<groupId>org.apache.maven.plugins</groupId>

<artifactId>maven-project-info-reports-plugin</artifactId>

</reportPlugin>

</reportPlugins>

</configuration>

</plugin>

</plugins>

</build>

<outputDirectory>d:\work\dev\vmanager-plugin\target\site</outputDirectory>

</reporting>

</project>

[INFO] ------------------------------------------------------------------------

[INFO] BUILD SUCCESS

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 58.518 s

[INFO] Finished at: 2016-08-18T09:10:38+03:00

[INFO] Final Memory: 19M/120M

[INFO] ------------------------------------------------------------------------

tyanai@PC-TYANAI-X230 /d/work/dev/vmanager-plugin (master)

Michelle Taylor

unread,

Oct 20, 2016, 12:32:39 PM10/20/16

to Jenkins Developers

I am having exactly the same problem as this, and this thread is the only hit which includes the full 'The requested profile "jenkins-release" could not be activated because it does not exist' warning which seems to be the main difference between my output and the output of another member of my team who is succeeding at release.

Was there any resolution to this?

Jesse Glick

unread,

Oct 20, 2016, 12:53:22 PM10/20/16

to Jenkins Dev

Effective POM looks OK offhand. Run with `-X` and track down where the
bogus URL is coming from.

Reply all

Reply to author

Forward

0 new messages