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

Provide a way to refresh Org Folder metadata without indexing

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Minor Minor
    • branch-api-plugin
    • None

      For Blue Ocean, we're trying to provide an optimized path to add a single repository in Github, which adds a containing org folder. We are currently sending a custom SCMSourceEvent to trigger the multibranch project creation instead of doing a full org scan, but this results in the org folder not having fetched the proper metadata. Please let me know if there's a way to trigger it with an event or provide a way to do so if one doesn't exist.

          [JENKINS-42976] Provide a way to refresh Org Folder metadata without indexing

          Keith Zantow created issue -

          Ryan Campbell added a comment -

          Blue Ocean has worked around this, so no longer a driver here.

          Ryan Campbell added a comment - Blue Ocean has worked around this, so no longer a driver here.
          Ryan Campbell made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Keith Zantow made changes -
          Attachment New: Screen Shot 2017-04-19 at 7.08.01 PM.png [ 37274 ]
          Keith Zantow made changes -
          Attachment New: Screen Shot 2017-04-19 at 7.10.21 PM.png [ 37275 ]

          Keith Zantow added a comment -

          recampbell this is still an issue, if you add a single repo it does not do a full scan and does not retrieve the metadata:

          If I then run a scan manually, I get the metadata:

          Keith Zantow added a comment - recampbell this is still an issue, if you add a single repo it does not do a full scan and does not retrieve the metadata: If I then run a scan manually, I get the metadata:
          Keith Zantow made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Keith Zantow made changes -
          Status Original: Reopened [ 4 ] New: Open [ 1 ]

          Does sending a SCMNavigatorEvent with UPDATED  not work? https://github.com/jenkinsci/branch-api-plugin/blob/a5e6362d03fdf31f6d7d7905885b38b67464a532/src/main/java/jenkins/branch/OrganizationFolder.java#L1033 

          as long as your SCMNavigatorEventImpl matches the SCMNavigator it should update the actions and that will include the organization avatar

          Stephen Connolly added a comment - Does sending a SCMNavigatorEvent with UPDATED  not work? https://github.com/jenkinsci/branch-api-plugin/blob/a5e6362d03fdf31f6d7d7905885b38b67464a532/src/main/java/jenkins/branch/OrganizationFolder.java#L1033   as long as your SCMNavigatorEventImpl matches the SCMNavigator it should update the actions  and that will include the organization avatar

          kzantow I have yet to implement the SCMNavigatorEvent for the GitHub Branch Source that would pick up an organization event and trigger the avatar update, and given that I seem to have missed test cases for event updating of the MetadataActionFolderIcon in branch-api there is a risk that the code path does not work, though in theory it should

          Stephen Connolly added a comment - kzantow I have yet to implement the SCMNavigatorEvent for the GitHub Branch Source that would pick up an organization event and trigger the avatar update, and given that I seem to have missed test cases for event updating of the MetadataActionFolderIcon in branch-api there is a risk that the code path does not work, though in theory it should

            Unassigned Unassigned
            kzantow Keith Zantow
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: