Lando news: patch conflict detail now available

2021-02-26 Thread Zeid Zabaneh
Greetings everyone, Are you tired of the cryptic, not-so-useful patch conflict messages that Lando normally spits out? If so, you're in luck -- a new feature has just been deployed to Lando that will hopefully provide you with more useful information*. *If not, don't worry, you'll still be able

Re: New system for landing + cancelling landing jobs in Lando

2020-08-04 Thread Zeid Zabaneh
! Zeid On Thu, Jul 16, 2020 at 12:20 PM Zeid Zabaneh wrote: > Greetings everyone, > > The new Lando landing worker system has now been enabled for the below > repositories. This system is part of Lando, and no longer uses the legacy > Autoland-Transplant system. > >-

New system for landing + cancelling landing jobs in Lando

2020-08-04 Thread Zeid Zabaneh
Greetings everyone, The new Lando landing worker system has now been enabled for the below repositories. This system is part of Lando, and no longer uses the legacy Autoland-Transplant system. - phabricator-qa-stage ( https://hg.mozilla.org/automation/phabricator-qa-stage) -

Re: New system for landing + cancelling landing jobs in Lando

2020-08-04 Thread Zeid Zabaneh
that came up. Please let me know if you do experience any unexpected behaviour, or you can directly file a bug <https://bugzilla.mozilla.org/enter_bug.cgi?product=Conduit=Lando> under Conduit::Lando. Regards, Zeid On Fri, Jul 24, 2020 at 1:48 PM Zeid Zabaneh wrote: > Hi all, > >

Re: Lando's "Appropriate token is expired" error

2020-03-09 Thread Zeid Zabaneh
Fri, Mar 6, 2020 at 4:09 PM Zeid Zabaneh wrote: > Greetings everyone, > > A new version of Lando was deployed yesterday around 5:15 PM UTC. This > release included a major version update to the authentication packages, as > well as some API changes in order to support those upda

Lando's "Appropriate token is expired" error

2020-03-09 Thread Zeid Zabaneh
Greetings everyone, A new version of Lando was deployed yesterday around 5:15 PM UTC. This release included a major version update to the authentication packages, as well as some API changes in order to support those updates. Those updates seem to have caused the issue below, and I am looking