kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abu...@apache.org
Subject [kudu] branch branch-1.9.x updated: Change all dependency sources to https
Date Sat, 01 Jun 2019 08:37:47 GMT
This is an automated email from the ASF dual-hosted git repository.

abukor pushed a commit to branch branch-1.9.x
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/branch-1.9.x by this push:
     new fd8c1e9  Change all dependency sources to https
fd8c1e9 is described below

commit fd8c1e923d5688cae5fc44f91325824c408f342b
Author: Attila Bukor <abukor@apache.org>
AuthorDate: Tue May 21 17:55:26 2019 +0200

    Change all dependency sources to https
    
    Some of our scripts and build tools used to pull dependencies using
    unsecured HTTP protocol, changing these to use HTTPS instead for added
    security.
    
    Change-Id: I1cb8b549cacdd1c94fcd0b214433a0827ce23de8
    (cherry picked from commit a78b6517791b32a2410258f5bc1d0fea649d3887)
    Reviewed-on: http://gerrit.cloudera.org:8080/13485
    Reviewed-by: Grant Henke <granthenke@apache.org>
    Tested-by: Attila Bukor <abukor@apache.org>
---
 README.adoc                           | 11 ++++++-----
 build-support/build_source_release.py |  2 +-
 build-support/release/README.adoc     |  4 ++--
 java/buildSrc/build.gradle            |  4 ++--
 java/kudu-jepsen/build.gradle         |  4 ++--
 thirdparty/package-llvm.sh            |  2 +-
 thirdparty/vars.sh                    |  2 +-
 7 files changed, 15 insertions(+), 14 deletions(-)

diff --git a/README.adoc b/README.adoc
index b796721..1c3352f 100644
--- a/README.adoc
+++ b/README.adoc
@@ -18,7 +18,8 @@
 
 == Building and installing Kudu
 
-Follow the steps in the http://getkudu.io/docs/installation.html#_build_from_source[documentation]
+Follow the steps in the
+https://kudu.apache.org/docs/installation.html#build_from_source[documentation]
 to build and install Kudu from source
 
 === Building Kudu out of tree
@@ -141,7 +142,7 @@ $ ctest -R failing-test
 to run just the failed test.
 
 NOTE: For more information on AddressSanitizer, please see the
-http://clang.llvm.org/docs/AddressSanitizer.html[ASAN web page].
+https://clang.llvm.org/docs/AddressSanitizer.html[ASAN web page].
 
 === Running tests with the clang Undefined Behavior Sanitizer (UBSAN) enabled
 
@@ -182,7 +183,7 @@ $ ctest -j8
 
 TSAN may truncate a few lines of the stack trace when reporting where the error
 is. This can be bewildering. It's documented for TSANv1 here:
-http://code.google.com/p/data-race-test/wiki/ThreadSanitizerAlgorithm
+https://code.google.com/p/data-race-test/wiki/ThreadSanitizerAlgorithm
 It is not mentioned in the documentation for TSANv2, but has been observed.
 In order to find out what is _really_ happening, set a breakpoint on the TSAN
 report in GDB using the following incantation:
@@ -294,7 +295,7 @@ This will invoke `docs/support/scripts/make_docs.sh`, which requires
 `asciidoctor` to process the doc sources and produce the HTML documentation,
 emitted to _build/docs_. This script requires `ruby` and `gem` to be installed
 on the system path, and will attempt to install `asciidoctor` and other related
-dependencies into `$HOME/.gems` using http://bundler.io/[bundler].
+dependencies into `$HOME/.gems` using https://bundler.io/[bundler].
 
 === Updating the Kudu web site documentation
 
@@ -436,7 +437,7 @@ once via a target and once via the raw source file. To fix this, simply
delete t
 on writing code, though it may affect your ability to build from within Eclipse.
 
 1. https://cmake.org/pipermail/cmake-developers/2011-November/014153.html
-2. http://public.kitware.com/Bug/view.php?id=15102
+2. https://public.kitware.com/Bug/view.php?id=15102
 
 == Export Control Notice
 
diff --git a/build-support/build_source_release.py b/build-support/build_source_release.py
index 5bf6950..ad53316 100755
--- a/build-support/build_source_release.py
+++ b/build-support/build_source_release.py
@@ -145,7 +145,7 @@ def run_rat(tarball_path):
     return
 
   # TODO: Cache and call the jar from the maven repo?
