« Return to Thread: file URLs a good idea for deployment?

file URLs a good idea for deployment?

by Doug Douglass-2 :: Rate this Message:

Reply to Author | View in Thread

We're transitioning from proximity (yes, very old!) to nexus. We've been running them both in parallel for several weeks now, so far so good.

Nexus, proximity and our CI server (CruiseControl) all run on the same host and as the same user.

We use a "ci-build" profile to override the scp:// deploymentUrl in our root pom and use local file:// URLs instead. This cut our CI build times in half.

Now, as we transition to nexus, we will replace scp:// with https:// deploymentUrl in our root pom, but what of the CI server?

Is it a good idea to use file:// deploymentUrl to deploy into nexus?

FYI, the CI artifacts are exclusively SNAPSHOT versions and we have unqiueVersion to false.

TIA,
Doug

 « Return to Thread: file URLs a good idea for deployment?