438d19c build: update release files location — heartwood

Radicle Heartwood Protocol & Stack

build: update release files location

✗ CI failure Fintan Halpenny committed 7 months ago

commit 438d19c674f3b0170590f0da1b1ca685023091d3
parent 19210faab807e9163feea8c4ca2d3fe99e00a011

1 failed (1 total) View logs

2 files changed +3 -3

modified build/release

@@ -12,6 +12,7 @@ SSH_KEY="$(rad path)/keys/radicle"

 main() {
   version="$1"
   destination="/var/www/files.radicle.xyz/releases/$version"
   if [ -z "$version" ]; then
     echo "fatal: empty version number" >&2 ; exit 1

@@ -28,7 +29,7 @@ main() {

   case "$confirmation" in
     [Yy]*)
       echo "Creating 'latest' symlink.."
       ssh -i "$SSH_KEY" "$SSH_ADDRESS" ln -snf "/mnt/radicle/files/releases/$version" /mnt/radicle/files/releases/latest ;;
       ssh -i "$SSH_KEY" "$SSH_ADDRESS" ln -snf "$destination/$version" /mnt/radicle/files/releases/latest ;;
     *)
       echo "Operation aborted."
       exit 1 ;;

modified build/upload

@@ -17,7 +17,7 @@ main() {

     echo "fatal: empty version number" >&2 ; exit 1
   fi
   destination="/mnt/radicle/files/releases/$version"
   destination="/var/www/files.radicle.xyz/releases/$version"
   # Create remote folder.
   ssh -i "$SSH_KEY" "$SSH_ADDRESS" mkdir -p "$destination"

@@ -52,7 +52,6 @@ main() {

     fi
   done < build/TARGETS
   # TODO(cloudhead): Don't pass `--tags` when we have canonical refs.
   # Pushes tags without assuming the remote the user is using. It does this by
   # using the pushurl directly, i.e.
   # `rad://z3gqcJUoA1n9HaHKufZs5FCSGazv5/<nid>`, where `<nid>` is the local Node