Re: Jenkins configuration in JCAS

[Anu S]

Hi Liejun* Tao,*

let me check on this secret management system,
Any links to guide me on this?

thanks & Regards,
Anu

On Fri, Jun 18, 2021 at 12:26 AM Liejun Tao  wrote:

> I assume when you put full configurations into JCasc, you already have a
> way to inject secrets into the config.
> You may treat the (changeable) global variable as a secret which could be
> changed from outside (the secret management system).
>
>
> On Thu, Jun 17, 2021 at 2:51 AM Anu S  wrote:
>
>> Hi Everyone,
>>
>> i need one info to proceed with my work.
>>
>> currently the new jenkins which my team is having - entire configuration
>> is in JCAS(jenkins configuration as code) in a yaml stored in gitlab.
>>
>> now for our current scenario  - we need to define, 3 jenkins global
>> variable which will decide the job has to run or not.
>>
>> to define it as global variable - i can do in yaml. - the thing is - we
>> are going to change the values every now and then.
>>
>> 1. either change the value in yaml everytime - this might introduce any
>> config error. any way we can avoid doing the change in yaml by changing it
>> manually under manage jenkins - configure system. (the concern here is -
>> any update in yaml will reset the value back to default for the 3 variable
>> and the manual configuration will go off)
>>
>> so any other way we can change the jenkins global variable value
>> configured in JCAS? without any impact or change?
>>
>> Regards,
>> Anu
>>
>> --
>> 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/1915a5af-c73d-4882-b4a8-4c62fd514786n%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Thanks,
> Baibai
>
> --
> 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/CAMRm5jacm%2BcK2Vd_n1U0KSNKGc1Q9dTgS6FueKy9_1Gx%3DqvdiA%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/CAE4p%3DdPzQZrCuaFzd_2LWmFu%2BSAt2zGLAiWzRbw4JEbJTpunEg%40mail.gmail.com.

Databinding while baking the AMI

[Prem Kumar]

Hi All,

I am getting the below error message while baking the AMI.

*Error: Error from DataBinding 'hiera' while looking up 
'role::startup::orchestration::rpm_packages': (): mapping values 
are not allowed in this context at line 91 column 13 on node 
ip-.au..local*

*Script giving the error:*

sudo -i sh -c "cd /opt/puppet && puppet apply --test --ordering=manifest 
--hiera_config=hiera.yaml --modulepath=modules manifests/site.pp || true"

Any suggestion or help is highly appreciated.

Thank you
Prem

-- 
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/f4ab596c-bd4f-437f-9474-a1d87f68d1a8n%40googlegroups.com.

Re: AMI Build Failures - New packer version

[Prem Kumar]

Hi All,

This issue is resolved by adding "sh" command in front of the (*.sh) script.

Thank you

On Wednesday, 16 June 2021 at 3:31:44 pm UTC+10 dheinric wrote:

> Am Dienstag, den 15.06.2021, 18:33 -0700 schrieb Prem Kumar:
>
> The error is attached to this conversion.
>
>
> Nobody opens attachments from unknown senders. Please simply copy/paste it.
>
> Bye...
>
> Dirk
>
> -- 
>
> *Dirk Heinrichs*
> Senior Systems Engineer, Delivery Pipeline
> OpenText ™ Discovery | Recommind
> *Phone*: +49 2226 15966 18 <+49%202226%201596618>
> *Email*: dhei...@opentext.com
> *Website*: www.recommind.de
> Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
> Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
> Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
> This e-mail may contain confidential and/or privileged information. If you 
> are not the intended recipient (or have received this e-mail in error) 
> please notify the sender immediately and destroy this e-mail. Any 
> unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail 
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und 
> vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte 
> Weitergabe dieser Mail sind nicht gestattet.
>

-- 
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/74dc765e-e789-475d-a8e9-9922b325bcc9n%40googlegroups.com.

Re: Jenkins configuration in JCAS

[Liejun Tao]

I assume when you put full configurations into JCasc, you already have a
way to inject secrets into the config.
You may treat the (changeable) global variable as a secret which could be
changed from outside (the secret management system).


On Thu, Jun 17, 2021 at 2:51 AM Anu S  wrote:

> Hi Everyone,
>
> i need one info to proceed with my work.
>
> currently the new jenkins which my team is having - entire configuration
> is in JCAS(jenkins configuration as code) in a yaml stored in gitlab.
>
> now for our current scenario  - we need to define, 3 jenkins global
> variable which will decide the job has to run or not.
>
> to define it as global variable - i can do in yaml. - the thing is - we
> are going to change the values every now and then.
>
> 1. either change the value in yaml everytime - this might introduce any
> config error. any way we can avoid doing the change in yaml by changing it
> manually under manage jenkins - configure system. (the concern here is -
> any update in yaml will reset the value back to default for the 3 variable
> and the manual configuration will go off)
>
> so any other way we can change the jenkins global variable value
> configured in JCAS? without any impact or change?
>
> Regards,
> Anu
>
> --
> 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/1915a5af-c73d-4882-b4a8-4c62fd514786n%40googlegroups.com
> 
> .
>


-- 
Thanks,
Baibai

-- 
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/CAMRm5jacm%2BcK2Vd_n1U0KSNKGc1Q9dTgS6FueKy9_1Gx%3DqvdiA%40mail.gmail.com.

Views on Folders

[Anderson Cruz]

Hello,

I have a Jenkins running properly with security roles for Teams in Folders.
Teams are able to control everything inside their own folder and works fine.

My problem starts with View plugin because it generates a View on Root of
Jenkins and permissions could not be applied to it. breaking my Team model
permissions.

Is there a way to create Views inside folders only? use another plugin that
allows me to do it or show jobs in a good way for wall display ?

Thanks
Anderson Cruz

-- 
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/CAAJ3s8uoqJB-1tTack9AQVrcGRvPOLq4Yhyu2eLNv%3DTZAZqV7Q%40mail.gmail.com.

Re: Permission denied returned from a container due to uid used = 1000

[Anderson Cruz]

Hello,

I had the same issue. Tried to force dockerfile and unix files fo force
Umask but always some files belongs to user and group different from
Jenkins Agent connected.
Looks like a cascade shell inside Container invokes and overwrite 055 umask
and ignore my directives ( or it's not propaged ).

My solution was all my nodes outside NIS system and using default jenkins
user 1000 to connect.

Anderson Cruz


On Thu, Jun 17, 2021 at 6:43 AM Charles Moulliard 
wrote:

> No as the container is not launched using docker but using jenkins
> kubernetes plugin as a pod where the UID needed is 1000:
> https://github.com/jenkinsci/kubernetes-plugin#pipeline-sh-step-hangs-when-multiple-containers-are-used
>
>
>
> On Wednesday, June 16, 2021 at 10:14:44 PM UTC+2 uday1...@gmail.com wrote:
>
>> Have you tried -u root while running the container?
>>
>> On Thu, 17 Jun, 2021, 1:35 am Charles Moulliard, 
>> wrote:
>>
>>> Hi
>>>
>>> One of our container is reporting a permission denied as git cannot
>>> write a file on the filesystem mounted. As the uid used during the pod
>>> creation to allow the jenkins jnlp client to work correctly is 1000, what
>>> should we do to design correctly the image of that container to be able to
>>> give write permission even when the pod created will use as uid 1000 ?
>>>
>>> Cheers
>>>
>>> Charles
>>>
>>> --
>>> 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/b973f0bc-210e-4a49-aaca-3936ada9b57cn%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/77786b52-017b-45c0-bcd7-2684dc8d3820n%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/CAAJ3s8uDq%2BUxExz79LbTeuY---WWMWcGQs-mokgT0diS9JYf-g%40mail.gmail.com.

Strange GitSCM behaviour

[the.n...@gmail.com]

I have a pipeline to build the git product, which uses the 'master' and 
'maint' branches. 'master' is used for new releases, like 2.32.0, while 
'maint' is used for 2.32.1. My pipeline refers to both branches for 
polling. The problem is that the job keeps rerunning with the change log 
showing nothing. The starting snippet is:

pipeline {
agent any
options {
buildDiscarder(logRotator(numToKeepStr: '5'))
}
triggers {
pollSCM('H H H * *')
}
stages {
stage('checkout') {
steps {
checkout([$class: 'GitSCM',
changelog: true,
poll: true,
branches: [[name: 'maint'],[name: 'master']],
extensions: [
[$class: 'CleanBeforeCheckout'],
[$class: 'SubmoduleOption', disableSubmodules: 
false, parentCredentials: true,
recursiveSubmodules: true, reference: '', 
trackingSubmodules: false]],
doGenerateSubmoduleConfigurations: false, extensions: [
[$class: 'CleanCheckout'],
[$class: 'CloneOption', timeout: 120, shallow: true],
[$class: 'CheckoutOption', timeout: 120],
],
userRemoteConfigs: [[url: 'https://github.com/git/git']]])
}
}


Once the builds start, multiple queue up until I kill them. After 
everything is in a quiet state with no jobs queued, the system goes back to 
an idle state, but if I leave it alone, I could get 10-20 jobs queued. What 
I have suspected is that the git build/test takes about 3 days - it's a 
very busy and not so fast system, so it seems like the poll interval is not 
taking into account that there is already a job being built for the 
triggering commit. This also happens on other long-running jobs.

I'm perplexed as to why the rerun is happening without new commits being 
pushed to those branches. Currently on Jenkins 2.281, with GitSCM at 4.6.0 
and Git Client at 3.6.0. We are using git 2.32.0 on the NonStop server. 
This is a standalone configuration. No agents.

Any wisdom on what to look for as a potential cause would be appreciated.

Thanks,
Randall

-- 
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/8d42584b-cd44-4766-81bd-42fd36804f56n%40googlegroups.com.

Re: jenkins status page checkmark instrad of green balls

[Ullrich Hafner]

> Am 17.06.2021 um 15:13 schrieb Fabian Cenedese :
> 
> At 14:41 17.06.2021, you wrote:
>> a) Downgrade your Jenkins version (not recommended). 
>> b) Write a Jenkins theme that uses the old and ugly ball images 
>> 
>>> Am 15.06.2021 um 08:36 schrieb sabsac123 
>>> <sab...@gmail.com>:
>>> 
>>> My jenkins project status page is showing a green checkmark for successful 
>>> buld instead of green balls. how to bring back the balls icon to the staus 
>>> page? 
> 
> Just to add to the original poster's comment. We too were surprised to
> see the new icons. The problem is not whether the new or the old ones
> were ugly or not. It's a simple case of clarity. The old icons (ugly or not)
> were a lot clearer to grasp.

You are talking about the weather icons? This is a different point, please add 
your comments in https://issues.jenkins.io/browse/JENKINS-65124 


> The new weather icons are all the same color.
> It's harder to see at one glance what the state of the dozens of jobs is.
> Obviously we eventually will get used to the new theme. But I still don't
> understand why all people think that flat and abstract is more modern.
> Modern is not necessarily also practical.
> Just my 1 cent.
> 
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/20210617131335.AB085467EA38%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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1BC191A9-75A4-4599-AC1D-8F8A16D2F947%40gmail.com.

Re: jenkins status page checkmark instrad of green balls

[Fabian Cenedese]

At 14:41 17.06.2021, you wrote:
>a) Downgrade your Jenkins version (not recommended). 
>b) Write a Jenkins theme that uses the old and ugly ball images 
>
>>Am 15.06.2021 um 08:36 schrieb sabsac123 
>><sab...@gmail.com>:
>>
>>My jenkins project status page is showing a green checkmark for successful 
>>buld instead of green balls. how to bring back the balls icon to the staus 
>>page? 

Just to add to the original poster's comment. We too were surprised to
see the new icons. The problem is not whether the new or the old ones
were ugly or not. It's a simple case of clarity. The old icons (ugly or not)
were a lot clearer to grasp. The new weather icons are all the same color.
It's harder to see at one glance what the state of the dozens of jobs is.
Obviously we eventually will get used to the new theme. But I still don't
understand why all people think that flat and abstract is more modern.
Modern is not necessarily also practical.
Just my 1 cent.

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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/20210617131335.AB085467EA38%40macserver.private.

Re: jenkins status page checkmark instrad of green balls

['Dirk Heinrichs' via Jenkins Users]

Am Donnerstag, den 17.06.2021, 14:41 +0200 schrieb Ullrich Hafner:

> b) Write a Jenkins theme that uses the old and ugly ball images

Uglyness always lies in the eye of the beholder, doesn't it? Some
people might find the new ones ugly...

Bye...

Dirk
-- 
Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

-- 
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/3297d29e5f5db7805f899f5aa6473ab952885fcb.camel%40opentext.com.


signature.asc
Description: This is a digitally signed message part

Re: jenkins status page checkmark instrad of green balls

[Ullrich Hafner]

a) Downgrade your Jenkins version (not recommended). 
b) Write a Jenkins theme that uses the old and ugly ball images 

> Am 15.06.2021 um 08:36 schrieb sabsac123 :
> 
> My jenkins project status page is showing a green checkmark for successful 
> buld instead of green balls. how to bring back the balls icon to the staus 
> page?
> 
> -- 
> 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/2b4c4cb4-e459-4a8e-8b86-670620e69295n%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/D6035D8B-5ED6-452D-9695-E61C95EEF843%40gmail.com.

Jenkins configuration in JCAS

[Anu S]

Hi Everyone, 

i need one info to proceed with my work.

currently the new jenkins which my team is having - entire configuration is 
in JCAS(jenkins configuration as code) in a yaml stored in gitlab.

now for our current scenario  - we need to define, 3 jenkins global 
variable which will decide the job has to run or not.

to define it as global variable - i can do in yaml. - the thing is - we are 
going to change the values every now and then.

1. either change the value in yaml everytime - this might introduce any 
config error. any way we can avoid doing the change in yaml by changing it 
manually under manage jenkins - configure system. (the concern here is - 
any update in yaml will reset the value back to default for the 3 variable 
and the manual configuration will go off)

so any other way we can change the jenkins global variable value configured 
in JCAS? without any impact or change?

Regards,
Anu

-- 
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/1915a5af-c73d-4882-b4a8-4c62fd514786n%40googlegroups.com.