ylqjgm
/
canvas-lms
mirror of https://github.com/instructure/canvas-lms.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
canvas-lms/docker-compose.new-jenkins-...

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

78 lines
2.1 KiB
YAML
Raw Normal View History

spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
# it is intended that this be used exclusive of all other docker-compose.*yml files in CI
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
version: "2.3"
spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
services:
spec: more parallel of docker, better even using the option project-name with docker-compose allows us to have all services separate for each group of tests. test plan: Jenkins passes all build logs are copied out of containers for archiving/test reports run with force-failure flag flag = none closes: CCI-341 Change-Id: I99820f64023dde17a1b75e76bcec2dfe84529e91 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/236029 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Derek Bender <djbender@instructure.com> Reviewed-by: Jacob Powell <spowell@instructure.com> Reviewed-by: Rex Fleischer <rfleischer@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2020-05-02 05:04:18 +08:00
canvas:
spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
links:
- selenium-chrome
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
- canvasrceapi
spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
environment:
Upgrade to Selenium 4 Switches from standalone containers to explicit node+hub config Selenium 4 has some differences in handling stale elements that we should be aware of moving forward closes OUT-4988 flag=none [skip-stages=Flakey Spec Catcher] Test-plan: - make sure screenshots can happen for failures - retrigger a few times and make sure things pass - verify build summaries are intact - verify FSC can still run seleniums - verify local selenium running still works - firefox / chrome / edge where applicable - verify docker selenium running still works - firefox / chrome / edge where applicable Change-Id: I8f2fe5a34d712b5ccd7191bae7a9aeeb6f1f473d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284811 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-10 06:53:07 +08:00
remote_url: http://selenium-hub:4444/wd/hub
spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
browser: chrome
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
RCE_HOST: "http://canvasrceapi"
spec: add wait_for_page_load before the expect Change-Id: I42a8fece2be46012213b0ebc0bf717a40718aa48 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/214365 Tested-by: Jenkins Reviewed-by: Anju Reddy <areddy@instructure.com> QA-Review: Anju Reddy <areddy@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-10-24 00:23:57 +08:00
# these are so we can use prod compiled assets in test environment
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
USE_OPTIMIZED_JS: 'true'
SASS_STYLE: 'compressed'
spec: separate selenium config into selenium.yml most builds do not need selenium container so move the selenium config into it's own yml and only add to env variable when needed. Removed docker-compose-build.sh, add docker-compose build code into the build scripts. closes: CORE-3253 Change-Id: I5698019c69dd8940624589928b8a7d4b65f940a5 Reviewed-on: https://gerrit.instructure.com/206247 Tested-by: Jenkins Reviewed-by: Robert Lamb <rlamb@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-08-22 21:21:41 +08:00
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
canvasrceapi:
update jenkins for canvas-rce-api image Closes LS-1661 flag=none Test Plan: Jenkins selenium runs pass Change-Id: I40b519f232926f97b8afb9c933fe6b461d123d7f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/254458 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Robin Kuss <rkuss@instructure.com>
2020-12-07 22:46:57 +08:00
image: starlord.inscloudgate.net/jenkins/canvas-rce-api
spec: knapsack for selenium Change-Id: I30c0c0006de8779dea1743d6c626022756f05d5a Reviewed-on: https://gerrit.instructure.com/210564 Tested-by: Jenkins Reviewed-by: James Williams <jamesw@instructure.com> Reviewed-by: Rob Orton <rob@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2019-09-11 23:49:35 +08:00
environment:
ECOSYSTEM_KEY: "astringthatisactually32byteslong"
ECOSYSTEM_SECRET: "astringthatisactually32byteslong"
HTTP_PROTOCOL_OVERRIDE: "http"
NODE_ENV: production
PASSENGER_MIN_INSTANCES: 2
PASSENGER_MAX_POOL_SIZE: 6
NGINX_WORKER_CONNECTIONS: 2048
update jenkins for canvas-rce-api image Closes LS-1661 flag=none Test Plan: Jenkins selenium runs pass Change-Id: I40b519f232926f97b8afb9c933fe6b461d123d7f Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/254458 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Robin Kuss <rkuss@instructure.com>
2020-12-07 22:46:57 +08:00
STATSD_HOST: 127.0.0.1
STATSD_PORT: 8125
Spec: add `init: true` to jenkins builds This will allow use to rely upon builtin "tini" functionality without needing to manually invoke it like before. This should ensure that stopping containers is faster across the board. Change-Id: I101770a6ddcf5cdc216b612bde83156d40198127 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/240309 Reviewed-by: Aaron Ogata <aogata@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: James Butters <jbutters@instructure.com> Product-Review: James Butters <jbutters@instructure.com>
2020-06-16 20:52:05 +08:00
init: true
Upgrade to Selenium 4 Switches from standalone containers to explicit node+hub config Selenium 4 has some differences in handling stale elements that we should be aware of moving forward closes OUT-4988 flag=none [skip-stages=Flakey Spec Catcher] Test-plan: - make sure screenshots can happen for failures - retrigger a few times and make sure things pass - verify build summaries are intact - verify FSC can still run seleniums - verify local selenium running still works - firefox / chrome / edge where applicable - verify docker selenium running still works - firefox / chrome / edge where applicable Change-Id: I8f2fe5a34d712b5ccd7191bae7a9aeeb6f1f473d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284811 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-10 06:53:07 +08:00
selenium-hub:
upgrade chromedriver to latest version 120 refs: DE-1673 Change-Id: I2dfc653740f9bdf679a52e2f57a873d9aa188336 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337715 QA-Review: James Butters <jbutters@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Build-Review: Aaron Ogata <aogata@instructure.com> Product-Review: James Butters <jbutters@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-16 23:56:58 +08:00
image: starlord.inscloudgate.net/jenkins/selenium-hub:${HUB_VERSION:-4.16}
Upgrade to Selenium 4 Switches from standalone containers to explicit node+hub config Selenium 4 has some differences in handling stale elements that we should be aware of moving forward closes OUT-4988 flag=none [skip-stages=Flakey Spec Catcher] Test-plan: - make sure screenshots can happen for failures - retrigger a few times and make sure things pass - verify build summaries are intact - verify FSC can still run seleniums - verify local selenium running still works - firefox / chrome / edge where applicable - verify docker selenium running still works - firefox / chrome / edge where applicable Change-Id: I8f2fe5a34d712b5ccd7191bae7a9aeeb6f1f473d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284811 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-10 06:53:07 +08:00
environment:
restore Karma/QUnit tests and re-enable partitioning also: - include tests with .jsx extension - automate partitioning of all QUnit tests - move old Ember-related tests back to their prior suffix - skip tests either consistently failing locally or in Jenkins - sometimes due to lack of maintenance (some weren't running before), or due to different order of running tests - fix some tests - upgrades karma-selenium-grid-launcher to fork which resolves longstanding bug cf. https://github.com/squarebracket/karma-selenium-grid-launcher/issues/4 skips three Gradebook-related test files that consistently hang in Jenkins, cf. EVAL-4267 Change-Id: Ib79f75963f6c4f5544e5dc1b5c31bc58d6c1110c Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/349561 Reviewed-by: Isaac Moore <isaac.moore@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Product-Review: Aaron Shafovaloff <ashafovaloff@instructure.com> Build-Review: James Butters <jbutters@instructure.com>
2024-06-08 01:44:04 +08:00
GRID_BROWSER_TIMEOUT: 5000
Upgrade to Selenium 4 Switches from standalone containers to explicit node+hub config Selenium 4 has some differences in handling stale elements that we should be aware of moving forward closes OUT-4988 flag=none [skip-stages=Flakey Spec Catcher] Test-plan: - make sure screenshots can happen for failures - retrigger a few times and make sure things pass - verify build summaries are intact - verify FSC can still run seleniums - verify local selenium running still works - firefox / chrome / edge where applicable - verify docker selenium running still works - firefox / chrome / edge where applicable Change-Id: I8f2fe5a34d712b5ccd7191bae7a9aeeb6f1f473d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284811 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-10 06:53:07 +08:00
selenium-chrome: &NODE_CHROME
upgrade chromedriver to latest version 120 refs: DE-1673 Change-Id: I2dfc653740f9bdf679a52e2f57a873d9aa188336 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/337715 QA-Review: James Butters <jbutters@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Build-Review: Aaron Ogata <aogata@instructure.com> Product-Review: James Butters <jbutters@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com>
2024-01-16 23:56:58 +08:00
image: starlord.inscloudgate.net/jenkins/selenium-node-chrome:${CHROME_VERSION:-120.0}
Upgrade to Selenium 4 Switches from standalone containers to explicit node+hub config Selenium 4 has some differences in handling stale elements that we should be aware of moving forward closes OUT-4988 flag=none [skip-stages=Flakey Spec Catcher] Test-plan: - make sure screenshots can happen for failures - retrigger a few times and make sure things pass - verify build summaries are intact - verify FSC can still run seleniums - verify local selenium running still works - firefox / chrome / edge where applicable - verify docker selenium running still works - firefox / chrome / edge where applicable Change-Id: I8f2fe5a34d712b5ccd7191bae7a9aeeb6f1f473d Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/284811 Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> Reviewed-by: James Butters <jbutters@instructure.com> QA-Review: Robin Kuss <rkuss@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-10 06:53:07 +08:00
environment: &NODE_CHROME_ENV
SE_EVENT_BUS_HOST: selenium-hub
SE_EVENT_BUS_PUBLISH_PORT: 4442
SE_EVENT_BUS_SUBSCRIBE_PORT: 4443
HUB_PORT_4444_TCP_ADDR: selenium-hub
HUB_PORT_4444_TCP_PORT: 4444
SE_NODE_HOST: selenium-chrome
JAVA_OPTS: '-Dwebdriver.chrome.whitelistedIps='
init: true
links:
- selenium-hub
selenium-chrome2:
<<: *NODE_CHROME
environment:
<<: *NODE_CHROME_ENV
SE_NODE_HOST: selenium-chrome2
selenium-chrome3:
<<: *NODE_CHROME
environment:
<<: *NODE_CHROME_ENV
SE_NODE_HOST: selenium-chrome3
selenium-chrome4:
<<: *NODE_CHROME
environment:
<<: *NODE_CHROME_ENV
SE_NODE_HOST: selenium-chrome4
selenium-chrome5:
<<: *NODE_CHROME
environment:
<<: *NODE_CHROME_ENV
SE_NODE_HOST: selenium-chrome5
selenium-chrome6:
<<: *NODE_CHROME
environment:
<<: *NODE_CHROME_ENV
Additional selenium 4 cleanup flag=none Test-plan: - Jenkins jobs pass - verify no references to docker-compose build context build/docker-compose or docker-compose/selenium-* Change-Id: Ia11e2564490a5713256a70e9b1f3e88d6ebc78e5 Reviewed-on: https://gerrit.instructure.com/c/canvas-lms/+/285944 Reviewed-by: Martin Yosifov <martin.yosifov@instructure.com> Reviewed-by: Aaron Ogata <aogata@instructure.com> Tested-by: Service Cloud Jenkins <svc.cloudjenkins@instructure.com> QA-Review: Brian Watson <bwatson@instructure.com> Product-Review: Brian Watson <bwatson@instructure.com>
2022-02-25 07:56:07 +08:00
SE_NODE_HOST: selenium-chrome6