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
programs
program1
program2
...
program99
library
library1
library2
...
library999
where each program depends on one of more libraries. I want
to create 99 Jenkins items, using declarative pipelines,
each building one of the 99 programs. We have several nodes
registered on different machines with different
environments. I want each node to checkout the SVN trunk
exactly once and use that working copy in each pipeline to
build each individual program. I do not understand how to
set it up in Jenkins because each pipeline seems to use its
own SVN working directory.
The current configurtion, setup by a previous maintainer,
relies on the Jenkins MSBuild plugin, and manages somehow to
retain a single SVN working direcotory per node and
executor, whose name is stored in a Jenkins global property
SVN_REPO with the value `ExecutorRepo_${EXECUTOR_NUMBER}.'
When I tried to specify this property in the "Local module
directory" for the pipeline, the `${EXECUTOR_NUMBER}' part
was left unexpanded in the actual path to the SVN working
directory. I don't understand how and why it is expanded
with the MSBuild plugin but is not with the declarative
pipeline.
> I think you are asking if it is possible to trigger
> multiple builds in a single workspace.
Yes.
> If you use a single pipeline, this is trivial.
As I said above, I prefer one pipeline per program, for the
convenience of having a dedicated page on the Jenkins web-
interface for each project and the ability to change the
settings for building individual projects independently of
other projects. It this can be achieved with a single
pipelike, I should like to know how.
> So perhaps you should consider writing a single pipeline
> that iterates over all libraries and projects and builds
> each one in turn.
Is such iteration possible with the declarative syntax, or
shall I switch to the scripted pipeline?
--
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/20200820014657.894b3c4a20c5f8006b123953%40gmail.com.
