Maamoun TK <[email protected]> writes:
> Debian.remote.s390x:
> image: $CI_REGISTRY/$BUILD_IMAGES_PROJECT:$DEBIAN_BUILD
> before_script:
> - apt-get update -qq
> - apt-get install -qq git
> - 'which ssh-agent || ( apt-get install -qq openssh-client )'
> - eval $(ssh-agent -s)
> - ssh-add <(echo "$SSH_PRIVATE_KEY")
> - mkdir -p ~/.ssh
> - echo -e "Host *\n\tStrictHostKeyChecking no\n\n" > ~/.ssh/config
> script:
> - ssh linux1@IP_ADDRESS "cd nettle && git pull origin s390x --rebase &&
> ./.bootstrap && ./configure --enable-fat && make && make check && exit"
> tags:
> - shared
> - linux
> except:
> - tags
It looks like this hardcodes the branch to test ("s390x"), while the ci
jobs usually runs on all branches. It also doesn't clean up the remote
state between builds.
I wonder if it would be more reliable to run make dist
PACKAGE_VERSION=snapshot on the ci build machine, and copy the resulting
tarball to the remote machine for build and test. The commands run on the
remote machine should unpack the snapshot in a fresh directory, run
configure, make, make check.
Regards,
/Niels
--
Niels Möller. PGP-encrypted email is preferred. Keyid 368C6677.
Internet email is subject to wholesale government surveillance.
_______________________________________________
nettle-bugs mailing list
[email protected]
http://lists.lysator.liu.se/mailman/listinfo/nettle-bugs
