Repository navigation
Create separate startup scripts for development and production - #13806
Conversation
|
Another possible benefit that hasn't been included in this PR is we can stop shipping $dev code, and set it as a default in exec. (like --base-path) |
|
❤️ If we're going to do this though, what do you think about removing the bin entirely for development and just going through /cc @spalger since he was just talking about separating out dev stuff from the CLI. |
|
+1 @epixa
|
|
Works for me, I'll make updates. |
|
Getting there - we'll need grunt-run to use exec or fork, I don't think spawn can start another node process. I need to switch gears for a few, will come back to this. |
Sure it can, it's just another executable. Try using |
e2086ba to
87f9ff1
Compare
|
jenkins, test it |
df691d2 to
5890360
Compare
There was a problem hiding this comment.
Are you sure this change is alright?
There was a problem hiding this comment.
We are going through scripts/kibana.js as opposed to bin/kibana in development, so this should be correct
There was a problem hiding this comment.
Whoops I forgot to comment on this. @spalger were you concerned about a different node version being used? I believe we're using the bin script anyways, the node build task isn't copied until after optimize.
I'll give this a double check.
There was a problem hiding this comment.
This is producing builds that don't have optimized assets because it's running the optimization in the repo, not the build output.
|
I'm removing |
|
I added it in case someone was using a global node installed. It's not supported but technically would work and probably throw someone off. |
|
@spalger - mind taking another look at this? |
There was a problem hiding this comment.
This is producing builds that don't have optimized assets because it's running the optimization in the repo, not the build output.
@jbudz you should update the dependency here, and then it'll be safe to merge this PR. |
4e59963 to
595b3f0
Compare
595b3f0 to
6f24929
Compare
|
Thanks @w33ble! @tylersmalley I opened https://github.com/elastic/kibana/pull/15066/files to address kibana-keystore - I separated it mostly because this is all green. Pending any red CI I'm going to get this merged in the morning so I can keep an eye on things. |
|
This script should probably be using snake_case |
|
@spalger When we adopted the snake_case thing for files, we did say that there may be some directories where it makes sense to use a different convention, and that we'd treat those case by case. Since these file names are essentially CLI commands for us, it's possible this is one of those cases. |
|
possible, but I think it's ideal to think of the scripts/ as just javascript, and there are other files in that directory that are already using snake case |
|
@spalger 👍 |
|
I opened #15318 and assigned myself. I'll need to make upstream changes in the plugin-helpers and generator repos. |
|
@jbudz If I understand this correctly, you're planning to move The plugin helpers are just using |
|
Ah yep you're right, brain fart. That makes life easier. |
|
@jbudz Should this be included in the Breaking Changes page for 7.0? |
|
I think we're okay, it has never been an approved or advertised workflow. I knew one case on the AUR repository that was swapping it out. We have it documented in a few GitHub issues which should be findable, I'll drop the breaking changes label. |
|
Thank you - sorry for the extra ping! |
…ic#13806) * Use separate startup scripts for development and production * build kibana directly * [build] Use downloaded node when pre-optimizing * clearer variable name * Add breaking changes docs
This creates a different set of startup scripts for development and production. Development scripts are not included in builds.
There's a few reasons behind this:
Closes #5673.
Development mode is now started with
node scripts/kibana, and for pluginsnode scripts/kibana-plugin. CLI args are the same.