From 644963255c4e5d90a81e3ebef8cfda6fb24fddce Mon Sep 17 00:00:00 2001 From: Tim McCormack Date: Fri, 30 Oct 2020 09:35:45 -0400 Subject: [PATCH] Move toggle annotation invocation to a Jenkins job (#25484) There wasn't any reason for this to be in edx-platform in particular. See https://github.com/edx/jenkins-job-dsl-internal/pull/444 -- we can run `make requirements; pip install -e .` in a code-annotations virtualenv and point it at each IDA in turn to generate reports for all of them. ARCHBOM-1583 --- scripts/generate-feature-toggle-annotation-report.sh | 12 ------------ 1 file changed, 12 deletions(-) delete mode 100644 scripts/generate-feature-toggle-annotation-report.sh diff --git a/scripts/generate-feature-toggle-annotation-report.sh b/scripts/generate-feature-toggle-annotation-report.sh deleted file mode 100644 index b4d8c87948..0000000000 --- a/scripts/generate-feature-toggle-annotation-report.sh +++ /dev/null @@ -1,12 +0,0 @@ -#!/usr/bin/env bash - -# generate-feature-toggle-annotation-report.sh - -# Generate a code annotations report for feature toggles in the platform. -# This script is part of the feature toggle generator tool. - -pip install -r requirements/edx/paver.txt -r requirements/edx/testing.txt -rm -Rf reports/* -code_annotations static_find_annotations --config_file=../$CODE_ANNOTATION_CONFIG_PATH -mkdir -p ../$SCRIPT_OUTPUT_PATH -cp reports/* ../$SCRIPT_OUTPUT_PATH/lms-annotations.yml