-  rat_url = "http://central.maven.org/maven2/org/apache/rat/apache-rat/0.12/apache-rat-0.12.jar"
+  rat_url = "https://search.maven.org/remotecontent?filepath=org/apache/rat/apache-rat/0.13/apache-rat-0.13.jar"
 
   tmpdir_path = tempfile.mkdtemp()
   rat_report_result = ''
diff --git a/build-support/release/README.adoc b/build-support/release/README.adoc
index cb24852..7383f06 100644
--- a/build-support/release/README.adoc
+++ b/build-support/release/README.adoc
@@ -21,9 +21,9 @@ Kudu has a script and an excludes file to allow for running RAT on a release
 artifact. You can use the following steps to verify a source tarball.
 
 1. Download a binary artifact of RAT:
-   `wget http://central.maven.org/maven2/org/apache/rat/apache-rat/0.11/apache-rat-0.11.jar`
+   `wget -O apache-rat-0.13.jar https://search.maven.org/remotecontent?filepath=org/apache/rat/apache-rat/0.13/apache-rat-0.13.jar`
 2. Run RAT:
-   `java -jar apache-rat-0.11.jar -x apache-kudu-X.Y.Z.tar.gz > rat-report.xml`
+   `java -jar apache-rat-0.13.jar -x apache-kudu-X.Y.Z.tar.gz > rat-report.xml`
 3. Run the report checker:
    `./build-support/release/check-rat-report.py build-support/release/rat_exclude_files.txt
rat-report.xml`
 
diff --git a/java/buildSrc/build.gradle b/java/buildSrc/build.gradle
index fe3c365..ffe1f68 100644
--- a/java/buildSrc/build.gradle
+++ b/java/buildSrc/build.gradle
@@ -20,8 +20,8 @@
 repositories {
   mavenCentral()
   jcenter()
-  maven { url "http://clojars.org/repo" } // Only used for the clojure plugin below.
-  maven { url "http://repo.spring.io/plugins-release" } // Only used for the propdeps plugin
below.
+  maven { url "https://clojars.org/repo" } // Only used for the clojure plugin below.
+  maven { url "https://repo.spring.io/plugins-release" } // Only used for the propdeps plugin
below.
   maven { url "https://plugins.gradle.org/m2/" }
 }
 
diff --git a/java/kudu-jepsen/build.gradle b/java/kudu-jepsen/build.gradle
index 8b99944..f143e31 100644
--- a/java/kudu-jepsen/build.gradle
+++ b/java/kudu-jepsen/build.gradle
@@ -18,7 +18,7 @@
 apply plugin: "nebula.clojure"
 
 repositories {
-  maven { url "http://clojars.org/repo/" }
+  maven { url "https://clojars.org/repo/" }
 }
 
 dependencies {
@@ -58,4 +58,4 @@ task runJepsen(type: JavaExec) {
 }
 
 // We don't publish kudu-jepsen
-uploadArchives.enabled = false
\ No newline at end of file
+uploadArchives.enabled = false
diff --git a/thirdparty/package-llvm.sh b/thirdparty/package-llvm.sh
index bfc7131..ec25174 100755
--- a/thirdparty/package-llvm.sh
+++ b/thirdparty/package-llvm.sh
@@ -41,7 +41,7 @@
 set -eux
 
 for ARTIFACT in llvm cfe compiler-rt libcxx libcxxabi lld clang-tools-extra; do
-  wget http://releases.llvm.org/$VERSION/$ARTIFACT-$VERSION.src.tar.xz
+  wget https://releases.llvm.org/$VERSION/$ARTIFACT-$VERSION.src.tar.xz
   tar xf $ARTIFACT-$VERSION.src.tar.xz
   rm $ARTIFACT-$VERSION.src.tar.xz
 done
diff --git a/thirdparty/vars.sh b/thirdparty/vars.sh
index fe4cd10..f6f981e 100644
--- a/thirdparty/vars.sh
+++ b/thirdparty/vars.sh
@@ -28,7 +28,7 @@ TP_BUILD_DIR="$TP_DIR/build"
 # This URL corresponds to the CloudFront Distribution for the S3
 # bucket cloudera-thirdparty-libs which is directly accessible at
 # http://cloudera-thirdparty-libs.s3.amazonaws.com/
-CLOUDFRONT_URL_PREFIX=http://d3dr9sfxru4sde.cloudfront.net
+CLOUDFRONT_URL_PREFIX=https://d3dr9sfxru4sde.cloudfront.net
 
 # Third party dependency downloading URL, default to the CloudFront
 # Distribution URL.


Mime
View raw message