Fix path to artifacts

[andyundso]

As I parallelized the cross-compilation process, the gems were moved into another folder dedicated to their target platform during the build. This change was not reflected when storing the artifacts.

[aharpervc]

I don't see anything on the artifacts tab here, should that be showing something now? https://app.circleci.com/pipelines/github/andyundso/tiny_tds/2/workflows/e920c589-ee26-4afd-ba5c-fd10bd257931/jobs/35/artifacts

[andyundso]

The artifacts are available from the cross compile jobs:

• https://app.circleci.com/pipelines/github/andyundso/tiny_tds/2/workflows/e920c589-ee26-4afd-ba5c-fd10bd257931/jobs/17/artifacts
• https://app.circleci.com/pipelines/github/andyundso/tiny_tds/2/workflows/e920c589-ee26-4afd-ba5c-fd10bd257931/jobs/19/artifacts
• https://app.circleci.com/pipelines/github/andyundso/tiny_tds/2/workflows/e920c589-ee26-4afd-ba5c-fd10bd257931/jobs/14/artifacts

But can also upload them from each Windows test, if this is your prefered solution.

[aharpervc]

I see. That sort of makes sense, although I'm concerned about accessibility. How I checked was I scrolled to the bottom of this PR, clicked "show all checks", clicked into the details for "windows-2.4", clicked artifacts, and didn't see anything.

I think it'd be great if repo visitors had quick access to the fat gems for whichever version of ruby they're using, quickly from each PR.

Thoughts?

[andyundso]

generally agree with you.

I would keep the artifacts upload on the precompile step, as the x86 version is not used in any test. But additionally, upload the artifact from each test, so people can get the correct version for their system, as suggest by you.

will take care of this tomorrow and amend the PR.

[andyundso]

@aharpervc took a while longer, had couple of other things to do first.

but as discussed, now each test on windows uploads the version it has tested as an artifact. would you mind to re-review?

[aharpervc]

Sweet, LGTM