[sysadmin/ci-tooling] helpers: Don't allow the dependency diagram data generation process to run on secondary platforms either.
Ben Cooksley
null at kde.org
Tue Jan 23 07:41:27 UTC 2018
Git commit 15c5d9a75f87ff5ac78fd8aff2824faa6fdaa349 by Ben Cooksley.
Committed on 23/01/2018 at 07:41.
Pushed by bcooksley into branch 'master'.
Don't allow the dependency diagram data generation process to run on secondary platforms either.
This runs into the same issue that the cmake dependency metadata extraction process did, which I fixed in a603dc47b518eb1f6d94379f19345748ebd7fb3a
CCMAIL: kde-frameworks-devel at kde.org
M +6 -0 helpers/generate-dependency-diagram-data.py
https://commits.kde.org/sysadmin/ci-tooling/15c5d9a75f87ff5ac78fd8aff2824faa6fdaa349
diff --git a/helpers/generate-dependency-diagram-data.py b/helpers/generate-dependency-diagram-data.py
index be5f549..e527151 100755
--- a/helpers/generate-dependency-diagram-data.py
+++ b/helpers/generate-dependency-diagram-data.py
@@ -20,6 +20,12 @@ buildEnvironment = EnvironmentHandler.generateFor( installPrefix=arguments.using
# We'll assume that the directory we're running from is where the sources are located
sourcesLocation = os.getcwd()
+# Are we allowed to run?
+# We only gather this metadata from the principal Linux platform, which at the moment is SUSEQt5.7 for Frameworks and SUSEQt5.9 for everyone else
+if arguments.platform != 'SUSEQt5.7' and arguments.platform != 'SUSEQt5.9':
+ # Then there is nothing for us to do
+ sys.exit(0)
+
# First determine where we the data will be stored, both temporarily and on the server
# As the API documentation can only be generated once, and we have the greatest capacity available for Linux we will use Linux dependency diagrams on api.kde.org.
outputDirectory = os.path.join( sourcesLocation, 'dotdata' )
More information about the Kde-frameworks-devel
mailing list