Re: Kubernetes plugin for Jenkins after dockershim runtime is deprecated

[Carlos Sanchez]

You cannot use the docker.sock anymore

On Wed, Oct 27, 2021 at 5:00 AM 'Mario Rodriguez' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> and how about if we are using the kubernetes plugin podTemplate
> 
> ?  more less like this:
>
> podTemplate(cloud: 'kubernetes', label: args.pipelineName,
> containers: getContainers(...),
> volumes: [
> hostPathVolume(hostPath: '/var/run/docker.sock', mountPath:
> '/var/run/docker.sock'),
> ])  {
>gcloud auth configure-docker --account=
> jenk...@myproject.iam.gserviceaccount.com
>docker build --pull -t ${env.btvImageFullName} -t
> ${env.btvLatestFullName} .
> }
>
> On Thursday, September 30, 2021 at 1:32:06 AM UTC-6 car...@apache.org
> wrote:
>
>> You can use a different builder like Kaniko with the plugin
>>
>>
>> https://github.com/jenkinsci/kubernetes-plugin/blob/master/examples/kaniko-declarative.groovy
>>
>>
>> On Thu, Sep 30, 2021 at 2:05 AM 'Mario Rodriguez' via Jenkins Users <
>> jenkins...@googlegroups.com> wrote:
>>
>>> Hello, Kubernetes project is planning to deprecate support for
>>> dockershim runtime is version 1.20 and fully drop it in version 1.24 as
>>> indicated here: https://kubernetes.io/blog/2020/12/02/dockershim-faq/
>>>
>>>
>>>
>>> Reading about the impacts of dockershim removal here:
>>> https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/check-if-dockershim-deprecation-affects-you/
>>>   and
>>> here
>>> https://kubernetes.io/docs/tasks/administer-cluster/migrating-from-dockershim/migrating-telemetry-and-security-agents/
>>>  ,  any
>>> apps that depend on the docker daemon by exposing /var/run/docker.sock will
>>> be impacted.  We use the Kubernetes plugin for Jenkins
>>>  using this docker daemon
>>> exposure technique.
>>>
>>>
>>> Assuming a transition from docker to containerd, any idea what changes
>>> will be needed by Kubernetes plugin users to continue working properly ?
>>>
>>>
>>> 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/3b883835-c0bd-49ac-9017-30163ad04a79n%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/1e0e5ccf-5983-4ac3-a806-e23a2801f89en%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/CALHFn6M1RSsy%3D1-Xhwk_YocX-1kMASY03x5Uuvgpa1qG%3DYOhhQ%40mail.gmail.com.

Re: Unable to Run jenkins job on zos slave

[Adharsha sri]

Thank you , will check on that part.

On Wed, 27 Oct 2021, 6:45 pm Ivan Fernandez Calvo, 
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, 
 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, 
>> wrote:
>>
>>> Can you please provide an example.
>>>
>>> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, <
>>> kuisat...@gmail.com> wrote:
>>>
 This is the output you see in the browser, isn't it? Did you try to
 download the "view as plain text" button output in a file and with an
 editor trying to find the correct encoding? the encoding you set in the
 Agent is only from Java process launched from the remoting thread, I 
 mean
 is you launch a script in a job this script will use the encodings 
 setting
 you have configured in the user you use to connect if in your .bashrc 
 (or
 other shell configuration) you choose other encodings different than 
 UTF-8
 you will have issues showing the build logs. In these cases I use to 
 try to
 run a job that shows me the effective environment I am running the job 
 by
 using the command `export`, `set`, or both, then I check the TERM, 
 LC_* and
 LANG setting in that user.

 El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2,
 adharsh...@gmail.com escribió:

