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

Upgrade Jenkins Node version to 8.9.3 #16680

Merged
merged 1 commit into from
Jan 23, 2018
Merged

Upgrade Jenkins Node version to 8.9.3 #16680

merged 1 commit into from
Jan 23, 2018

Conversation

arizzitano
Copy link
Contributor

@arizzitano arizzitano force-pushed the ari/node-8 branch 2 times, most recently from c996297 to 9e6ea56 Compare January 10, 2018 18:35
@arizzitano arizzitano changed the title WIP: Upgrade Jenkins Node version to 8.9.1 WIP: Upgrade Jenkins Node version to 8.9.3 Jan 10, 2018
@arizzitano
Copy link
Contributor Author

jenkins run js

bump node version to 8.9.3 [FEDX-409]

bump node version to 8.9.1 [FEDX-409]

8.9.3

don't clean cache

try ignoring course_experience

another attempt

back out that coverage patch
@arizzitano arizzitano changed the title WIP: Upgrade Jenkins Node version to 8.9.3 Upgrade Jenkins Node version to 8.9.3 Jan 22, 2018
# Manage the npm cache on Jenkins.
# (In this case, remove it. That ensures from run-to-run, it is a clean npm environment)
echo "--> Cleaning npm cache"
npm cache clean
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't hold up the PR, but I'm curious -- why was this part removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

As of npm 5, it exits nonzero unless you use --force, since supposedly now the npm cache is self-healing. npm cache verify works similarly, but it might be a better idea for us to just force the clean and wipe it out entirely -- what do you think @ormsbee?

Copy link
Contributor

Choose a reason for hiding this comment

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

Thanks for the explanation. I think it's fine to leave it as you already have it here. If it turns out to be problematic, we can always adjust later.

@arizzitano arizzitano merged commit a54b6d2 into master Jan 23, 2018
@jdmulloy jdmulloy deleted the ari/node-8 branch April 5, 2018 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants