Have you added the "Checkout over SSH" behaviour?
Richard.
On Fri, Feb 15, 2019 at 3:20 PM Cameron Morrison
wrote:
> Hi,
>
> I am using the bitbucket-source-branch plugin - it's working, but I cannot
> figure out how to provide "SSH & private key" type credentials to the
> branch source, when
I suspect that it is using API calls that are not available through an ssh
connection.
On Thu, Feb 14, 2019, 6:19 PM Cameron Morrison Hi,
>
> I am using the bitbucket-source-branch plugin - it's working, but I cannot
> figure out how to provide "SSH & private key" type credentials to the
>
Hi,
I am using the bitbucket-source-branch plugin - it's working, but I cannot
figure out how to provide "SSH & private key" type credentials to the
branch source, when using the Bitbucket source type.
It does work with username/password authentication, and a bare Git type
branch source
Hi,
We use a when clause to run the stage or not based on finding
a specific string in the commit message
stage('Publish') {
// if we dont find SKIP_PUBLISH in git log
// then we proceed with push
// note, we're checking the status of the grep command
// not the output. grep
How do I use this to copy a job in a folder to another job in the same
folder?
On Wednesday, November 23, 2011 at 11:59:14 AM UTC-5, domi wrote:
>
> Manuel, thats a cool idea - I would not have thought about this! :)
> btw. If you use the scriptler plugin [1], you get even around the copy
>
Hi.
Out Jenkins installation use 24CPU 60G RAM GCE node. And connected about
400+ slaves. Mainly used pipeline in .
Some time web interface doesn't respond. It looks like 504 Gateway
Time-out. So respond time very long. Usually happens at high load (LA >
30).
Have such java and jenkins
You may be able to reduce clone times by using a reference repository when
performing the checkout from your pipeline. I've found that an explicitly
declared checkout significantly reduces the network data transfer and the
disc usage when I have a reference repository on the agent and on the
Can anyone advise me what to do about this Jenkins console message please?
JENKINS-2111 path sanitization ineffective when using legacy Workspace Root
Directory ‘${ITEM_ROOTDIR}/workspace’; switch to
‘${JENKINS_HOME}/workspace/${ITEM_FULL_NAME}’ as in JENKINS-8446 /
JENKINS-21942
Best regards
14.02.2019 12:58, Steven Foster пишет:
It would definitely be my preferred way of building code, but
unfortunately the Jenkins master has to clone and perform the merge
per pipeline every time. That doesn't scale on a sizeable repo with
many active PRs and 12 multibranch pipelines :(
Agree.
Since SIkuli is a screen capture and replay based testing framework, it
needs access to the Windows desktop. Running as a Windows service does not
give access to the Windows desktop by default.
I suggest that you should configure a dedicated Windows machine that is
logged into the Desktop
Is the job configuration setting -xmx248 ? Are jobs manually configured on
your instance or did it somehow get misconfigured?
On Thu, Feb 14, 2019 at 05:38 wrote:
> Hi,
>
> Recently i increased the -xmx in the starting script to 2048. However, a
> random Jenkins job is starting with -xmx248 and
Hi,
Recently i increased the -xmx in the starting script to 2048. However, a
random Jenkins job is starting with -xmx248 and as a result this job fails.
What's the cause of this and how can I solve this.
With kind regards, Will
--
You received this message because you are subscribed to the
James, Nord - thank you!
For my pipeline scaling is not an issue, but merging strategy is breaking
SonarSource orchestration.
I think "The current pull request revision" will be nice as far as I'll
add a check that branch was updated from the master into pipeline itself.
On Thursday, February
Hi,
I have a robot sikuli script when run from terminal it just runs fine.
When executed from jenkins as a job it is throwing a exception as
om.github.rainmanwy.robotframework.sikulilib.exceptions.TimeoutException:
Timeout happend, could not find P(signin.PNG) S: 0.7.
Jenkins is installed as
It would definitely be my preferred way of building code, but unfortunately
the Jenkins master has to clone and perform the merge per pipeline every
time. That doesn't scale on a sizeable repo with many active PRs and 12
multibranch pipelines :(
I've seen people merge PRs with an old base
>
> Thanks on the tip
>
> Can you please elaborate how did you exit ?
--
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
the main reason for using it is you want to check that the result of a PR
if merged would result in working code.
a PR can be based on any code even 1 year old, so this strategy makes sure
it is up to date before building and testing.
On Thu, 14 Feb 2019, 05:58 Vitaly Karasik GitHub Branch
17 matches
Mail list logo
