Remove old build instructions

Author: chris-janidlo

RELEASING.md

@@ -161,30 +161,3 @@ run another Jenkins build to push it to live if GCS is not doing a release the s
 
    - https://builds.globus.org/jenkins/view/all/job/Synchronize%20GCSv5%20Stable/build?delay=0sec
      - Leave `SYNC_WHEELS_ONLY` unchecked
-
-#### Old Build Instructions
-
-(Previously) As a temporary workaround, we needed to add a few lines to manually set some
-env variables in our [JenkinsFile](https://github.com/globus/globus-compute/blob/743fa1e398fd40a00efb5880c55e3fa6e47392fc/compute_endpoint/packaging/JenkinsFile#L24) before triggering the build, as detailed below.
-
-1. Notes
-   - Example of unstable repo:
-     - https://downloads.globus.org/globus-connect-server/unstable/rpm/el/9/x86_64/
-
-   - Directory of testing images:
-     - https://builds.globus.org/downloads.globus.org/globus-connect-server/testing/rpm/el/8/x86_64/
-
-   - Stable repo:
-     - The images will be in the below build directory after we finish our build process, but not public:
-       - https://builds.globus.org/downloads.globus.org/globus-connect-server/stable/rpm/el/8/x86_64/
-
-     - After GCS push during deploy day (or if we ping them to do so), the public images will be located at: \* https://downloads.globus.org/globus-connect-server/stable/rpm/el/9/x86_64/
-       [publishResults.groovy line 85](https://github.com/globusonline/gcs-build-scripts/blob/168617a0ccbb0aee7b3bee04ee67940bbe2a80f6/vars/publishResults.groovy#L85)
-
-1. (Access on VPN) Click the [build button here](https://builds.globus.org/jenkins/job/BuildGlobusComputeAgentPackages/build?delay=0sec)
-
-1. Wait 20-30 minutes and confirm that the [build is green](https://builds.globus.org/jenkins/job/BuildGlobusComputeAgentPackages/)
-
-1. For production release, we will have finished the build before the GCS
-   team, and can notify them that our build is complete. They then will
-   publish all packages when they finish their builds, which includes ours.