> Number of executors: 1
> Launch method: launch agents via SSH
> Host: host name
> Host key verification strategy: Non verifying verification
> strategy
>
> Port : 22
>
> Java path: /usr/lpp/java/J8.0/bin/Java
>
> JVM Options: -Dfile.encoding=ISO8859-1
> -Djava.io.tmpdir=/usr/lpp/test
>
> Prefix start Agent command:
> export JAVA_HOME =/usr/lpp/java/J8.0/ && export
> IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&
>
> Suffix start Agent command:
>  -text
>
> Connection timeout  in seconds:210
>
>
> On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
> geoffroy...@gmail.com> wrote:
>
>> can you please show a screenshot of the zos agent configuration
>> (all fields)?
>>
>> On Tuesday, 26 October 2021 at 04:27:21 UTC+2
>> adharsh...@gmail.com wrote:
>>
>>> Yes , based on that page , we have configured the slave. But
>>> still facing the same issue.
>>>
>>> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
>>> geoffroy...@gmail.com> wrote:
>>>
 Hi
 have you checked this page (first results in google):
 https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
 Seems you might need to tune the JVM options, using
 -Dfile.encoding=ISO8859-1


 On Monday, 25 October 2021 at 13:49:52 UTC+2
 adharsh...@gmail.com wrote:

> Can you please consider this as priority. Actually  it is
> critical issue for us.
> Whether z/ os platform is supported for jenkins or not . If it

Re: Unable to Run jenkins job on zos slave

[Ivan Fernandez Calvo]

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,  
>>> 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,  
> wrote:
>
>> Can you please provide an example.
>>
>> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, <
>> kuisat...@gmail.com> wrote:
>>
>>> This is the output you see in the browser, isn't it? Did you try to 
>>> download the "view as plain text" button output in a file and with an 
>>> editor trying to find the correct encoding? the encoding you set in the 
>>> Agent is only from Java process launched from the remoting thread, I 
>>> mean 
>>> is you launch a script in a job this script will use the encodings 
>>> setting 
>>> you have configured in the user you use to connect if in your .bashrc 
>>> (or 
>>> other shell configuration) you choose other encodings different than 
>>> UTF-8 
>>> you will have issues showing the build logs. In these cases I use to 
>>> try to 
>>> run a job that shows me the effective environment I am running the job 
>>> by 
>>> using the command `export`, `set`, or both, then I check the TERM, LC_* 
>>> and 
>>> LANG setting in that user.
>>>
>>> El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2, 
>>> adharsh...@gmail.com escribió:
>>>
 Number of executors: 1
 Launch method: launch agents via SSH
 Host: host name
 Host key verification strategy: Non verifying verification strategy 

 Port : 22

 Java path: /usr/lpp/java/J8.0/bin/Java

 JVM Options: -Dfile.encoding=ISO8859-1 
 -Djava.io.tmpdir=/usr/lpp/test

 Prefix start Agent command:
 export JAVA_HOME =/usr/lpp/java/J8.0/ && export  
 IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&

 Suffix start Agent command:
  -text

 Connection timeout  in seconds:210


 On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
 geoffroy...@gmail.com> wrote:

> can you please show a screenshot of the zos agent configuration 
> (all fields)?
>
> On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com 
> wrote:
>
>> Yes , based on that page , we have configured the slave. But 
>> still facing the same issue.
>>
>> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
>> geoffroy...@gmail.com> wrote:
>>
>>> Hi
>>> have you checked this page (first results in google): 
>>> https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
>>> Seems you might need to tune the JVM options, using  
>>> -Dfile.encoding=ISO8859-1
>>>
>>>
>>> On Monday, 25 October 2021 at 13:49:52 UTC+2 
>>> adharsh...@gmail.com wrote:
>>>
 Can you please consider this as priority. Actually  it is 
 critical issue for us.
 Whether z/ os platform is supported for jenkins or not . If it 
 is supported, where we are missing and why we are not getting the 
 output. 
 Please help on this issue. 

 On Mon, 25 Oct 2021, 17:12 Adharsha 

Re: Unable to Run jenkins job on zos slave

[Adharsha sri]

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, <
>> kuisathave...@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, 
 wrote:

> Can you please provide an example.
>
> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, <
> kuisat...@gmail.com> wrote:
>
>> This is the output you see in the browser, isn't it? Did you try to
>> download the "view as plain text" button output in a file and with an
>> editor trying to find the correct encoding? the encoding you set in the
>> Agent is only from Java process launched from the remoting thread, I mean
>> is you launch a script in a job this script will use the encodings 
>> setting
>> you have configured in the user you use to connect if in your .bashrc (or
>> other shell configuration) you choose other encodings different than 
>> UTF-8
>> you will have issues showing the build logs. In these cases I use to try 
>> to
>> run a job that shows me the effective environment I am running the job by
>> using the command `export`, `set`, or both, then I check the TERM, LC_* 
>> and
>> LANG setting in that user.
>>
>> El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2,
>> adharsh...@gmail.com escribió:
>>
>>> Number of executors: 1
>>> Launch method: launch agents via SSH
>>> Host: host name
>>> Host key verification strategy: Non verifying verification strategy
>>>
>>> Port : 22
>>>
>>> Java path: /usr/lpp/java/J8.0/bin/Java
>>>
>>> JVM Options: -Dfile.encoding=ISO8859-1 -Djava.io.tmpdir=/usr/lpp/test
>>>
>>> Prefix start Agent command:
>>> export JAVA_HOME =/usr/lpp/java/J8.0/ && export
>>> IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&
>>>
>>> Suffix start Agent command:
>>>  -text
>>>
>>> Connection timeout  in seconds:210
>>>
>>>
>>> On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
>>> geoffroy...@gmail.com> wrote:
>>>
 can you please show a screenshot of the zos agent configuration
 (all fields)?

 On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com
 wrote:

> Yes , based on that page , we have configured the slave. But still
> facing the same issue.
>
> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
> geoffroy...@gmail.com> wrote:
>
>> Hi
>> have you checked this page (first results in google):
>> https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
>> Seems you might need to tune the JVM options, using
>> -Dfile.encoding=ISO8859-1
>>
>>
>> On Monday, 25 October 2021 at 13:49:52 UTC+2 adharsh...@gmail.com
>> wrote:
>>
>>> Can you please consider this as priority. Actually  it is
>>> critical issue for us.
>>> Whether z/ os platform is supported for jenkins or not . If it
>>> is supported, where we are missing and why we are not getting the 
>>> output.
>>> Please help on this issue.
>>>
>>> On Mon, 25 Oct 2021, 17:12 Adharsha sri, 
>>> wrote:
>>>
 We are running just date command or simple echo command
 through execute shell but not getting the actual output

 On Mon, 25 Oct 2021, 17:09 Adharsha sri, 
 wrote:

> +□?EA/¤
> Some thing like above
>
> On Mon, 25 Oct 2021, 15:56 Fabian Cenedese, 
> wrote:
>
>> At 

Re: Declarative Pipeline: Add trigger only on when condition

[Sverre Moe]

User branches are like
origin/username/CICD
Official branches are origin/CICD og origin/master

All part of the same project.
CICD branch has a different Declarative Pipeline for CICD release build and 
deployment.
Same goes for user branches that are based on this CICD branch.

All other branches have our standard Scripted Pipeline.
So we have already splitt different pipelines for these.

When all branches based on CICD are building, we don't want to build 
release and deploy from user branches of it, only the origin/CICD.
I wanted to avoid username/CICD being automatically triggered and built 
when origin/master had built. It should only trigger on origin/CICD.

onsdag 27. oktober 2021 kl. 09:25:01 UTC+2 skrev victormar...@gmail.com:

> I'm not sure if I understood correctly what user branches of the CICD mean 
> in this particular case, can you clarify it?
> Some other questions:
> - Are the master and CICD branches part of the same projectA? 
> - If so, how do users interact with the project?
>
> As far as I see the upstream trigger option allows to listen for changes 
> in some other projects.
>
> Will it work if you split two pipelines instead?
>
> *Pipeline for the master branch *
>
> or even a multibranch pipeline if needed, then you can exclude  the CICD 
> branch to be built.
>
> *Pipeline for the branch CICD*
>
> or event a multibranch pipeline if needed, then you can exclude everything 
> but the CICD branch.
>
> triggers {
>   upstream("projectA/master'")
> }
>
>
> Cheers
>
> On Friday, 22 October 2021 at 11:17:46 UTC+1 sverr...@gmail.com wrote:
>
>> We have a branch in projectA called CICD.
>> This branch we want to be triggered automatically after the master branch 
>> has built.
>> However we do not want user branches of the CICD to be triggered 
>> automatically.
>>
>> Is it possible to avoid configuring a trigger if the branch is not CICD?
>>
>> This is probably not possible, but would be very useful.
>>
>> triggers {
>>   upstream 'projectA/master'
>>   when {
>> branch 'CICD'
>>   }
>> }
>>
>

