New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add static build testing into CI #3668
Comments
Up. Today we noticed that a link in dockerfile returns 404. Therefore static build is now broken https://github.com/tarantool/tarantool/blob/master/Dockerfile.staticbuild#L66 $ curl -L http://download.savannah.nongnu.org/releases/libunwind/libunwind-1.3-rc1.tar.gz
<html>
<head><title>404 Not Found</title></head>
<body bgcolor="white">
<center><h1>404 Not Found</h1></center>
<hr><center>nginx/1.4.6 (Trisquel GNU/Linux)</center>
</body>
</html> |
Up, static build is broken in 2.x again |
Up #4245 |
avtikhon
added a commit
that referenced
this issue
Aug 8, 2019
Added static build using Dockerfile on Centos 7 to release commit criteria only. Also cleaned up the Dockerfile from duplicating code and added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 8, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Also cleaned up the Dockerfile from duplicating code and added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 8, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Also cleaned up the Dockerfile from duplicating code and added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 8, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Also cleaned up the Dockerfile from duplicating code and added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the staic build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 20, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 20, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668
avtikhon
added a commit
that referenced
this issue
Aug 21, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668
Totktonada
pushed a commit
that referenced
this issue
Aug 21, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668 (cherry picked from commit f750918)
Totktonada
pushed a commit
that referenced
this issue
Aug 21, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668 (cherry picked from commit f750918)
Totktonada
pushed a commit
that referenced
this issue
Aug 21, 2019
Added static build using Dockerfile on Centos 7 for release commit criteria only. Added the cleanup for cmake generating CMakeCache.txt files and CMakeFiles directories to avoid of cmake localy created setup failing inside the docker after the whole tarantool path was copied into it. Added testing into the static build, running only when RUN_TESTS environment variable set to non empty value, used in gitlab-ci job to run the testing after the build. Closes #3668 (cherry picked from commit f750918)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: