-
Notifications
You must be signed in to change notification settings - Fork 148
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
update webpack to v3.0 #1693
update webpack to v3.0 #1693
Conversation
http://koji.katello.org/kojifiles/work/tasks/8155/8155/build.log fails because there's no npm:
|
@dLobatog any idea why there is no npm? |
[test] |
@ehelms the tests fails because of it cant find packages introduced in this ps, is there a way to test all changes in one pr? or must i break it down to a PR per package? thanks. |
@ohadlevy Traditionally these kinds of changes have been done in a PR like this one. But it puts a burden on the reviewer to check it out locally, run mockchain builds to ensure everything passes. So while I prefer smaller individual PRs to address, this is fine but will take me a (or another maintainer) a bit longer to get to. |
@ohadlevy How many packages are updated in this PR? It's really hard to tell with the number of files changed what all has been changed and waht is going to need updating and what are new packages. If you could either list that out or split this up it would help a ton. |
@ohadlevy there appear to be some actual build errors when looking at (http://ci.theforeman.org/job/packaging_test_pull_request/2329/) that aren't in root log (typically the case for when dependent packages are missing. For example, I see (http://koji.katello.org/koji/taskinfo?taskID=8560) failing in the build.log with what appears to be a legitimate error. Can you check these and confirm? |
@ohadlevy what's the status here? |
@ehelms I'm not seeing the actual error - does koji no longer keeps it? |
@ohadlevy it will keep scratch builds for a short time, we can re-run it |
[test] |
I had to make the following changes to get the builds passing:
|
@ehelms I've applied your changes. |
[test] |
Thanks @ohadlevy . The webpack package is passing so I expect the plugins to also pass as they did locally. Merging and will build. |
No description provided.