-- 
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/7a23f6f9-cebd-44b0-b72c-4546d27128f5n%40googlegroups.com.

Re: Unable to Run jenkins job on zos slave

[Adharsha sri]

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, <
> kuisathave...@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,  wrote:
>>>
 Can you please provide an example.

 On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, <
 kuisat...@gmail.com> wrote:

> This is the output you see in the browser, isn't it? Did you try to
> download the "view as plain text" button output in a file and with an
> editor trying to find the correct encoding? the encoding you set in the
> Agent is only from Java process launched from the remoting thread, I mean
> is you launch a script in a job this script will use the encodings setting
> you have configured in the user you use to connect if in your .bashrc (or
> other shell configuration) you choose other encodings different than UTF-8
> you will have issues showing the build logs. In these cases I use to try 
> to
> run a job that shows me the effective environment I am running the job by
> using the command `export`, `set`, or both, then I check the TERM, LC_* 
> and
> LANG setting in that user.
>
> El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2,
> adharsh...@gmail.com escribió:
>
>> Number of executors: 1
>> Launch method: launch agents via SSH
>> Host: host name
>> Host key verification strategy: Non verifying verification strategy
>>
>> Port : 22
>>
>> Java path: /usr/lpp/java/J8.0/bin/Java
>>
>> JVM Options: -Dfile.encoding=ISO8859-1 -Djava.io.tmpdir=/usr/lpp/test
>>
>> Prefix start Agent command:
>> export JAVA_HOME =/usr/lpp/java/J8.0/ && export
>> IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&
>>
>> Suffix start Agent command:
>>  -text
>>
>> Connection timeout  in seconds:210
>>
>>
>> On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
>> geoffroy...@gmail.com> wrote:
>>
>>> can you please show a screenshot of the zos agent configuration (all
>>> fields)?
>>>
>>> On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com
>>> wrote:
>>>
 Yes , based on that page , we have configured the slave. But still
 facing the same issue.

 On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
 geoffroy...@gmail.com> wrote:

> Hi
> have you checked this page (first results in google):
> https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
> Seems you might need to tune the JVM options, using
> -Dfile.encoding=ISO8859-1
>
>
> On Monday, 25 October 2021 at 13:49:52 UTC+2 adharsh...@gmail.com
> wrote:
>
>> Can you please consider this as priority. Actually  it is
>> critical issue for us.
>> Whether z/ os platform is supported for jenkins or not . If it is
>> supported, where we are missing and why we are not getting the 
>> output.
>> Please help on this issue.
>>
>> On Mon, 25 Oct 2021, 17:12 Adharsha sri, 
>> wrote:
>>
>>> We are running just date command or simple echo command  through
>>> execute shell but not getting the actual output
>>>
>>> On Mon, 25 Oct 2021, 17:09 Adharsha sri, 
>>> wrote:
>>>
 +□?EA/¤
 Some thing like above

 On Mon, 25 Oct 2021, 15:56 Fabian Cenedese, 
 wrote:

> At 14:21 21.10.2021, you wrote:
>
> >Can you please help me for this issue
> >
> >On Wed, 20 Oct 2021, 18:53 Adharsha sri, < adharsh...@gmail.com>adharsh...@gmail.com> wrote:
> >Hi Team,
> >

Re: Unable to Run jenkins job on zos slave

