Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14326

Pipeline should log when it doesn't generate stages because the same type failed previously

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.17.0, 7.17.0-alpha5
    • None
    • None
    • None

      Acceptance Criteria (Required on creation):

      • If pipeline stages are not generated because a previous h2 build of the same type, this should be logged

      Hints (optional):

      • Without this, it is not obvious why the stages are not generated and I have spent a good amount of time understanding this case two times

        This is the controller panel for Smart Panels app

            [CAM-14326] Pipeline should log when it doesn't generate stages because the same type failed previously

            When trying this out, I tried to provoke a failure of the authorization profile build by adding the Maven enforcer plugin and let it always fail. It fails the build before surefire runs.

            In my tests, the following authorization stages were then all executed. The cause was that the authorization stage type was not added to the list of failed stage types. This in turn was, because we do this as a postFailure action and this particular action did not execute, because a previous postFailure action had failed. The failing postFailure action was the publishing of JUnit results, because there were not JUnit results (surefire never executed).

            As it can be a regular expected case that there are no JUnit results on a failure (e.g. any Maven build problems that occur before surefire executes), I'm trying to change the publishing of JUnit results so that it doesn't fail when it publishes no test results and instead logs the numbers of executed tests.

            Thorben Lindhauer added a comment - When trying this out, I tried to provoke a failure of the authorization profile build by adding the Maven enforcer plugin and let it always fail. It fails the build before surefire runs. In my tests, the following authorization stages were then all executed. The cause was that the authorization stage type was not added to the list of failed stage types. This in turn was, because we do this as a postFailure action and this particular action did not execute, because a previous postFailure action had failed. The failing postFailure action was the publishing of JUnit results, because there were not JUnit results (surefire never executed). As it can be a regular expected case that there are no JUnit results on a failure (e.g. any Maven build problems that occur before surefire executes), I'm trying to change the publishing of JUnit results so that it doesn't fail when it publishes no test results and instead logs the numbers of executed tests.

              thorben.lindhauer Thorben Lindhauer
              thorben.lindhauer Thorben Lindhauer
              Thorben Lindhauer Thorben Lindhauer
              Nikola Koevski Nikola Koevski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: