search

agola-io / agola

Agola: CI/CD Redefined
https://agola.io
Apache License 2.0
1.45k stars 117 forks source link

External git repos in workflows #510

Open IngwiePhoenix opened 2 weeks ago

IngwiePhoenix commented 2 weeks ago

Hello there!

GitHub is not the right place for support requests or questions. Please use the Agola Forum

Yes, I am aware. But my topic from nearly half a year ago hadn't been replied to. So, I am trying my luck here now. Apologies!

So I am currently looking for a way to run automated builds within my Kubernetes cluster, so that I may feed finished containers to my RISC-V server, by providing builds that the community hasn't made yet, and also publishing them in the process. However, while reading through the docs top to bottom, I couldn't find a specific bit of information:

Most of the repos I am interested in building for, are not mine. Be it libretro's libretro-super repository that I want to run against a specialized toolchain for jailbroken webOS TVs, building custom docker containers off someone else's WebApp to put my own webserver logic inside or just outright redo the container structure of the Piped API containers to suit my needs - all of them are external, every single one.

How do I configure external repositories and respond to their recent changes with my own tasks?

Let's take this one for instance: https://git.v0l.io/Kieran/snort I have a custom Dockerfile that uses a different HTTP server and can build up-to-date and minimal images. How do I bind this repository to Agola, and make it run the tasks whenever Kieran pushes new changes (bleeding-edge) or makes a new tag ($tag/:latest)?

Thank you and kind regards, Ingwie

sgotti commented 2 weeks ago

@IngwiePhoenix please take a look at https://agola.io/tryit/ it'll explain the steps you should do to configure a gitea oauth2 app, create a remote source and so on. Instead of a local gitea use the one you prefer.