write validation tests to ensure published content has been correctly published ------------------------------------------------------------------------------- Key: JBIDE-22173 URL: https://issues.jboss.org/browse/JBIDE-22173 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build, install-tests Affects Versions: 4.3.1.CR1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.4.2.AM1 Once we're done running stage.sh, we need a way to automatically review the content has been correctly published. Today, we do this: {code} versionWithRespin=4.3.1.CR1b # a, b, c... tmpfile=/tmp/jbosstools-staging__verify.txt for site in site coretests-site central-site earlyaccess-site discovery.central discovery.earlyaccess; do if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${versionWithRespin}-build-${sitename}/ " >> $tmpfile echo "http://download.jboss.org/jbosstools/mars/staging/updates/${sitename}/${versionWithRespin}/ " >> $tmpfile done for site in browsersim-standalone; do if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi echo "http://download.jboss.org/jbosstools/mars/staging/builds/jbosstools-${versionWithRespin}-build-${sitename}/ " >> $tmpfile done echo "" >> $tmpfile cat $tmpfile firefox `cat $tmpfile` rm -fr $tmpfile # verify changes echo "Check 6 URLs:" firefox \ http://download.jboss.org/jbosstools/mars/staging/updates/discovery.centr... \ http://download.jboss.org/jbosstools/mars/staging/updates/discovery.early... \ http://download.jboss.org/jbosstools/mars/staging/updates/compositeConten... \ http://download.jboss.org/jbosstools/mars/staging/updates/core/compositeC... \ http://download.jboss.org/jbosstools/mars/staging/updates/core/ \ http://download.jboss.org/jbosstools/mars/staging/updates/ {code} or {code} versionWithRespin=9.1.0.CR1b # a, b, c... tmpfile=/tmp/jbosstools-staging__verify.txt for site in central earlyaccess discovery.central discovery.earlyaccess; do if [[ ${site} == "site" ]]; then sitename="core"; else sitename=${site/-site/}; fi echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRespin}-build-${sitename}/ " >> $tmpfile echo "https://devstudio.redhat.com/9.0/staging/updates/${sitename}/${versionWithRespin}/ " >> $tmpfile done echo "https://devstudio.redhat.com/9.0/staging/builds/devstudio-${versionWithRespin}-build-product/ " >> $tmpfile echo "http://www.qa.jboss.com/binaries/RHDS/9.0/staging/builds/devstudio-${versionWithRespin}-build-product/ " >> $tmpfile echo "https://devstudio.redhat.com/9.0/staging/builds/#_____(5_folders_w/_${versionWithRespin}) " >> $tmpfile echo "https://devstudio.redhat.com/9.0/staging/updates/core/#_____(6_zips,_6_sums,_1_folder_w/_${versionWithRespin}) " >> $tmpfile echo "" >> $tmpfile cat $tmpfile firefox `cat $tmpfile` popd >/dev/null rm -fr $tmpfile # verify changes echo "Check 4 URLs:" firefox \ https://devstudio.redhat.com/9.0/staging/updates/discovery.central/${vers... \ https://devstudio.redhat.com/9.0/staging/updates/discovery.earlyaccess/${... \ https://devstudio.redhat.com/9.0/staging/updates/compositeContent.xml \ https://devstudio.redhat.com/9.0/staging/updates/ {code} But ideally we could fetch those pages via curl and sed to check if the content we expect has been correctly published. Need to pseudocode the rules to verify, then figure out how to sed/grep the html to ensure what we need is present. May also need to forgive gently -- try again 3 times at 2 min intervals before raising an alarm.