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

Enhancing with Pipeline Plugin Usage

    XMLWordPrintable

Details

    Description

      Hi froque

      I am planning to develop a new plugin which will find the plugin usage within Pipelines/Workflow Jobs.

      I though, If it fits with your goals, I can add this feature to plugin-usage-plugin rather than creating a new one.

      What would you think about his ?

      Thanks

      Attachments

        Activity

          froque Filipe Roque added a comment -

          I am not seeing a use case for this. How would a user use this ?

          froque Filipe Roque added a comment - I am not seeing a use case for this. How would a user use this ?
          aytuncbeken Aytunc BEKEN added a comment -

          Assume that you are using a step in a scriptive/directive pipeline from a plugin. This kind of usage doesn’t add any config to job itself, therefore it can’t be reported/found.
          In this scenario, if you remove that plugin, which is showed as never used, pipelines will fail.

          This is the feature I want to add to this plugin

          aytuncbeken Aytunc BEKEN added a comment - Assume that you are using a step in a scriptive/directive pipeline from a plugin. This kind of usage doesn’t add any config to job itself, therefore it can’t be reported/found. In this scenario, if you remove that plugin, which is showed as never used, pipelines will fail. This is the feature I want to add to this plugin
          froque Filipe Roque added a comment -

          I think I get it now. Sure, make a pull request

          froque Filipe Roque added a comment - I think I get it now. Sure, make a pull request
          ianw Ian Williams added a comment -

          @aytuncbeken,

          Definitely +1 from.me.on this. We presently have no insights to what plugins are used by pipelines in our mixed environment. Caused headaches when we decided to aplit a team's pipeline jobs to separate instance. We either reinstall too many plugins that are not req'd or miss some.

           What is your intended approach? Scanning pipelines from SCM can be a big overhead. Scanning last run would be faster.

           

           

          ianw Ian Williams added a comment - @aytuncbeken, Definitely +1 from.me.on this. We presently have no insights to what plugins are used by pipelines in our mixed environment. Caused headaches when we decided to aplit a team's pipeline jobs to separate instance. We either reinstall too many plugins that are not req'd or miss some.  What is your intended approach? Scanning pipelines from SCM can be a big overhead. Scanning last run would be faster.    
          aytuncbeken Aytunc BEKEN added a comment -

          ianw
          I am planning to use StepListener Extension Points. This way I can gather the Steps and find which plugins are they belonged.

          aytuncbeken Aytunc BEKEN added a comment - ianw I am planning to use StepListener Extension Points. This way I can gather the Steps and find which plugins are they belonged.
          aytuncbeken Aytunc BEKEN added a comment - - edited

          Hi froque, ianw

          After my tests, I am planning to use StepListener for catching running steps in both scriptive and declarative pipelines.
          This means that usage will be fulfilled in time as pipelines are executed

          Parsing defined pipelines is not effective. There can be hundred of sub workflow jobs ( MultiBranchJob) from different branches.

          If this approach is okay for you, I will start developing. Please let me know.

          Best.

          aytuncbeken Aytunc BEKEN added a comment - - edited Hi froque , ianw After my tests, I am planning to use StepListener for catching running steps in both scriptive and declarative pipelines. This means that usage will be fulfilled in time as pipelines are executed Parsing defined pipelines is not effective. There can be hundred of sub workflow jobs ( MultiBranchJob) from different branches. If this approach is okay for you, I will start developing. Please let me know. Best.
          froque Filipe Roque added a comment -

          I am fine with that approach. But it seems there is a need to save that information to disk to survive Jenkins reboots ?

          froque Filipe Roque added a comment - I am fine with that approach. But it seems there is a need to save that information to disk to survive Jenkins reboots ?
          aytuncbeken Aytunc BEKEN added a comment -

          Yes, I will look into it

          aytuncbeken Aytunc BEKEN added a comment - Yes, I will look into it
          romanz Roman Zwi added a comment -


          This would also be very useful for the case that a plugin gets deprecated.
          Like it hit me with the old warnings-plugin - I couldn't figure out all the pipeline jobs that used it and therefore one failed after removing it...

          romanz Roman Zwi added a comment - This would also be very useful for the case that a plugin gets deprecated. Like it hit me with the old warnings-plugin - I couldn't figure out all the pipeline jobs that used it and therefore one failed after removing it...

          People

            froque Filipe Roque
            aytuncbeken Aytunc BEKEN
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: