Greenhouse automation stuff

Install

git clone [email protected]:tvansteenburgh/greenhouse.git
cd greenhouse
python3 -m venv .venv
source .venv/bin/activate
pip install selenium

If you are using Chrome you'll need to install the appropriate version of ChromeDriver for your browser, see https://chromedriver.chromium.org/downloads.

Duplicate job posts to different locations

Start with a Greenhouse job with one job posting (the one that will be duplicated).

Get the numeric id for the job. You can get this by going to the job dashboard and copying the id out of the url. It will look something like this:

https://canonical.greenhouse.io/sdash/1592880

That number at the end of the url is the job id.

Now run the script and tell it which job id(s) you want to update with new job posts, and which regions you want to post in:

[email protected] \
SSO_PASSWORD=mysecretpassword \
./post-job.py 1592880 1726996 --region americas emea

The browser will open and things will happen:

• Script will log you in to Ubuntu SSO and then pause for you to 2fa. If you don't define SSO env vars, the script will pause for you to auth manually. If you don't auth within 60 seconds the script will time out.
• New posts will be created for each city in the region that doesn't already have a post.
• The new posts (and any others that are OFF) will be turned ON (made live on the 'Canonical - Jobs' board).

If the script fails partway through you can safely rerun it, since it won't create a duplicate job post for cities that already have one.

Browsers

Default browser is Chrome but you can alternatively pass the --browser firefox option.

I have only tested on Chrome.

Regions

The available regions are americas, emea, and apac. You can view/update the lists of cities in those regions directly in the source file.

Troubleshooting

The script crashes with an error about element click intercepted.

• The script is trying to 'click' on something, but another element on the page is blocking the click.
• Try making your browser bigger (especially wider). This is most likely the quickest workaround.
• Create an issue with the full error message and I'll fix it if I can.