2014-08-26 11:20:02 -04:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
|
#*----------------------------------------------------------------------------*#
|
2019-12-06 17:46:29 -05:00
|
|
|
#* Copyright (c) 2014-2019 FIRST. All Rights Reserved. *#
|
2014-08-26 11:20:02 -04:00
|
|
|
#* Open Source Software - may be modified and shared by FRC teams. The code *#
|
|
|
|
|
#* must be accompanied by the FIRST BSD license file in the root directory of *#
|
2019-12-06 17:46:29 -05:00
|
|
|
#* the project. *#
|
2014-08-26 11:20:02 -04:00
|
|
|
#*----------------------------------------------------------------------------*#
|
|
|
|
|
|
|
|
|
|
# If this is changed, update the .gitignore
|
2020-08-31 00:33:11 -07:00
|
|
|
# so that test results are not committed to the repo
|
2014-08-26 11:20:02 -04:00
|
|
|
DEFAULT_LOCAL_TEST_RESULTS_DIR=../test-reports
|
|
|
|
|
|
2015-09-30 10:52:02 -04:00
|
|
|
ROBOT_ADDRESS=admin@roboRIO-190-FRC.local
|
2015-09-27 14:09:17 -04:00
|
|
|
ADMIN_ROBOT_ADDRESS=admin@roboRIO-190-FRC.local
|
2014-08-26 11:20:02 -04:00
|
|
|
DEFAULT_LOCAL_RUN_TEST_SCRIPT="run-tests-on-robot.sh"
|
|
|
|
|
|
2015-09-30 10:52:02 -04:00
|
|
|
DEFAULT_DESTINATION_DIR=/home/admin
|
2014-08-26 11:20:02 -04:00
|
|
|
DEFAULT_TEST_SCP_DIR=${DEFAULT_DESTINATION_DIR}/deployedTests
|
|
|
|
|
DEFAULT_DESTINATION_TEST_RESULTS_DIR=${DEFAULT_DESTINATION_DIR}/testResults
|
|
|
|
|
|
|
|
|
|
# C++ test variables
|
|
|
|
|
DEFAULT_CPP_TEST_NAME=FRCUserProgram
|
|
|
|
|
DEFAULT_CPP_TEST_ARGS="--gtest_color=yes"
|
2017-08-18 21:35:53 -07:00
|
|
|
DEFAULT_LOCAL_CPP_TEST_FILE=../build/integrationTestFiles/cpp/FRCUserProgram
|
Gradle Build
This adds gradle support for building wpilibj and wpilibc. At this
point, both of these libraries should be fully ready to go.
Gradle should give us a number of improvements, including less
dependencies for getting building up and running, and MUCH faster build
times. I'm noticing significantly faster build times already compared to
Maven, with neither system building the plugins. The changes here should
be pretty straight forward. The basic command for gradle is './gradlew'.
This is the gradle wrapper, and it will find and download the correct
gradle executable for your system. There is no need to install anything
yourself. To see every task available, run './gradlew tasks'. The
important tasks for us are listed under the WPILib header when the tasks
command is run. To generate unit test binaries, the
fRCUserProgramExecutable command will create the C++ tester, and the
wpilibjIntegrationTestJar command will create the Java tester. The Jenkins
deploy scripts have been modified to know the difference between maven
generated and gradle generated jars with an environment variable. Creating
the eclipse plugins still requires Maven, but gradle will handle calling
it correctly and generating the proper dependencies for it. Create the
plugins by calling ./gradlew eclipsePlugins.
Jenkins can now be modified to support the new build system. Unit tests
are run with ./gradlew test. Generating the integration tests uses the
above two commands, and then process proceeds exactly as it did before.
For publishing documentation, a new task has been created, ./gradlew
publishDocs, which handles putting the documentation where Jenkins expects
for publishing.
Change-Id: I9a260d391984f98ef9170993efe933e4026161dc
2015-05-05 09:54:14 -04:00
|
|
|
|
2014-08-26 11:20:02 -04:00
|
|
|
CPP_REPORT=cppreport.xml
|
|
|
|
|
DEFAULT_LOCAL_CPP_TEST_RESULT=${DEFAULT_LOCAL_TEST_RESULTS_DIR}/${CPP_REPORT}
|
|
|
|
|
DEFAULT_DESTINATION_CPP_TEST_RESULTS=${DEFAULT_DESTINATION_TEST_RESULTS_DIR}/${CPP_REPORT}
|
|
|
|
|
|
|
|
|
|
# Java test variables
|
|
|
|
|
DEFAULT_JAVA_TEST_NAME=FRCUserProgram.jar
|
|
|
|
|
DEFAULT_JAVA_TEST_ARGS=""
|
Gradle Build
This adds gradle support for building wpilibj and wpilibc. At this
point, both of these libraries should be fully ready to go.
Gradle should give us a number of improvements, including less
dependencies for getting building up and running, and MUCH faster build
times. I'm noticing significantly faster build times already compared to
Maven, with neither system building the plugins. The changes here should
be pretty straight forward. The basic command for gradle is './gradlew'.
This is the gradle wrapper, and it will find and download the correct
gradle executable for your system. There is no need to install anything
yourself. To see every task available, run './gradlew tasks'. The
important tasks for us are listed under the WPILib header when the tasks
command is run. To generate unit test binaries, the
fRCUserProgramExecutable command will create the C++ tester, and the
wpilibjIntegrationTestJar command will create the Java tester. The Jenkins
deploy scripts have been modified to know the difference between maven
generated and gradle generated jars with an environment variable. Creating
the eclipse plugins still requires Maven, but gradle will handle calling
it correctly and generating the proper dependencies for it. Create the
plugins by calling ./gradlew eclipsePlugins.
Jenkins can now be modified to support the new build system. Unit tests
are run with ./gradlew test. Generating the integration tests uses the
above two commands, and then process proceeds exactly as it did before.
For publishing documentation, a new task has been created, ./gradlew
publishDocs, which handles putting the documentation where Jenkins expects
for publishing.
Change-Id: I9a260d391984f98ef9170993efe933e4026161dc
2015-05-05 09:54:14 -04:00
|
|
|
|
2019-11-26 01:00:35 -05:00
|
|
|
DEFAULT_LOCAL_JAVA_TEST_FILE=../build/integrationTestFiles/java/wpilibjIntegrationTests-all.jar
|
Gradle Build
This adds gradle support for building wpilibj and wpilibc. At this
point, both of these libraries should be fully ready to go.
Gradle should give us a number of improvements, including less
dependencies for getting building up and running, and MUCH faster build
times. I'm noticing significantly faster build times already compared to
Maven, with neither system building the plugins. The changes here should
be pretty straight forward. The basic command for gradle is './gradlew'.
This is the gradle wrapper, and it will find and download the correct
gradle executable for your system. There is no need to install anything
yourself. To see every task available, run './gradlew tasks'. The
important tasks for us are listed under the WPILib header when the tasks
command is run. To generate unit test binaries, the
fRCUserProgramExecutable command will create the C++ tester, and the
wpilibjIntegrationTestJar command will create the Java tester. The Jenkins
deploy scripts have been modified to know the difference between maven
generated and gradle generated jars with an environment variable. Creating
the eclipse plugins still requires Maven, but gradle will handle calling
it correctly and generating the proper dependencies for it. Create the
plugins by calling ./gradlew eclipsePlugins.
Jenkins can now be modified to support the new build system. Unit tests
are run with ./gradlew test. Generating the integration tests uses the
above two commands, and then process proceeds exactly as it did before.
For publishing documentation, a new task has been created, ./gradlew
publishDocs, which handles putting the documentation where Jenkins expects
for publishing.
Change-Id: I9a260d391984f98ef9170993efe933e4026161dc
2015-05-05 09:54:14 -04:00
|
|
|
|
2014-08-26 11:20:02 -04:00
|
|
|
JAVA_REPORT=javareport.xml
|
2017-08-18 21:35:53 -07:00
|
|
|
DEFAULT_LIBRARY_NATIVE_FILES=../build/integrationTestFiles/libs
|
2016-11-06 21:47:18 -08:00
|
|
|
DEFAULT_LIBRARY_NATIVE_DESTINATION=/usr/local/frc/lib
|
2014-08-26 11:20:02 -04:00
|
|
|
DEFAULT_LOCAL_JAVA_TEST_RESULT=${DEFAULT_LOCAL_TEST_RESULTS_DIR}/${JAVA_REPORT}
|
|
|
|
|
DEFAULT_DESTINATION_JAVA_TEST_RESULTS=${DEFAULT_DESTINATION_TEST_RESULTS_DIR}/AntReports/TEST-edu.wpi.first.wpilibj.test.TestSuite.xml
|