Skip to content
Snippets Groups Projects
Select Git revision
  • 4ee939224b4f83d1505c2a2b54edf0e69b5101c3
  • master default protected
  • release/beta-qt-202301101210
  • stable
  • release/beta-qt-202211182015
  • release/beta-qt-202211181752
  • release/beta-qt-202211171508
  • release/beta-qt-202211081754
  • release/beta-qt-202211071518
  • release/beta-qt-202210270957
  • release/beta-qt-202210071648
  • release/beta-qt-202209291549
  • release/beta-qt-202209011129
  • release/beta-qt-202208261640
  • release/beta-qt-202208241511
  • release/beta-qt-202208231849
  • release/beta-qt-202208091525
  • release/beta-qt-202207191241
  • release/beta-qt-202207181708
  • release/beta-qt-202207131914
  • release/beta-qt-202207131513
  • android/release_358
  • android/release_357
  • android/release_356
  • android/release_355
  • android/release_354
  • 20221220.0956.79e1207
  • android/release_353
  • android/release_352
  • android/release_350
  • android/release_349
  • android/release_348
  • android/release_347
  • 20221031.1308.130cc26
  • android/release_346
  • android/release_345
  • android/release_344
  • android/release_343
  • android/release_342
  • android/release_341
  • android/release_340
41 results

jami-project

  • Clone with SSH
  • Clone with HTTPS
  • Maxim Cournoyer's avatar
    Maxim Cournoyer authored
    When a packaging target fails to build, deploy the successful builds
    to the repository anyway.
    
    * Jenkinsfile (BUILD_OWN_QT): Remove parameter.  The Qt builds are now
    implicitly made as part of the regular packaging targets.
    (Build packages): Wrap make invocation in a catchError so that the
    stage appears as failed while the build is marked as a success, which
    allows the 'Sign & deploy packages' stage to run despite packaging
    errors.
    
    Change-Id: I5785d154f5e1963aa824576f7f0f62043446456a
    4ee93922
    History
    Name Last commit Last update