Re: Scripts not permitted to use a method already approve in In-process Script Approval GUI

[Romaric Crailox]

For information, I open a ticket here 
<https://issues.jenkins-ci.org/browse/JENKINS-43813>.

Best regards
Romaric Crailox

-- 
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/601c751a-870f-4ea3-9230-09da93a2a1c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Scripts not permitted to use a method already approve in In-process Script Approval GUI

[Romaric Crailox]

I'm pretty sure that it started less than one month. 
I am on Jenkins 2.55.

Furthermore I have Permissive Script Security Plugin installed.

Le mercredi 26 avril 2017 04:57:48 UTC+2, Lucas Brendel a écrit :

> I have been running in to this exact same issue, in fact i just posted 
> here  
> about 
> it also. Do you know when it started for you? I can't tell if my update of 
> Jenkins to 2.46 caused it or if it was due to an update to Script Security, 
> which was February, and i just wasn't paying attention. 
>

-- 
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/59963810-b250-4b95-b67d-147e0587f4d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Scripts not permitted to use a method already approve in In-process Script Approval GUI

[Romaric Crailox]

Hello all,

I have this error during execution of a Jenkins job with "Scan for compiler 
warnings" in "post build action" (two parsers are use : parser1 and 
parser2)  :

[WARNINGS] Parsing warnings in files 'output1' with parser parser1
[WARNINGS] Groovy sandbox rejected the parsing script for parser parser1: 
Scripts not permitted to use method java.util.regex.MatchResult group int. 
You will need to manually approve the call in the Script Approval UI.
[WARNINGS] Parsing warnings in files 'output2' with parser parser2
[WARNINGS] Groovy sandbox rejected the parsing script for parser parser2: 
Scripts not permitted to use method java.util.regex.MatchResult group int. 
You will need to manually approve the call in the Script Approval UI.

Problem, java.util.regex.MatchResult method already approve in "In-process 
Script Approval" Windows (in Manage Jenkins) : see script_aproval.png file.
In "Manage Jenkins" > "Configure System" > "Compiler Warnings" > "Parsers" 
there is no error message below parser1 and parser2... (I think about error 
message like "An exception occurred during evaluation of the Groovy script: 
Scripts not permitted to use method 
hudson.plugins.analysis.util.model.FileAnnotation setModuleName 
java.lang.String").

Can you help me to understand what thing I have missed to make please ?

Best regards

Romaric Crailox

-- 
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/1869648b-63d2-48ef-a231-da57e08b092f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Delete workspace on slave

[Romaric Crailox]

Thanks for this answere and solution (I use Git).

Le vendredi 7 avril 2017 15:30:34 UTC+2, Mark Waite a écrit :
>
> I suspect that is behaving as expected.  The "Delete workspace before 
> build starts" probably only deletes the "flyweight" workspace when it is 
> used in the context of a multi-configuration job.
>
> If you're using Git as your SCM, there is an "Additional Behaviours" 
> choice to "Wipe out repository and force clone".  That will wipe the 
> workspace in each of the multi-configuration jobs.
>
> Mark Waite
>
> On Fri, Apr 7, 2017 at 12:47 AM Romaric Crailox <romaric...@gmail.com 
> > wrote:
>
>> Hello, 
>>
>> I do not know if it's normal or a Jenkins error, but I have a job with 
>> configuration matrix to perform build on 2 computer.
>> I have "Delete workspace before build starts" option checked on this job.
>>
>> Unfortunately, workspace is delete only on "master" node, that is node 
>> where main job (job which launch all the job necessary to cover 
>> configuration matrix) is perform.
>> Workspace on second node is not delete.
>>
>> Do you know if it's normal?
>>
>> Thanks
>>
>> -- 
>> 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/8bdfc171-45fa-4fd2-ba22-7f9b021b09ec%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/8bdfc171-45fa-4fd2-ba22-7f9b021b09ec%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/d7a80d65-8067-4e8b-9003-fc4f00a4d997%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Delete workspace on slave

[Romaric Crailox]

Hello, 

I do not know if it's normal or a Jenkins error, but I have a job with 
configuration matrix to perform build on 2 computer.
I have "Delete workspace before build starts" option checked on this job.

Unfortunately, workspace is delete only on "master" node, that is node 
where main job (job which launch all the job necessary to cover 
configuration matrix) is perform.
Workspace on second node is not delete.

Do you know if it's normal?

Thanks

-- 
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/8bdfc171-45fa-4fd2-ba22-7f9b021b09ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Delete workspace relative to matrix configuration

[Romaric Crailox]

Hello,

Say me if I wrong but I don't see anything to delete a part of a Jenkins 
job's workspace relative to matrix configuration.
If "Delete workspace before build starts" option is checked, you can't 
configure it to delete only the part of the workspace corresponding of only 
one value of an user-defined axis.

Is this exact ?

Best Regards

-- 
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/c9e683d4-a601-4baa-b3fa-f2456ddca09c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Delete workspace for only failed part of the matrix

[Romaric Crailox]

Hello,

I have a Jenkins jobs use for compilation. 
I have 2 axis : PLATFORM and MODE. PLATFORM can take x86 or crosscompile 
value. MODE can take debug or notdebug value.

I have "Delete workspace before build starts" option checked, and "Rerun 
build only for failed parts on the matrix" option of "Retry build after 
failure" plugin checked.
My problem is that if, for exemple, MODE debug on x86 PLATFORM failed, 
Jenkins rerun this part of matrix but delete all workspace at the begining 
of this new rerun. At the end, I have a workspace with only MODE debug on 
x86 PLATFORM that is compiled. Other part of matrix are not compile.


I can't "Delete workspace before build starts" in "Post Build Action" 
instead of "Delete workspace before build starts" because I need a compiled 
project to achieve some test, analysis later.
I would like to keep the principle of cleaning my workspace before build 
because, in my opinion, it permit to supress side effect of some old file 
or folder remaining of an old compilation or test.


Do you have, please, some ideas ?


Best Regards

-- 
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/b293ae53-78a1-4b0b-9d2f-0b9ef98ae4a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.