Open Bug 1557741 Opened 4 months ago Updated 14 days ago

Stop building geckodriver as part of the build job

Categories

(Testing :: geckodriver, defect, P3)

defect

Tracking

(Not tracked)

People

(Reporter: whimboo, Unassigned)

References

(Depends on 1 open bug)

Details

Once bug 1534533 is fixed, we can stop building geckodriver as part of the build job. Given that test jobs rely on the geckodriver binary as part of the common tests package, those will have to be updated first to be dependent on the geckodriver-repack job instead.

https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&searchStr=geckodriver-repack

Note that right now this job only runs for Nightly builds of Firefox, which will also change with bug 1534533. By then we will built it for every commit, but only sign the binaries for Nightly builds of Firefox.

Does geckodriver-repack also build? In that case it’s somewhat
misleadingly named.

No, the repack job doesn't build, but I don't see the naming as problematic right now.

I’m confused, where will geckodriver be built then?

Sorry the summary from bug 1534533 was a bit misleading. The build would happen in the toolchain task, if we agree on that. For a while we will run this job in parallel, and then we can remove this repack job.

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