Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-3675

Execute final packaging and deployment of Rice 1.0.1

    Details

    • Type: Task Task
    • Status: Closed Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.0.1
    • Component/s: Packaging
    • Labels:
      None
    • Similar issues:
      KULRICE-3875Execute final packaging and deployment of Rice 1.0.1.1
      KULRICE-3670Create final upgrade scripts for Oracle and MySQL for Rice 1.0.0 to 1.0.1
      KULRICE-4650Final package and release of Rice 1.0.3
      KULRICE-6384Work on packaging of web content for production deploy
      KULRICE-3413Add dataset packaging to the Rice packaging scripts
      KULRICE-4130Perform final packaging of the Rice 1.0.2 release
      KULRICE-4804maven no longer executing tests for empty packages
      KULRICE-2815 Deploy CAS-enabled Rice standalone server to test environment
      KULRICE-1475Deploy a test Rice Standalone application to a test environment
      KULRICE-3823rice-kew 1.0.1 artifact not present in Maven

      Description

      I would like to include at the very least Garey and Jeremy in on this process. We should work on ensuring that it's documented as part of this. Also, Farooq is going to set up a kulcfg account on wsa123 that we can use in order to perform our maven deployments.

        Issue Links

          Activity

          Hide
          Eric Westfall added a comment -

          Added Farooq as a watcher.

          Show
          Eric Westfall added a comment - Added Farooq as a watcher.
          Hide
          Farooq Sadiq (Inactive) added a comment -

          The account used to deploy to the maven repository and to deploy the site directory is
          kualicfg.

          • If you are deploying rice. You will need to generate a private-public key pair.
            Instructions to be posted tomorrow on confluence for windows putty and macosx/linux

          Then the public key needs to be added to the authorized_keys file on the uits server you are connecting to.
          (This will be done my a Configuration Manager - me)

          You will have to create a local .settings file. And the pom.xml will have to be updated.

          Show
          Farooq Sadiq (Inactive) added a comment - The account used to deploy to the maven repository and to deploy the site directory is kualicfg. If you are deploying rice. You will need to generate a private-public key pair. Instructions to be posted tomorrow on confluence for windows putty and macosx/linux Then the public key needs to be added to the authorized_keys file on the uits server you are connecting to. (This will be done my a Configuration Manager - me) You will have to create a local .settings file. And the pom.xml will have to be updated.
          Hide
          Eric Westfall added a comment -

          Series of steps:

          0) Update the license headers by running the script for that purpose (this has already been done for 1.0.1)
          1) Update the version numbers in the pom from 1.0.1-SNAPSHOT to 1.0.1 (this has already been done)
          2) Update deployment locations in the pom if needed for the new setup
          3) Run the packaging scripts to generate the distributions, generate binary, source and server
          – ensure that things are setup correctly in my settings.xml
          4) Deploy the 1.0.1 version to the maven repository, deploy jars, source and javadocs (in a jar) to the maven repository
          5) Deploy the maven site (this is what deploys the javadocs)
          6) Create the 1.0.1 documentation "portal"
          7) Generate the doc-to-help documentation
          – we have a new process surrounding this where the final content is in a subversion project

          Show
          Eric Westfall added a comment - Series of steps: 0) Update the license headers by running the script for that purpose (this has already been done for 1.0.1) 1) Update the version numbers in the pom from 1.0.1-SNAPSHOT to 1.0.1 (this has already been done) 2) Update deployment locations in the pom if needed for the new setup 3) Run the packaging scripts to generate the distributions, generate binary, source and server – ensure that things are setup correctly in my settings.xml 4) Deploy the 1.0.1 version to the maven repository, deploy jars, source and javadocs (in a jar) to the maven repository 5) Deploy the maven site (this is what deploys the javadocs) 6) Create the 1.0.1 documentation "portal" 7) Generate the doc-to-help documentation – we have a new process surrounding this where the final content is in a subversion project
          Hide
          Eric Westfall added a comment -

          We should move the documentation on the Rice release process to the KULRICE space. Current document is linked from here:

          https://test.kuali.org/confluence/display/KULFOUND/Release+Management

          Show
          Eric Westfall added a comment - We should move the documentation on the Rice release process to the KULRICE space. Current document is linked from here: https://test.kuali.org/confluence/display/KULFOUND/Release+Management
          Hide
          Eric Westfall added a comment - - edited

          Other things that need to be updated:

          1) Update documentation on where to upload the final distribution files to (it's somewhere in drupal now, wsa141.uits.indiana.edu, same as rice.kuali.org)
          2) We should document the information on what needs to be setup to perform the dist-database (there are some properties that need to be set in kuali-build.properties)
          3) We should also include a description of what the process does (and how it uses the packaging database to stage everything)
          4) Document that they need to be sure that they have an up to date copy of kul-cfg-dbs checked out (the impex tool)
          5) Run the "ant dist-all" command to create all of the distributions
          – as part of this, we should record the expected amount of time that we think this should take
          6) We should come up with a standard checklist of "QA" items that need to be dealt with every release so that we don't forget, some examples:
          – create release notes
          – update installation guide (it has version numbers in it)
          – ensure that the bootstrap and demo dataset cleanup scripts are up to date based on the database changes made since the last version of Rice
          – make sure that the latest exports of all of the databases succedded (we need to make sure that rice-cfg-dbs and friends are up to date with the latest copy of what's in the master databases)
          – updating the license headers
          – updating acknowledgments page if there are new libraries added (or removed)
          – generating an updated schema.html
          – update the ERD if there are database changes (need to document how we create our ERDs and what tools to use, MySQL Workbench)
          – update README.txt, NOTICE.txt and LICENSE.txt each release (if needed)
          – check to make sure that the servers (rice.kuali.org and test.kuali.org) have enough free space for the distros, docs, and maven deployments
          – ensure that all unit tests are at 100%
          7) Bring over and update the documentation on the various rice distributions and what they include, need to figure out if this is already in readme files (which I think it is) because we don't want to duplicate it
          8) Location where we are uploading the distributions is /opt/www/drupal/contents/rice/downloads/1.0.1
          – we need to document the location
          – we currently have to manually upload these, should we script it?
          9) Total dist-all process took approximately 45 minutes
          10) The maven site-deploy does not appear to be properly deploying javadocs, plus it's really really slow and has lots of errors, we should look into this

          Show
          Eric Westfall added a comment - - edited Other things that need to be updated: 1) Update documentation on where to upload the final distribution files to (it's somewhere in drupal now, wsa141.uits.indiana.edu, same as rice.kuali.org) 2) We should document the information on what needs to be setup to perform the dist-database (there are some properties that need to be set in kuali-build.properties) 3) We should also include a description of what the process does (and how it uses the packaging database to stage everything) 4) Document that they need to be sure that they have an up to date copy of kul-cfg-dbs checked out (the impex tool) 5) Run the "ant dist-all" command to create all of the distributions – as part of this, we should record the expected amount of time that we think this should take 6) We should come up with a standard checklist of "QA" items that need to be dealt with every release so that we don't forget, some examples: – create release notes – update installation guide (it has version numbers in it) – ensure that the bootstrap and demo dataset cleanup scripts are up to date based on the database changes made since the last version of Rice – make sure that the latest exports of all of the databases succedded (we need to make sure that rice-cfg-dbs and friends are up to date with the latest copy of what's in the master databases) – updating the license headers – updating acknowledgments page if there are new libraries added (or removed) – generating an updated schema.html – update the ERD if there are database changes (need to document how we create our ERDs and what tools to use, MySQL Workbench) – update README.txt, NOTICE.txt and LICENSE.txt each release (if needed) – check to make sure that the servers (rice.kuali.org and test.kuali.org) have enough free space for the distros, docs, and maven deployments – ensure that all unit tests are at 100% 7) Bring over and update the documentation on the various rice distributions and what they include, need to figure out if this is already in readme files (which I think it is) because we don't want to duplicate it 8) Location where we are uploading the distributions is /opt/www/drupal/contents/rice/downloads/1.0.1 – we need to document the location – we currently have to manually upload these, should we script it? 9) Total dist-all process took approximately 45 minutes 10) The maven site-deploy does not appear to be properly deploying javadocs, plus it's really really slow and has lots of errors, we should look into this
          Hide
          Eric Westfall added a comment -

          We completed all of the deployments and uploads. The final step is the generation of the documentation which Casey is working on.

          Show
          Eric Westfall added a comment - We completed all of the deployments and uploads. The final step is the generation of the documentation which Casey is working on.

            People

            • Assignee:
              Eric Westfall
              Reporter:
              Eric Westfall
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Structure Helper Panel