[Adharsha sri]

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, 
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,  wrote:
>>
>>> Can you please provide an example.
>>>
>>> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, 
>>> wrote:
>>>
 This is the output you see in the browser, isn't it? Did you try to
 download the "view as plain text" button output in a file and with an
 editor trying to find the correct encoding? the encoding you set in the
 Agent is only from Java process launched from the remoting thread, I mean
 is you launch a script in a job this script will use the encodings setting
 you have configured in the user you use to connect if in your .bashrc (or
 other shell configuration) you choose other encodings different than UTF-8
 you will have issues showing the build logs. In these cases I use to try to
 run a job that shows me the effective environment I am running the job by
 using the command `export`, `set`, or both, then I check the TERM, LC_* and
 LANG setting in that user.

 El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2,
 adharsh...@gmail.com escribió:

> Number of executors: 1
> Launch method: launch agents via SSH
> Host: host name
> Host key verification strategy: Non verifying verification strategy
>
> Port : 22
>
> Java path: /usr/lpp/java/J8.0/bin/Java
>
> JVM Options: -Dfile.encoding=ISO8859-1 -Djava.io.tmpdir=/usr/lpp/test
>
> Prefix start Agent command:
> export JAVA_HOME =/usr/lpp/java/J8.0/ && export
> IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&
>
> Suffix start Agent command:
>  -text
>
> Connection timeout  in seconds:210
>
>
> On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
> geoffroy...@gmail.com> wrote:
>
>> can you please show a screenshot of the zos agent configuration (all
>> fields)?
>>
>> On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com
>> wrote:
>>
>>> Yes , based on that page , we have configured the slave. But still
>>> facing the same issue.
>>>
>>> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
>>> geoffroy...@gmail.com> wrote:
>>>
 Hi
 have you checked this page (first results in google):
 https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
 Seems you might need to tune the JVM options, using
 -Dfile.encoding=ISO8859-1


 On Monday, 25 October 2021 at 13:49:52 UTC+2 adharsh...@gmail.com
 wrote:

> Can you please consider this as priority. Actually  it is critical
> issue for us.
> Whether z/ os platform is supported for jenkins or not . If it is
> supported, where we are missing and why we are not getting the output.
> Please help on this issue.
>
> On Mon, 25 Oct 2021, 17:12 Adharsha sri, 
> wrote:
>
>> We are running just date command or simple echo command  through
>> execute shell but not getting the actual output
>>
>> On Mon, 25 Oct 2021, 17:09 Adharsha sri, 
>> wrote:
>>
>>> +□?EA/¤
>>> Some thing like above
>>>
>>> On Mon, 25 Oct 2021, 15:56 Fabian Cenedese, 
>>> wrote:
>>>
 At 14:21 21.10.2021, you wrote:

 >Can you please help me for this issue
 >
 >On Wed, 20 Oct 2021, 18:53 Adharsha sri, <>>> adharsh...@gmail.com>adharsh...@gmail.com> wrote:
 >Hi Team,
 >
 >I am unable to run a jenkins job ( shell command : date) on
 zos slave . The slave is active and online but getting some 
 gibberish
 values in console output. Please help.

 Please post the "gibberish".

 

Re: Unable to Run jenkins job on zos slave

[Ivan Fernandez Calvo]

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,  wrote:
>
>> Can you please provide an example.
>>
>> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo,  
>> wrote:
>>
>>> This is the output you see in the browser, isn't it? Did you try to 
>>> download the "view as plain text" button output in a file and with an 
>>> editor trying to find the correct encoding? the encoding you set in the 
>>> Agent is only from Java process launched from the remoting thread, I mean 
>>> is you launch a script in a job this script will use the encodings setting 
>>> you have configured in the user you use to connect if in your .bashrc (or 
>>> other shell configuration) you choose other encodings different than UTF-8 
>>> you will have issues showing the build logs. In these cases I use to try to 
>>> run a job that shows me the effective environment I am running the job by 
>>> using the command `export`, `set`, or both, then I check the TERM, LC_* and 
>>> LANG setting in that user.
>>>
>>> El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2, 
>>> adharsh...@gmail.com escribió:
>>>
 Number of executors: 1
 Launch method: launch agents via SSH
 Host: host name
 Host key verification strategy: Non verifying verification strategy 

 Port : 22

 Java path: /usr/lpp/java/J8.0/bin/Java

 JVM Options: -Dfile.encoding=ISO8859-1 -Djava.io.tmpdir=/usr/lpp/test

 Prefix start Agent command:
 export JAVA_HOME =/usr/lpp/java/J8.0/ && export  
 IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&

 Suffix start Agent command:
  -text

 Connection timeout  in seconds:210


 On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
 geoffroy...@gmail.com> wrote:

> can you please show a screenshot of the zos agent configuration (all 
> fields)?
>
> On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com 
> wrote:
>
>> Yes , based on that page , we have configured the slave. But still 
>> facing the same issue.
>>
>> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
>> geoffroy...@gmail.com> wrote:
>>
>>> Hi
>>> have you checked this page (first results in google): 
>>> https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
>>> Seems you might need to tune the JVM options, using  
>>> -Dfile.encoding=ISO8859-1
>>>
>>>
>>> On Monday, 25 October 2021 at 13:49:52 UTC+2 adharsh...@gmail.com 
>>> wrote:
>>>
 Can you please consider this as priority. Actually  it is critical 
 issue for us.
 Whether z/ os platform is supported for jenkins or not . If it is 
 supported, where we are missing and why we are not getting the output. 
 Please help on this issue. 

 On Mon, 25 Oct 2021, 17:12 Adharsha sri,  
 wrote:

> We are running just date command or simple echo command  through 
> execute shell but not getting the actual output
>
> On Mon, 25 Oct 2021, 17:09 Adharsha sri,  
> wrote:
>
>> +□?EA/¤
>> Some thing like above 
>>
>> On Mon, 25 Oct 2021, 15:56 Fabian Cenedese,  
>> wrote:
>>
>>> At 14:21 21.10.2021, you wrote:
>>>
>>> >Can you please help me for this issue
>>> >
>>> >On Wed, 20 Oct 2021, 18:53 Adharsha sri, <>> adharsh...@gmail.com>adharsh...@gmail.com> wrote:
>>> >Hi Team,
>>> >
>>> >I am unable to run a jenkins job ( shell command : date) on zos 
>>> slave . The slave is active and online but getting some gibberish 
>>> values in 
>>> console output. Please help.
>>>
>>> Please post the "gibberish".
>>>
>>> bye  Fabi
>>>
>>> -- 
>>> 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 
>>> 

Re: Declarative Pipeline: Add trigger only on when condition

[Victor Martinez]

I'm not sure if I understood correctly what user branches of the CICD mean 
in this particular case, can you clarify it?
Some other questions:
- Are the master and CICD branches part of the same projectA? 
- If so, how do users interact with the project?

As far as I see the upstream trigger option allows to listen for changes in 
some other projects.

Will it work if you split two pipelines instead?

*Pipeline for the master branch *

or even a multibranch pipeline if needed, then you can exclude  the CICD 
branch to be built.

*Pipeline for the branch CICD*

or event a multibranch pipeline if needed, then you can exclude everything 
but the CICD branch.

triggers {
  upstream("projectA/master'")
}


Cheers

On Friday, 22 October 2021 at 11:17:46 UTC+1 sverr...@gmail.com wrote:

> We have a branch in projectA called CICD.
> This branch we want to be triggered automatically after the master branch 
> has built.
> However we do not want user branches of the CICD to be triggered 
> automatically.
>
> Is it possible to avoid configuring a trigger if the branch is not CICD?
>
> This is probably not possible, but would be very useful.
>
> triggers {
>   upstream 'projectA/master'
>   when {
> branch 'CICD'
>   }
> }
>

-- 
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/78393c2a-24ca-4780-b259-9f8e1a40b310n%40googlegroups.com.

Re: Unable to Run jenkins job on zos slave

[Adharsha sri]

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, 
wrote:

> Can you please provide an example.
>
> On Tue, 26 Oct 2021, 11:52 pm Ivan Fernandez Calvo, <
> kuisathave...@gmail.com> wrote:
>
>> This is the output you see in the browser, isn't it? Did you try to
>> download the "view as plain text" button output in a file and with an
>> editor trying to find the correct encoding? the encoding you set in the
>> Agent is only from Java process launched from the remoting thread, I mean
>> is you launch a script in a job this script will use the encodings setting
>> you have configured in the user you use to connect if in your .bashrc (or
>> other shell configuration) you choose other encodings different than UTF-8
>> you will have issues showing the build logs. In these cases I use to try to
>> run a job that shows me the effective environment I am running the job by
>> using the command `export`, `set`, or both, then I check the TERM, LC_* and
>> LANG setting in that user.
>>
>> El martes, 26 de octubre de 2021 a las 8:34:50 UTC+2,
>> adharsh...@gmail.com escribió:
>>
>>> Number of executors: 1
>>> Launch method: launch agents via SSH
>>> Host: host name
>>> Host key verification strategy: Non verifying verification strategy
>>>
>>> Port : 22
>>>
>>> Java path: /usr/lpp/java/J8.0/bin/Java
>>>
>>> JVM Options: -Dfile.encoding=ISO8859-1 -Djava.io.tmpdir=/usr/lpp/test
>>>
>>> Prefix start Agent command:
>>> export JAVA_HOME =/usr/lpp/java/J8.0/ && export
>>> IBM_JAVA_ENABLE_ASCII_FILETAG=ON && _BPXK_AUTOCVT=ON &&
>>>
>>> Suffix start Agent command:
>>>  -text
>>>
>>> Connection timeout  in seconds:210
>>>
>>>
>>> On Tue, 26 Oct 2021, 11:20 am geoffroy...@gmail.com, <
>>> geoffroy...@gmail.com> wrote:
>>>
 can you please show a screenshot of the zos agent configuration (all
 fields)?

 On Tuesday, 26 October 2021 at 04:27:21 UTC+2 adharsh...@gmail.com
 wrote:

> Yes , based on that page , we have configured the slave. But still
> facing the same issue.
>
> On Mon, 25 Oct 2021, 11:30 pm geoffroy...@gmail.com, <
> geoffroy...@gmail.com> wrote:
>
>> Hi
>> have you checked this page (first results in google):
>> https://gdams.medium.com/adding-zos-to-our-jenkins-build-farm-27ab5171fb35
>> Seems you might need to tune the JVM options, using
>> -Dfile.encoding=ISO8859-1
>>
>>
>> On Monday, 25 October 2021 at 13:49:52 UTC+2 adharsh...@gmail.com
>> wrote:
>>
>>> Can you please consider this as priority. Actually  it is critical
>>> issue for us.
>>> Whether z/ os platform is supported for jenkins or not . If it is
>>> supported, where we are missing and why we are not getting the output.
>>> Please help on this issue.
>>>
>>> On Mon, 25 Oct 2021, 17:12 Adharsha sri, 
>>> wrote:
>>>
 We are running just date command or simple echo command  through
 execute shell but not getting the actual output

 On Mon, 25 Oct 2021, 17:09 Adharsha sri, 
 wrote:

> +□?EA/¤
> Some thing like above
>
> On Mon, 25 Oct 2021, 15:56 Fabian Cenedese, 
> wrote:
>
>> At 14:21 21.10.2021, you wrote:
>>
>> >Can you please help me for this issue
>> >
>> >On Wed, 20 Oct 2021, 18:53 Adharsha sri, <> adharsh...@gmail.com>adharsh...@gmail.com> wrote:
>> >Hi Team,
>> >
>> >I am unable to run a jenkins job ( shell command : date) on zos
>> slave . The slave is active and online but getting some gibberish 
>> values in
>> console output. Please help.
>>
>> Please post the "gibberish".
>>
>> bye  Fabi
>>
>> --
>> 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/20211025102601.192AF48935CC%40macserver.private
>> .
>>
> --
>> 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/61ef6928-d20b-4e57-b30c-658c5e176474n%40googlegroups.com