Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-29076

As an eZ Platform maintainer, I want to know if a release broke because of a dependency update

    XMLWordPrintable

Details

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: High High
    • None
    • None
    • CI System
    • None

    Description

      With our current CI infrastructure, the meta-repositories tests will only run when a pull-request is issued there. This may conceal errors that happen after a dependency was updated (recent exemples with Routing and Doctrine). By keeping track of dependencies of previously successful builds, we can get a list of packages that may have caused the issue, and save time fixing the problem.

      To be informed of those, we can trigger nightly builds of supported branches / versions, and run our behat test suites on those. These builds should run on the LTS branch, latest FTR and current master.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bertrand.dunogier@ibexa.co Bertrand Dunogier
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: