Add support for generating a new plugin file based on current Jenkins folder

[timja]

Ideally it should support the following outputs:

• console (human readable)
• txt
• yaml

The --list flag along with the --output flags can probably be used for this

Also relevant #226 and #173

[jehon]

It should be great to generate the plugin.txt out of the jenkins, so that this tool could be used easily to copy plugins from instance to another instance...

[MarkEWaite]

It should be great to generate the plugin.txt out of the jenkins, so that this tool could be used easily to copy plugins from instance to another instance...

The Jenkins groovy script console can generate the contents of a plugins.txt file with the script:

Jenkins.instance.pluginManager.plugins
    .collect()
    .sort { it.getShortName() }
    .each {
        plugin -> println("${plugin.getShortName()}:${plugin.getVersion()}")
    }
return

[pamgluss-slack]

I am confused, what does --output txt / --output yaml actually do right now? Isn't this their intended purpose?

[MarkEWaite]

I am confused, what does --output txt / --output yaml actually do right now? Isn't this their intended purpose?

I use the following command to generate a plugins.txt file based on the existing plugins.txt file and available updates.

$ ./jenkins-plugin-cli.sh --jenkins-version 2.319.3 --plugin-download-directory ref/plugins --plugin-file plugins.txt --no-download --available-updates --output txt > x && mv x plugins.txt

In my case, it needs the "starter" plugins.txt file. It doesn't generate a fresh one from the ref/plugins directory.