Re: [Fuego] fuego add-nodes issue
Pavan Arun Deshpande <[email protected]> Thu, 10 Mar 2022 15:50:34 +0530
| Newsgroups | dev.linux.lists.fuego |
|---|---|
| Message-ID | <CAMQEYMfNvRObTXBy58UeSJv73oHGXMXPNv-8ks2FEkkvVHmtHQ@mail.gmail.com> |
--0000000000002b1ee805d9da9190 Content-Type: text/plain; charset="UTF-8" Hi Tim, Now the issue is resolved. Yes, it was due to the jenkins plugins . regards Pavan Arun Deshpande On Thu, Mar 10, 2022 at 12:59 AM Bird, Tim <[email protected]> wrote: > Pavan, > > It looks like this is due to a problem with the latest Jenkins plugins > working properly > with the (frozen) Jenkins server version that is used by Fuego. > > In previous releases of Fuego, we froze the plugin versions so that they > would be > compatible with the frozen server version that we installed in the docker > container. > The "floating" plugin versions problem was reported by another user, but > the > symptoms were different. However, it now appears that the plugin versions > have > changed more, and are enough to cause the problem you are seeing. > > I just checked in some code to freeze the plugin versions to those that > will work > with Jenkins version 2.249.3 (the version currently supported by Fuego). > > Can you please check out the latest code, and try again. The change is in > the > 'fuego' repository (not 'fuego-core'), and here is the commit id and > description: > > 8dd5774 install: use frozen plugin versions for Jenkins 2.249.3 > > Please try again and let me know what happens. I'm leaving town on > Friday, March 11, and I'm out-of-office on March 10, but I'll try to check > to see if this worked for you, before I go on my extended vacation. > > If you have more problems, try checking the Jenkins log files, > that are under the directory /var/lib/jenkins/logs inside the container. > > Hopefully this will work, though. > -- Tim > > > -----Original Message----- > > From: Pavan Arun Deshpande <[email protected]> > > > > hi , > > one team in our company is setting up fuego.they are getting some errors > while adding boards to the jenkins(they have the latest code > > base). > > > > I have attached the screenshot of the error and also the git commit logs > also. > > Let us know your thoughts on this. > > > > > > regards > > > > Pavan Arun Deshpande > > > > > > > > > > > > This message contains confidential information and is intended only for > the individual(s) named. If you are not the intended recipient, you > > are notified that disclosing, copying, distributing or taking any action > in reliance on the contents of this mail and attached file/s is strictly > > prohibited. Please notify the sender immediately and delete this e-mail > from your system. E-mail transmission cannot be guaranteed to be > > secured or error-free as information could be intercepted, corrupted, > lost, destroyed, arrive late or incomplete, or contain viruses. The > > sender therefore does not accept liability for any errors or omissions > in the contents of this message, which arise as a result of e-mail > > transmission. > > -- This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. --0000000000002b1ee805d9da9190 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi Tim,</div><div><br></div><div>Now the issue is res= olved. <br></div><div><br></div><div>Yes, it was due to the jenkins plugins= .</div><div><br></div><div>regards</div><div>Pavan Arun Deshpande<br></div= ></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"= >On Thu, Mar 10, 2022 at 12:59 AM Bird, Tim <<a href=3D"mailto:Tim.Bird@= sony.com">[email protected]</a>> wrote:<br></div><blockquote class=3D"gm= ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,= 204,204);padding-left:1ex">Pavan,<br> <br> It looks like this is due to a problem with the latest Jenkins plugins work= ing properly<br> with the (frozen) Jenkins server version that is used by Fuego.<br> <br> In previous releases of Fuego, we froze the plugin versions so that they wo= uld be<br> compatible with the frozen server version that we installed in the docker c= ontainer.<br> The "floating" plugin versions problem was reported by another us= er, but the<br> symptoms were different. However, it now appears that the plugin versions h= ave<br> changed more, and are enough to cause the problem you are seeing.<br> <br> I just checked in some code to freeze the plugin versions to those that wil= l work<br> with Jenkins version 2.249.3 (the version currently supported by Fuego).<br= > <br> Can you please check out the latest code, and try again.=C2=A0 The change i= s in the<br> 'fuego' repository (not 'fuego-core'), and here is the comm= it id and description:<br> <br> 8dd5774 install: use frozen plugin versions for Jenkins 2.249.3<br> <br> Please try again and let me know what happens.=C2=A0 I'm leaving town o= n<br> Friday, March 11, and I'm out-of-office on March 10, but I'll try t= o check<br> to see if this worked for you, before I go on my extended vacation.<br> <br> If you have more problems, try checking the Jenkins log files,<br> that are under the directory /var/lib/jenkins/logs inside the container.<br= > <br> Hopefully this will work, though.<br> =C2=A0-- Tim<br> <br> > -----Original Message-----<br> > From: Pavan Arun Deshpande <<a href=3D"mailto:pavan.ad@pathpartnert= ech.com" target=3D"_blank">[email protected]</a>><br> > <br> > hi ,<br> > one team in our company is setting up fuego.they are getting some erro= rs while adding boards to the jenkins(they have the latest code<br> > base).<br> > <br> > I have attached the screenshot of the error and also the git commit lo= gs also.<br> > Let us know your thoughts on this.<br> > <br> > <br> > regards<br> > <br> > Pavan Arun Deshpande<br> > <br> > <br> > <br> > <br> > <br> > This message contains confidential information and is intended only fo= r the individual(s) named. If you are not the intended recipient, you<br> > are notified that disclosing, copying, distributing or taking any acti= on in reliance on the contents of this mail and attached file/s is strictly= <br> > prohibited. Please notify the sender immediately and delete this e-mai= l from your system. E-mail transmission cannot be guaranteed to be<br> > secured or error-free as information could be intercepted, corrupted, = lost, destroyed, arrive late or incomplete, or contain viruses. The<br> > sender therefore does not accept liability for any errors or omissions= in the contents of this message, which arise as a result of e-mail<br> > transmission.<br> <br> </blockquote></div> <br> <p><span lang=3D"EN-IN">This message contains confidential information and is intended only for the individual(s) named.</span><span lang=3D"EN-IN"> </span>If you are not the = intended recipient, you are notified that disclosing, copying, distributing or takin= g any action in reliance on the contents of this mail and attached file/s is stri= ctly prohibited<span lang=3D"EN-IN">. Please notify the sender immediately and delete this e-mail from your system. E-mail transmis= sion cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or cont= ain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mai= l transmission.</span></p> --0000000000002b1ee805d9da9190--