[Meta] Make the Treeherder contributing experience less painful

ASSIGNED
Assigned to

Status

enhancement
P2
normal
ASSIGNED
2 years ago
21 days ago

People

(Reporter: emorley, Assigned: kthiessen)

Tracking

(Depends on 3 bugs, {meta})

Details

(Reporter)

Description

2 years ago
Rewind a year ago and contributing to Treeherder was much simpler. Install vagrant/virtualbox, run `vagrant up` and you're pretty much ready to go.

However now that we have to build the UI for it to work at all (due to the use of JSX; bug 1336556), the workflow is more complex, more error prone, not as well documented and some things just don't work.

For example:
* to do front-end only development you have to appease yarn's engines check (ie have the correct version of node installed), otherwise it gives an annoying error (bug 1416257)
* to do full stack development, you have to juggle both `yarn start` and `./manage.py runserver` and know which port to use to actually view the thing
* login doesn't work in many combinations and you have to read to docs to figure out which (bug 1363722, 1317752)
* source maps aren't working, so debugging the site in the browser is a pain
* `yarn start` in vagrant doesn't auto-reload since it's not using the poll option
* building and running `yarn start` take ages
* (until recently) it wasn't possible to run the new JS/selenium tests in the vagrant instance because firefox/geckodriver wasn't installed (bug 1340305)
* Pulse ingestion doesn't work without having created an account manually on pulse.m.o and adding the credentials to the vagrant environment
* ...and so on

We really must make Treeherder development painless again.
(Reporter)

Comment 1

2 years ago
Oh and also in the last year or two:
* more and more jobs are moving from buildbot to taskcluster, so the buildbot only `ingest_pulse` is less useful
* Vagrant seems to be increasingly unreliable, whilst Docker is looking more and more polished
Assignee: nobody → emorley
Depends on: 1169263
(Reporter)

Updated

a year ago
Depends on: 1417099
(Reporter)

Updated

a year ago
Depends on: 1418956
(Reporter)

Updated

a year ago
Depends on: 1418982
(Reporter)

Updated

a year ago
Depends on: 1419167
(Reporter)

Updated

a year ago
Depends on: 1419168
(Reporter)

Updated

a year ago
Depends on: 1420941
(Reporter)

Updated

a year ago
Depends on: 1421241
(Reporter)

Updated

a year ago
Depends on: 1421327
(Reporter)

Updated

a year ago
Depends on: 1429988
(Reporter)

Updated

a year ago
Depends on: 1056052
(Reporter)

Updated

11 months ago
Depends on: 1461649
(Reporter)

Updated

11 months ago
Depends on: 1364045
(Reporter)

Updated

11 months ago
Blocks: 1166905
(Reporter)

Updated

10 months ago
Depends on: 1468573
(Reporter)

Updated

9 months ago
Depends on: 1466084
(Reporter)

Updated

9 months ago
Depends on: 1478711
(Reporter)

Updated

8 months ago
Depends on: 1484192
(Reporter)

Updated

6 months ago
Depends on: 1502306
(Reporter)

Updated

3 months ago
Depends on: 1451483
(Reporter)

Updated

2 months ago
Assignee: emorley → nobody
(Reporter)

Updated

2 months ago
Depends on: 1530206
(Reporter)

Updated

2 months ago
Depends on: 1530965
(Reporter)

Updated

2 months ago
No longer depends on: 1451483
(Assignee)

Updated

2 months ago
Assignee: nobody → kthiessen
Status: NEW → ASSIGNED
Priority: P3 → P2

This is something Armen and I will be looking at in 2019Q2.

You need to log in before you can comment on or make changes to this bug.