Re: All jobs disappeared from view

2021-01-02 Thread Ivan Fernandez Calvo 
Did you check the logs? I bet you have an exception related to one or more 
plugins not loaded correctly

El sábado, 2 de enero de 2021 a las 4:22:33 UTC+1, dma...@gmail.com 
escribió:

> Yes, I had tried that, numerous times.  (All the jobs data is there).  I 
> even restored a backup done earlier today when everything was fine.  No 
> luck.  HOWEVER, I just downloaded a newer jenkins.war (2.263) , and 
> then restarted jenkins, and the jobs all reappeared.  *Perhaps this will 
> help someone else*.
>
> On Friday, January 1, 2021 at 10:19:55 PM UTC-5 jaychandran...@gmail.com 
> wrote:
>
>> Pls check what is there in /var/lib/jenkins/jobs folder if all jobs 
>> present in this folder just restart Jenkins service
>>
>> On Sat, 2 Jan 2021, 8:37 am David Maul,  wrote:
>>
>>> All of a sudden my jobs have all disappeared from the :8080 web page.  
>>> They are very much there on disk. I have tried reloading configuration from 
>>> disk - no luck.  I have tried restoring /var/lib/jenkins entirely from a 
>>> backup, still no luck.  Nothing seems to help.  I am only greeted with:
>>>
>>> "This view has no jobs associated with it. You can either add some 
>>> existing jobs  to this view or create a new 
>>> job  in this view." 
>>>
>>> I know all of my job data is there, but I cannot figure out why jenkins 
>>> will not show it to me.
>>>
>>> I am running 2.150.3 on Centos7.  Usually has been very good.  This is 
>>> kind of a crisis.
>>>
>>> Thanks in advance for help, and Happy New year. 
>>>
>>> -- 
>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/c677f342-2873-4e40-aa84-22077b9262dbn%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/175301f5-7dd6-448c-ad5b-1b7c3019f7c0n%40googlegroups.com.

Re: Gracefully ignoring unavailable agents

2021-01-02 Thread Mark Waite 
Apologies for the empty message that preceded this one.  Fat fingers on an
unfamiliar keyboard.

I've been using the pipeline step 'nodesByLabel' in scripted pipelines to
select label based subsets of agents that are currently available.  I'm not
sure that the same technique can be used with declarative pipeline.

On Sat, Jan 2, 2021 at 10:30 AM Mark Waite 
wrote:

>
>
> On Thu, Dec 31, 2020 at 2:27 PM 'Mark Raynsford' via Jenkins Users <
> jenkinsci-users@googlegroups.com> wrote:
>
>> Hello!
>>
>> Let's say I'm using a declarative pipeline setup like this:
>>
>> ~~
>> #!groovy
>>
>> pipeline {
>>
>>   agent none
>>
>>   stages {
>> stage('Build') {
>>   parallel {
>> stage('Build Linux') {
>>   stages {
>> stage('Build:linux:openjdk-11-hotspot') {
>>   agent {
>> label 'linux'
>>   }
>>   ...
>> }
>> stage('Build:linux:openjdk-15-hotspot') {
>>   agent {
>> label 'linux'
>>   }
>>   ...
>> }
>>   }
>> }
>>
>> stage('Build Windows') {
>>   stages {
>> stage('Build:windows:openjdk-11-hotspot') {
>>   agent {
>> label 'windows'
>>   }
>>   ...
>> }
>> stage('Build:windows:openjdk-15-hotspot') {
>>   agent {
>> label 'windows'
>>   }
>>   ...
>> }
>>   }
>> }
>>   }
>> }
>>   }
>> }
>> ~~
>>
>> As you can see, I use labels to select agents to run builds on specific
>> operating systems and with a fixed set of specific JDK versions. This
>> all works fine. However: With my current hardware setup, the Windows
>> node is _not_ going to be online 24/7 (the Linux node is always
>> available).
>>
>> Is there a way I can adapt the above pipeline to basically say "If
>> there's a Windows node online, run the stages, otherwise trivially
>> succeed"? Right now, if no Windows node is available, the pipeline will
>> hang until either one becomes available or the entire job times out.
>>
>> --
>> Mark Raynsford | https://www.io7m.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/20201231212628.447a21b5%40sunflower.int.arc7.info
>> .
>>
>

-- 
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/CAO49JtEdA-UxmdmRsSLKo1eNvHxJ%2BGq%2BSzpucQ%3DtepLFy2kZiw%40mail.gmail.com.

Re: Gracefully ignoring unavailable agents

2021-01-02 Thread Mark Waite 
On Thu, Dec 31, 2020 at 2:27 PM 'Mark Raynsford' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hello!
>
> Let's say I'm using a declarative pipeline setup like this:
>
> ~~
> #!groovy
>
> pipeline {
>
>   agent none
>
>   stages {
> stage('Build') {
>   parallel {
> stage('Build Linux') {
>   stages {
> stage('Build:linux:openjdk-11-hotspot') {
>   agent {
> label 'linux'
>   }
>   ...
> }
> stage('Build:linux:openjdk-15-hotspot') {
>   agent {
> label 'linux'
>   }
>   ...
> }
>   }
> }
>
> stage('Build Windows') {
>   stages {
> stage('Build:windows:openjdk-11-hotspot') {
>   agent {
> label 'windows'
>   }
>   ...
> }
> stage('Build:windows:openjdk-15-hotspot') {
>   agent {
> label 'windows'
>   }
>   ...
> }
>   }
> }
>   }
> }
>   }
> }
> ~~
>
> As you can see, I use labels to select agents to run builds on specific
> operating systems and with a fixed set of specific JDK versions. This
> all works fine. However: With my current hardware setup, the Windows
> node is _not_ going to be online 24/7 (the Linux node is always
> available).
>
> Is there a way I can adapt the above pipeline to basically say "If
> there's a Windows node online, run the stages, otherwise trivially
> succeed"? Right now, if no Windows node is available, the pipeline will
> hang until either one becomes available or the entire job times out.
>
> --
> Mark Raynsford | https://www.io7m.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/20201231212628.447a21b5%40sunflower.int.arc7.info
> .
>

-- 
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/CAO49JtF93ptAXbZzCXtBTFuVhCz2P62TgNPvFu8H8E%3DKfAXB8Q%40mail.gmail.com.