Skip to content
Snippets Groups Projects
Select Git revision
  • release/beta-qt-202301101210
  • stable
  • master default protected
  • 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
40 results

deploy-packages.sh

Blame
    • Maxim Cournoyer's avatar
      0739ac22
      Jenkinsfile: Publish release artifacts for release branches. · 0739ac22
      Maxim Cournoyer authored
      Previously, the Jenkinsfile did not publish anything except for the
      repositories: the release tarball would not get copied to
      https://dl.jami.net for stable channel, and no commit nor tag would be
      published for the release.
      
      This change addresses these shortcomings with the following changes:
      
      1. Tarballs can be published for the stable channel.
      2. Release commits/tags can be published to their corresponding
      branch (stable/nightly).
      
      The RELEASE_VERSION string is also once again derived in a
      deterministic fashion, from the date of the last commit.
      
      * Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
      (RING_PUBLIC_KEY_FINGERPRINT): Rename to...
      (JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
      (GIT_USER_EMAIL, GIT_USER_NAME, GIT_PUSH_URL)
      (JENKINS_SSH_KEY, DL_SSH_KEY): New variables.
      (params.DEPLOY): Fix description.
      (Checkout channel branch): New stage.
      (Generate release tarball): Also commit and tag.
      (Publish release artifacts): New stage to publish conditionally based on the
      DEPLOY parameter and the selected channel.
      (Sign & deploy packages): Use the 'sshagent' step to setup SSH access.
      <--remote-ssh-identity-file>: Remove argument.
      <--keyid>: Adjust variable name.
      * scripts/deploy-packages.sh (package_snap): Simplify.
      
      Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d
      Jenkinsfile: Publish release artifacts for release branches.
      Maxim Cournoyer authored
      Previously, the Jenkinsfile did not publish anything except for the
      repositories: the release tarball would not get copied to
      https://dl.jami.net for stable channel, and no commit nor tag would be
      published for the release.
      
      This change addresses these shortcomings with the following changes:
      
      1. Tarballs can be published for the stable channel.
      2. Release commits/tags can be published to their corresponding
      branch (stable/nightly).
      
      The RELEASE_VERSION string is also once again derived in a
      deterministic fashion, from the date of the last commit.
      
      * Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
      (RING_PUBLIC_KEY_FINGERPRINT): Rename to...
      (JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
      (GIT_USER_EMAIL, GIT_USER_NAME, GIT_PUSH_URL)
      (JENKINS_SSH_KEY, DL_SSH_KEY): New variables.
      (params.DEPLOY): Fix description.
      (Checkout channel branch): New stage.
      (Generate release tarball): Also commit and tag.
      (Publish release artifacts): New stage to publish conditionally based on the
      DEPLOY parameter and the selected channel.
      (Sign & deploy packages): Use the 'sshagent' step to setup SSH access.
      <--remote-ssh-identity-file>: Remove argument.
      <--keyid>: Adjust variable name.
      * scripts/deploy-packages.sh (package_snap): Simplify.
      
      Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.