Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

autoupdater: if selected branch is not in selectbox, show empty selection #201

Open
rubo77 opened this issue Oct 17, 2018 · 4 comments
Open

Comments

@rubo77
Copy link
Contributor

rubo77 commented Oct 17, 2018

If a node has a value for branch in the config that is not in the list of autoupdater mirrors from site.conf, then the selectbox is mislieadingly showing the first option as selected.

In that case, it should either show an empty selection or better, show the stored selection as new added option to the selectbox.

@neocturne
Copy link
Member

Hmm, I think it would be a better idea to ensure that the default branch always exists. That way, the broken configuration you mention can not occur (unless you manually break it using uci).

@rubo77
Copy link
Contributor Author

rubo77 commented Oct 17, 2018

problem is, that there is no warning, that something is wrong. and especially, if the first entry is the same entry as the one, you expect, then you never notice, because the page in config mode shows something, that is not there.

there should be a warning like

"Warning! The node is on autoupdater branch 'XY' which is not in the list"

Or better: during the build process, you should stop with an error if you try to build on a branch, that is not listed in the mirrors list in site.conf.

It is easy to prevent this from happening, if you call the build command by hand, but there are several steppingstones:

  • a typo like make GLUON_BRANCH=experimentell statt experimental
  • if you use a CI with a build script, that generates the commands

Also, you will see, if a branch is abandoned, and your node still is on an old branch that doesn't exist any more

@rotanid
Copy link
Member

rotanid commented Oct 18, 2018

as we never support custom modifications, the change in config mode shouldn't be necessary.

i'm not sure, if your case of a typo during build should be checked by the build scripts...

@rubo77
Copy link
Contributor Author

rubo77 commented Oct 18, 2018

I just had no typo, our problem was, that I noticed, that our beta firmware "rc" had "release-candidate" stored as branch in the config, which is not in the list. Created by our "intelligent" ci

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants