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

Added automated build action #3

Merged
merged 2 commits into from
Dec 21, 2024

Conversation

shaaanuu
Copy link
Contributor

It uses the github's action for building and uploading the builds into the tags section.

currently it contains windows and linux.
macos shows some errors, so i will look into it ( and i don't think it will work without signing the build).

Comment on lines +4 to +7
push:
branches: ["main"]
pull_request:
branches: ["main"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since you are using upload-release-action step, I doubt it will work without a ref to a release. So I think it is better to change to something like on tag creation or on release creation.

Example:

on:
  release:
    types: [published]

@shaaanuu
Copy link
Contributor Author

As far as the main branch contains the files. It will work. Inshallah. I tested it with the forked code. It works there.

@iqfareez
Copy link
Member

As far as the main branch contains the files. It will work. Inshallah. I tested it with the forked code. It works there.

I see, sure it will work. But I feel we should not be creating a new release every time the code is pushed to the branch. Also, the tag value is hardcoded.

Copy link
Member

@iqfareez iqfareez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I will merge it into another branch before merging it to main. To check & test the actions. Thank you

.github/workflows/main.yml Show resolved Hide resolved
uses: svenstaro/upload-release-action@v2
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: build\windows\x64\runner\Release\quran_publisher_desktop.exe
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Flutter Windows app cannot run with only the .exe, it needs .dll files as well.

image

Read detail here: https://docs.flutter.dev/platform-integration/windows/building#building-your-own-zip-file-for-windows

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will check into it

Comment on lines +27 to +29
tag: v1.0-${{ github.run_number }}
overwrite: true
body: "It's beta"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hard-coded value

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

well we could change the tag. We can get the version from pubscpec.yaml. And for body, what you have in mind?

.github/workflows/main.yml Show resolved Hide resolved
@iqfareez iqfareez changed the base branch from main to ci/release-build December 21, 2024 05:20
@iqfareez iqfareez merged commit 0769eb4 into My-Quran-Tajwid:ci/release-build Dec 21, 2024
@iqfareez
Copy link
Member

@shaaanuu Your PR has been merged to main but with minor modification. See it in actions. I want to clean up few things first before we do the first release.

Thank you for your help. 😄 Ohh, and if you're interested, you can try to do CI for build .deb & .rpm package. I tried using https://pub.dev/packages/flutter_distributor but not fully working on my machine (maybe because I'm using WSL)

@shaaanuu
Copy link
Contributor Author

Mine is arch. Even though I tried build it, I can't test it

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

Successfully merging this pull request may close these issues.

2 participants