Merge pull request #11291 from IQSS/7031-phoenix-schemaspy

Remove phoenix docs and scripts, update refs to SchemaSpy

Author: ofahimIQSS

doc/sphinx-guides/source/developers/making-releases.rst

@@ -331,15 +331,19 @@ Deploy Final Release on Demo
 
 Above you already did the hard work of deploying a release candidate to https://demo.dataverse.org. It should be relatively straightforward to undeploy the release candidate and deploy the final release.
 
+.. _update-schemaspy:
+
 Update SchemaSpy
 ----------------
 
-We maintain SchemaSpy at URLs like https://guides.dataverse.org/en/6.3/schemaspy/index.html
+We maintain SchemaSpy at URLs like https://guides.dataverse.org/en/latest/schemaspy/index.html and (for example) https://guides.dataverse.org/en/6.6/schemaspy/index.html
 
 Get the attention of the core team and ask someone to update it for the new release.
 
 Consider updating `the thread <https://groups.google.com/g/dataverse-community/c/f95DQU-wlVM/m/cvUp3E9OBgAJ>`_ on the mailing list once the update is in place.
 
+See also :ref:`schemaspy`.
+
 Alert Translators About the New Release
 ---------------------------------------
 

doc/sphinx-guides/source/developers/testing.rst

@@ -477,25 +477,6 @@ reduced anyway.
 
 You will obviously have to utilize caching functionality of your CI service or do proper Docker layering.
 
-The Phoenix Server
-~~~~~~~~~~~~~~~~~~
-
-How the Phoenix Tests Work
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-A server at http://phoenix.dataverse.org has been set up to test the latest code from the develop branch. Testing is done using chained builds of Jenkins jobs:
-
-- A war file is built from the latest code in develop: https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-build-develop/
-- The resulting war file is depoyed to the Phoenix server: https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-deploy-develop/
-- REST Assured Tests are run across the wire from the Jenkins server to the Phoenix server:  https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-apitest-develop/
-
-How to Run the Phoenix Tests
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-- Take a quick look at http://phoenix.dataverse.org to make sure the server is up and running Dataverse. If it's down, fix it.
-- Log into Jenkins and click "Build Now" at https://build.hmdc.harvard.edu:8443/job/phoenix.dataverse.org-build-develop/
-- Wait for all three chained Jenkins jobs to complete and note if they passed or failed. If you see a failure, open a GitHub issue or at least get the attention of some developers.
-
 Accessibility Testing
 ---------------------
 

doc/sphinx-guides/source/developers/tips.rst

@@ -143,14 +143,20 @@ pgAdmin
 
 If you followed the :doc:`classic-dev-env` section, we had you install pgAdmin, which can help you explore the tables and execute SQL commands. It's also listed in the :doc:`tools` section.
 
+.. _schemaspy:
+
 SchemaSpy
 ~~~~~~~~~
 
 SchemaSpy is a tool that creates a website of entity-relationship diagrams based on your database.
 
-We periodically run SchemaSpy and publish the output: https://guides.dataverse.org/en/6.2/schemaspy/index.html
+As part of our release process (:ref:`update-schemaspy`), we run SchemaSpy and publish the output at https://guides.dataverse.org/en/latest/schemaspy/index.html and (for example) https://guides.dataverse.org/en/6.6/schemaspy/index.html
+
+To run SchemaSpy locally, you can try something like this (after downloading the jars from https://github.com/schemaspy/schemaspy/releases and https://jdbc.postgresql.org/download/):
+
+``java -jar /tmp/schemaspy-6.2.4.jar -t pgsql -host localhost -db dvndb -u postgres -p secret -s public -dp /tmp/postgresql-42.7.5.jar -o /tmp/latest``
 
-To run SchemaSpy locally, take a look at the syntax in ``scripts/deploy/phoenix.dataverse.org/post``.
+See also :ref:`db-name-creds`.
 
 Deploying With ``asadmin``
 --------------------------
@@ -246,10 +252,9 @@ See also discussion of version numbers in :ref:`run-build-create-war`.
 Sample Data
 -----------
 
-You may want to populate your **non-production** Dataverse installations with sample data. You have a couple options:
+You may want to populate your **non-production** Dataverse installations with sample data.
 
-- Code in https://github.com/IQSS/dataverse-sample-data (recommended). This set of sample data includes several common data types, data subsetted from production datasets in dataverse.harvard.edu, datasets with file hierarchy, and more.
-- Scripts called from ``scripts/deploy/phoenix.dataverse.org/post``.
+https://github.com/IQSS/dataverse-sample-data includes several common data types, data subsetted from production datasets in dataverse.harvard.edu, datasets with file hierarchy, and more.
 
 Switching from Glassfish to Payara
 ----------------------------------

doc/sphinx-guides/source/installation/installation-main.rst

@@ -196,7 +196,7 @@ Rerun Installer
 
 With all the data cleared out, you should be ready to rerun the installer per above.
 
-Related to all this is a series of scripts at https://github.com/IQSS/dataverse/blob/develop/scripts/deploy/phoenix.dataverse.org/deploy that Dataverse Project Team and Community developers use have the test server http://phoenix.dataverse.org rise from the ashes before integration tests are run against it. For more on this topic, see :ref:`rebuilding-dev-environment` section of the Developer Guide.
+For more on this topic, see :ref:`rebuilding-dev-environment` section of the Developer Guide.
 
 Getting Support for Installation Trouble
 ----------------------------------------