How to Use npm cache on Server with Multiple Build Agents
up vote
1
down vote
favorite
I'd like to use npm on an on-premises Windows server hosting multiple TFS 2015 Build Agents. The agents themselves are set up and configured already, and npm has been installed on the server. The issue that concerns me is the possibility of npm cache collisions and possible corruption if multiple agents are accessing the npm cache at the same time for different builds. All agents must run under the same service account, so even if I override the cache setting in the user config .npmrc file located at %USERPROFILE%.npmrc, this will still have all build agents using the same npm cache location (since they're all using the same account and thus use the same .npmrc file). Is there a way to specify an npm cache for each agent on the same machine, such that each agent folder could have its own nested npm-cache sub-folder (and would be used only by builds executed by that respective agent)?
node.js npm msbuild
azure-devops tfs2015 asked Nov 10 at 23:39
Michael
1,1191716
add a comment |
up vote
1
down vote
favorite
I'd like to use npm on an on-premises Windows server hosting multiple TFS 2015 Build Agents. The agents themselves are set up and configured already, and npm has been installed on the server. The issue that concerns me is the possibility of npm cache collisions and possible corruption if multiple agents are accessing the npm cache at the same time for different builds. All agents must run under the same service account, so even if I override the cache setting in the user config .npmrc file located at %USERPROFILE%.npmrc, this will still have all build agents using the same npm cache location (since they're all using the same account and thus use the same .npmrc file). Is there a way to specify an npm cache for each agent on the same machine, such that each agent folder could have its own nested npm-cache sub-folder (and would be used only by builds executed by that respective agent)?
node.js npm msbuild
azure-devops tfs2015 asked Nov 10 at 23:39
Michael
1,1191716
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'd like to use npm on an on-premises Windows server hosting multiple TFS 2015 Build Agents. The agents themselves are set up and configured already, and npm has been installed on the server. The issue that concerns me is the possibility of npm cache collisions and possible corruption if multiple agents are accessing the npm cache at the same time for different builds. All agents must run under the same service account, so even if I override the cache setting in the user config .npmrc file located at %USERPROFILE%.npmrc, this will still have all build agents using the same npm cache location (since they're all using the same account and thus use the same .npmrc file). Is there a way to specify an npm cache for each agent on the same machine, such that each agent folder could have its own nested npm-cache sub-folder (and would be used only by builds executed by that respective agent)?
node.js npm msbuild
azure-devops tfs2015 asked Nov 10 at 23:39
Michael
1,1191716
I'd like to use npm on an on-premises Windows server hosting multiple TFS 2015 Build Agents. The agents themselves are set up and configured already, and npm has been installed on the server. The issue that concerns me is the possibility of npm cache collisions and possible corruption if multiple agents are accessing the npm cache at the same time for different builds. All agents must run under the same service account, so even if I override the cache setting in the user config .npmrc file located at %USERPROFILE%.npmrc, this will still have all build agents using the same npm cache location (since they're all using the same account and thus use the same .npmrc file). Is there a way to specify an npm cache for each agent on the same machine, such that each agent folder could have its own nested npm-cache sub-folder (and would be used only by builds executed by that respective agent)?
node.js npm msbuild
azure-devops tfs2015 node.js npm msbuild
azure-devops tfs2015 asked Nov 10 at 23:39
Michael
1,1191716
asked Nov 10 at 23:39
Michael
1,1191716
asked Nov 10 at 23:39
Michael
1,1191716
asked Nov 10 at 23:39
Michael
1,1191716
asked Nov 10 at 23:39
Michael
1,1191716
1,1191716
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30
add a comment |
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53244502%2fhow-to-use-npm-cache-on-server-with-multiple-build-agents%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
did you try to run some builds at the same time and check if it doing corruption?
– Shayki Abramczyk
Nov 12 at 10:56
@ShaykiAbramczyk, I haven't tried on this current server, but I've seen it happen before on a previous build server that hosted multiple TFS XAML build agents. I'm trying to prevent that from happening this time around. :-)
– Michael
Nov 12 at 14:30