Strange build trigger behaviour

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

XMLWordPrintable

      We have several Maven2 projects set up. Hudson, after parsing the poms, knows
      the downstream and upstream projects. So normally, the downstream project should
      be build after the upstream project finished. But instead the downstream is
      triggered too early.

      Also when doing the cvs polling and a project and its downstream project has
      updates, the downstream project gets build twice. One is the cvs trigger and the
      second one the upstream trigger. I think the cvs trigger should be discarded
      when the upstream project is build, shouldn't it?

            Assignee:
            Unassigned
            Reporter:
            cfk
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: