-
Notifications
You must be signed in to change notification settings - Fork 10
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
Automate reporting when experimental builds are created by having CI post to an optional open PR/ticket #50
Comments
Hints: Looks like we need a Personal Access Token + leveraging the |
So you would like those same comments that are posted on the PR in FreeCAD-snap to be posted to some user-specified issue/PR in FreeCAD/FreeCAD, correct? In that case: yes, you'd need a PAT. |
@luzpaz do you want to take a crack at it? |
I'll try doing so this week. |
|
Spent sometime researching this and it's out of my scope ATM. Anyone free to take this over? |
Thanks to the work of ppd, we now have a more streamlined approach to build experimental builds and test them comfortably.
Re: https://github.com/FreeCAD/FreeCAD-snap/blob/master/docs/index.md#build-snaps-from-freecad-branches-or-forks
It would be sweet if we could also functionality (add a field to the snap.yaml) that would automate posting the instructions on how to install experimental snaps to a specific ticket or PR. Currently the instructions are posted to the PR that triggers the builds, but someone needs to manually post said instructions elsewhere. I remember that TravisCI has this option where you could specify it to connect to an IRC channel and post it's results. Can we do something less fancy by just posting an open ticket/PR ?
The text was updated successfully, but these errors were encountered: