Version the bootstrap.urbit.org boot pill URL #998
Conversation
|
Can this use the meson defined URBIT_VERSION? Line 225 in ba709ca I think it's just #defined as a string constant, judging by https://github.com/urbit/urbit/search?q=URBIT_VERSION
|
|
Oh, good point @ohAitch. Thanks! |
This way, between continuity breaches, we can update the old pills, adding printf's to them that will trigger upon `~zod is not responding` messages such as urbit/arvo@c83fb6e, telling people to pull the latest Vere. And upon breaches, we can update these bootstrap links. This is a simple/hacky yet reasonably effective way to help get more people on the same page as it relates to handling users running different Veres with breaking changes.
|
What's up with the Travis build fail on this merge? The build for the commit itself succeeded, but the PR build failed: https://travis-ci.org/urbit/urbit/builds/390887270?utm_source=github_status&utm_medium=notification See the red X in the master commit list here: |
|
That’s a clever hack, I like it!
…Sent from my iPhone
On Jun 11, 2018, at 4:59 PM, Keaton Dunsford ***@***.***> wrote:
What's up with the Travis build fail on this merge? The build for the commit itself succeeded, but the PR build failed:
https://travis-ci.org/urbit/urbit/builds/390887270?utm_source=github_status&utm_medium=notification
See the red X in the master commit list here:
https://github.com/urbit/urbit/commits/master
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@keatondunsford, the travis build succeeded, the post-build deployment failed with bad github credentials. I'd guess the github API key needs to be rotated, or some credentials got revoked. |
|
I find it plausible that my credentials got revoked :P see travis-ci/travis-ci#2457 (comment): basically, run |
This way, between continuity breaches, we can update the old pills,
adding printf's to them that will trigger upon
~zod is not respondingmessages such as urbit/arvo@c83fb6e,
telling people to pull the latest Vere. And upon breaches, we
can update these bootstrap links. This is a simple/hacky yet reasonably
effective way to help get more people on the same page as it relates to
handling users running different Veres with breaking changes.