Call createJob API to create job directly thru db (#46)

* call createJob API to create job directly thru db

* add more details to jobs

* add more details to job

* fix browser name

* update base image

* add framework and platform version

* fix conflict

* upgrade node-saucelabs

* update release BUILD_TAG

Author: tianfeng92

.github/workflows/release.yml

@@ -37,6 +37,9 @@ jobs:
           tags: |
             saucelabs/stt-playwright-jest-node:latest
             saucelabs/stt-playwright-jest-node:${{ steps.prep.outputs.version }}
+          build-args: |
+            BUILD_TAG=${{ steps.prep.outputs.version }}
+
   # TODO: Re-enable this once we start making playwright bundles
   #release-windows-bundle:
     #runs-on: windows-latest
@@ -77,6 +80,7 @@ jobs:
           #asset_path: ./sauce-playwright-win.zip
           #asset_name: sauce-playwright-win.zip
           #asset_content_type: application/zip
+
   release-template-bundle:
     runs-on: ubuntu-latest
     steps:

Dockerfile

@@ -1,4 +1,4 @@
-FROM saucelabs/testrunner-image:v0.1.0
+FROM saucelabs/testrunner-image:v0.1.1
 
 USER root
 
@@ -83,6 +83,8 @@ WORKDIR /home/seluser
 COPY package.json .
 COPY package-lock.json .
 RUN npm ci --production
+ENV PLAYWRIGHT_VERSION=^1.4.1
+
 
 # Playwright caches the downloaded browser by default in ~/.cache/ms-playwright
 # However, running the container in CI may result in a different active user and therefore home folder.
@@ -94,6 +96,10 @@ COPY --chown=seluser:seluser . .
 # Workaround for permissions in CI if run with a different user
 RUN chmod 777 -R /home/seluser/
 
+ENV IMAGE_NAME=saucelabs/stt-playwright-jest-node
+ARG BUILD_TAG
+ENV IMAGE_TAG=${BUILD_TAG}
+
 #==================
 # ENTRYPOINT & CMD
 #==================