Repository routing?

View: New views
3 Messages — Rating Filter:   Alert me  

Repository routing?

by Nord, James-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Hi all,

 

I had what I thought was a correctly setup pair of rules to say the artefacts from myco are in myrepo and myrepo only contains myco artifacts.

 

Route                                  Type        Group           Repo

!(.*/com/myco/.*)        exclusive       *                internalReleases, internalShapshots

.*/com/myco/.*             inclusive        *                internalReleases, internalShapshots

 

However these repositories sit on a different server to the nexus proxy server that has the routes and groups.

 

Today the server that hosts the internalReleases and internalShanpshots decided to not respond to requests in a timely fashion.

Because of this any download took a stupidly long length of time to retrieve (many minutes for a kb pom file) even if it was not an artefact in com.myco.xxx

 

e.g.

2009-10-21 11:21:48 DEBUG [oviders-1.2.pom] - o.s.n.p.s.r.RemoteR~:apacheH~ - Invoking HTTP GET method against remote location http://internal-repo.myco.com/content/repositories/releases/org/apache/maven/scm/maven-scm-providers/1.2/maven-scm-providers-1.2.pom

 

This should never happen as internal-repo only hosts com.myco.* so it would appear my exclusive rule doesn’t work and I dreamed up the ability to inverse the match with the use of an exclamation mark.  So how do I do this negative type matching?

 

/James

 


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

Re: Repository routing?

by Tamás Cservenák :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Thy the "exclusive" with:

(?!.*/com/myco/.*).*

instead.


Hope helps,
~t~

On Wed, Oct 21, 2009 at 2:27 PM, Nord, James <JNord@...> wrote:

Hi all,

 

I had what I thought was a correctly setup pair of rules to say the artefacts from myco are in myrepo and myrepo only contains myco artifacts.

 

Route                                  Type        Group           Repo

!(.*/com/myco/.*)        exclusive       *                internalReleases, internalShapshots

.*/com/myco/.*             inclusive        *                internalReleases, internalShapshots

 

However these repositories sit on a different server to the nexus proxy server that has the routes and groups.

 

Today the server that hosts the internalReleases and internalShanpshots decided to not respond to requests in a timely fashion.

Because of this any download took a stupidly long length of time to retrieve (many minutes for a kb pom file) even if it was not an artefact in com.myco.xxx

 

e.g.

2009-10-21 11:21:48 DEBUG [oviders-1.2.pom] - o.s.n.p.s.r.RemoteR~:apacheH~ - Invoking HTTP GET method against remote location http://internal-repo.myco.com/content/repositories/releases/org/apache/maven/scm/maven-scm-providers/1.2/maven-scm-providers-1.2.pom

 

This should never happen as internal-repo only hosts com.myco.* so it would appear my exclusive rule doesn’t work and I dreamed up the ability to inverse the match with the use of an exclamation mark.  So how do I do this negative type matching?

 

/James

 


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************


RE: Repository routing?

by Nord, James-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

Thanks.

 

/James

 

From: t.cservenak@... [mailto:t.cservenak@...] On Behalf Of Tamás Cservenák
Sent: 21 October 2009 13:39
To: nexus-user@...
Subject: Re: [nexus-user] Repository routing?

 

Thy the "exclusive" with:

 

(?!.*/com/myco/.*).*

 

instead.

 

 

Hope helps,

~t~

On Wed, Oct 21, 2009 at 2:27 PM, Nord, James <JNord@...> wrote:

Hi all,

 

I had what I thought was a correctly setup pair of rules to say the artefacts from myco are in myrepo and myrepo only contains myco artifacts.

 

Route                                  Type        Group           Repo

!(.*/com/myco/.*)        exclusive       *                internalReleases, internalShapshots

.*/com/myco/.*             inclusive        *                internalReleases, internalShapshots

 

However these repositories sit on a different server to the nexus proxy server that has the routes and groups.

 

Today the server that hosts the internalReleases and internalShanpshots decided to not respond to requests in a timely fashion.

Because of this any download took a stupidly long length of time to retrieve (many minutes for a kb pom file) even if it was not an artefact in com.myco.xxx

 

e.g.

2009-10-21 11:21:48 DEBUG [oviders-1.2.pom] - o.s.n.p.s.r.RemoteR~:apacheH~ - Invoking HTTP GET method against remote location http://internal-repo.myco.com/content/repositories/releases/org/apache/maven/scm/maven-scm-providers/1.2/maven-scm-providers-1.2.pom

 

This should never happen as internal-repo only hosts com.myco.* so it would appear my exclusive rule doesn’t work and I dreamed up the ability to inverse the match with the use of an exclamation mark.  So how do I do this negative type matching?

 

/James

 


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************

 


**************************************************************************************
This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmaster@... and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00
**************************************************************************************