playwright/browser_patches/firefox/clean.sh

#!/bin/bash
set -e
set +x

trap "cd $(pwd -P)" EXIT
if [[ ! -z "${FF_CHECKOUT_PATH}" ]]; then
  cd "${FF_CHECKOUT_PATH}"
  echo "WARNING: checkout path from FF_CHECKOUT_PATH env: ${FF_CHECKOUT_PATH}"
else
  cd "$HOME/firefox"
fi

OBJ_FOLDER="obj-build-playwright"
if [[ -d $OBJ_FOLDER ]]; then
  rm -rf $OBJ_FOLDER
fi
devops: build bots should do clean builds 2019-11-23 06:07:39 +03:00			`#!/bin/bash`
			`set -e`
			`set +x`

			`trap "cd $(pwd -P)" EXIT`
devops: support FF_CHECKOUT_PATH to customize browser checkout (#4607) Preamble 1. We're trying to setup a windows-based github self-hosted runner in the playwright-internal repo. 1. Commands on Windows are mandated to have total arguments length less then 32767 characters. 1. On windows, github self-hosted runner framework puts repository checkout at `c:\w\playwright-internal\playwright-internal` 1. Our scripts create a checkout at `c:\w\playwright-internal\playwright-internal\browser_patches\firefox\checkout` 1. One of the scripts in Firefox buildsystem tries to execute a command, passing lots of absolute paths to various webidl's 1. The command fails due to restriction in (2) Problem Firefox build fails since checkout is deeply nested and hits max arg size on windows. Solution This patch introduces a new variable `FF_CHECKOUT_PATH` that is respected by all browser-related scripts. This way we'll be able to checkout firefox to `c:\firefox` and avoid hitting long arguments limit. 2020-12-05 05:46:20 +03:00			`if [[ ! -z "${FF_CHECKOUT_PATH}" ]]; then`
			`cd "${FF_CHECKOUT_PATH}"`
			`echo "WARNING: checkout path from FF_CHECKOUT_PATH env: ${FF_CHECKOUT_PATH}"`
			`else`
devops: move Firefox and WebKit checkouts to $HOME (#9485) This moves default Firefox and WebKit checkouts to $HOME folder, unless browser specific env variables are specified. In other words: - Firefox checkouts goes to `$HOME/firefox` unless there's a `$FF_CHECKOUT_PATH` that specifies a custom location. - WebKit checkout goes to `$HOME/webkit` unless there's a `$WK_CHECKOUT_PATH` that specifies a custom location. With this change, all build bots will now re-use checkouts between builds, which should speed up compilation. 2021-10-14 20:20:06 +03:00			`cd "$HOME/firefox"`
devops: support FF_CHECKOUT_PATH to customize browser checkout (#4607) Preamble 1. We're trying to setup a windows-based github self-hosted runner in the playwright-internal repo. 1. Commands on Windows are mandated to have total arguments length less then 32767 characters. 1. On windows, github self-hosted runner framework puts repository checkout at `c:\w\playwright-internal\playwright-internal` 1. Our scripts create a checkout at `c:\w\playwright-internal\playwright-internal\browser_patches\firefox\checkout` 1. One of the scripts in Firefox buildsystem tries to execute a command, passing lots of absolute paths to various webidl's 1. The command fails due to restriction in (2) Problem Firefox build fails since checkout is deeply nested and hits max arg size on windows. Solution This patch introduces a new variable `FF_CHECKOUT_PATH` that is respected by all browser-related scripts. This way we'll be able to checkout firefox to `c:\firefox` and avoid hitting long arguments limit. 2020-12-05 05:46:20 +03:00			`fi`
devops: build bots should do clean builds 2019-11-23 06:07:39 +03:00
devops: strictly configure build folder for Firefox builds (#1454) This strictly defines Firefox build folder as `obj-build-playwright`. Currently, Firefox build folder encodes current Mac OS version including patch versions, and thus we might end up with multiple different build folders. 2020-03-21 05:24:38 +03:00			`OBJ_FOLDER="obj-build-playwright"`
devops: build bots should do clean builds 2019-11-23 06:07:39 +03:00			`if [[ -d $OBJ_FOLDER ]]; then`
			`rm -rf $OBJ_FOLDER`
			`fi`