WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Concurrent bower install error. #79

@raphaelquati

Description

@raphaelquati

We have a Jenkins server running a multibranch job. When a release is finished in the repo (gitflow), develop and master branches are updated. The multibranch job is triggered, starting building develop and master branches at same time.

The build job execute grunt that call "bower install". One branch runs ok, the other stops with an error.

Running "shell:bowerInstall" (shell) task
C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\node_modules\configstore\index.js:70
				throw err;
				^

Error: EPERM: operation not permitted, rename 'C:\Users\jenkinssvc\.config\configstore\bower-github.json.716917364' -> 'C:\Users\jenkinssvc\.config\configstore\bower-github.json'
    at Object.fs.renameSync (fs.js:741:18)
    at Function.writeFileSync [as sync] (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\node_modules\write-file-atomic\index.js:81:8)
    at Configstore.set (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\node_modules\configstore\index.js:63:21)
    at Configstore (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\node_modules\configstore\index.js:28:11)
    at readCachedConfig (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\config.js:19:23)
    at defaultConfig (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\config.js:11:12)
    at Object.<anonymous> (C:\Users\jenkinssvc\AppData\Roaming\npm\node_modules\bower\lib\index.js:16:32)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
Warning: Command failed: bower install

OS: Windows Server 2016
Jenkins version: 2.59 
Nodejs: v7.2.1
Bower: 1.8.0

I know the problem is not with bower directly. The problem is in configstore (2.0.0) which uses write-file-atomic

npm/write-file-atomic/issues/10

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions