trigger build and tag on OctoPrint/OctoPrint master/release about octoprint-docker HOT 8 CLOSED

Looks like there's no one perfect way to do this, but several approaches that would probably work:

1. Just set a schedule to watch for releases
2. Use a workflow in the octoprint/octprint project to send a workflow_dispatch or repository_dispatch event on release of octoprint/octoprint, to the octoprint/docker to run specific workflows in specific branches

from octoprint-docker.

May also be able to use the discord bot for octoprint/octoprint to actually trigger workflows in octoprint/docker 🤔 The key is making sure the payload is formatted correctly, and that may actually be easier to do using the discord bot than github itself (github actions really needs the ability to trigger on organization events and not just repository events)

from octoprint-docker.

https://github.community/t/run-action-on-event-in-another-repository/17667

from octoprint-docker.

Yes, the second option works well. I use it at work for several private repos. The one repo they all push the event to just "queues up" the releases. This is better than a polling method IMO as it keeps an order to the queue

I'd offer to help but I'm swamped with face shields for schools at the moment.

from octoprint-docker.

I see that OctoPrint/OctoPrint#3667 is out for review -- are you working on the octoprint/octoprint-docker side of things to handle the event? If not I can take a stab at it

from octoprint-docker.

from octoprint-docker.

@eaceaser sorry for the short reply earlier, I was mobile. I am working on creating a matrix of tags from the same upstream release. I've actually been live-streaming my work as I go (part 1, part 2, but I tend to only work on OctoPrint stuff on the weekends only, and i didn't finish in time last weekend so I'll be wrapping it up friday or saturday.

This has actually inspired me to create a new github action that I call Tagging Strategy (HackerHappyHour/tagging-strategy), that will do what I'm looking to do here.

(Basically, take a release event such as 1.4.1, and produce image tags all pointing to the same digest for 1, 1.4, 1.4.1 and latest, as well as the same tags for any variants. )

I've cloned both OctoPrint and octoprint-docker into the HackerHappyHour org that I own so I can trigger release events from that octoprint fork for testing.

If you want to contribute or collaborate now that you're up to speed, just hop into discord.octoprint.org and say hello to @CHIEFdotJS in the #dev-misc channel and we can figure out how to insert you into this WIP (what fork & branch you can branch from).

from octoprint-docker.

fixed via #59

from octoprint-docker.