Not dumb at all. Right now we don't store the output of the build as we have limited of that in GitHub Actions. This is more to prevent if we make mistakes and break, so it's not possible to build at all. If you want to be able to get the output file from iOS and Android you can add this to your workflow which will let you store the actual files. Not sure if you can just copy paste this but should work. - name: Upload iPA uses: actions/upload-artifact@master with: name: ios-build path: build/ios/iphoneos - name: Upload APK uses: actions/upload-artifact@master with: name: apk-build path: build/app/outputs/apk/release
I never really understood how to use GitHub actions, and this explained it so well, that now I think I'm a pro! Great video! Also i know there is a way to do CD on github actions with Fastlane (i think?). A video on that would be awesome as well 😊
Thanks! Yes that is indeed possible, right now I have not dived in to it with GitHub Actions but instead doing that part with Codemagic. Will for sure do this in the future though!
@@tadaspetra Nope I usually trigger my deployments manually on Codemagic or on Tag. Prefer pressing the button myself when I want to deploy most of the times!
Very informative. Thank you! Please consider a tutorial on Flutter app flavors (for e.x : Prod, Dev, QA), it would pair up with this tutorial nicely :D
Hi Robert, thank you for the great videos. We need a complete testing video for Provider, Mobx structure with unit, widget, integration testing and every other thing related to testing Flutter with Provider and MobX. Everyone is talking about how to build cool stuff but there is no testing tutorial. Thank you.
is there a way to push the final release apks to another branch on the same repo?? like there is an automatic action to deploy web apps to github pages via gh-pages branch so I was wondering if there was something similar for uploading apks
@RobertBrunhage Great Tutorial. I am implementing this for the first time and i do have one question here that i am using Intl and Jsonserializable which create generated folder in developer mode and just because it's use on developer mode only i didnt push and this generated folder to git which is best practice i guess. But when i automate build it's giving an error jus because this path won't be found so what is the solution here and the correct way ??
Hello can you do a tutorial for building for windows and adding it in releases section and also make it so that workflow can only be triggered manually?
I am DevOps, and it's the first time I'm dealing with flutter. I keep getting an error during the flutter build apk, which is basically main.dart not found. I've updated the pubspec.yaml, and the gradle file to point to the lib folder. Any ideas
I would recommend general reading on CI/CD. I use flutter actions for what I showed in the video and also showing code coverage for my tests. Then I prefer using codemagic for publishing just because it's so easy to set up! So if anything I would recommend checking out codemagic for publishing the app to play and app store in very easy steps!
@@vincent-thomas Beror på skulle jag säga, jag är väldigt för trunk-based men github-flow är snarlikt det också. Viktigast för mig är att branches är korta, oftast där det dyker upp problem. Gör det som är så simpelt som möjligt och ta det som det kommer (ifall man stöter på problem kan man kolla andra lösningar)
@@RobertBrunhage Det känns nästan som att gitflow är samma sak som trunk-based, fast brancherna är kortare. Vad är skillnaden ( om man bortser från 'hotfix' och 'release' brancher )?
Robert, great video! (maybe dumb) question: where are the binaries located once you build them? Thanks!
Not dumb at all. Right now we don't store the output of the build as we have limited of that in GitHub Actions. This is more to prevent if we make mistakes and break, so it's not possible to build at all.
If you want to be able to get the output file from iOS and Android you can add this to your workflow which will let you store the actual files. Not sure if you can just copy paste this but should work.
- name: Upload iPA
uses: actions/upload-artifact@master
with:
name: ios-build
path: build/ios/iphoneos
- name: Upload APK
uses: actions/upload-artifact@master
with:
name: apk-build
path: build/app/outputs/apk/release
@@RobertBrunhage Great stuff, exactly what I was looking for.
@@RobertBrunhage Hi, where to put this?
@@Apoorvpandey i think you should put this under the build code
@@RobertBrunhage so I can build ios app without having a mac 😛
A lot of Fireship vibes in your videos. Great work, keep em comin!
I never really understood how to use GitHub actions, and this explained it so well, that now I think I'm a pro! Great video! Also i know there is a way to do CD on github actions with Fastlane (i think?). A video on that would be awesome as well 😊
Thanks!
Yes that is indeed possible, right now I have not dived in to it with GitHub Actions but instead doing that part with Codemagic.
Will for sure do this in the future though!
@@RobertBrunhage Awesome! Do you link codemagic to GitHub Actions?
@@tadaspetra Nope I usually trigger my deployments manually on Codemagic or on Tag.
Prefer pressing the button myself when I want to deploy most of the times!
Robert Brunhage got it! Honestly that’s probably easier unless you work with a team!
Very informative. Thank you!
Please consider a tutorial on Flutter app flavors (for e.x : Prod, Dev, QA), it would pair up with this tutorial nicely :D
Great suggestion, will think about it!
+1
Hi Robert, thank you for the great videos. We need a complete testing video for Provider, Mobx structure with unit, widget, integration testing and every other thing related to testing Flutter with Provider and MobX. Everyone is talking about how to build cool stuff but there is no testing tutorial. Thank you.
Very nice. Very very nice. Thank you for sharing.
Amazing work!!!
Can you show how to deploy to store on the final job on GitHub?
Thank you very much. This video helped greatly!
Excellently Demonstrated
Thanks!
AWESOME content! It's my first time studying about CI
Damn this video is insane! Can't describe by words how useful your job is ❤️❤️❤️
Thank you so much and I am so happy you found the video helpful! 😊
Amazing video
Thanks so much learnt a lot
Amazing job keep doing it brother 🙌
Thanks!
Awesome content, thanks for you job and shared your knowledge.
Glad you enjoyed it!
Wow.. awesome content and good explanation...
Thanks a lot 😊
is there a way to push the final release apks to another branch on the same repo?? like there is an automatic action to deploy web apps to github pages via gh-pages branch so I was wondering if there was something similar for uploading apks
Where is the apk of the build gets stored at ? how to tell it to upload it on google drive or something ?
@RobertBrunhage Great Tutorial.
I am implementing this for the first time and i do have one question here that i am using Intl and Jsonserializable which create generated folder in developer mode and just because it's use on developer mode only i didnt push and this generated folder to git which is best practice i guess. But when i automate build it's giving an error jus because this path won't be found so what is the solution here and the correct way ??
Hi! Can you please do a video on GitHub Actions + Fastlane?
Thanks a lot🎉
Should have covered where the builds have gone and how we can use them.
Check the pinned comment!
Thanks bruh❤
How to push the ios app build to testflight through github actions ?
Please make video on continouse delivery too...
Will do!
Merci very helpful
thank's it was helpful
Hello can you do a tutorial for building for windows and adding it in releases section and also make it so that workflow can only be triggered manually?
Hi bro...ur videos are really very good... i never thought i could understand github actions so easily
Thanks so much and glad you finally understood it!
Check the pinned comment, regarding the files
Hi Robert,
Is this feature available all developers or is this a paid version for GITHUB
This is free for everyone. If you have a private repo you have limited build minutes and for public you have infinite!
I am DevOps, and it's the first time I'm dealing with flutter. I keep getting an error during the flutter build apk, which is basically main.dart not found. I've updated the pubspec.yaml, and the gradle file to point to the lib folder. Any ideas
can we deploy api made with dart on github ?
Can you please show, how can we use environment variables with it?
Hi Robert.
How can I deploy to play store and app store with github actions?
A bit more tricky but look in to this: gist.github.com/rodydavis/bde9a9a8c2fcdcf3474c0f50248f2e3a
How can I learn more about CI/CD as a mobile dev in flutter ...please cos I nust love this easy steps
I would recommend general reading on CI/CD.
I use flutter actions for what I showed in the video and also showing code coverage for my tests.
Then I prefer using codemagic for publishing just because it's so easy to set up!
So if anything I would recommend checking out codemagic for publishing the app to play and app store in very easy steps!
my case show this
git st
git: 'st' is not a git command. See 'git --help'.
The most similar commands are
status
reset
stage
stash
Im pretty sure its just a shortcut he made for git status
How to get apk link, ipa link
Want to get github job run time (total time job spent)
Sverige accent for sure.
How to solve error
Flutter users should run `flutter pub get` instead of `pub get`.
Du måste vara svensk va? 😊
japp 😊
Schysst! 😄
Jag funderar på vilken `branching` teknik jag ska använda. Antingen trunk based development, gitflow eller githubflow. Vad tycker du är bäst?
@@vincent-thomas Beror på skulle jag säga, jag är väldigt för trunk-based men github-flow är snarlikt det också.
Viktigast för mig är att branches är korta, oftast där det dyker upp problem.
Gör det som är så simpelt som möjligt och ta det som det kommer (ifall man stöter på problem kan man kolla andra lösningar)
@@RobertBrunhage Det känns nästan som att gitflow är samma sak som trunk-based, fast brancherna är kortare. Vad är skillnaden ( om man bortser från 'hotfix' och 'release' brancher )?
Workflow should have failed but it passed