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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate the publishing of new versions with GitHub Actions CD pipeline #369

Closed
MarkOSullivan94 opened this issue Jun 19, 2022 · 6 comments 路 Fixed by #376
Closed

Automate the publishing of new versions with GitHub Actions CD pipeline #369

MarkOSullivan94 opened this issue Jun 19, 2022 · 6 comments 路 Fixed by #376
Assignees

Comments

@MarkOSullivan94
Copy link
Collaborator

馃挰 Description

As pointed out by @RatakondalaArun there's no CD pipeline in place to automate the publication of new versions of this package: #363 (comment)

Right now, I am essentially a bottleneck and could slow down / delay new versions from being published if I'm unavailable and so it would be great that any new tag starting with v would result in a new version of the package being published to pub.

Resource: https://www.bradcypert.com/dart-packages-with-github-actions/

@RatakondalaArun
Copy link
Collaborator

RatakondalaArun commented Jun 20, 2022

I think it will be better if we could trigger the CD workflow when we publish a new release on GitHub instead of tag push

name: CD

on:
  release:
    types: [published]

cc @bradintheusa

@MarkOSullivan94
Copy link
Collaborator Author

@RatakondalaArun definitely would much rather that!

@bradintheusa
Copy link
Collaborator

I like the new release Idea. That's how I set my projects up and it works well.

@RatakondalaArun
Copy link
Collaborator

@MarkOSullivan94 we also need a CI pipeline for PRs and tests

I can work on the CI pipeline as a separate PR if you are occupied.

as a bonus we can have a code-coverage as well 馃檪 flutter test all_tests.dart --coverage

@MarkOSullivan94
Copy link
Collaborator Author

@RatakondalaArun what CI pipeline are you planning to do?

Migrating the existing one from Travis to GitHub actions?

@RatakondalaArun
Copy link
Collaborator

I didn't notice that there is a Travis CI in place.

I think it's better if we can migrate the CI pipeline to GitHub as well because it can provide better visibility for PR reviews

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