Yes, that's why.
Jim Krueger wrote on 11/27/18 9:38 AM:
Bill, No I have not changed to use version 1.0.5
yet. My projects were already in staging before that version
was released. I planned to make that change after all release
activities were done. Perhaps that is why I was hitting those
difficulties?
# Maven plugins
HELP_PLUGIN='org.apache.maven.plugins:maven-help-plugin:3.1.0'
NEXUS_PLUGIN='org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7'
NEXUS_PLUGIN_PARAMS='-DnexusUrl= https://oss.sonatype.org/
-DserverId=ossrh'
and changed the mvn commands in the sample to
this:
for name in $(mvnq -B ${NEXUS_PLUGIN_PARAMS}
${NEXUS_PLUGIN}:rc-list-profiles | \
and
for id in $(mvnq -B ${NEXUS_PLUGIN_PARAMS}
${NEXUS_PLUGIN}:rc-list | \
I've added -X on the maven command "mvn -X
nexus-staging:rc-list-profiles" and I now see the
following error. Any thoughts on how to resolve this?
[ERROR] No plugin found for prefix 'nexus-staging' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/jenkins/.m2/repository), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/)] -> [Help 1]
org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No plugin found for prefix 'nexus-staging' in the current project and in the plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available from the repositories [local (/home/jenkins/.m2/repository), eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/)]
at org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve (DefaultPluginPrefixResolver.java:95)
at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix (MojoDescriptorCreator.java:266)
at org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor (MojoDescriptorCreator.java:220)
at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:104)
at org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments (DefaultLifecycleTaskSegmentCalculator.java:83)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:89)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:954)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:192)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
Did you set up
the job with all the required secret keys and such?
I've gotten to the point where once I have one of
these jobs set up correctly, I create new jobs by
using the "copy existing job" option, and then just
change the shell script within the job to do
something different. There's just so much setup
that's required and that you can't "copy and paste"
that this seems like the best way to do it.
Romain
Grecourt wrote on 11/26/18 02:25 PM:
The logic in the script is
to release all the staging repositories listed for
each profile listed.
Looking at the output you shared I'd say it didn't
list any profile.
That could indicate some issue with the nexus
credentials or with the nexus account itself.
On
11/26/18 1:52 PM, Jim Krueger wrote:
Hi,
These instructions indicate that after
the release review I should run the script
listed at the bottom of that page and that
the script should not be customized per
project.
To be careful I decided to test run the
script commenting out the following line:
# mvnq -DstagingRepositoryId="$id" nexus-staging:rc-release
I was expecting to see an echo of whatever would be release if I'd run the script with
the line uncommented. However, I do not get any listings at all.
Is there something special I need to do?
Here is the output I see:
Started by user James Krueger
Agent default-java-k23ct is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] ():
[EnvInject] - Loading node environment variables.
Building remotely on default-java-k23ct in workspace /home/jenkins/workspace/Nexus-Release
[WS-CLEANUP] Deleting project workspace...
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-jdqfXz0qhu1I/agent.74
SSH_AGENT_PID=76
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/workspace/Nexus-Release@tmp/private_key_3609070332237703964.key (/home/jenkins/workspace/Nexus-Release@tmp/private_key_3609070332237703964.key)
[ssh-agent] Using credentials jakartaee-stable-bot (GitHub Bot SSH)
provisioning config files...
copy managed file [settings-jakartaee-stable.xml] to file:/home/jenkins/.m2/settings.xml
copy managed file [settings-security.xml] to file:/home/jenkins/.m2/settings-security.xml
[Nexus-Release] $ /bin/bash -ex /tmp/jenkins6059823826643264114.sh
+ TOOLS_PREFIX=/opt/tools
+ JAVA_PREFIX=/opt/tools/java/oracle
+ MVN_HOME=/opt/tools/apache-maven/latest
+ JAVA_HOME=/opt/tools/java/oracle/jdk-8/latest
+ PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/oracle/jdk-8/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
++ mvnq nexus-staging:rc-list-profiles
++ grep -v 'Central Bundles'
++ awk '$3 == "BOTH" {print $4}'
++ mvn -B nexus-staging:rc-list-profiles
++ grep -v '^\[INFO\] Download'
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 76 killed;
[ssh-agent] Stopped.
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: SUCCESS
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your
password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-build
|