-
Task
-
Resolution: Unresolved
-
Major
-
None
If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in blueocean-core-js being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on blueocean-core-js, which then triggers bundle:watch in those plugins etc etc.
So, no more need to publish + install etc when developing ... make a change and see the effect immediately (that's the hope/theory anyway ).
- depends on
-
JENKINS-40403 Javascript bundle:watch for multi-module projects
-
- Open
-
-
JENKINS-40404 Javascript "slink" (or other) for multi-module projects
-
- Open
-
[JENKINS-40405] Combined global "watch" + "slink" for multi-module
Epic Link | New: JENKINS-40392 [ 177055 ] |
Link | New: This issue depends on JENKINS-40403 [ JENKINS-40403 ] |
Link | New: This issue depends on JENKINS-40404 [ JENKINS-40404 ] |
Description | New: If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in {{blueocean-core-js}} being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on {{blueocean-core-js}}, which in then triggers bundle:watch in those plugins etc etc. |
Description | Original: If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in {{blueocean-core-js}} being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on {{blueocean-core-js}}, which in then triggers bundle:watch in those plugins etc etc. | New: If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in {{blueocean-core-js}} being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on {{blueocean-core-js}}, which then triggers bundle:watch in those plugins etc etc. So, no more need to publish + install etc when developing ... make a change and see the effect immediately (that's the hope/theory anyway ;) ). |
Description | Original: If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in {{blueocean-core-js}} being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on {{blueocean-core-js}}, which then triggers bundle:watch in those plugins etc etc. So, no more need to publish + install etc when developing ... make a change and see the effect immediately (that's the hope/theory anyway ;) ). |
New:
If we combine the global "watch" (see JENKINS-40403) and "slink" (see JENKINS-40404) commands into a single new command that also operates across a multi-module project then we're getting closer to the sort of automated dev process we want e.g. a change in {{blueocean-core-js}} being picked up by the "global" watch and triggering a build of it, which generates new files in it's dist folder, which in turn gets picked up by the global slink which triggers linking of those changes to all HPIs etc that depend on {{blueocean-core-js}}, which then triggers bundle:watch in those plugins etc etc. So, no more need to publish + install etc when developing ... make a change and see the effect immediately (that's the hope/theory anyway ;) ). |