Disable plugins autoupdate.

[ivansher]

Please add the configuration option to disable auto-update plug-ins.

[supermarin]

@Zatoichy what's the usecase for that?

[ivansher]

Update (improvement) of some plug-ins led to a disruption of Xcode. In the worst possible moment.

[supermarin]

@Zatoichy would you mind posting which plugins caused the issue?

[ivansher]

For example: MCLog. yuhua-chen/MCLog#9
And something did not give Xcode start.

[supermarin]

Hmm.. I'm not sure how to feel about that.
I think we should shoot for more automation and somehow have a way of testing if Xcode crashes with the new plugins when they're added / updated.

Putting the plugin updates to the users manually seems like a degradation of the service.
@kattrali @jurre thoughts?

[ivansher]

I do not call to remove auto-update. A choice to not be redundant.

[jurre]

Yeah I'm not a fan of disabling auto-update altogether (even by user choice).

Maybe we could let users specify a git tag/commit for specific plugins? Won't work with binary installs though, in that case they might specify a release nr?

[kattrali]

Maybe we could let users specify a git tag/commit for specific plugins? Won't work with binary installs though, in that case they might specify a release nr?

This seems plausible for the alcatrazrc file, if people prefer to lock their plugins to a particular version. Though I'd say it seems like something uncommon enough that it doesn't need new UI, especially since locking versions might hide a different set of unintended behaviors, like plugins going missing between xcode versions because they never updated to the latest version with new UUIDs.

[supermarin]

Yeah makes sense. I think automation is a better answer here,
and if a certain plugin keeps breaking, we should remove it from the list.

On Thu, Mar 19, 2015 at 12:20 PM Delisa Mason notifications@github.com
wrote:

Maybe we could let users specify a git tag/commit for specific plugins?
Won't work with binary installs though, in that case they might specify a
release nr?

This seems plausible for the alcatrazrc file, if people prefer to lock
their plugins to a particular version. Though I'd say it seems like
something uncommon enough that it doesn't need new UI, especially since
locking versions might hide a different set of unintended behaviors, like
plugins going missing between xcode versions because they never updated to
the latest version with new UUIDs.

—
Reply to this email directly or view it on GitHub
#236 (comment).