Publishing Artifacts on RTC using Ant build tool
2 answers
Comments
I read your article and find it a good one. I understand that I should use Apache HTTP server and ArtifactLinkPublisher ant task to achieve my goal.
Usually, the files generated during a build are stored somewhere relative to the source code. It depends on how you organize your build. In the JKE Banking Example, the generated data is in the folder /build under the folder created for each build. So if the build output is published in e.g. the folder I20151028-1738, it contains the loaded repository workspace and the executable result as well.
I think this is a good approach, because that keeps all relevant data together for each build.
You mean that I can find the executables somewhere in the Load Directory? I have tried to find it but could not see any thing.
I wrote these articles because I wanted them to be read. All your questions are pretty much answered there.
1. Each build has its own folder, the way it is set up in that scenario, so there is nothing to be deleted and deletion is not desired, as you want to publish the result.
2. Where the binaries reside is up to your build scripts, the JKE example stores them in the build folder.