Update the Integrity-plugin to match the "Generic SCM step" interface requirements.

      This would include

      • various methods in SCM which formerly took an AbstractBuild now take a more generic Run (i.e., potentially a workflow build) plus a FilePath (i.e., a workspace).
      • use the specified workspace rather than the former build.getWorkspace()
      • some methods formerly taking AbstractProject now take the more generic Job.
      • use @Override wherever possible to make sure you are using the right overloads.
      • Replace AbstractBuild.getProject with Run.getParent.
      • BuildListener has to be replaced with TaskListener in new method overloads.
      • Note that changelogFile may now be null in checkout. If so, just skip changelog generation.
      • checkout now takes an SCMRevisionState so you can know what to compare against without referring back to the build.
      • replace getBuiltOn with FilePath.getComputer.
      • SCMDescriptor.isApplicable should be switched to the Job overload.
        ....

      see details here:
      https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md

      This would generally include the use case of a "random checkout", which means that there is a single run that only want's to fetch a project content, defined only for this very job (e.g. a config path to a build project); no changelog or history required.

          [JENKINS-27140] Workflow support for Integrity SCM Plugin

            cdsouza Cletus D'Souza
            maschuru Matthias Rump
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: