Removed testStatus

Author: StuartWheater

azure-pipelines.yml

@@ -3,11 +3,9 @@
 # Starts with a vanilla Opal docker composition, installs dsBase
 # and dsBaseClient (as well as dependencies - including a fully functional
 # Opal server).
-# Does checks and tests then saves results to testStatus repo.
 #
 # Inside the root directory $(Pipeline.Workspace) will be a file tree like:
 # /dsBaseClient               <- Checked out version of datashield/dsBaseClient
-# /testStatus                 <- Checked out version of datashield/testStatus
 # /logs                       <- Where results of tests and lots are collated
 #
 # As of May 2020 this takes ~ 70 mins to run.
@@ -36,18 +34,6 @@ variables:
   _r_check_system_clock_: 0
 
 
-#########################################################################################
-# Need to define all the GH repos and their access tokens, see:
-# https://docs.microsoft.com/en-us/azure/devops/pipelines/library/service-endpoints?view=azure-devops&tabs=yaml
-resources:
-  repositories:
-  - repository: testStatusRepo
-    type: github
-    endpoint: datashield-testing
-    name: datashield/testStatus
-    ref: master
-
-
 #########################################################################################
 # When and under what condition to run the pipeline.
 schedules:
@@ -82,11 +68,6 @@ jobs:
   - checkout: self
     path: 'dsBaseClient'
 
-  - checkout: testStatusRepo
-    path: 'testStatus'
-    persistCredentials: true
-    condition: and(eq(variables['Build.Repository.Name'], 'datashield/dsBaseClient'), ne(variables['Build.Reason'], 'PullRequest'))
-
 
     #####################################################################################
     # The MySQL install that comes with the VM doesn't seem compatable with our set up
@@ -524,75 +505,6 @@ jobs:
     displayName: 'Down Opal Docker Composition'
     condition: succeeded()
 
-    #####################################################################################
-    #                                Windup phase
-    #####################################################################################
-
-    #####################################################################################
-    # Output some important version numbers to file. This gets added to the testStatus 
-    # commit so it can be parsed and used on the status table.
-  - bash: |
-
-      echo 'branch:'$(branchName) >> $(datetime).txt
-      echo 'os:'$(lsb_release -ds) >> $(datetime).txt
-      echo 'R:'$(R --version | head -n 1) >> $(datetime).txt
-      echo 'opal:'$(opal system --opal localhost:8443 --user administrator --password "datashield_test&" --version) >> $(datetime).txt
-
-    workingDirectory: $(Pipeline.Workspace)/logs
-    displayName: 'Write versions to file'
-    condition: succeededOrFailed()
-
-
-    #####################################################################################
-    # Checkout the testStatus repo, add the results from here, push back to GH.
-    # TODO: Automatically pull in better email/name info from somewhere.
-    # TODO: More debug info in commit message
-  - bash: |
-
-      # Git needs some config set to be able to push to a repo. 
-      git config --global user.email "you@example.com"
-      git config --global user.name "Azure pipeline"
-
-      # This repo is checked out in detatched head state, so reconnect it here.
-      git checkout master
-
-      # It is possible that other commits have been made to the testStatus repo since it 
-      # was checked out. i.e. other pipeline runs might have finished.
-      git pull
-
-      # Make the directories if they dont already exist
-      mkdir --parents logs/$(projectName)/$(branchName)
-      mkdir --parents docs/$(projectName)/$(branchName)/latest
-
-      cp $(Pipeline.Workspace)/logs/coveragelist.csv logs/$(projectName)/$(branchName)/
-      cp $(Pipeline.Workspace)/logs/coveragelist.csv logs/$(projectName)/$(branchName)/$(datetime).csv
-
-      cp $(Pipeline.Workspace)/logs/test_results.xml logs/$(projectName)/$(branchName)/
-      cp $(Pipeline.Workspace)/logs/test_results.xml logs/$(projectName)/$(branchName)/$(datetime).xml
-
-      cp $(Pipeline.Workspace)/logs/$(datetime).txt logs/$(projectName)/$(branchName)/
-
-      # Run the script to parse the results and build the html pages.
-      # status.py JUnit_file.xml coverage_file.csv output_file.html local_repo_path remote_repo_name branch
-      source/status.py logs/$(projectName)/$(branchName)/$(datetime).xml logs/$(projectName)/$(branchName)/$(datetime).csv logs/$(projectName)/$(branchName)/$(datetime).txt status.html $(Pipeline.Workspace)/$(projectName) $(projectName) $(branchName)
-
-      cp status.html docs/$(projectName)/$(branchName)/latest/index.html
-      git add logs/$(projectName)/$(branchName)/coveragelist.csv
-      git add logs/$(projectName)/$(branchName)/test_results.xml
-      git add logs/$(projectName)/$(branchName)/$(datetime).xml
-      git add logs/$(projectName)/$(branchName)/$(datetime).csv
-      git add logs/$(projectName)/$(branchName)/$(datetime).txt
-      git add docs/$(projectName)/$(branchName)/latest/index.html
-
-      git commit -m "Azure auto test for $(projectName)/$(branchName) @ $(datetime)" -m "Debug info:\nProjectName:$(projectName)\nBranchName:$(branchName)\nDataTime:$(datetime)"
-      git push
-      exit 0
-
-    workingDirectory: $(Pipeline.Workspace)/testStatus
-    displayName: 'Parse test results'
-    condition: and(eq(variables['Build.Repository.Name'], 'datashield/dsBaseClient'), ne(variables['Build.Reason'], 'PullRequest'))
-
-
     #####################################################################################
     # Output the environment information to the console. This is useful for debugging.
     # Always do this, even if some of the above has failed or the job has been cacelled.