Confluence Publisher plugin: publishConfluence return value

['MtnBill' via Jenkins Users]

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 first new page, but newTop has no value, so I 
cannot create an additional page under it.

Am I doing something silly, or does the plug-in just not support that?
And if the latter, does anyone have suggestions for a workaround 
(preferably not making my own independent REST calls).

Thanks.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/8814cb77-d587-4888-b6d0-6c1e25b09449n%40googlegroups.com.

Re: ExcludedRegions for SVN not working in Pipeline

[Ven H]

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 are some projects inside that
> as well. So, I want to exclude some projects within the Build folder. So I
> put the ExcludedRegions like */Build/ProjectFolder1/.** and so on. But
> this is not working. Any help will be appreciated.
>
> Regards,
> Venkatesh
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPp28ep_VigjFK-S5yEVYmXSiLWkJAzA96%3DLiUMnZ2g2hMLoAg%40mail.gmail.com.

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

[Anton Shepelev]

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
> > happening with this.  The Workspace_Dir has these many
> > directories now.
> >
> > trunk%2FPlatform
> > trunk%2FPlatform@tmp
> > trunk%2FPlatform@2
> > trunk%2FPlatform@2@tmp
> > trunk%2FPlatform@3
> > trunk%2FPlatform@3@tmp
> > trunk%2FPlatform@4
> > trunk%2FPlatform@4@tmp
> > and so on...
>
> This standard behaviour if jobs run in parallel.

Does the official documentation tell about it, or is it
considred an internal part of the implementation?

Ven H:

> Can you please advise on how to stop / control this
> behavior?

Try limiting the number of executors to unity.

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20200820162541.e1737ad14f672cc5e2e656b5%40gmail.com.

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

[Ven H]

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 => 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 subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/5219e400-ad91-48c8-ac50-dd9f81767c3bn%40googlegroups.com
> 
> .
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPp28eo7h-dRd6K1BvLGGMZgWhWS9i%2BOXsBspTOkrB-mu-iOGA%40mail.gmail.com.

Re: Multibranch Pipeline job creating multiple Checkout Directories in Workspace

['Björn Pedersen' via Jenkins Users]

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 subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5219e400-ad91-48c8-ac50-dd9f81767c3bn%40googlegroups.com.