Re: thread safety of scripted pipeline parallel and usage of nested parallel
So nested parallel is allowed too ? ---Original--- From: "'Devin Nusbaum' via Jenkins Users"https://github.com/jenkinsci/workflow-cps-plugin#technical-design for a few more details. You should not need to worry about Java thread safety across the various branches in a parallel step as long as you are not doing anything with Java threads directly in your Pipeline. On Mon, Nov 1, 2021 at 7:03 AM kuisathaverat https://groups.google.com/d/msgid/jenkinsci-users/0712b8c5-42dc-439f-a017-2a5ca45ad1e9n%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/fed01b0e-a04c-448b-9f32-3d2b3ffd6c40n%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/tencent_579508DE2429C25B92D7BFFF6AED09115C08%40qq.com. -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/9fzFnwLkfxU/unsubscribe. To unsubscribe from this group and all its topics, 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/tencent_E81808632457C23792EEBFC46A5A093E5C08%40qq.com. -- Un SaludoIván Fernández Calvo https://www.linkedin.com/in/iv%C3%A1n-fern%C3%A1ndez-calvo-21425033 -- 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/CAKo5Qrq%2BP9qYn%3Dm9Ssc4aSCAkedr_7D1jRTSuKYPQNxJ_3xrmw%40mail.gmail.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/CAF73ShC883ws%3DYvMVcBeeR%3Dyub8iyjA0%3DidL_pzDocki0Rp5dg%40mail.gmail.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/tencent_9808132449C2AC9235BF756AD809F75CD008%40qq.com.
Re: Resource Root Problem Post Upgrade
yeah, its a doozy of a stack trace 01-Nov-2021 14:08:40.829 WARNING [Handling POST /descriptorByName/jenkins.security.ResourceDomainConfiguration/checkUrl from xx.x.xx.xxx : https-jsse-nio-9443-exec-22] hudson.init.impl.InstallUncaughtExceptionHandler.handleException Caught unhandled exception with ID 5d0d5334--4ac8-a484-7deef5d062fa javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:816) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:281) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:766) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:898) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:694) at org.kohsuke.stapler.Stapler.service(Stapler.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:156) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:80) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:60) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:64) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:153) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:159) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:92) at jenkins.security.AcegiSecurityExceptionFilter.doFilter(AcegiSecurityExceptionFilter.java:52) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:97) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:53) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:97) at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:121) at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:115) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:97) at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:105) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:97) at org.springframework.security.web.authentication.rememberme.RememberMeAuthenticationFilter.doFilter(RememberMeAuthenticationFilter.java:101) at org.springframework.security.web.authentication.rememberme.RememberMeAuthenticationFilter.doFilter(RememberMeAuthenticationFilter.java:92) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:97) at org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:218) at org.springframework.security.web.authentication.AbstractAuthenticationProce
Re: Resource Root Problem Post Upgrade
On Mon, Nov 1, 2021 at 8:11 PM Matt Wilson wrote: > Logging ID=5d0d5334--4ac8-a484-7deef5d062fa > Check the Jenkins system log for the corresponding error message. -- 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/CAMo7PtKMT7k5o9ho8gboFWg36UFBv5APyS-AgMw7bRpcoS_VoQ%40mail.gmail.com.
Re: Resource Root URL certificate
Sorry, I know this doesn't really answer your question, but though I'd share since it might help someone else. We use a Mutli Domain EV cert for this purpose. Its worked well and is probably less maintenance... On Tuesday, February 11, 2020 at 12:33:19 PM UTC-5 Stefan Spieker wrote: > I would like to use the Resource root URL feature and have an alternative > name for the server. > Since it is currently accessible by https, I would also like to keep it > https also for the resources. > > How do I specify the second certificate to the jenkins startup command? > I'm using the embedded winstone. > -- 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/8ef28ef9-1ae3-4acf-b351-bf5f87300b1cn%40googlegroups.com.
Resource Root Problem Post Upgrade
I just upgraded to LTS 2.303.2 from 2.289.3. Post upgrade I'm having problems with my system. I can no longer download artifacts from my server. When I try, I get a 404 error "*Message* Jenkins serves only static files on this domain.". Interestingly enough, using the download zip feature works fine. I've been using a Resource Root URL for some time now with no issues. I noticed on my main configuration screen I'm seeing an error under my URL entry A problem occurred while processing the request. Logging ID=5d0d5334--4ac8-a484-7deef5d062fa I tried removing my Resource root url, and my download issues went away. this of course causes a lot of issues with other features that rely on the resource root url to be displayed properly. Anyone run into anything like this recently? -- 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/b1f4cdf2-034b-4a26-8190-f017782172d7n%40googlegroups.com.
Need to adjust Jenkins pipeline logs using Groovy syntax at each stage
Hi, I am working on below to suppress Jenkins pipeline logs using Groovy syntax at each stage, like for Initialization or Build stage we need to log only "ERROR" level. and for Deployment Stage we need to log DEBUG level logs.. And don't want to print each and every message in console output. Thanks, Anil -- 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/cdbc4b93-fcab-4c49-a427-94c82a4655b5n%40googlegroups.com.
Re: thread safety of scripted pipeline parallel and usage of nested parallel
The Pipeline execution engine uses a "green thread" model internally -
there is only ever one Java thread executing the Groovy DSL for a given
Pipeline (step execution may use additional Java threads, but this should
always be transparent to users). See the final paragraph under
https://github.com/jenkinsci/workflow-cps-plugin#technical-design for a few
more details. You should not need to worry about Java thread safety across
the various branches in a parallel step as long as you are not doing
anything with Java threads directly in your Pipeline.
On Mon, Nov 1, 2021 at 7:03 AM kuisathaverat
wrote:
> Jenkins pipelines have two types of code, the steps and directives
> provided by Jenkins, and the Groovy code.
> All the Jenkins steps and directives are thread safe. On your Groovy you
> must guarantee is thread-safe if it needs to be.
> Unstash and archive are Jenkins steps you can use them in parallel tasks
> and they must work as expected, I only see one case that archive can cause
> issues and is when you archive the same artifact name from different tasks,
> but is completely logical that fails or corrupt the file due to you ar
> doing something wrong (the same happens with stash in parallel tasks)
> The last thought, try to minimize all the groovy code you add to your
> pipelines, all Groovy code run in the Jenkins controller, try to delegate
> on scripts, commands, tools, ... as much as possible.
>
> El dom, 31 oct 2021 a las 18:55, 'abstrakta' via Jenkins Users (<
> jenkinsci-users@googlegroups.com>) escribió:
>
>> sorry, pipeline code should be correct like this:
>> pipeline {
>> agent any
>> stages {
>> stage('Parallel Build') {
>> steps {
>> script {
>> def builds = [:]
>> def tests = [:]
>> stash name: 'src', include: 'src/**'
>>
>> def build_action = { platform, tests ->
>>
>> //build in some slave node.
>> node ("${platform}") {
>> //unstash need thread mutex lock?
>> unstash name: 'src'
>>
>> sh "make ${platform}"
>>
>> //archive need thread mutex lock?
>> archive name: "./${platform}"
>> }
>>
>> //nested parallel, outside of node block
>> parallel tests
>> }
>>
>> def test_action = { platform ->
>> //test in some slave node.
>> node ("${platform}") {
>> sh "make ${platform}-test"
>> }
>> }
>>
>> tests["A1"] = { test_action("A1") }
>> tests["A2"] = { test_action("A2") }
>> tests["A3"] = { test_action("A3") }
>> builds["A"] = { build_action("A",tests) }
>>
>> tests = [:]
>> tests["B1"] = { test_action("B1") }
>> tests["B2"] = { test_action("B2") }
>> builds["B"] = { build_action("B",tests) }
>>
>> tests = [:]
>> tests["C1"] = { test_action("C1") }
>> tests["C2"] = { test_action("C2") }
>> builds["C"] = { build_action("B",tests) }
>>
>> parallel builds
>> }
>> }
>> }
>> }
>> }
>>
>> ---原始邮件---
>> *发件人:* "'abstrakta' via Jenkins Users"
>> *发送时间:* 2021年10月31日(周日) 晚上10:48
>> *收件人:* "jenkinsci-users";
>> *主题:* 回复： thread safety of scripted pipeline parallel and usage of
>> nested parallel
>>
>> OK,I know what you means. But I test these pipeline that data is not
>> synchronized many times( about more than 700 times,I use periodical build
>> to test it automatically). Shared data that is not synchronized is
>> processed correctly every time. Do you really encounter the situation that
>> shared data is corrupt in parallel task?
>>
>> In some scenarios, I want to parallel build one more artifacts that used
>> in different platforms from the same source code. And then I parallel test
>> all artifacts in their corresponding platforms(One artifact might be used
>> in one more platforms).
>>
>> build platform: A B C
>> test platform: A(A1 A2 A3), B(B1 B2), C(C1 C2)
>>
>>-> A1
>> -> A -> A2
>>| -> A3
>> /
>> source code --> B -> B1
>> \-> B2
>>|
>> -> C -> C1
>>-> C2
>>-> C3
>>
>> Pipeline code like this:
>>
>> pipeline {
>> agent any
>> stages {
>> stage('Parallel Build') {
>> steps {
>>
Re: thread safety of scripted pipeline parallel and usage of nested parallel
Jenkins pipelines have two types of code, the steps and directives provided
by Jenkins, and the Groovy code.
All the Jenkins steps and directives are thread safe. On your Groovy you
must guarantee is thread-safe if it needs to be.
Unstash and archive are Jenkins steps you can use them in parallel tasks
and they must work as expected, I only see one case that archive can cause
issues and is when you archive the same artifact name from different tasks,
but is completely logical that fails or corrupt the file due to you ar
doing something wrong (the same happens with stash in parallel tasks)
The last thought, try to minimize all the groovy code you add to your
pipelines, all Groovy code run in the Jenkins controller, try to delegate
on scripts, commands, tools, ... as much as possible.
El dom, 31 oct 2021 a las 18:55, 'abstrakta' via Jenkins Users (<
jenkinsci-users@googlegroups.com>) escribió:
> sorry, pipeline code should be correct like this:
> pipeline {
> agent any
> stages {
> stage('Parallel Build') {
> steps {
> script {
> def builds = [:]
> def tests = [:]
> stash name: 'src', include: 'src/**'
>
> def build_action = { platform, tests ->
>
> //build in some slave node.
> node ("${platform}") {
> //unstash need thread mutex lock?
> unstash name: 'src'
>
> sh "make ${platform}"
>
> //archive need thread mutex lock?
> archive name: "./${platform}"
> }
>
> //nested parallel, outside of node block
> parallel tests
> }
>
> def test_action = { platform ->
> //test in some slave node.
> node ("${platform}") {
> sh "make ${platform}-test"
> }
> }
>
> tests["A1"] = { test_action("A1") }
> tests["A2"] = { test_action("A2") }
> tests["A3"] = { test_action("A3") }
> builds["A"] = { build_action("A",tests) }
>
> tests = [:]
> tests["B1"] = { test_action("B1") }
> tests["B2"] = { test_action("B2") }
> builds["B"] = { build_action("B",tests) }
>
> tests = [:]
> tests["C1"] = { test_action("C1") }
> tests["C2"] = { test_action("C2") }
> builds["C"] = { build_action("B",tests) }
>
> parallel builds
> }
> }
> }
> }
> }
>
> ---原始邮件---
> *发件人:* "'abstrakta' via Jenkins Users"
> *发送时间:* 2021年10月31日(周日) 晚上10:48
> *收件人:* "jenkinsci-users";
> *主题:* 回复： thread safety of scripted pipeline parallel and usage of nested
> parallel
>
> OK,I know what you means. But I test these pipeline that data is not
> synchronized many times( about more than 700 times,I use periodical build
> to test it automatically). Shared data that is not synchronized is
> processed correctly every time. Do you really encounter the situation that
> shared data is corrupt in parallel task?
>
> In some scenarios, I want to parallel build one more artifacts that used
> in different platforms from the same source code. And then I parallel test
> all artifacts in their corresponding platforms(One artifact might be used
> in one more platforms).
>
> build platform: A B C
> test platform: A(A1 A2 A3), B(B1 B2), C(C1 C2)
>
>-> A1
> -> A -> A2
>| -> A3
> /
> source code --> B -> B1
> \-> B2
>|
> -> C -> C1
>-> C2
>-> C3
>
> Pipeline code like this:
>
> pipeline {
> agent any
> stages {
> stage('Parallel Build') {
> steps {
> script {
> def builds = [:]
> def tests = [:]
> stash name: 'src', include: 'src/**'
>
> def build_action = { platform, tests ->
>
> //build in some slave node.
> node ("${platform}") {
> //unstash need thread mutex lock?
> unstash name: 'src'
>
> sh "make ${platform}"
>
> //archive need thread mutex lock?
> archive name: "./${platform}"
> }
>
> //nested parallel, outside of
Re: Unable to Run jenkins job on zos slave
This is an Error of zOS I dunno which file is trying to open, I doubt that
you can even run the script in an SSH session with something like this
Try the following in a machine with access by SSH to the zOS Agent,
create a hello.sh file locally with the script
pwd
echo foo
date
Execute an ssh command like this (you have to change the access method,
user, and host)
ssh AGENT_USER@LINUX_IP 'sh -s' < hello.sh
ssh AGENT_USER@LINUX_IP 'bash -s' < hello.sh
I am not wrong you will see the same error
this is a similar issue I have found in a IBM
forum https://ibmmainframes.com/about67532.html
El lunes, 1 de noviembre de 2021 a las 5:57:33 UTC+1, adharsh...@gmail.com
escribió:
> Yes, please find the below output.
>
> FSUM7343 cannot open □?EC□?¤IA for output : no such file or directory.
>
> On Fri, 29 Oct 2021, 1:00 pm kuisathaverat, wrote:
>
>> Did you test other commands in the Freestyle job? try this
>>
>> #!/bin/bash
>> pwd
>> echo foo
>> date
>>
>>
>>
>> El vie, 29 oct 2021 a las 7:21, Adharsha sri ()
>> escribió:
>>
>>> Hi,
>>>
>>> In /etc/profile added the below bash environment variables
>>> export _CEE_RUNOPTS=“FILETAG(AUTOCVT,AUTOTAG) POSIX(ON)”
>>> export _BPXK_AUTOCVT=ON
>>> export _TAG_REDIR_ERR=txt
>>> export _TAG_REDIR_IN=txt
>>> export _TAG_REDIR_OUT=txt
>>>
>>>
>>> And then able to run the below pipeline job
>>>
>>> node('hostname')
>>> {
>>> stage('test')
>>> {
>>> sh "pwd"
>>> sh " hostname"
>>> sh "date"
>>> }}
>>>
>>> But when running the below freestyle job , gettingerror
>>>
>>> Execute shell:
>>> date
>>>
>>> Error:
>>>
>>> +□?A/EA
>>> /tmp/jenkjns123456789.sh 1: FSUM7351 not found
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Thu, 28 Oct 2021, 9:51 pm Ivan Fernandez Calvo,
>>> wrote:
>>>
should not, the FreeStyle "Execute shell" step and the Pipeline sh step
work more or less in the same way, I never see a fail one when the other
works. In any case, it is difficult to help you if you do not provide more
info about what you did, what does not work exactly, Why does not work,
what error you see in the Jenkins logs (if any), what error you see in the
build logs(if any), What did you change in the Agents, and so on.
El jueves, 28 de octubre de 2021 a las 13:38:06 UTC+2,
adharsh...@gmail.com escribió:
> Now I am able run shell commands using pipeline job but unable to run
> using freestyle job. Will there be any difference
>
> On Wed, 27 Oct 2021, 10:10 pm Adharsha sri,
> wrote:
>
>> Thank you , will check on that part.
>>
>> On Wed, 27 Oct 2021, 6:45 pm Ivan Fernandez Calvo, <
>> kuisat...@gmail.com> wrote:
>>
>>> the echo step is pure Groovy, however, the sh step uses bash, so
>>> probably you do not have bash in the PATH of that user, check that bash
>>> is
>>> installed and that user can use it.
>>>
>>> El miércoles, 27 de octubre de 2021 a las 15:01:08 UTC+2,
>>> adharsh...@gmail.com escribió:
>>>
Able to run the echo commands but not able to run the shell commands
On Wed, 27 Oct 2021, 4:12 pm Adharsha sri,
wrote:
> Can anyone help on this error
>
> On Wed, 27 Oct 2021, 2:38 pm Adharsha sri,
> wrote:
>
>> Thanks for the sample pipeline but getting error like " process
>> apparently never started in path
>> ( running jenkins temporarily with
>> -Dorg.jenkinsci.plugins.durabletask.BourneshellScript.LAUNCH_DIAGNOSTICS=true
>>
>> might make the problem clearer).
>>
>> Thanks.
>>
>> On Wed, 27 Oct 2021, 1:18 pm Ivan Fernandez Calvo, <
>> kuisat...@gmail.com> wrote:
>>
>>> This is a pretty simple pipeline to expose your environment
>>> settings
>>>
>>> pipeline {
>>> agent { label 'YOUR_AGENT_LABELS' }
>>> stages {
>>> stage('test') {
>>> steps {
>>> sh 'export'
>>> sh 'set'
>>> }
>>> }
>>> }
>>> }
>>>
>>> El miércoles, 27 de octubre de 2021 a las 9:13:59 UTC+2,
>>> adharsh...@gmail.com escribió:
>>>
The Configuration from agent is fine right, but it will be
useful only when we run the jave script. So for shell commands we
need to
check .bashrc file in the agent server. Can you please provide the
screenshot of the .bashrc file and please provide the script you
are using
and examples of export and set. This will be very helpful for us.
Thanks.
On Wed, 27 Oct 2021, 8:04 am Adharsha sri, <
adharsh...@gmail.com> wrote:
> Can you please provide an example.
>>>
