For personalised dashboard we want to tell the user if their pipelines branch state is behind commits in master and what commits it is behind on.

      Scenario

      • There are three commits: 1, 2, 3
      • Jenkins is currently building commit 1
      • We want to tell the user that commits 2 and 3 have not been built

          [JENKINS-36057] API to retrieve unbuilt commits for a branch

          James Dumay added a comment -

          michaelneale KK wanted a ticket to show other Jenkins devs to find a path forward for this one.

          James Dumay added a comment - michaelneale KK wanted a ticket to show other Jenkins devs to find a path forward for this one.

          Michael Neale added a comment -

          jamesdumay can you rephrase? I can't parse your sentence. Need a bit more clarity on this ticket.

          Michael Neale added a comment - jamesdumay can you rephrase? I can't parse your sentence. Need a bit more clarity on this ticket.

          Jesse Glick added a comment -

          An API already exists for listing SCMRevision between a build currently running and the current branch head, but not to get any metadata for these such as commit message. GitHub offers an API to retrieve commit info but it seems there is no facility for batching this.

          Jesse Glick added a comment - An API already exists for listing SCMRevision between a build currently running and the current branch head, but not to get any metadata for these such as commit message. GitHub offers an API to retrieve commit info but it seems there is no facility for batching this.

          jamesdumay I really find it hard to understand the use-case here. EITHER there has been a scan, in which case there will be builds scheduled... OR we'd have to do a scan, in which case there will be builds scheduled... OR we need a magic unicorn that will tell us about commits that have not been notified to us yet...

          Or is your ask: of the builds scheduled, how long is each build's chain of unbuilt commits? That could be costly to determine.

          Inclined to close as WONTFIX but I will give you an opportunity to explain your ask better

          Stephen Connolly added a comment - jamesdumay I really find it hard to understand the use-case here. EITHER there has been a scan, in which case there will be builds scheduled... OR we'd have to do a scan, in which case there will be builds scheduled... OR we need a magic unicorn that will tell us about commits that have not been notified to us yet... Or is your ask: of the builds scheduled, how long is each build's chain of unbuilt commits? That could be costly to determine. Inclined to close as WONTFIX but I will give you an opportunity to explain your ask better

            Unassigned Unassigned
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: