prelim teamcity config changes#14764
Conversation
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
| }) | ||
|
|
||
| step(ScriptBuildStep { | ||
| name = "Run via jen20/teamcity-go-test" |
There was a problem hiding this comment.
Could you change the name to reflect the new behavior? We aren't using jen20/* as far as I know
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
| fun BuildSteps.runDiffTests() { | ||
| if (UseTeamCityGoTest) { | ||
| step(ScriptBuildStep { | ||
| name = "Run Tests" |
There was a problem hiding this comment.
currently running this on our teamcity test project here
it seems like we shouuld hvae the build test step be unique for Diff Tests. it could just be as simple as having it be named Run Diff Tests instead of leaving it as Run Tests
| fi | ||
|
|
||
| echo "Compiling teamcity-diff-test..." | ||
| cd scripts/teamcitytestscripts |
There was a problem hiding this comment.
19:17:28 Starting: /opt/teamcity-agent/temp/agentTmp/custom_script10331266477049267803
19:17:28 in directory: /opt/teamcity-agent/work/c1b141985ceeadbf/google-beta/services/accessapproval
19:17:28 Compiling teamcity-diff-test...
19:17:28 /opt/teamcity-agent/temp/agentTmp/custom_script10331266477049267803: line 8: cd: scripts/teamcitytestscripts: No such file or directory
19:17:29 /opt/teamcity-agent/temp/agentTmp/custom_script10331266477049267803: line 12: ./test-binary: No such file or directory
19:17:29 Found 0 tests that match the given test prefix TestAcc
19:17:29 Skipping test execution; no tests to run
19:17:29 Process exited with code 0
It looks like the script starts from c1b141985ceeadbf/google-beta/services/accessapproval aka PACKAGE_PATH, so you probably need something like ../../../scripts/teamcitytestscripts (you also need to get back to PACKAGE_PATH after, so probably easier to use pushd/popd)
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
roaks3
left a comment
There was a problem hiding this comment.
LGTM, seems ready for another check
BBBmau
left a comment
There was a problem hiding this comment.
just merged your changes into the test project and ran a test, getting the following error:
Starting: /opt/teamcity-agent/temp/agentTmp/custom_script3800832839859704229
11:23:24 in directory: /opt/teamcity-agent/work/c1b141985ceeadbf/google-beta/services/accessapproval
11:23:24 Compiling teamcity-diff-test...
11:23:25 Found 4 tests that match the given test prefix TestAcc
11:23:25 /opt/teamcity-agent/temp/agentTmp/custom_script3800832839859704229: line 21: ./teamcity-diff-test: No such file or directory
11:23:25 Starting tests
11:23:25 Process exited with code 127
11:23:26 Process exited with code 127 (Step: Run via scripts/teamcitytestscripts/teamcity-diff-test (Command Line))
11:23:26 Step Run via scripts/teamcitytestscripts/teamcity-diff-test (Command Line) failed
11:23:26 Error message: Step Run via scripts/teamcitytestscripts/teamcity-diff-test (Command Line) failed
how does the hashicorp agent interact with the provider? I am compiling this in the base directory of terraform-google-beta, but this file path differs from the ones above it |
i added so this is why there's a no directory found error, it's attempting to access the directory within the service folder that its ran in @luckyswaminathan TC Build where i tried this out: https://hashicorp.teamcity.com/buildConfiguration/Development_TerraformProviderGoogleDiffTestProject_GOOGLE_BETA_DIFF_TEST_NIGHTLYTESTS_GOOGLEBETA_PACKAGE_ACCESSAPPROVAL/440748?showLog=440748_1256_1251&logView=flowAware |
|
if it helps here's the repo where i have the test project setup |
|
just changed the path of the teamcity binary (I think this logically should work?) assuming it fails after it echoes starting tests |
|
Hi there, I'm the Modular magician. I've detected the following information about your changes: Diff reportYour PR generated some diffs in downstreams - here they are.
|
that fixed it! i noticed though that we're missing some things in this PR that I added in the test project, were you intending to add this here or in a separate PR? Referencing the test project repo for context |
yeah I was intending to add the scheduling, etc later, thanks for doing it for the test one! will port over once I verify this works |
PASS |
ah this is left out since we're focusing on just testing the project + release test step setup |
39c2ebc
…e how to test
Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.