Yes it was before configured for 5 days.
But I wanted to speedup a bit. On the repo itself this can't be changed as
it got inherited from the GitHub Organization.
I changed then for a test the Organization and turned the Orphaned Item off.
But it is still there. What else can be done to get it fo
El El dom, 16 feb 2020 a las 14:48, Vincent Massol
escribió:
> This is why I've been asking from the beginning if it's normal :) Usually
> when there's a stack trace it's not really normal. But it happens so
> frequently that the only explanation I can think of is that it's the normal
> behavior
Hi Ivan,
> so the only difference is the stack trace of the exception, the log level
> is the same.
Is it possible that you misunderstood the data at
https://up1.xwikisas.com/#vI0VAypIpe_tD9LrQRTdMA ? :)
As is mentioned there, ALL of the lines are the same as the ones at the top
(ie they
> El 16 feb 2020, a las 11:15, Georges Moulinier
> escribió:
>
> Do you think I could "hide" this syntax " kubernetes { ..." or this "docker {
> ..." behind a label ?
On both plugins you can configure templates , those templates can be triggered
by labels so you still can use the agent { la
> El 16 feb 2020, a las 14:15, Vincent Massol escribió:
>
> In both cases it"ll be reported as INFO in the logs too. Right?
It seems like, I didn’t noticed that the exception is also a INFO messages, so
the only difference is the stack trace of the exception, the log level is the
same.
--
>
> After seen the log I understand you are asking for the INFO messages that
> inform that a Docker agent is disconnected, IIRC those messages are normal
> they only inform about the Docker agent status,
>
>
Thanks for your reply. Let me make sure I understand. So the Docker Cloud
plugin will
Thanks Ivan for your answer.
Do you think I could "hide" this syntax " kubernetes { ..." or this "docker
{ ..." behind a label ?
A label represent a slave declared in Jenkins. But in my case I did'nt
declare slaves directly. For one of my Jenkins master I just declared a
Kubernetes cluster.
Hi,
Maybe you have to configure the Orphaned Item Strategy in the Jenkins
project.
By default, Jenkins keeps repo or branch even if they are "orphaned" (no
more link with git repo).
You can add the value 0 to "Days to keep old items" and to "Max # of old
items to keep".
Le dimanche 16 févri
Hi Jan,
yes, it stays still with the list. Did it several times. No change.
Am Sonntag, 16. Februar 2020 05:14:56 UTC+1 schrieb Jan Monterrubio:
>
> Does it disappear if you force an Organization Scan?
>
> On Sat, Feb 15, 2020 at 15:10 'Maik Brauer' via Jenkins Users <
> jenkins...@googlegroups.c
