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

SCM with non-AbstractProject, revisited

    XMLWordPrintable

Details

    Description

      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?

      Attachments

        Issue Links

          is blocking

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-28946 JIRA support for Workflow jobs

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-30412 Access to build's own changelog from script

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. JENKINS-23365 Allow SCM to work with non-AbstractProject

          • Major - Major loss of function.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-26100 SCM steps should return revision state

          • Major - Major loss of function.
          • Resolved
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-35462 Culprit detection does not work with Pipeline jobs

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-37872 WorkflowRun should have getCulprits()

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-33016 Jenkins doesn't detect CVS polling on Pipeline (Workflow) Job

          • Blocker - Blocks development and/or testing work, production could not run.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-30252 Provide easy access to git branch name in multibranch workflow scripts

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link PR #2730

          Web Link workflow-job-plugin PR #35

          mentioned in

          Page Loading...

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: