jeremy mordkoff:
> You need 99 jobs for the 99 programs, but what about the
> libraries?
Yes, one job per project, and let MSBuild take care of
building the libraries. Thankfully, I do not have to worry
about it in Jenkins. The libraries will be available at
their correct relative paths in the r
You need 99 jobs for the 99 programs, but what about the libraries? I
assume a program will depend on one or more libraries. Are there
dependencies between libraries? (this is common and not a problem if it is
understood.) Are there dependencies between programs? (this would be bad.)
How fast
jeremy mordkoff:
> I'm having a little trouble understanding exactly what you
> are asking.
I am sorry for an insufficiently clear description. Let me
try again.
Since our .NET projects are highly interdependent, we
maintain them in a single SVN repository with a strucure
like this:
trunk
pr
Hi any resolution on this ? please share.
On Wednesday, January 4, 2017 at 6:54:15 PM UTC+5:30 vdab...@gmail.com
wrote:
> Hi,
>
> Some requests have response time very short (6ms) and relative comparison
> give difference to high (6ms compare to 7ms => 16% diff).
>
> For example :
>
> =
Hi,
I have a Multibranch Pipeline job setup for SVN. In Trunk, I have a
directory called Platform which has a Jenkins file. The workspace structure
is something like Drive\Workspace_Dir\trunk%2FPlatform.
After a few builds, I can see some strange things happening with this.
The Workspace_Dir has
Hi all,
We use the Build Failure Analyzer to help identify causes of build failures in
our Jenkins. It works well on our Pipeline jobs via the Jenkins GUI, linking
directly to the failure in the console output.
We use the REST API to get the failure data. We'd like to know in which
pipeline st
