-
Notifications
You must be signed in to change notification settings - Fork 176
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
Explicitly set version in balena.yml #48
Conversation
hey @vipulgupta2048 how can I re-trigger this now as I am a member of balena-io-examples now |
@shaunmulligan Click the |
Sorry @vipulgupta2048 I am probably being daft, but when I follow the |
@shaunmulligan You are not being daft. Take your time; I wrote the instructions for the button out of memory, it's called re-run jobs. Do you see a If you don't, then maybe send a screenshot or I can trigger it for you |
Okay, I'm now properly part of the membership. For some reason it took me a while to actually find the invite. It wasn't in my notifications or inbox 🙄 |
Hey @vipulgupta2048 It seems something is still missing, managed to re-run things but getting this error:
Do you know what the problem is here? |
@balena-ci I self-certify! |
@vipulgupta2048 I'll actually close this because it looks like the version was added to balena.yml here: 4045ba0#diff-8448e809945865b05ca68634bac731b7197e4631eebe6531f849cb56918e6908 |
If you push the current project without having the version defined, it won't allow you to add it later. There appears to be some issue with caching in the builder, so using
--no-cache
will fix the behaviour, but I think we should add this explicitly so the user can have it working from the start and as its easy to learn from seeing it present in the file.