Details

    • Similar issues:
      KULRICE-3061Finish getting Rice test environments in place
      KULRICE-5665Implement the ability to run rice sample app as a seperate application integrated with the Rice Standalone Server, put process in place to automatically deploy to a test environment using CI
      KULRICE-4944Implement multiple test environments
      KULRICE-4925Set up 2.1 Test Environments
      KULRICE-4914Set up test environments for Rice 2.0 running Tomcat 6/7, do daily and weekly deploys
      KULRICE-4941Design & plan test environments
      KULRICE-1475Deploy a test Rice Standalone application to a test environment
      KULRICE-11445Modify performance test plan to prepare for creation of test environment
      KULRICE-13022Create Environment(s) for Rice 2.5 performance testing
      KULRICE-13784Create test environments for Rice 2.5 performance testing
    • Application Requirement:
      Rice

      Description

      Also document how to re-deploy.

      Let AG know when this is done so that he can work with testers at CU to get some QA going.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Comment copied from KULRICE-1475 duplicate issue:

          We want to be able to deploy this using the standard app deploy scripts. I'd like to investigate using the Maven Ant plugin for doing the packaging (instead of the maven assemblies) prior to doing this task.

          The machine this will happen on is wsa131, may need to get ESA involved to get this up and going.

          Show
          Eric Westfall added a comment - Comment copied from KULRICE-1475 duplicate issue: We want to be able to deploy this using the standard app deploy scripts. I'd like to investigate using the Maven Ant plugin for doing the packaging (instead of the maven assemblies) prior to doing this task. The machine this will happen on is wsa131, may need to get ESA involved to get this up and going.
          Hide
          Eric Westfall added a comment -

          This is going to require at least the following:

          1) get a tomcat environment set up on wsa131 for this
          2) modify the app deployment script to allow for checkouts from SVN
          3) add a "dist" target to our build.xml which can do a regexp to change environment in rice-config.xml, runs the dist-standalone target,and copies resulting war to the appropriate location for the appdeploy script to deploy it.
          4) Get a /usr/local/rice directory setup on wsa131 with write permissions to kualicfg
          5) Set up rice-config.xml in /usr/local/rice and env-rice-config.xml for environment specific configuration.
          6) Configure database connections for environment. For now just point to rice092dev? Or should it have it's own dedicated database that we can test upgrades on?
          7) Determine what app code should be, kr?

          I'm going to start with sending the esa requests to get everything set up and look at modifying the appdeploy script to allow for subversion checkouts.

          Show
          Eric Westfall added a comment - This is going to require at least the following: 1) get a tomcat environment set up on wsa131 for this 2) modify the app deployment script to allow for checkouts from SVN 3) add a "dist" target to our build.xml which can do a regexp to change environment in rice-config.xml, runs the dist-standalone target,and copies resulting war to the appropriate location for the appdeploy script to deploy it. 4) Get a /usr/local/rice directory setup on wsa131 with write permissions to kualicfg 5) Set up rice-config.xml in /usr/local/rice and env-rice-config.xml for environment specific configuration. 6) Configure database connections for environment. For now just point to rice092dev? Or should it have it's own dedicated database that we can test upgrades on? 7) Determine what app code should be, kr? I'm going to start with sending the esa requests to get everything set up and look at modifying the appdeploy script to allow for subversion checkouts.
          Hide
          Brian McGough (Inactive) added a comment -

          sounds like a good plan to me, careful on the build script stuff so we can be backwards compatible.
          Thanks,
          Brian

          Show
          Brian McGough (Inactive) added a comment - sounds like a good plan to me, careful on the build script stuff so we can be backwards compatible. Thanks, Brian
          Hide
          Eric Westfall added a comment -

          Thanks, yes the environment-builder.xml script should be backward compatible. I will make it so that it does cvs checkouts by default still.

          Show
          Eric Westfall added a comment - Thanks, yes the environment-builder.xml script should be backward compatible. I will make it so that it does cvs checkouts by default still.
          Hide
          Eric Westfall added a comment -

          Linking with the 2 KULCFG issues which this relies on.

          Show
          Eric Westfall added a comment - Linking with the 2 KULCFG issues which this relies on.
          Hide
          Eric Westfall added a comment -

          An environment pointing to our dev environment is up now at https://test.kuali.org/kr-dev/

          I still need to do the documentation on the layout and how to re-deploy.

          Show
          Eric Westfall added a comment - An environment pointing to our dev environment is up now at https://test.kuali.org/kr-dev/ I still need to do the documentation on the layout and how to re-deploy.
          Hide
          Ailish Byrne added a comment -

          very exciting!

          Show
          Ailish Byrne added a comment - very exciting!

            People

            • Assignee:
              Eric Westfall
              Reporter:
              Aaron Godert (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 4 hours
                4h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 4 hours
                4h

                  Structure Helper Panel