Re: Extracting of jenkins error

[Victor Martinez]

I understand now, thanks.

I'm afraid in your case the issue is related to a syntax error in the 
Pipeline so nothing about a runtime error, so there is no way to run any 
echo as you want.

Though If I recall the Text Area field had a syntax validation, but I 
cannot find if that's true or something I just wrongly said. I might need 
to dig a bit deeper, so I'll comment here if I can find something.

In any case, if you use pipeline script from SCM definition then you could 
benefit of the linting in your local environment:

   - https://www.jenkins.io/doc/book/pipeline/development/#linter

Cheers

On Tuesday, 19 January 2021 at 18:13:12 UTC jamespr...@gmail.com wrote:

> For example I made a missing of closing statement " } " in my pipeline 
> script as shown below
> [image: cats2.jpg]
>
>
>
> Which  produces the error in jenkins console output as shown below 
> [image: cats1.jpg]
>
>
> So I want to print out the wrong statement in my jenkins output (using 
> echo ) along with buildnumber ,build outcome as shown below .
>
>
> [image: catsw.jpg]
>
> For example in this particular build it should say expecting '}', found '' 
> @ line 23, column 1. 
>
>  
> On Tuesday, January 19, 2021 at 6:51:59 PM UTC+5:30 victormar...@gmail.com 
> wrote:
>
>> There are different approaches but need more information, can you 
>> elaborate? 
>>
>> On Tuesday, 19 January 2021 at 10:14:08 UTC jamespr...@gmail.com wrote:
>>
>>> How to find specific errors from jenkins console output and print them 
>>> by echo statement 
>>>
>>

-- 
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/f5385f0d-d84c-42dd-9991-7db573cf9fdcn%40googlegroups.com.

Increasing number of unavailable plugin updates

[Alan Sparks]

We're running the LTS version of Jenkins (2.263.2).   Starting a few weeks back 
or so, we're getting more and more updates listed in the plugin manager that 
are not installable.  I'm trying to understand if at least one of them is not 
compatible with LTS and requires a higher version of Jenkins, or if there's 
some interdependency that makes the list depend on itself...

So far I have a list of the following that can't be updated (listed as 
UNAVAILABLE):
Branch API 2.6.3
Environment Injector 2.4.0
Favorite 2.3.3
LDAP 2.3
Maven Integration 3.9
Parameterized Trigger 2.40
Token Macro 2.14

Is there something I'm missing, or must I just wait for LTS to catch up 
somehow?  Thanks in advance for your response.
-Alan

-- 
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/DM6PR18MB3306BE46A355B1241E779EA6C5A21%40DM6PR18MB3306.namprd18.prod.outlook.com.

Re: Increasing number of unavailable plugin updates

[Mark Waite]

On Wed, Jan 20, 2021 at 4:13 PM Alan Sparks 
wrote:

> We’re running the LTS version of Jenkins (2.263.2).   Starting a few weeks
> back or so, we’re getting more and more updates listed in the plugin
> manager that are not installable.  I’m trying to understand if at least one
> of them is not compatible with LTS and requires a higher version of
> Jenkins, or if there’s some interdependency that makes the list depend on
> itself…
>
>
A Jenkins plugin release declares the minimum Jenkins version that it
supports.  The Jenkins versions after 2.263 (2.264 through 2.276 and
beyond) include the changes described in "Major changes in weekly releases
".
Supporting those major changes in the plugins you listed has required that
the plugins increase their minimum Jenkins version to a version 2.264 or
higher.

Those plugin versions are listed as unavailable because they won't run in
Jenkins 2.263.

The most recent weekly releases are able to install those plugins.  Users
of the weekly releases are leading the effort to check that the major
changes are ready for the March 2021 Jenkins long term support release.

If there is something critical that you need in those newer plugin
releases, you'll need to switch from the Jenkins LTS to the Jenkins weekly
release.  In general, those plugin releases were created so that they could
support the changes in weekly releases after 2.263.

If there isn't something critical that you need in those newer plugin
releases, you can remain with Jenkins LTS and remain with the releases that
support Jenkins 2.263.x.

Mark Waite


>
>
> So far I have a list of the following that can’t be updated (listed as
> UNAVAILABLE):
>
> Branch API 2.6.3
>
> Environment Injector 2.4.0
>
> Favorite 2.3.3
>
> LDAP 2.3
>
> Maven Integration 3.9
>
> Parameterized Trigger 2.40
>
> Token Macro 2.14
>
>
>
> Is there something I’m missing, or must I just wait for LTS to catch up
> somehow?  Thanks in advance for your response.
>
> -Alan
>
> --
> 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/DM6PR18MB3306BE46A355B1241E779EA6C5A21%40DM6PR18MB3306.namprd18.prod.outlook.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/CAO49JtFGV9k9M-cyiSXBMFvd7pPdagWQK1XkabucjPkfR6zaEg%40mail.gmail.com.

Re: Extracting of jenkins error

[james prakash]

Thanks alot for your help @victor

On Wednesday, January 20, 2021 at 6:35:59 PM UTC+5:30 
victormar...@gmail.com wrote:

> I understand now, thanks.
>
> I'm afraid in your case the issue is related to a syntax error in the 
> Pipeline so nothing about a runtime error, so there is no way to run any 
> echo as you want.
>
> Though If I recall the Text Area field had a syntax validation, but I 
> cannot find if that's true or something I just wrongly said. I might need 
> to dig a bit deeper, so I'll comment here if I can find something.
>
> In any case, if you use pipeline script from SCM definition then you could 
> benefit of the linting in your local environment:
>
>- https://www.jenkins.io/doc/book/pipeline/development/#linter
>
> Cheers
>
> On Tuesday, 19 January 2021 at 18:13:12 UTC jamespr...@gmail.com wrote:
>
>> For example I made a missing of closing statement " } " in my pipeline 
>> script as shown below
>> [image: cats2.jpg]
>>
>>
>>
>> Which  produces the error in jenkins console output as shown below 
>> [image: cats1.jpg]
>>
>>
>> So I want to print out the wrong statement in my jenkins output (using 
>> echo ) along with buildnumber ,build outcome as shown below .
>>
>>
>> [image: catsw.jpg]
>>
>> For example in this particular build it should say expecting '}', found 
>> '' @ line 23, column 1. 
>>
>>  
>> On Tuesday, January 19, 2021 at 6:51:59 PM UTC+5:30 
>> victormar...@gmail.com wrote:
>>
>>> There are different approaches but need more information, can you 
>>> elaborate? 
>>>
>>> On Tuesday, 19 January 2021 at 10:14:08 UTC jamespr...@gmail.com wrote:
>>>
 How to find specific errors from jenkins console output and print them 
 by echo statement 

>>>

-- 
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/e3730992-62e6-4ea4-ab6a-79cc5233fc2bn%40googlegroups.com.