Project

General

Profile

Actions
Copy link

Feature #23

closed
EJ AB

Allow factory builds to be triggered from gitlab MRs (and their results retrieved)

Feature #23: Allow factory builds to be triggered from gitlab MRs (and their results retrieved)

Added by Emmanuel Jubera [SAFT] almost 4 years ago. Updated about 3 years ago.

Status:
Closed
Priority:
High
Assignee:
Armand Bénéteau [Iot.bzh]
Target version:
armel-1.1
Start date:
06/02/2022
Due date:
% Done:

100%

Estimated time:
Affects Version/s:
armel-1.0
Fix Version/s:
armel-1.1
Labels:

Description

The factory should provide an API allowing builds to be triggered from gitlab. Triggers could be commits or merge requests for example.

EJ Updated by Emmanuel Jubera [SAFT] almost 4 years ago Actions
Copy link
 #1

  • 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

EJ Updated by Emmanuel Jubera [SAFT] almost 4 years ago Actions
Copy link
 #2

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.

EJ Updated by Emmanuel Jubera [SAFT] almost 4 years ago Actions
Copy link
 #3

A first discussion brought up some topics to explore:

  • factory backend hooks
  • gitlab runners (factory accessible ?)
  • rp-cli

SD Updated by Sebastien Douheret [IoT.bzh] almost 4 years ago Actions
Copy link
 #4

  • Priority changed from Normal to High

VR Updated by Vincent Rubiolo almost 4 years ago Actions
Copy link
 #5

We have reviewed this ticket and are currently discussing adding it into the factory roadmap. Stay tuned.

SD Updated by Sebastien Douheret [IoT.bzh] almost 4 years ago Actions
Copy link
 #6

  • Affects Version/s armel-1.0 added

SD Updated by Sebastien Douheret [IoT.bzh] almost 4 years ago Actions
Copy link
 #7

  • Target version changed from armel-RC 0.11.2 to armel-1.1

VR Updated by Vincent Rubiolo almost 4 years ago Actions
Copy link
 #8

  • 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)

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #9

  • Assignee changed from Vincent Rubiolo to Armand Bénéteau [Iot.bzh]

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #10

  • Status changed from New to In Progress

AB Updated by Armand Bénéteau [Iot.bzh] over 3 years ago Actions
Copy link
 #11

  • % Done changed from 0 to 50

AB Updated by Armand Bénéteau [Iot.bzh] over 3 years ago Actions
Copy link
 #12

  • % 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.

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #13

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

SD Updated by Sebastien Douheret [IoT.bzh] over 3 years ago Actions
Copy link
 #14

  • Status changed from In Progress to Resolved

EJ Updated by Emmanuel Jubera [SAFT] about 3 years ago Actions
Copy link
 #15

  • Status changed from Resolved to Closed

Test done with feature/29 branch merge.

Actions
Copy link

Also available in: PDF Atom