JENKINS-23365 made it possible to use SCM from other contexts. But there are still some SCM-oriented things stuck in AbstractProject/AbstractBuild which ought to be generalized.

      • AbstractBuild.getChangeSets (as used by project-changes.jelly) does not implement any method. Either this should be pushed up into Run so that it can be used more generally (simple though an awkward introduction of SCM specifics into Run); or SCMTriggerItem should add getChangeSets(Run) (more sensible architecturally, though awkward since it could not have a generic type for the build).
      • getCulprits and hasParticipant would seem to apply to any build with changes.
      • AbstractProject.doRssChangelog could be moved elsewhere and use getChangeSets.
      • View.AsynchPeople could use getChangeSets.

      Possibly there needs to be an interface for a Run with changes, tied somehow to SCMTriggerItem and with some default methods?

          [JENKINS-24141] SCM with non-AbstractProject, revisited

          Jesse Glick created issue -
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-23365 [ JENKINS-23365 ]

          Jesse Glick added a comment -

          Perhaps also need to add SCM.buildEnvVars(Run, FilePath, Map<String,String>).

          Jesse Glick added a comment - Perhaps also need to add SCM.buildEnvVars(Run, FilePath, Map<String,String>) .
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-26100 [ JENKINS-26100 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-30252 [ JENKINS-30252 ]
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-28946 [ JENKINS-28946 ]
          Flávio Augusto Valones made changes -
          Link New: This issue is related to JENKINS-33016 [ JENKINS-33016 ]

          Alexander Vorobiev added a comment - Per http://stackoverflow.com/questions/30398465/how-to-get-culprits-or-committers-inside-a-jenkins-workflow-with-one-or-more-scm this blocks https://issues.jenkins-ci.org/browse/JENKINS-34763 . Is it still correct? I see JENKINS-34763 as the main blocker on the way to Jenkins pipeline. Can this be prioritized?
          Jesse Glick made changes -
          Link New: This issue is blocking JENKINS-30412 [ JENKINS-30412 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 157015 ] New: JNJira + In-Review [ 179480 ]

            abayer Andrew Bayer
            jglick Jesse Glick
            Votes:
            23 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated:
              Resolved: