Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40403

Javascript bundle:watch for multi-module projects

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None

      A version of bundle:watch that watches across a multi-module project (HPI plugins and pure NPM packages) and auto bundles/builds when there are changes.

      So in the case of blueocean, you could run a command in the root that results in a bundle:watch across all relevant HPIs and NPM packages in the multi-module project, triggering rebuilds and rebundles where necessary, saving the developer the need to turn on 5 or 6 bundle watches and probably forgetting to do one and then be frustrated wondering why things re not updating.

          [JENKINS-40403] Javascript bundle:watch for multi-module projects

          Tom FENNELLY created issue -
          Tom FENNELLY made changes -
          Epic Link New: JENKINS-40392 [ 177055 ]
          Tom FENNELLY made changes -
          Description Original: A version of {{bundle:watch}} that watches across a multi-module project (HPI plugins and pure NPM packages) and auto bundles/builds when there are changes.

          So in the case of blueocean, you could run a command in the root that results in a bundle:watch across all relevant HPIs and NPM packages in the multi-module project, triggering rebuilds and rebundles where necessary, saving the developer the need to turn on 5 or 6 bundle watches and probably forgetting to do one and then be frustrated wondering why things re not updating.

          If we combine this with a slink 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: A version of {{bundle:watch}} that watches across a multi-module project (HPI plugins and pure NPM packages) and auto bundles/builds when there are changes.

          So in the case of blueocean, you could run a command in the root that results in a bundle:watch across all relevant HPIs and NPM packages in the multi-module project, triggering rebuilds and rebundles where necessary, saving the developer the need to turn on 5 or 6 bundle watches and probably forgetting to do one and then be frustrated wondering why things re not updating.

          If we combine this with a slink command that also operates across a multi-module project (see JENKINS-40404) 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.
          Tom FENNELLY made changes -
          Link New: This issue is related to JENKINS-40404 [ JENKINS-40404 ]
          Tom FENNELLY made changes -
          Link New: This issue is blocking JENKINS-40405 [ JENKINS-40405 ]
          Tom FENNELLY made changes -
          Description Original: A version of {{bundle:watch}} that watches across a multi-module project (HPI plugins and pure NPM packages) and auto bundles/builds when there are changes.

          So in the case of blueocean, you could run a command in the root that results in a bundle:watch across all relevant HPIs and NPM packages in the multi-module project, triggering rebuilds and rebundles where necessary, saving the developer the need to turn on 5 or 6 bundle watches and probably forgetting to do one and then be frustrated wondering why things re not updating.

          If we combine this with a slink command that also operates across a multi-module project (see JENKINS-40404) 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: A version of {{bundle:watch}} that watches across a multi-module project (HPI plugins and pure NPM packages) and auto bundles/builds when there are changes.

          So in the case of blueocean, you could run a command in the root that results in a bundle:watch across all relevant HPIs and NPM packages in the multi-module project, triggering rebuilds and rebundles where necessary, saving the developer the need to turn on 5 or 6 bundle watches and probably forgetting to do one and then be frustrated wondering why things re not updating.

            Unassigned Unassigned
            tfennelly Tom FENNELLY
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: