Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The error is clear: the user <code>tangens</code> doesn't have the permission to create <code>/nexus</code> on the remote machine. Actually, your <code>scp</code> url is not correct and isn't pointing to the right location as you mentioned it. You'd have to give the user <code>tangens</code> the right permission or to configure sshd to allow root to connect but this is not a good idea.</p> <p>Having that said, I don't think that <code>scp</code> is the way to go with Nexus. If you deploy using <code>scp</code>, Nexus won't be notified of the deployment and your artifacts won't be visible. According to <a href="http://svn.sonatype.org/m2eclipse/trunk/org.maven.ide.eclipse.book/book/ch14s06.html" rel="nofollow noreferrer">Deploying Artifacts to Nexus</a> and to the chapter <a href="http://www.sonatype.com/books/nexus-book/reference/staging-sect-deployment.html#staging-sect-update-pom" rel="nofollow noreferrer">9.4.2. Update the POM: Deployment Configuration</a> of the Nexus book, deployment must be done with HTTP PUT. In other words, your <code>distributionManagement</code> section should look like something like this:</p> <pre><code> &lt;distributionManagement&gt; ... &lt;repository&gt; &lt;id&gt;releases&lt;/id&gt; &lt;name&gt;Internal Releases&lt;/name&gt; &lt;url&gt;http://localhost:8081/nexus/content/repositories/releases&lt;/url&gt; &lt;/repository&gt; ... &lt;/distributionManagement&gt; </code></pre> <p>I noticed you said that SecureCI uses a firewall that is configured to drop connections on port 80. However, as I'm not using SecureCI myself, I have a few (maybe stupid) questions:</p> <ul> <li>Did you enabled deployment for a hosted repository under Nexus?</li> <li>Is Nexus listening on port 80?</li> <li>If a firewall is not allowing HTTP, why don't you just add an exception for HTTP connections from the "host" IP?</li> </ul> <p><strong>EDIT:</strong> According to the OP answers, I think that using HTTPS might be indeed the "natural" way to go with SecureCI. But, before you can upload via HTTPS, you'll need to add the SecureCI's CA certificate (the certificate of the issuer of their certificate) into your JDK. You can follow <a href="http://docs.codehaus.org/display/HAUSMATES/WebDAV#WebDAV-InstallingtheUserTrustCAintotheJavaJDK" rel="nofollow noreferrer">these instructions</a> to do this. But before going further, the real question is: </p> <ul> <li>Does SecureCI provide the CA certificate (the certificate of the issuer of their certificate)?</li> </ul> <p>If they don't, I don't know how to make deployment possible without tweaking the firewall rules.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload