-
Notifications
You must be signed in to change notification settings - Fork 17
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
subscribe/listen interface documentation #537
Comments
Hi! I built simple example, but i did shortcut and didn't used cloudevents to parse events properly, still it should work: |
Hello,
Could you please provide me which is your preferred way of receiving events? I assume you want to listen to events outside of pipeline environment. |
You may also want to take a look at a service polling for build events: kernelci/kernelci-pipeline#594 |
@JenySadadia I saw the docs, but they're a bit confusing. For example, what is the channel I should subscribe to? The docs say I'm not sure whether I will try to reuse the kernelci-pipeline or write something else. The main idea is to receive events from the API and not depend on the pipeline instance you're running. @nuclearcat I'll try it. Thank you! |
Atm API is publishing events on 2 channels i.e.
Then I'd recommend using API endpoints directly or |
If you want to create a new channel for instance
I hope this helps. |
@JenySadadia thank you, much appreciated! |
Should I close this issue @mwasilew ? |
Sorry, I forgot to comment. Please close. I think I got all the details I needed. |
The docs (https://kernelci.org/docs/api/#publisher--subscriber-interface) say that
Any client code can subscribe to receive events with an API token
. I tried callingsubscribe
interface, but I didn't manage to receive any events. Could you please provide an example on how to use the interface? I would like to schedule tests to our internal devices. These tests are usually hardware specific and require special setup which I believe doesn't belong to kernelci-core. So the events I'm interested in arebuild completed
for selected kernel trees.The text was updated successfully, but these errors were encountered: