Uploaded image for project: 'transportpce'
  1. transportpce
  2. TRNSPRTPCE-663

Adapt TransportPCE CI to a better usage of lighty build

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • Phosphorus
    • None
    • None
    • None

      Currently, lighty build integrates the TAPI functionality per default, because tapi functional tests are embeded inside functional tests of devices 2.2.1 (although logically they should not be specific to devices 221). And yet, in karaf, Tapi is managed as an optional feature.
      It would be worth adapting the CI to be able to build lighty without TAPI functionalities activated when not necessary.

            gthouenon Gilles Thouenon
            gthouenon Gilles Thouenon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day
                1d