Confluence Publisher plugin: publishConfluence return value

In order to create nested new pages, I need to get the new page-Id from the first new one to pass as the parentId when creating its child. However, if I do the following: topPageId = 332914247 newTop = publishConfluence siteName: ., parentId: topPageId , ... It successfully creates the

Re: ExcludedRegions for SVN not working in Pipeline

Does anyone have a solution for this? Regards, Venkatesh On Thu, Aug 13, 2020 at 12:00 PM Ven H wrote: > Hi, > > I have a pipeline which is configured for the SVN path in Jenkins > pipeline. https://svn.domain.com/org/project/trunk/Platform/Src > > Within Src, I have a Build folder and there

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Bjorn Pedersen to Ven H: > > 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

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

Thanks a lot. Can you please advise on how to stop / control this behavior? Regards, Venkatesh On Thu, Aug 20, 2020 at 3:34 PM 'Björn Pedersen' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > This standard behaviour if jobs run in parallel. The first run uses: > trunk%2FPlatform

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

This standard behaviour if jobs run in parallel. The first run uses: trunk%2FPlatform => the workdir for the job trunk%2FPlatform@tmp => the checkout for the Jenkinsfile to set up the job. the @n dirs are created for further parallel runs. Björn > -- You received this message because you are