Skip to content
Snippets Groups Projects
Select Git revision
20 results

deploy-packages.sh

Blame
    • Maxim Cournoyer's avatar
      d0e3d621
      Jenkinsfile: Publish release artifacts for release branches. · d0e3d621
      Maxim Cournoyer authored and Maxim Cournoyer's avatar Maxim Cournoyer committed
      Previously, the Jenkinsfile did not publish anything except from the
      repositories: tarballs would not get copied to https://dl.jami.net for
      the nighty and stable channels, and no commit nor tag would be
      published for the release.
      
      This change addresses these shortcomings with the following changes:
      
      1. Tarballs are produced for the nightly and stable channels, and
      organized in a sub-directory matching their channel name.
      2. Release commits are made to their corresponding
      channel (stable/nightly).
      3. Stable releases are also tagged with 'YYYYmmdd.$day_commits_count.$commit_id'.
      
      * Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
      (RING_PUBLIC_KEY_FINGERPRINT): Rename to...
      (JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
      (GIT_USER_EMAIL, SSH_CRED_ID): 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.
      * scripts/deploy-packages.sh (package_snap): Simplify.
      
      Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d
      d0e3d621
      History
      Jenkinsfile: Publish release artifacts for release branches.
      Maxim Cournoyer authored and Maxim Cournoyer's avatar Maxim Cournoyer committed
      Previously, the Jenkinsfile did not publish anything except from the
      repositories: tarballs would not get copied to https://dl.jami.net for
      the nighty and stable channels, and no commit nor tag would be
      published for the release.
      
      This change addresses these shortcomings with the following changes:
      
      1. Tarballs are produced for the nightly and stable channels, and
      organized in a sub-directory matching their channel name.
      2. Release commits are made to their corresponding
      channel (stable/nightly).
      3. Stable releases are also tagged with 'YYYYmmdd.$day_commits_count.$commit_id'.
      
      * Jenkinsfile (SSH_PRIVATE_KEY): Remove variable.
      (RING_PUBLIC_KEY_FINGERPRINT): Rename to...
      (JAMI_PUBLIC_KEY_FINGERPRINT): ... this.
      (GIT_USER_EMAIL, SSH_CRED_ID): 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.
      * scripts/deploy-packages.sh (package_snap): Simplify.
      
      Change-Id: I9008ecc2a4ef9820dbc96e26c966ae72110d897d
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.