Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mgr/dashboard: Add package-lock.json #23285

Merged
merged 2 commits into from Aug 6, 2018
Merged

Conversation

tspmelo
Copy link
Contributor

@tspmelo tspmelo commented Jul 27, 2018

Today we had another problem in jenkins, caused by an update of a frontend dependency.
More specifically, it was an update of a dependency of a dependency of a dependency.

Using fixed versions in our package.json is not enough to prevent this problem
and the only solution is to use and track the package-lock.json file.

@tspmelo
Copy link
Contributor Author

tspmelo commented Jul 30, 2018

jenkins retest this please

@tspmelo tspmelo force-pushed the wip-package-lock branch 2 times, most recently from b08f9a6 to 978dfe1 Compare July 30, 2018 16:56
@tspmelo tspmelo added the DNM label Jul 30, 2018
This will make sure that, at anytime, when someone runs 'npm install'
the resulting packages that are installed are allways the same.

Signed-off-by: Tiago Melo <tmelo@suse.com>
"npm ci" is the recommended command to install dependencies
in a continuous integration system.

It will make sure node_modules is empty and that the version in
"package-lock.json" match the ones in "package.json"

Signed-off-by: Tiago Melo <tmelo@suse.com>
Copy link
Contributor

@rjfd rjfd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@tchaikov tchaikov merged commit 02b4e23 into ceph:master Aug 6, 2018
@tspmelo tspmelo deleted the wip-package-lock branch August 6, 2018 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants