search

tabeyti / jenkins-jack

Jack into your Jenkins to execute Pipeline scripts, provide Pipeline step autocompletions, pull Shared Library step documenation, run console groovy scripts across multiple nodes, and more! Honestly, not that much more.
Other
100 stars 32 forks source link

Support for Team Folders #58

Open mbravo-cbw opened 3 years ago

mbravo-cbw commented 3 years ago

Cloudbees CI provides Team Based Masters. Each of these masters are created with a Team Folder. This folder is not a normal folder, though it acts basically the same. Can you add support for this folder? class com.cloudbees.opscenter.bluesteel.folder.BlueSteelTeamFolder When we add the connections to the Jenkins Master, this is seen as a 'default' job rather than acting as a folder to find additional jobs to populate the ItemTree. If the folder is selected it will get stuck in an infinite loop causing the VSCode needing to be restarted. (This is to be expected as this is not a job so there are no builds to get).

would adding it to the JobType.Folder correct this behaviour?


public static classNameToType(classStr: string): JobType {

    case 'com.cloudbees.hudson.plugins.folder.Folder': {
    return JobType.Folder;
    }
    case 'com.cloudbees.opscenter.bluesteel.folder.BlueSteelTeamFolder': {
    return JobType.Folder;
    }
tabeyti commented 3 years ago

@mbravo-cbw , I can and I will 👍

I'll slate this for after 1.1.3, which will be released in the next week or so.

FYI, I don't have, nor have I ever worked with, the Cloudbees flavor of Jenkins, so I wouldn't be able to validate this change locally ☹️. When 1.1.3 is released and current fixes for issues are validated, I'll be attaching a .vsix with the change to this ticket for you to install and validate for me. If you say it works, I'll cut another minor version update with the change.

mbravo-cbw commented 3 years ago

@tabeyti, that's awesome. Thanks! I'm looking forward to testing out this enhancement.