list top level items in the controller

[KevinRealAlcalde]

No description provided.

[duemir]

It looks like it is skipping Multibranch Pipelines and Organization folders
Why is this needed?

[KevinRealAlcalde]

The objective of this script is to avoid counting how many Jobs you have in a big cluster. Multibranch and Organization folders are counted but only as 1 regardless the amount of repos/branches inside, because as said, the objective is to retrieve the amount of jobs in the cluster

[Dohbedoh]

I am bit confused too here. By top level items, do you mean TopLevelItem objects ? Or items at the Jenkins root ?

Seems to me that we could simply use jenkins.model.Jenkins.instance.allItems(hudson.model.TopLevelItem.class) and avoid the recursion ?

[KevinRealAlcalde]

The script does not retrieve only Items at the Jenkins root. iterating jenkins.model.Jenkins.instance.allItems(hudson.model.TopLevelItem.class) is quite similar to the output of this script but not exactly the same. The difference is this script does not count separately the different branches in a Job while TopLevelItem does it. Also, the TopLevelItem counts Folders as something to be counted, while this script does not.

[duemir]

I still don't see the point and am confused by the script's output.
CloudBees CI Lexicon | Item, not very clearly, define an item as "A folder, Pipeline, or Project in the Jenkins environment." This includes all the things skipped in this script, yet the script claims it prints the "total" number of items.

Who is going to use this script and why? What is the story behind it?