#48 Add example how to send update with bodhi cmdline tool
Closed 3 months ago by astepano. Opened 3 months ago by astepano.
fedora-docs/ astepano/modularity bodhi_cmdline  into  master

@@ -17,4 +17,30 @@ 

         nodejs-10-20180607142235.6c81f848   <- MODULE_BUILD_ID

  ----

  

- that is removing the "module-" part at the beginning, and replacing the last "-" with a ".". 

\ No newline at end of file

+ that is removing the "module-" part at the beginning, and replacing the last "-" with a ".".

+ 

+ Also you can do the same with help of command line bodhi-client: https://fedoraproject.org/wiki/Bodhi/bodhi-client

+ 

+ ---

+ bodhi updates new --request=testing --notes="Update to 3.0" --type=enhancement --user astepano standard-test-roles-3.0-2820190114142648.9c690d0e

+ Password: <Your FAS password>

+ ================================================================================

+      standard-test-roles-3.0-2820190114142648.9c690d0e

+ ================================================================================

+    Update ID: FEDORA-MODULAR-2019-cee54ead99

+ Content Type: module

+      Release: Fedora 28 Modular

+       Status: pending

+         Type: enhancement

+        Karma: 0

+    Autokarma: False  [-3, 3]

+      Request: testing

+        Notes: Update to 3.0

+    Submitter: astepano

+    Submitted: 2019-01-23 11:14:56

+     Comments: bodhi - 2019-01-23 11:14:56 (karma 0)

+               This update has been submitted for testing by

+               astepano.

+ 

+   https://bodhi.fedoraproject.org/updates/FEDORA-MODULAR-2019-cee54ead99

+ ---

@@ -28,6 +28,40 @@ 

  

  https://release-engineering.github.io/mbs-ui/modules

  

+ == Submitting module build from VM or remote host

+ 

+ +fedpkg module-build+ requires authorization to MBS.

+ Fedora infra uses +OpenID Connect (OIDC)+ authorization for web applications.

+ When +fedpkg+ authorizes to MBS with next steps:

+ 

+ . +fedpkg+ prints to terminal URL, something like:

+ 

+ ---

+ Please visit https://id.fedoraproject.org/openidc/Authorization?scope=openid+https%3A%2F%2Fid.fedoraproject.org%2Fscope%2Fgroups+https%3A%2F%2Fmbs.fedoraproject.org%2Foidc%2Fsubmit-build&response_type=code&client_id=mbs-authorizer&redirect_uri=http%3A%2F%2Flocalhost%3A12345%2F&response_mode=query to grant authorization

+ ---

+ 

+ .You must open it in your Firefox/Chrome/etc..

+ .After auth step your browser will complain with:

+ 

+ ---

+ This site can’t be reached localhost refused to connect.

+ Search Google for localhost 12345

+ ERR_CONNECTION_REFUSED

+ ---

+ 

+ .Your browser at this point in address-line will have URL:

+ 

+ ---

+ http://localhost:12345/?code=7c35ded4-054b-4df0-9151-7ef12c7fb838_xe3JWkvf_sL1UyLOzftHJZ3uIlfOo00N

+ ---

+ 

+ .At this point +fedpkg+ waits on port 12345 of your VM for incoming connection from OpenID IdP (identity provider).

+ .While +fedpkg+ waits for incoming OIDC answer from IdP, imitate it with curl in parallel terminal:

+ 

+ ---

+ $ curl 'http://localhost:12345/?code=7c35ded4-054b-4df0-9151-7ef12c7fb838_xe3JWkvf_sL1UyLOzftHJZ3uIlfOo00N'

+ ---

+ 

  == Rebuild strategies

  

  In case you want to control which packages get rebuilt and which get reused, you can enforce a specific rebuild strategy while submitting a build.

no initial comment

Pull-Request has been closed by astepano

3 months ago