pipeline plugin doesn't handle the case of job history having inconsistent build numbers

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      We just changed the format to help us relate the job instance to a build, which is perfectly reasonable.

      What we're assuming is that the pipeline plugin makes assumptions about jobs visible in the pipeline, and doesn't handle the case of job history having inconsistent build numbers.
      This is just an assumption at this point.

            Assignee:
            Unassigned
            Reporter:
            Ram Sugasi
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: