Feature #23
closed
Allow factory builds to be triggered from gitlab MRs (and their results retrieved)
100%
Description
The factory should provide an API allowing builds to be triggered from gitlab. Triggers could be commits or merge requests for example.
Updated by Emmanuel Jubera [SAFT] almost 2 years ago
- Subject changed from The factory should provide an API allowing builds to be triggered from gitlab to The factory should provide an API allowing access from gitlab
Updated by Emmanuel Jubera [SAFT] almost 2 years ago
The factory should provide an API allowing builds to be triggered from gitlab. Triggers could be commits or merge requests for example.
Also when RPM tests are completed, the result of the tests should be accessible from gitlab in order to finalize commit or merge request.
Updated by Emmanuel Jubera [SAFT] almost 2 years ago
A first discussion brought up some topics to explore:
- factory backend hooks
- gitlab runners (factory accessible ?)
- rp-cli
Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago
- Priority changed from Normal to High
Updated by Vincent Rubiolo almost 2 years ago
We have reviewed this ticket and are currently discussing adding it into the factory roadmap. Stay tuned.
Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago
- Affects Version/s armel-1.0 added
Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago
- Target version changed from armel-RC 0.11.2 to armel-1.1
Updated by Vincent Rubiolo almost 2 years ago
- Subject changed from The factory should provide an API allowing access from gitlab to Allow factory builds to be triggered from gitlab MRs (and their results retrieved)
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- Assignee changed from Vincent Rubiolo to Armand Bénéteau [Iot.bzh]
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- Status changed from New to In Progress
Updated by Armand Bénéteau [Iot.bzh] over 1 year ago
- % Done changed from 0 to 50
Updated by Armand Bénéteau [Iot.bzh] over 1 year ago
- % Done changed from 50 to 100
- Fix Version/s armel-1.1 added
So, a POC has been done on Iot.bzh side and this is actually already possible. However no documentation existed until now.
The documentation explaining how to do has been merged in master-next today. Therefore, it will be available on the next documentation release, for Armel 1.1.
This is why I put 100% on the progress indicator. I guess we will set the status to "Resolved" when the documentation will be publicly available.
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
This feature is now available (from Factory armel 1.1) and is documented here :
https://docs.redpesk.bzh/docs/en/master/redpesk-factory/docs/introduction-ext-trig.html
Updated by Sebastien Douheret [IoT.bzh] over 1 year ago
- Status changed from In Progress to Resolved
Updated by Emmanuel Jubera [SAFT] about 1 year ago
- Status changed from Resolved to Closed
Test done with feature/29 branch merge.