Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-20765

Run maven proxy tests with Fuse 7.12 AR3

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • fuse-7.12-GA
    • None
    • Fuse Standalone
    • None
    • Very Likely

      Trigger job:

      • latest fuse-7.x-proxy-trigger job in Proxy tab link
      • CUSTOM_BUILD_NAME #job
      • VERSION_REDHAT_FUSE #polarion
      • FUSE_VERSION #job #polarion (version of Karaf component)
      • GIT_BRANCH #job
      • MAVEN_ADDITIONAL_PARAMETERS #job (e.g. -Dopenstack.image= -Dopenstack.patch=true)
      • FAFRAM8_FUSE_ZIP #job (Where Fafram8 should look for FUSE zip archive.)
      • FAFRAM8_JAVA_HOME #job (Version of JRE Faframe8 should set for Fuse on Fafram8 managed node)
      • FAFRAM8_VERSION #job
      • SSH_USER #job (credentials used to connect to Fafram8 managed node)
      • SSH_PASSWORD #job (credentials used to connect to Fafram8 managed node)
      • Other parameters are inherited and useless for job execution
        Trigger job will execute all downstream jobs:
      • Check results in trigger job view
      • To debug you can run downstream jobs with:
      • KEEP_OS_RESOURCES (Check to keep Openstack nodes)
      • KEEP_CONTAINERS (Check to keep containers)
      • Find root container IP in console output and connect with credentials entered in trigger job (default: hudson/redhat)

      There are no special steps needed as it's fully automated. It's not viable to run locally as tests are spawning proxy server on openstack however it is possible but you need to follow exact steps according to test code.

              ecervena@redhat.com Emil Cervenan
              tveskrna Tomas Veskrna
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: