How to transfer binary files created upstream to a remote slave

Question

We use Hudson for Windows to create a .NET solution and run unit tests (NUnit). Thus, Hudson is used to run batch files that do the actual work.

Now I am trying to set up a new test that will run on a slave and will work for a very long time. The test should use binary files created by the upstream assembly.

I searched the Hudson documentation, but cannot find how to pass upstream artifact assemblies to subordinate subordinates. How can I do it?

Answer 1

Use the Copy Artifact Plugin in your downstream build.

Just provide the name of the upstream job and the path for copying to the downstream workspace.

Answer 2

Depending on the source control you are using, you can trick and use this. I am not a fan of checking binary files, especially if they are large. But in the past, I received generated binaries or installers generated using the CI assembly, automated their verification into a separate svn repository, and had a slave machine from this repo, when dictated by the wizard, and performed all the tests that you need to perform.

Answer 3

This might be a bit crowded for you if you depend only on binaries. But there is also a Clone Workspace SCM Plugin that archives your entire workspace, and you can check it with the next work, as if it came from SCM. This is pretty new.

We are currently using a different setting. We have a repository of artifacts where we push our binaries. The second task pulls binary files from this repository. Physically, this is just a standard Windows share, where we create a subfolder with the number of the specified job. If you also use [Parameterized Trigger Plugin] [2], you can transfer the build number from task 1 to task 2 and run your test in binary format on the right. A side effect is that you can reuse binaries later without having to keep a long history in Hudson.

[2]: http: // Parameterized Trigger plugin