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

"Auto-discover jenkinsfiles" missing from Create pipeline

XMLWordPrintable

      I am not able any longer to use Blue Ocean to create a Jenkins project from a Github Organization.

      Before, when creating a pipeline in blue ocean, I could click the option/button "Auto-Discover Jenkinsfiles" after selecting my Github Enterprise organization. This is described here, https://jenkins.io/user-handbook.pdf, at page 116. However, I don't get that option any longer, I only see a list of the repositories, and I have to select one of them to create the pipeline.

      If I do create a pipeline from one of those repositories, Blue Ocean creates a pipeline for only that project.

      What I want is the equivalent of using, in the regular Jenkins UI, "New item" -> "Github organization". In other words, a Jenkins project containing all repositories for a organization, that auto scans new repositories.

      I am running the jenkins:2.88-slim docker image, and have installed the latest version of most Blue Ocean plugins.

      I don't really know if or what I did to lose the possiblity of creating this kind of project.

       

        1. createpipeline.png
          createpipeline.png
          35 kB

          [JENKINS-47857] "Auto-discover jenkinsfiles" missing from Create pipeline

          James Dumay added a comment -

          Hey yngvark,

          We removed the option to create organization folders in 1.2. There were a few reasons we remove it but mostly because developers cannot change settings for an individual Pipeline that is contained in an Organization Folder.

          To change any setting related to the Pipeline the user must change this at an Organization Folder level and this will apply the change to all Pipelines contained within it.

          This means that individual projects cannot have their own project settings and puts severe practical limits on the utility of this feature. Utility jobs that are not linked to a repository within the organization cannot be placed with an organization folder which limits its use as an Pipeline categorisation structure.

          To fix these problems with Organization Folders requires a significant re-engineering for a feature that has little value to the majority of users we spoke to (most users have trouble creating their first pipeline vs managing 100s of them).

          I hope this explanation helps your understanding.

          Thanks,
          James

          James Dumay added a comment - Hey yngvark , We removed the option to create organization folders in 1.2. There were a few reasons we remove it but mostly because developers cannot change settings for an individual Pipeline that is contained in an Organization Folder. To change any setting related to the Pipeline the user must change this at an Organization Folder level and this will apply the change to all Pipelines contained within it. This means that individual projects cannot have their own project settings and puts severe practical limits on the utility of this feature. Utility jobs that are not linked to a repository within the organization cannot be placed with an organization folder which limits its use as an Pipeline categorisation structure. To fix these problems with Organization Folders requires a significant re-engineering for a feature that has little value to the majority of users we spoke to (most users have trouble creating their first pipeline vs managing 100s of them). I hope this explanation helps your understanding. Thanks, James

          Israel Sotomayor added a comment - - edited

          Hi jamesdumay!

          Thanks for the clarification 

           

          Would you mind to explain then if it would be possible to auto load somehow all the repositories in a G/H organization with a Jenkinsfile into our BlueOcean pipelines? or does this meas that we just have to use the Github Organization folder plugin?

          I found an issue which it's close since Oct without a reason https://github.com/jenkinsci/blueocean-plugin/pull/1188 that kind of show few screenshot of what could be an integration between the two BlueOcean +  Github Organization folder but to be fair it's a bit difficult to keep track of all the work you guys are doing

           

          If you could at least point us out to which direction is right I want to use BlueOcean UI and Autodiscover our GitHub Organization projects (not sure if that's possible at this point)

           

          Thanks,

           

          UPDATE:

           

          I have figure out that using GitHub Branch Source plugin you can autoscan your org and then Blue Ocean will just show all the jobs 

           

          Thanks,

          Israel Sotomayor added a comment - - edited Hi jamesdumay ! Thanks for the clarification    Would you mind to explain then if it would be possible to auto load somehow all the repositories in a G/H organization with a Jenkinsfile into our BlueOcean pipelines? or does this meas that we just have to use the Github Organization folder plugin? I found an issue which it's close since Oct without a reason  https://github.com/jenkinsci/blueocean-plugin/pull/1188  that kind of show few screenshot of what could be an integration between the two BlueOcean +  Github Organization folder but to be fair it's a bit difficult to keep track of all the work you guys are doing   If you could at least point us out to which direction is right I want to use BlueOcean UI and Autodiscover our GitHub Organization projects (not sure if that's possible at this point)   Thanks,   UPDATE:   I have figure out that using  GitHub Branch Source plugin you can autoscan your org and then Blue Ocean will just show all the jobs    Thanks,

            Unassigned Unassigned
            yngvark Yngvar Kristiansen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: