I'm having a little trouble understanding exactly what you are asking. I think you are asking if it is possible to trigger multiple builds in a single workspace. If you use a single pipeline, this is trivial.
So perhaps you should consider writing a single pipeline that iterates over all libraries and projects and builds each one in turn. On Saturday, August 15, 2020 at 6:13:33 PM UTC-4 Anton Shepelev wrote: > Hello, all > > We maintain hundreds of interdependent .NET libraries and programs > that typically reference tenths of those libraries each in a single > SVN repository. Maybe it is a non-standard, and even not a > recommended approach, but creating a repository per program or > library would introduce its own problems, especially because we use > source (project) references by relative path instead of binary > references. > > I have inherited a Jenkins configuration from a previous > maintainer, whom I can no longer contact. He configured the > building of each project not by means of pipelines, but entirely > through the web-interface, as Freestyle projects with an MSBuild > step. I think it is not a standard Jenkins functionality but a > feature of the MSBuild plugin: https://plugins.jenkins.io/msbuild/ . > > He configured Jenkins so that it should build each project in the > same local SVN mirror, in order not to checkout our unified > repository for each of the many projects. He created a Jenkins > global property `SVN_REPO' with the value > `ExecutorRepo_${EXECUTOR_NUMBER}', > but I can't understand how and where it is referenced, expanded, and > used instead of the default working directory of each project. Can > you help me to find that out? When I tried to specify that variable > as "Local module directory" in the pipeline configuration, > ${EXECUTOR_NUMBER} was not expanded, perhaps because that settings > is expanded before an executor is chosen. > > Is there a way to confire multiple pipelines to reuse the same > global SVN working directory on each node? For example, supposing I > have this SVN repository: > > trunk > programs > program1 > program2 > ... > program99 > library > library1 > library2 > ... > library99 > > I want each agent to checkout trunk exactly once and build each > program inside the same working directory. Is it possible? > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f2b22fa-041e-4340-b290-f49ee2d02c10n%40googlegroups.com.
