Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Jesse Glick
    @jglick
    @oleg-nenashev had prototyped some work for JEP-212 on https://github.com/oleg-nenashev/external-logging-logstash-plugin but I am not sure of the status. It is not, as written, compatible with JEP-210.
    mathieucoavoux
    @mathieucoavoux
    Ok, yes I remember this from @oleg-nenashev but for my understanding at that time the purpose of this plugin was to send logs to ES but didn't cover the JEP-210 aspect. I understand, for the sake of clarify that it's better to dissociate this logging plugin with another build-storage plugin. Aside from this I think that at the time @oleg-nenashev wrote the plugin the LogFactory wasn't yet implemented and he prefered to use the extlogging plugin but I may be wrong.
    Jesse Glick
    @jglick
    Well, it is complicated. We were working on the same overall design, but from different physical APIs. JEP-210, purely implemented in Pipeline, shipped; 207/212, with hooks in core to also support freestyle projects etc., did not. And then all work on this area was suspended indefinitely. Can I ask again what your goals are here? You said something about “serializing builds in JSON” but I have no idea what that is about.
    mathieucoavoux
    @mathieucoavoux
    Yes, so what I wanted initially was to store all builds + logs in an central storage to be able to put multiple Jenkins masters behind a proxy to have a HA platform. I made a video available here just to see the context. Sorry it's a bit long+ a robot voice for comments. So I understand that efforts made for the logging are also usable in the Jenkins X context and that's very great. But I was trying to see how I can have a custom plugin for a while which is not that good compare to what you have developped but at least align with what has been adopted along the way and when JEP-210 is implemented give up this plugin. Of course if I can help somehow I will.
    Jesse Glick
    @jglick
    JEP-210 and related efforts are not used in Jenkins X.
    Or at least, not in the recommended serverless mode (i.e., --prow). Containers using jenkinsfile-runner or Tekton are run and pod logs are optionally copied to permanent storage (as per jx get storage) when the build completes. Very different from JEP-207/210/212, which deals with regular Jenkins servers that should upload logs of potentially in-progress builds from agents to external storage and (as needed) retrieve from storage to the master.
    Jesse Glick
    @jglick
    Anyway, 210 is usable today (so long as you care only about Pipeline projects), though master-based log display has some structural inefficiencies since the browsing API in Jenkins core (used by both the traditional console and Blue Ocean) is oriented towards byte offsets rather than the opaque cursors you would use in a typical cloud system.
    mathieucoavoux
    @mathieucoavoux
    Sorry I again confused. What I have put in my plugin was the Runs (https://jenkins.io/sigs/cloud-native/pluggable-storage/ ) in addition to external logging. And that the one I had issue with the serialization
    mathieucoavoux
    @mathieucoavoux
    Do you think that the configuration storage and run storage shall/must be different than the logs storage in the future ? For example logs are sent to cloudwatch but runs status are kept in an SQL database?
    Jesse Glick
    @jglick
    @mathieucoavoux yes that would be my expectation. Build metadata is structured and Jenkins needs it in indexed form sometimes; whereas logs are textual, streamed, full-text-searchable, etc.
    mathieucoavoux
    @mathieucoavoux
    Ok thanks :) @jglick
    Oleg Nenashev
    @oleg-nenashev
    @mathieucoavoux @jglick Yes, separate storages would be my expectation as well. or configurations and runs there is JEP-213 (https://github.com/jenkinsci/jep/tree/master/jep/213) which could do the job. But it is stalled as well
    mathieucoavoux
    @mathieucoavoux
    Thank you @oleg-nenashev I've just been through the JEP-213 and JENKINS-41196, I will take sometimes to see what this custom-war-packager is. I will read comments in the jenkinsci/jenkins#2754 accordingly. Thanks
    Oleg Nenashev
    @oleg-nenashev
    @mathieucoavoux yw. Enjoy the exploration
    370672701
    @370672701
    Hello, I'm new to Jenkins,
    Is any way can configure active-standby servers for jenkins, to keep it HA
    thanks advance
    Oleg Nenashev
    @oleg-nenashev
    @370672701 short answer is "no". I have done and presented a lame PoC at some point, but it has never been productized
    If you want scalability && your projects follow GitOps && can be run in Kubernetes, then it makes sense to consider Jenkins X Serverless mode
    Oleg Nenashev
    @oleg-nenashev
    @370672701 you may be also interested in https://go.cloudbees.com/docs/cloudbees-documentation/cje-install-guide/#high-availability . It somewhat implements active-standby
    370672701
    @370672701
    got it, thanks a lot @oleg-nenashev
    Philipp Garbe
    @pgarbe
    Anyone interested in taking over the maintainer for the ecs plugin from me?
    Martin d'Anjou
    @martinda
    @pgarbe are you talking about https://github.com/jenkinsci/amazon-ecs-plugin ?
    We have a GSoC project on this topic. It was meant to add ECS to https://github.com/jenkinsci/external-workspace-manager-plugin but we are coming to the realization that ECS should be its own thing.
    If you have any ideas with regards to the direction ECS should take, please share it with us.
    Here is what the student recently wrote about it: https://groups.google.com/forum/#!topic/jenkinsci-gsoc-all-public/oRHraEPb_cA
    @/all We have a GSoC project on ECS. What are your thoughts on ECS in Jenkins? See this post from the student.
    Andreas Sieferlinger
    @webratz
    The post talks about EFS? Which is unrelated. So whats the goal ECS or EFS?
    But i agree that EFS / shared workspaces could be a interesting topic to be used together with the ECS plugin, especially if you are using multiple containers in a pipeline which each usually start off with a completely fresh filesystem
    Nguyen Le Vu Long
    @longngn
    Hi everyone, nice to meet you. Currently I'm implementing Jenkins Cloud. How can I add a textbox field value to Jenkins' Labels (so that new job could use that label to run on Cloud) ?
    Oleg Nenashev
    @oleg-nenashev
    jenkins-infra/jenkins.io#2387 - blog post for Azure artifact manager
    tahaa karim
    @tahaalibra
    Hi, I am using docker plugin and have a few docker cloud agents, what I want to do now is to be able to choose a label eg. node 'my-label', and also specify slave image to be used. is there any way to achieve this?
    Jesse Glick
    @jglick
    @tahaalibra probably more appropriate for a general channel like #jenkins
    Daniel Belenky
    @danielBelenky

    Hey, I'm looking to add support for kubevirt (https://github.com/kubevirt/kubevirt) VMs as dynamic Jenkins agents on K8s (similar to the existing kubernetes-plugin). I wonder if there is a place to extend the current plugin and maybe add another provider along with the existing pod... since all the infra code will be the same and the difference is only in the kind of the object we request from K8s and the arguments it accepts...

    I understand that it will require some refactoring to let users choose the kind of the object he wants to provision, and the alternative is to maintain a plugin which is 90% the same as the existing one

    Carlos Sanchez
    @csanchez_twitter
    @danielBelenky you would need to change the pod creation in https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesLauncher.java#L124
    pod is used all over but maybe you can refactor it a bit
    Daniel Belenky
    @danielBelenky
    @csanchez_twitter yes I assumed it will cost me some refactoring time, but wanted to ensure that something like this is ok by the plugin's community and maintainers before I start the work
    Carlos Sanchez
    @csanchez_twitter
    @danielBelenky it would be better if you prepare a proposal on what would change and how and run it by Vincent Latombe and me to see how would affect the plugin
    Daniel Belenky
    @danielBelenky
    @csanchez_twitter :+1: no problem
    Rainer Frey
    @rainerfrey
    Hi! Before I go into any details: is this room appropriate to ask questions about using the kubernetes-plugin?
    Nguyen Le Vu Long
    @longngn
    @rainerfrey I think it is, there're people asking about the plugin before
    Rainer Frey
    @rainerfrey
    Ok, I'm looking into template inheritance in declarative pipelines. While the documentation states that there is no default inheritance between the pipeline's agent pod template and a stage's agent pod template (as there would be in a scripted pipeline), it also states that it is possible to define inheritance explicitly. How / by what name do I reference the pipeline pod template in a inheritFrom statement in the stage's agent configuration? I tried to use the label, but then the inheritance seems to be ignored, and the stage pod only contains the containers from its own template. I have more details and an example in this stack overflow question: https://stackoverflow.com/questions/58709163/jenkins-kubernetes-plugin-declarative-pipeline-and-pod-template-inheritance
    Oleg Nenashev
    @oleg-nenashev
    @csanchez_twitter ^
    Oleg Nenashev
    @oleg-nenashev
    Threads have been enabled in this room
    Sladyn
    @sladyn98
    Do we have a Jenkins-X office hours?
    Oleg Nenashev
    @oleg-nenashev
    @sladyn98 yes, but Jenkins X is not a part of this SIG. Seen https://jenkins-x.io/community/events/#office-hours
    Sladyn
    @sladyn98
    Oh missed the meeting :(
    Does this come under the Jenkins-x domain or just a general cloud-native Jenkins project
    Oleg Nenashev
    @oleg-nenashev
    @sladyn98 Cloud Native Jenkins
    Sladyn
    @sladyn98
    Yeah thnx I'll try and get involved with it
    Oleg Nenashev
    @oleg-nenashev
    :+1:
    Lavanya
    @lavanyaanbuatgmaildotcom

    Hi All, I am new to jenkins and using enkins ver. 2.190.2 which is installed in Azure Kubernetes version 1.14.6 . I am trying to export the jenkins jobs using the command line using a simple script by passing the job name. Export_jobs()
    {
    mkdir JOB
    while read -r i
    do
    java -jar jenkins-cli.jar -s $URL -auth $username:$password get-job "$i" </dev/null > JOB/$i.xml
    done < list_jobs.txt

    }

    Jenkins has a folder within that there are multiple jobs, the above export command only exports the folder but not the jobs. Is there any other command i should use?