Uploaded image for project: 'Spring Boot & Cloud'
  1. Spring Boot & Cloud
  2. SB-244

Move to Arquillian Cube

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • None
    • booster
    • None

    Description

      This task refers to the migration process of the boosters and testsuite to use latest version of Arquillian Cube

      Here are the steps proposed to do this transition :

      Task Status Additional info
      Test HTTP Booster using Arquillian Cube PR sent https://github.com/snowdrop/spring-boot-http-booster/pull/63
      Sync with@claprun if Spring Boot BOM or Spring Boot Booster BOM should be updated Waiting  
      Run its corresponding Jenkins Job LINK TO THE JOB RESULT  
      If previous task is OK, then update all the boosters    
      Update Testuite to use Arquillian Cube    
      Run its corresponding Jenkins Job LINK TO THE JOB RESULT  
      Report result    

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. SB-340 Track Arquillian Cube fix for ConfigMap / RoleBinding usage

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is blocked by

          Task - Represents a small unit of work that is not end-user facing. SB-332 Add Arquillian Cube dependencies to the booster parent

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is duplicated by

          Sub-task - The sub-task of the issue SB-348 Migrate all tests to Arquillian Cube

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              ajustin@redhat.com Ales Justin
              claprun Chris Laprun
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: