Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 10:49
    casz commented #1218
  • 10:49
    casz commented #1218
  • 10:47
    casz commented #1218
  • 10:40
    casz edited #1027
  • 09:54
    LinuxSuRen synchronize #1218
  • 09:47
    timja synchronize #1027
  • 09:46
    timja labeled #1027
  • 09:44
    timja commented #1027
  • 09:44
    timja review_requested #1027
  • 09:43
    timja synchronize #1027
  • 09:42
    oleg-nenashev commented #917
  • 09:41
    oleg-nenashev commented #917
  • 09:41
    timja closed #917
  • 09:41
    timja commented #917
  • 09:41
    oleg-nenashev edited #1215
  • 09:40
    oleg-nenashev commented #1215
  • 09:40
    LinuxSuRen commented #1218
  • 09:26
    oleg-nenashev commented #1215
  • 09:18
    timja synchronize #1027
  • 09:16
    timja synchronize #1027
ricardompcarvalho
@ricardompcarvalho
because i cant configure it
ricardompcarvalho
@ricardompcarvalho
I configure this way but give me error
nodeProperties:
                    - toolLocation:
                        locations:
                          - home: (Git) Default
                            key: "C:\Program Files (x86)\Git\bin\git.exe"
ricardompcarvalho
@ricardompcarvalho
I already discover it, thanks anyway @sladyn98
Torsten Walter
@torstenwalter

The stable/jenkins helm chart. Already has support for the configuration as code plugin. It's possible to enable by setting master.JCasC.enabled to true. It also has support for automatically reloading any configuration change without restarting Jenkins. This is done via a sidecar container which watches for config map changes which contain the configuration (master.sidecars.configAutoReload.enabled). You can also supply your JCasC configuration files via master.JCasC.configScripts.

That's all good to have, but I think the JCasC support could be improved even more. I just created an issue with a proposal in that regards: helm/charts#16931. I would love to here your feedback. If you want you can also support it by creating PRs which add better JCasC support.

Sladyn
@sladyn98

I already discover it, thanks anyway @sladyn98

Your Welcome :smile:

Joseph Petersen
@casz
@ricardompcarvalho you could configured it in UI and use export. If it does not appear in the export it is most likely broken
Tim Jacomb
@timja
Just merged all the dependabot PRs (closed the ones that need to come from the bom in jenkins core)
Joseph Petersen
@casz
@timja @oleg-nenashev let it :ship:? :laughing:
suryatej yaramada
@yrsurya
A quick question who are using JCAC plugin to build their Jenkins , how youguys are deploying jenkins initially ? I had a helm chart for Jenkins and want to deploy on EKS clusters. for application helm charts using jenkins we are going to deploy but for deploying jenkins helm chart how I can achieve this any thoughts ?
Tim Jacomb
@timja
do you mean the initial jenkins deployment?
we use fluxcd
@yrsurya
suryatej yaramada
@yrsurya
yeah initial deployment for Jenkins, right now I deployed dev env of Jenkins from my local but like to have a gitops jenkins , I think spinnaker which we can achieve this , will go through fluxcd docs. Thanks @timja
Joseph Petersen
@casz
:sob: @oleg-nenashev making it more difficult to automate Jenkins. With the changes to the CrumbIssuer we can no longer generate a API token on the fly when we spin up our test setup :sob:
Time to explore other options for generating an API token for a user.
Tim Jacomb
@timja
what do you need the api token for?
which changes?
Joseph Petersen
@casz
Figured out we needed some changes to our code. It needs to retrieve the session id due to: https://jenkins.io/doc/upgrade-guide/2.176/#SECURITY-626
Oleg Nenashev
@oleg-nenashev
CC @Wadeck for the crumb token
do we have a meeting today? If so, I will prepare Zoom
Jon Brohauge
@jonbrohauge
was just going to ask...
Tim Jacomb
@timja
Yes
Joseph Petersen
@casz
It would be nice to generate a API token from JCasC in some way either for internal local user or any user :)
Tim Jacomb
@timja
some sort of local system account when you're logged in via ldap / saml etc would be nice :D
make automating a lot easier
Joseph Petersen
@casz
exactly my point :)
Tim Jacomb
@timja
what're you using the API for?
Jon Brohauge
@jonbrohauge
meeting link?
Oleg Nenashev
@oleg-nenashev
I am wrapping up the current meeting, need few mins
Jon Brohauge
@jonbrohauge
:thumbsup:
Tim Jacomb
@timja
it's here: https://zoom.us/j/286266977
needs starting from Oleg though
Jon Brohauge
@jonbrohauge
Same link every time? Maybe it should be put in an obvious spot in the docs... Or maybe I just couldn't find it :wink:
Tim Jacomb
@timja
Yeah, it's a recurring invite, it's on the meeting invitation
added
Jon Brohauge
@jonbrohauge
gotcha... thx
Oleg Nenashev
@oleg-nenashev
oops
Tim Jacomb
@timja
or not :p
that's a different one to the invite
which one @oleg-nenashev
Oleg Nenashev
@oleg-nenashev
sorry for confusion
Tim Jacomb
@timja
image.png
@jonbrohauge joining?
ah there you are :)
Jon Brohauge
@jonbrohauge
sry had to run for a charger... 1% power isn't much for a video conference
Wadeck Follonier
@Wadeck
Hey there, perhaps you could be interested in the Jenkins PR about API Token: jenkinsci/jenkins#4027
that could potentially help you with the crumbIssuer problem
Joseph Petersen
@casz
@Wadeck perhaps a downstream test in JCasC would be nice :)
KreativeKrise
@KreativeKrise

Hi there :) I need some help with the file credentials. My configuration looks like this:

credentials:
  system:
    domainCredentials:
      - credentials:
          - file:
                  description: "google-service-account"
                  fileName: "jenkins_google-service-account.json"
                  id: "google-service-account"
                  secretBytes: ${GOOGLE-SERVICE-ACCOUNT_JSON}
                  scope: GLOBAL

After I startet Jenkins, the credential was created successfully. But it seems, that the value of the secret isn't correct, because my build fails. If I upload the json file through the web interface of Jenkins, the build works. ${GOOGLE-SERVICE-ACCOUNT_JSON} is a base64 encoded json file. Anyone has an idea how I can fix it?