• Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 5.9.5.Final
    • None
    • Build System, LRA
    • None

      This could be similar to how the XTS and RTS profile is constructed.

      Changes are anticipated in the narayana.sh, maybe pom IDK, and the pull job and main job

            [JBTM-3104] Define a separate CI profile for LRA

            No problem. I will take a look at this, hopefully this week.

            Ondrej Chaloupka (Inactive) added a comment - No problem. I will take a look at this, hopefully this week.

            Michael Musgrove added a comment - - edited

            ochaloup@redhat.com I am reassigning to you since you understand how the set of profiles in the lra-test module interact with each other. Note also that I had to disable running the TCK by default (see JBTM-3115).

            But do let me know if you disagree and I will take another look.

            Michael Musgrove added a comment - - edited ochaloup@redhat.com I am reassigning to you since you understand how the set of profiles in the lra-test module interact with each other. Note also that I had to disable running the TCK by default (see JBTM-3115 ). But do let me know if you disagree and I will take another look.

            Michael Musgrove added a comment - - edited

            The XTS and RTS profiles are for testing with WildFly whereas LRA is a standard module. The tests for LRA are just standard module tests and we do not use profiles to disable tests. Also profiles were introduced to speed up PR testing and the LRA module does not take long to run.

            The current issue with code coverage tests failing on LRA arose because I accidentally reverted my fix to disable the site plugin (JBTM-3093). I have just raised PR 1404 to disable the site plugin for LRA.

            thjenkin@redhat.com do you mind if I close this as will not fix?

            Michael Musgrove added a comment - - edited The XTS and RTS profiles are for testing with WildFly whereas LRA is a standard module. The tests for LRA are just standard module tests and we do not use profiles to disable tests. Also profiles were introduced to speed up PR testing and the LRA module does not take long to run. The current issue with code coverage tests failing on LRA arose because I accidentally reverted my fix to disable the site plugin ( JBTM-3093 ). I have just raised PR 1404 to disable the site plugin for LRA. thjenkin@redhat.com do you mind if I close this as will not fix?

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: