Hi all, tl;dr: * We have been using new Lando at https://lando.moz.tools/ since early 2025. * We are planning to *turn of the old Lando instance on or shortly after 2026-09-07*. * Treestatus's canonical API URL is https://lando.moz.tools/api/treestatus/trees * *Watch out for and update any of those URLs*: https://treestatus.mozilla-releng.net and https://treestatus.prod.lando.prod.cloudops.mozgcp.net. * If you *still rely on **LANDO_TRY_CONFIG when using mach try, please reach out now*.
We migrated to a new version of Lando at https://lando.moz.tools/ in early 2025, ahead to the Git migration. Since then, this is the instance you have been using when following links from Phabricator revisions. The old Lando instance at https://lando.services.mozilla.com/ has however remained in operation. Until recently, it was still supporting pushes to Try, as well as the Treestatus API. We moved Try support to the new instance a couple of months back, and we have just migrated Treestatus over as well. The Treestatus API is now available at https://lando.moz.tools/api/treestatus/trees, with the same data format as before. There is a HTML dashboard at https://lando.moz.tools/treestatus/, too. With all this migrated, the old Lando instance no longer supports any useful traffic, and we are going to turn it off https://bugzilla.mozilla.org/show_bug.cgi?id=2064783. This shouldn't cause any disruption to core services. However, if you have custom tools that rely on the old instance, most likely the Treestatus API, you will have to review them, and make sure to point them to the new API URL. Namely, *you'll need the following changes to base paths*: * https://treestatus.prod.lando.prod.cloudops.mozgcp.net/trees -> https://lando.moz.tools/api/treestatus/trees * https://treestatus.mozilla-releng.net/trees -> https://lando.moz.tools/api/treestatus/trees * https://lando.services.mozilla.com/ -> https://lando.moz.tools/ * https://api.lando.services.mozilla.com/landing_jobs/ -> https://lando.moz.tools/landing_jobs/ Try support is already configured for Firefox in autoland, main and current ESRs, with the exception of ESR115, which pre-dates Lando support. For this one, we recommend the use of a cinnabar tree, and `./mach try --push-to-vcs` to push directly to HgMO. For any other branch, you should be using a Git checkout, and `./mach try` will just do the Right Thing^TM (you may have to rebase your work if you have stacks based on revisions prior to . *If you are still relying on **LANDO_TRY_CONFIG, please reach out now*, so we can assess why you need it, and how we can fix it. As always, if you run into any any issue, please reach out to #conduit on Matrix https://matrix.to/#/#conduit:mozilla.org. Cheers! -- Olivier Mehani [:shtrom] <[email protected]> Please consider the environment before using AI on this email. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/CALm144YfNm5fOYTeJyuwX5QMv_S-Wgj3NCsfSX87YkXF-QmO5Q%40mail.gmail.com.
