[ https://issues.jboss.org/browse/JBIDE-20904?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20904 at 4/13/16 12:29 PM: -------------------------------------------------------------- Agreed, but since Jenkins is slow to run (finding a slave on which to run sometimes blocked by other jobs) & slow to config (https = painful), for now I'm just running the script as hudson@dev01 to synthesize the effect of running in jenkins but with more interactivity. Once it's working for not just ci -> stage but also stage -> dev (will have to fake this up with the master branch jobs, I suspect), I can wrap a jenkins job around it. Here are the current staging steps: 0. run quick verification tests: a. does o.j.t.foundation.core have the correct version in it? [Aside: this should be moved to the Central CI job] b. are all the branches correct? c. are all the SHAs in github == SHAs built in Jenkins? 1. disable jobs (now scripted via curl) 2. fire discovery job w/ specific param (again, curl), then disable once the build has started 3a. wget staging script; run with some params passed in (this is 5 + 6 steps for JBT and for JBDS, but the 11 steps can be run in parallel processes) 3b. verify that all the new pages are created correctly (11+ URLs to review, some which need additional time to refresh as devstudio.redhat.com can be fickle about showing new content) - verify content (JBIDE-22173) 4. update composite sites for JBT and JBDS [scripted w/ sed] - verify content (JBIDE-22173) 5. merge in IS content to discovery sites (scripted but needs to know the latest IS site URLs to use as source) - verify content (JBIDE-22173) 6. update ide-config.properties (manual for now but could eventually be scripted w/ sed?) - verify content (JBIDE-22173) 7. re-enable jobs (scripted w/ curl) Then we could fire the smoke tests automatically (p2director, install-grinder) and when those were done, generate the 2 template-based email notifications that the staging was done. Currently we run BYOE tests for JBT and JBDS. I don't believe we have an automated test of the installer + installing all the EA content from Central. - JBIDE-22172 Only thing I can't see a way to do is push the changes on download.jboss.org and devstudio.redhat.com into github. So that would need to be some sort of rsync fetch script + manual review and check-in. Bonus there is that it could be done while the smoke test was underway, and should a bug happen (eg., wrong URL for Central TP site) the fix could be done both in github and pushed back to the server. was (Author: nickboldt): Agreed, but since Jenkins is slow to run (finding a slave on which to run sometimes blocked by other jobs) & slow to config (https = painful), for now I'm just running the script as hudson@dev01 to synthesize the effect of running in jenkins but with more interactivity. Once it's working for not just ci -> stage but also stage -> dev (will have to fake this up with the master branch jobs, I suspect), I can wrap a jenkins job around it. Here are the current staging steps: 0. run quick verification tests: a. does o.j.t.foundation.core have the correct version in it? [Aside: this should be moved to the Central CI job] b. are all the branches correct? c. are all the SHAs in github == SHAs built in Jenkins? 1. disable jobs (now scripted via curl) 2. fire discovery job w/ specific param (again, curl), then disable once the build has started 3a. wget staging script; run with some params passed in (this is 5 + 6 steps for JBT and for JBDS, but the 11 steps can be run in parallel processes) 3b. verify that all the new pages are created correctly (11+ URLs to review, some which need additional time to refresh as devstudio.redhat.com can be fickle about showing new content) 4. update composite sites for JBT and JBDS [scripted w/ sed] 5. merge in IS content to discovery sites (scripted but needs to know the latest IS site URLs to use as source) 6. update ide-config.properties (manual for now but could eventually be scripted w/ sed?) 7. re-enable jobs (scripted w/ curl) Then we could fire the smoke tests automatically (p2director, install-grinder) and when those were done, generate the 2 template-based email notifications that the staging was done. Currently we run BYOE tests for JBT and JBDS. I don't believe we have an automated test of the installer + installing all the EA content from Central. - JBIDE-22172 Only thing I can't see a way to do is push the changes on download.jboss.org and devstudio.redhat.com into github. So that would need to be some sort of rsync script + manual review and check-in. Bonus there is that it could be done while the smoke test was underway, and should a bug happen (eg., wrong URL for Central TP site) the fix could be done both in github and pushed back to the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)