Upgrade Chrome patch to 50.0.2661.94

Author: elgalu

CHANGELOG.md

@@ -7,6 +7,28 @@ Note image ids also change after scm-source.json has being updated which trigger
 ###### To get container versions
     docker exec grid versions
 
+## TBD_DOCKER_TAG
+ + Date: TBD_DATE
+ + Upgrade Chrome patch to 50.0.2661.94
+ + Image tag details:
+  + Selenium: vTBD_SELENIUM_VERSION (TBD_SELENIUM_REVISION)
+  + Chrome stable:  TBD_CHROME_STABLE
+  + Firefox stable: TBD_FIREFOX_STABLE
+  + Chromedriver: TBD_CHROME_DRIVER (TBD_CHROMEDRIVER_COMMIT)
+  + Java: TBD_JAVA_VENDOR Java TBD_JAVA_BUILD
+  + Timezone: TBD_TIME_ZONE
+  + FROM ubuntu:UBUNTU_FLAVOR-UBUNTU_DATE
+  + Python: TBD_PYTHON_VERSION
+  + Sauce Connect TBD_SAUCE_CONNECT_VERS, build TBD_SAUCE_CONNECT_BUILD TBD_SAUCE_CONNECT_REVISION
+  + BrowserStack Local version TBD_BROWSER_STACK_VERSION
+  + Tested on kernel dev host: 4.4.0-22-generic x86_64
+  + Tested on kernel CI  host: TBD_HOST_UNAME
+  + Built at dev host with: Docker version 1.11.0, build 4dc5990
+  + Built at CI  host with: Docker version TBD_DOCKER_VERS, build TBD_DOCKER_BUILD
+  + Image size: TBD_IMAGE_SIZE
+  + Digest: TBD_DIGEST
+  + Image ID: TBD_IMAGE_ID
+
 ## 2.53.0j
  + Date: 2016-04-27
  + Upgrade Firefox major to 46.0

CONTRIBUTING.md

@@ -11,19 +11,19 @@ For pull requests:
     open ./images/grid_console.png #to verify the versions are correct
     git checkout ./images/grid_console.png && open ./videos/chrome/test.mkv
     travis lint #if you changed .travis.yml
-    git checkout -b tmp-2.53.0j #name your branch according to your changes
+    git checkout -b tmp-2.53.0k #name your branch according to your changes
     #git add ... git commit ... git push ... open pull request
 
 For repository owners only:
 
-    git commit -m "Upgrade Firefox 46 & Ubuntu 20160422. Fixes #83"
+    git commit -m "Upgrade Chrome patch to 50.0.2661.94"
     git tag -d latest #tag latest will be updated from TravisCI
-    git tag 2.53.0j && git push origin tmp-2.53.0j && git push --tags
+    git tag 2.53.0k && git push origin tmp-2.53.0k && git push --tags
 
 -- Wait for Travis to pass OK
 -- Make sure changes got merged into master by elgalubot
 
-    git checkout master && git pull && git branch -d tmp-2.53.0j && git push origin --delete tmp-2.53.0j
+    git checkout master && git pull && git branch -d tmp-2.53.0k && git push origin --delete tmp-2.53.0k
 
 -- Re-add TBD_* section in CHANGELOG.md starting with TBD_DOCKER_TAG
 -- Upgrade release tag in github.com with latest CHANGELOG.md
@@ -34,15 +34,15 @@ For repository owners only:
 ### Chrome artifact
 Keep certain bins if chrome version changed for example:
 
-    VER="50.0.2661.86"
+    VER="50.0.2661.94"
     wget -nv --show-progress -O binaries/google-chrome-stable_${VER}_amd64.deb "https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb"
 
 ## Retry
 Failed in Travis? retry
 
-    git tag -d 2.53.0j && git push origin :2.53.0j
+    git tag -d 2.53.0k && git push origin :2.53.0k
     #git add ...
