Hi,
I have Jenkins master (v2.190.1) installed as EC2 t2.small - it worked as
expected until i've updated plugins recently and restarted jenkins.
Now i can see that jenkins process consumes 100% CPU and it's caused by
IOwait - disk performance is a bottleneck.
Jenkins started to do some heavy
you would need to check the pod logs, to see what happened
probably the pods can't connect to jenkins and you may need to set the hot
ip in maven
anyway if you submit a PR it will be tested in jenkins infra and will give
you the test results
If your minikube is running in a VM (e.g. on virtualbox)
Thanks.
Could you open an issue on Jira
https://issues.jenkins-ci.org/secure/Dashboard.jspa that describes the
environment more fully?
I'm running CLI git 2.7 on at least one machine (Ubuntu 16.04) and can
successfully clone an https private repository from Visual Studio Online at
https://markwai
Hi,
Maybe it's a "mister obvious" answer but have you set up the build trigger
on the receiving pipeline? In the pipeline configuration you should have an
option "Build when a change is pushed to gitlab" that you can enable and
select the set of the events that would trigger the pipeline.
Also
Thanks Carlos,
"Some integration tests run a local jenkins" is it possible that this is
not starting correctly? I can't see a copy of Jenkins running anywhere
during testing.
I'm using minikube on hyperkit for testing
Andrew
On Monday, October 21, 2019 at 11:14:11 AM UTC+1, Carlos Sanchez wr
a jenkins server is started for each of those integration tests.
the port used is printed in the logs
On Mon, Oct 21, 2019 at 6:03 PM 'Andrew Douglas' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Thanks Carlos,
>
> "Some integration tests run a local jenkins" is it possible that
Created issue 59875: https://issues.jenkins-ci.org/browse/JENKINS-59875
Let me know if you need additional information.
On Tuesday, 22 October 2019 00:41:45 UTC+13, Mark Waite wrote:
>
> Thanks.
>
> Could you open an issue on Jira
> https://issues.jenkins-ci.org/secure/Dashboard.jspa that des
Thanks. I think you provided the information I needed. I'm not planning
to take any action on that bug report other than to watch that it is not a
common occurrence for other users.
On Mon, Oct 21, 2019 at 1:01 PM Patrick van der Velde <
petrikvanderve...@gmail.com> wrote:
> Created issue 59875
Hi Gabriele,
yes, you are right,thanks. The issue was the URL used (I need to RTFM
carefully)... as it seems you have experience with this: by using pipeline
so far I get in Jenkins only a note like "Started by GitLab push by.."
without any link to gitlab merg request.. by using freestyle j
Hi Pablo,
which Links? I am seeing Links to GitLab “Commits” in “Changes” section
(scripted pipeline; only “Push Events” is enabled for GitLab Triggers; Git
checkout has configured “gitlab” as repository browser; this requires Git
plugin in beta version IIRC; in addition the pipeline finally ca
Hi Martin,
This (markup rendering) works fine for me (with HTML markup used in
“vars/foo.txt”); of course only once the build succeeds; but I guess you have a
different problem (than non-successful builds), because otherwise it does not
change at all or is rendered at all.
Maybe it also depend
11 matches
Mail list logo