.github/workflows/test_linux.yml

@@ -41,7 +41,7 @@ jobs:
             conda create -n idaes python=3.9 pip psutil
             conda activate idaes
             pip install -r requirements-dev.txt
-            idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/test-release/ --distro ${{ matrix.bin_platform }} --extra petsc'
+            idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/3.4.2/ --distro ${{ matrix.bin_platform }} --extra petsc'
 
       - name: Test IDAES-PSE
         run: |

.github/workflows/test_macos_main.yml

@@ -17,7 +17,7 @@ jobs:
           cd idaes-pse
           git checkout main
           pip install -r requirements-dev.txt
-          idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/test-release/ --extra petsc
+          idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/3.4.2/ --extra petsc
       - name: "Test IDAES-PSE"
         run: |
           cd idaes-pse/idaes

.github/workflows/test_windows_main.yml

@@ -17,7 +17,7 @@ jobs:
           cd idaes-pse
           git checkout main
           pip install -r requirements-dev.txt
-          idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/test-release/ --extra petsc
+          idaes get-extensions --nochecksum --url https://github.com/IDAES/idaes-ext/releases/download/3.4.2/ --extra petsc
       - name: "Test IDAES-PSE"
         shell: cmd
         run: |

doc/build.md

@@ -20,7 +20,9 @@ On Windows, except for one excpetion noted below the git Bash shell can be used.
 4. From the a bash shell run `sh build.sh {flavor}` Replace `{flavor}` with the 
   platform (el7, el8, ubuntu1804, ubuntu2004, ubuntu2204, or windows). On ARM64 
   there is no el7 or windows.
-5. Usually testing is done by GitHub actions and the testing images are built on
+  - **NOTE**: If you are behind certain corporate firewalls/proxies, you will
+    need to add lines to the beginning of the Dockerfiles for your SSL certificates.
+6. Usually testing is done by GitHub actions and the testing images are built on
   DockerHub, but ARM64 is not supported.  If you need to build testing containers,
   go to the test-platform directory and run `sh build.sh {platform}`.  The platform
   argument is slightly differnt than flavor.  For testing it indicates a specific

scripts/compile_solvers.sh

@@ -109,7 +109,7 @@ if [ ${GFMV[0]} -ge 10 ]; then
 fi
 
 # Fetch coin-or stuff and dependencies
-SKIP_PKGS='ThirdParty/Lapack ThirdParty/Blas ThirdParty/glpk ThirdParty/Metis ThirdParty/Mumps'
+SKIP_PKGS='ThirdParty/Lapack ThirdParty/Blas ThirdParty/Glpk ThirdParty/Metis ThirdParty/Mumps'
 bash coinbrew fetch Clp --no-prompt --skip "$SKIP_PKGS"
 bash coinbrew fetch Cbc --no-prompt --skip "$SKIP_PKGS"
 SKIP_PKGS="$SKIP_PKGS Cbc Clp Cgl Osi"
@@ -131,7 +131,7 @@ if [ ${osname} = "el7" ]; then
   # Looks like the only things in therd party are thing that Ipopt gets, so this should be ok.
   rm -rf ./Thirdparty/*
 fi
-bash coinbrew fetch $IPOPT_REPO@$IPOPT_BRANCH --no-prompt --skip 'ThirdParty/Lapack ThirdParty/Blas ThirdParty/glpk'
+bash coinbrew fetch $IPOPT_REPO@$IPOPT_BRANCH --no-prompt --skip 'ThirdParty/Lapack ThirdParty/Blas ThirdParty/Glpk'
 cp -r Ipopt Ipopt_share
 
 # Make sure I don't include any dependencies I don't want