We got an 30 minute free CloudBees support. It was too short to dig deeper
to find the problem, but the person I was talking to (after examining our
logs) mentioned what he thought was the problem and gave a suggestion.
We should not use Jenkins master at all for builds (allocated with the
" build only the branches that you specify.". I am assuming that this is
something in the script that does this, as when creating the MultiBranch
job, I see no option to allow for the selection of doing executing the job
for only one branch. Not to harp on the documentation, but if this can
What does the changelog for the plug-in say that could relate to your
Le mar. 13 août 2019 à 16:20, Chris McIntosh
a écrit :
> Thanks for the help all,
> This is fixed. I saw that the jobDsl plugin had an update, so I bumped
> the version up to 1.75 and it started working again. (I
Thanks also for detecting that issue. The documentation does say that
local repositories are supported. I was wrong. However, there are
important limitations with local repositories that make them a poor choice
for any user and an especially poor choice for first time users.
When you used those steps in Blue Ocean, you defined a Pipeline in the
branch where the Jenkinsfile was stored by Blue Ocean. I think that is
what you wanted in the SCM repository. You're correct that Blue Ocean
created a multibranch pipeline as part of that editing process.
If you'd like a
I only have the option to downgrade to 1.18 of Server Sent Events (SSE)
I would have to download the 1.17 and manually downgrade it.
>From the discussions it seems I also need to downgrade BlueOcean to 1.17
> Downgrading to BlueOcean 1.17 (which in turn uses sse-gateway 1.17)
We have Jenkins 2.0 , Scripted Pipeline and i want to
1. Push an environment variable VAR1=FOO in a Job A, and2. Access that
environment variable from another Job B.
Job A and B both are independent.
When I invoke Job B, I want to go and find the latest build of Job A and then
I have not read the whole thread in detail, but the “Unable to create new
native thread” OutOfMemoryErrors from your original thread where one of the
stack traces involves
looks like it could be related to
Hi Sverre Moe,
I am the person who talked to you this morning :-)
Long term solution is to avoid building on the master to avoid performance
issue and the need to increase the number of processes and open files in
the machine where the jenkins master is located. Building on the master is
I created a Pipeline job to run jstack every 10 minutes (though running on
Jenkins master since that is where the Jenkins is running).
onsdag 14. august 2019 16.07.02 UTC+2 skrev Félix Belzunce Arcos følgende:
> Hi Sverre Moe,
> I am the person who talked to you this morning :-)
This morning, I basically did what you just recommended. I created a new
Pipeline job (not using Blue Ocean), selected "Pipeline Script from SCM',
and pointed to the Jenkinsfile that I had created yesterday in the master
branch. Because this job is not a MultiBranch job, even thought you can
On Wed, Aug 14, 2019 at 8:36 AM Louis Elston wrote:
> This morning, I basically did what you just recommended. I created a new
> Pipeline job (not using Blue Ocean), selected "Pipeline Script from SCM',
> and pointed to the Jenkinsfile that I had created yesterday in the master
BitBucket server and other Git servers do have a limit on the maximum number of
concurrent clones, which is a factor of the resources you have on the BitBucket
server machine. See
You received this
Oh, that is very helpful!
I had searched with so many terms, EXCEPT for scaling. Duh.
On Wed, Aug 14, 2019 at 10:07 AM Gareth Bowles wrote:
> BitBucket server and other Git servers do have a limit on the maximum number
> of concurrent clones, which is a factor of the resources you
Mail list logo