-    git commit --amend && git tag 2.53.0j && git push --force origin tmp-2.53.0j && git push --tags
+    git commit --amend && git tag 2.53.0k && git push --force origin tmp-2.53.0k && git push --tags
 
 ## Docker push from Travis CI
 Travis [steps](https://docs.travis-ci.com/user/docker/#Pushing-a-Docker-Image-to-a-Registry) involve `docker login` and docker credentials encryptions.

Dockerfile

@@ -764,7 +764,7 @@ RUN mkdir -p ${NORMAL_USER_HOME}/tmp && cd ${NORMAL_USER_HOME}/tmp \
 # TODO: Use Google fingerprint to verify downloads
 #  https://www.google.de/linuxrepositories/
 # Also fix .deb file names with correct version
-RUN  latest_chrome_version_trigger="50.0.2661.86" \
+RUN  latest_chrome_version_trigger="50.0.2661.94" \
   && mkdir -p ${NORMAL_USER_HOME}/chrome-deb \
   && export CHROME_URL="https://dl.google.com/linux/direct" \
   && wget -nv -O \

README.md

@@ -27,10 +27,10 @@ The purpose of this project is to have [Selenium][] running as simple and as fas
 
 1. Pull the image and run the container
 
-        docker pull elgalu/selenium:2.53.0j
+        docker pull elgalu/selenium:2.53.0k
 
         docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
-            -v /dev/shm:/dev/shm -e VNC_PASSWORD=hola elgalu/selenium:2.53.0j
+            -v /dev/shm:/dev/shm -e VNC_PASSWORD=hola elgalu/selenium:2.53.0k
 
 2. Wait until the grid starts properly before starting the tests _(Optional but recommended)_
 
@@ -65,7 +65,7 @@ You can also ssh into the machine as long as `SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa
     docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
       -e SSHD=true \
       -e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
-      -v /dev/shm:/dev/shm elgalu/selenium:2.53.0j
+      -v /dev/shm:/dev/shm elgalu/selenium:2.53.0k
 
 Then
 
@@ -76,7 +76,7 @@ Include `-X` in ssh command if you want to redirect the started GUI programs to
     docker run --rm -ti --name=grid -p=4444:24444 -p=5900:25900 -p=22222:22222 \
       -e SSHD=true -e SSHD_X11FORWARDING=yes \
       -e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" \
-      -v /dev/shm:/dev/shm elgalu/selenium:2.53.0j
+      -v /dev/shm:/dev/shm elgalu/selenium:2.53.0k
 
 Then
 
@@ -94,12 +94,12 @@ Supervisor exposes an http server but is not enough to bind the ports via `docke
 ### Screen size
 You can set a custom screen size at docker run time by providing `SCREEN_WIDTH` and `SCREEN_HEIGHT` environment variables:
 
-    docker pull elgalu/selenium:2.53.0j
+    docker pull elgalu/selenium:2.53.0k
 
     docker run -d --name=grid -p 4444:24444 -p 5900:25900 \
       -v /dev/shm:/dev/shm -e VNC_PASSWORD=hola \
       -e SCREEN_WIDTH=1920 -e SCREEN_HEIGHT=1480 \
-      elgalu/selenium:2.53.0j
+      elgalu/selenium:2.53.0k
 
     docker exec grid wait_all_done 10s
 
@@ -157,7 +157,7 @@ You need to pass the environment variable `-e NOVNC=true` in order to start the
 
     docker run --rm -ti --name=grid -p 4444:24444 -p 5900:25900 \
       -v /dev/shm:/dev/shm -p 6080:26080 -e NOVNC=true \
-      elgalu/selenium:2.53.0j
+      elgalu/selenium:2.53.0k
 
 If the VNC password was randomly generated find out with
 
@@ -230,9 +230,9 @@ There are also additional steps you can take to ensure you're using the correct
 
 You can simply verify that image id is indeed the correct one.
 
-    # e.g. full image id for tag 2.53.0j
+    # e.g. full image id for tag 2.53.0k
     export IMGID="<<Please see CHANGELOG.md>>"
-    if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0j |grep ${IMGID} &> /dev/null; then
+    if docker inspect -f='{{.Id}}' elgalu/selenium:2.53.0k |grep ${IMGID} &> /dev/null; then
         echo "Image ID tested ok"
     else
         echo "Image ID doesn't match"
@@ -242,7 +242,7 @@ You can simply verify that image id is indeed the correct one.
 
 Given docker.io currently allows to push the same tag image twice this represent a security concern but since docker >= 1.6.2 is possible to fetch the digest sha256 instead of the tag so you can be sure you're using the exact same docker image every time:
 
-    # e.g. sha256 for tag 2.53.0j
+    # e.g. sha256 for tag 2.53.0k
     export SHA=<<Please see CHANGELOG.md>>
     docker pull elgalu/selenium@sha256:${SHA}
 
@@ -274,7 +274,7 @@ Host machine, terminal 2:
       -v /dev/shm:/dev/shm \
       -e SCREEN_WIDTH -e SCREEN_HEIGHT -e XE_DISP_NUM \
       -v /tmp/.X11-unix/X${XE_DISP_NUM}:/tmp/.X11-unix/X${XE_DISP_NUM} \
-      elgalu/selenium:2.53.0j
+      elgalu/selenium:2.53.0k
 
 Now when you run your tests instead of connecting. If docker run fails try `xhost +`
 
@@ -296,7 +296,7 @@ ANYPORT=0
 REMOTE_DOCKER_SRV=localhost
 CONTAINER=$(docker run -d -p=0.0.0.0:${ANYPORT}:22222 -p=0.0.0.0:${ANYPORT}:24444 \
     -p=0.0.0.0:${ANYPORT}:25900 -e SCREEN_HEIGHT=1110 -e VNC_PASSWORD=hola \
-    -e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" elgalu/selenium:2.53.0j
+    -e SSH_AUTH_KEYS="$(cat ~/.ssh/id_rsa.pub)" elgalu/selenium:2.53.0k
 
 # -- Option 2.docker run- Running docker on remote docker server like in the cloud
 # Useful if the docker server is running in the cloud. Establish free local ports
@@ -306,7 +306,7 @@ ssh ${REMOTE_DOCKER_SRV} #get into the remote docker provider somehow
 # it acts as a jump host so my public key is already on that server
 CONTAINER=$(docker run -d -p=0.0.0.0:${ANYPORT}:22222 -e SCREEN_HEIGHT=1110 \
     -e VNC_PASSWORD=hola -e SSH_AUTH_KEYS="$(cat ~/.ssh/authorized_keys)" \
-    elgalu/selenium:2.53.0j
+    elgalu/selenium:2.53.0k
 
 # -- Common: Wait for the container to start
 ./host-scripts/wait-docker-selenium.sh grid 7s
@@ -377,7 +377,7 @@ If you git clone this repo locally, i.e. cd into where the Dockerfile is, you ca
 
 If you prefer to download the final built image from docker you can pull it, personally I always prefer to build them manually except for the base images like Ubuntu 14.04.2:
 
-    docker pull elgalu/selenium:2.53.0j
+    docker pull elgalu/selenium:2.53.0k
 
 ### 2. Use this image
 

TBD_DOCKER_TAG.md

@@ -0,0 +1,21 @@
+## TBD_DOCKER_TAG
+ + Date: TBD_DATE
+ + TBD_COMMIT_MSG
+ + Image tag details:
+  + Selenium: vTBD_SELENIUM_VERSION (TBD_SELENIUM_REVISION)
+  + Chrome stable:  TBD_CHROME_STABLE
+  + Firefox stable: TBD_FIREFOX_STABLE
+  + Chromedriver: TBD_CHROME_DRIVER (TBD_CHROMEDRIVER_COMMIT)
+  + Java: TBD_JAVA_VENDOR Java TBD_JAVA_BUILD
+  + Timezone: TBD_TIME_ZONE
+  + FROM ubuntu:UBUNTU_FLAVOR-UBUNTU_DATE
+  + Python: TBD_PYTHON_VERSION
+  + Sauce Connect TBD_SAUCE_CONNECT_VERS, build TBD_SAUCE_CONNECT_BUILD TBD_SAUCE_CONNECT_REVISION
+  + BrowserStack Local version TBD_BROWSER_STACK_VERSION
+  + Tested on kernel dev host: 4.4.0-22-generic x86_64
+  + Tested on kernel CI  host: TBD_HOST_UNAME
+  + Built at dev host with: Docker version 1.11.0, build 4dc5990
+  + Built at CI  host with: Docker version TBD_DOCKER_VERS, build TBD_DOCKER_BUILD
+  + Image size: TBD_IMAGE_SIZE
+  + Digest: TBD_DIGEST
+  + Image ID: TBD_IMAGE_ID

docs/interview.md

@@ -11,6 +11,7 @@ The project aims to provide [Selenium][] inside a [docker][] container.
 The project started while I was in charge of building and maintaining the test automation suite of an [AngularJS][] project at [AppNexus][]. I was also doing DevOps tasks related to the test infrastructure.
 
 The objective was to run the tests headless, different solutions existed for that and there is [PhantomJS][] for example but we needed real browsers like Chrome or Firefox to run our tests on, one reason was to get better test confidence and the other was that [Protractor][] doesn't [play nice][prot-browser-support] with [PhantomJS][].
+Recently [Wallaby.js][] announced they will support [Electron][] as an alternative to [PhantomJS][] because it allows to use the latest Chromium/V8 which might be equivalent to running in Chrome however I haven't looked into that yet.
 
 With [Selenium][], you can always run your tests locally but as soon as your tests runs the browser popping up in your main display can be annoying, you could configure your windows manager to move it automatically to another workspace for example and similar solutions exists but why going into all those troubles if you can just `docker run selenium`.
 
@@ -20,7 +21,7 @@ So back in 2014 the first thing I did was googling "selenium in docker", looked
 
 <h4 id="LONG">How long has it been around?</h4>
 
-It started mid 2014 so almost 2 years, it wasn't maintained consistently all these time but yes lately thanks to my role here at [Zalando][] and the fact that some teams here are using it.
+It started mid 2014 so almost 2 years, it [wasn't maintained consistently][gource] all these time but yes lately thanks to my role here at [Zalando][] and the fact that some teams here are using it.
 
 <h4 id="TESTED">How is it tested? How is being built/deployed?</h4>
 
@@ -69,7 +70,7 @@ Good extensive documentation helps gain users for sure but should always include
 ##### Getting users
 
 A couple of users wrote me they preferred my project because it was well maintained, up to date and issues were addressed quickly (no more than 3 days).
-I can understand that in a huge widely used project like [AngularJS][] you get to see hundreds of [open issues without comments][angular-issues] nor assignee nor labels or 36 issues unattended like I see today [in docker][docker-issues] but some projects that have that huge amount of incoming opened issues and yet you still see them not even labeled, like the author not caring at all, ever.
+I can understand that in a huge widely used project like [AngularJS][] you get to see hundreds of [open issues without comments][angular-issues] nor assignee nor labels or 36 issues unattended like I see today [in docker][docker-issues] but some projects that have that huge amount of incoming opened issues and yet you still see them not even labeled, like the author not caring enough.
 
 ##### Working with contributors
 
@@ -134,3 +135,6 @@ Right now people tend to build long running selenium grids by using the [stock][
 [CI]: https://en.wikipedia.org/wiki/Continuous_integration
 [stock-208]: https://github.com/SeleniumHQ/docker-selenium/issues/208
 [tests]: https://github.com/elgalu/docker-selenium/tree/master/test
+[Wallaby.js]: https://wallabyjs.com
+[Electron]: https://wallabyjs.com/docs/integration/electron.html
+[gource]: ./gource.md

docs/videos.md

@@ -5,14 +5,14 @@
 ### Pull
 Pull image
 
-    docker pull elgalu/selenium:2.53.0j
+    docker pull elgalu/selenium:2.53.0k
 
 ### Run
 Run a new grid
 
     docker run --rm --name=grid -p 4444:24444 -p 5920:25900 \
       -v /dev/shm:/dev/shm -e VNC_PASSWORD=hola \
-      -e VIDEO=true elgalu/selenium:2.53.0j
+      -e VIDEO=true elgalu/selenium:2.53.0k
 
 ### Wait
 Wait for the grid to start