--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFs-%3DeBOnFeTthXmViVzeBdbPCkNP%3DXn3Mq2-97zoFvQQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4oyntgMxch8Pm_QhHFMpB34PUrG756iHG5kFb95WWokJEA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAC-LeqsHQL71HCuefGVNqAVYQ--xvzfVFeZs8D2jX%3DfY6RpprQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTEaQPd1WXLG0SDohM-Lg7BHycxyB_yN_BSzGUh0BxuX4A%40mail.gmail.com.
For many users, they download Jenkins first, then select some plugins and config them. It might take a lot of time, like hours. But if we can get a perfect Jenkins distribution which contains all we need, it can save that time for us. Yes, I propose an out of the box solution.
--You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtK6EzOF8ghN1tyE_bKp5A-X5xe%2Bjgmd-oKO7nfpg2GMdA%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/903a4f91-d290-4d66-b22c-13ac031597b8%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/91a4c831-c6c8-42fc-9ea6-d7d4d5c9ed14%40www.fastmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CADVhPTrJQdynocY-S-LVxZzxovK151t%2BCG2Dm614m6EH_KfEBg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTHB3Gt_tNf3UhzszTGrPzBMuUGPkNe8WVbkCN%3DsnG57_w%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/0371C77F-E9D3-48B1-BD77-D5B0C1173F90%40chriskilding.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3YQsE50L%2BqTnKqYFMyDrDSYbRNr_FWjFEsKZ6mK1C6Uw%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/623C5041-5D06-47C9-BD2F-CA7336B7BC53%40chriskilding.com.
Hi.I've been working on some ideas pretty similar to all you are suggesting here. The ultimate goal is, sort of:* Allow to have a Jenkins ready with all stuff in a single click or command. Or compared to IKEA: avoid having to mount the IKEA furniture manually because unlike IKEA, we have dozens of Shrönghon screw (aka plugins) and people usually don't know what to use to get their furniture mounted :-)* Allow people to share "their Jenkins", meaning Jenkins version + plugins + sample-running jobs + configurations (but credentials) to allow community to reuse them. Some projects have contributed to allow that without too much effort, like JCasC, custom-war-packager, ...* Allow people to kind of vote for packages to be able to find out the most mature or relevant among all existing.* Have a centralized and easy to maintain repository of such "Jenkins configurations". It could be as easy as a GH repo with a certain template (readme + configuration file + assets), although some features like voting may be missed.Beyond the specific proposal I made I find there are a lot of people thinking on the same problem and slightly different solutions. So it would be great to align efforts on the same direction to extract the most from us to achieve something deliverable in a short time.Not sure under what umbrella we could do that, GSoC, JEP, ... though.Best regards.
On Mon, Feb 24, 2020 at 11:55 PM Chris Kilding <ch...@chriskilding.com> wrote:
Jesse - cheers for pointing out the previous AWS packaging attempt, I will take a look.
Re version pinning, if this can’t be done in the POM, are there any Jenkins tools which can do this, apart from the cloudbees assured update feed? (I’m thinking of how we could support users on Jenkins community edition.)
Re what gets included - we could insist that any plugins included in a cloud vendor metapackage meet certain criteria, so that they can play together better:
- They must be able to no-op if the user doesn’t need them (ie their default is to quietly sit on the Jenkins server and not do anything, until the user configures them).
- They must all use the same cloud provider SDK artifact (probably the Jenkins re-packaged HPI version of the SDK).
- If appropriate, they must all take their baseline configuration from the same cloud provider ‘global config’ plugin.
Re pre-defined packages - I would certainly like to see the cloud vendors get more involved with supporting their respective Jenkins plugins.
Chris
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/3b8b4036-9774-40eb-ac99-42ce54a2b6a0%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/TzZ5mVqinuU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1281a09.2371.1707bc6d370.Coremail.zxjlwt%40126.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAd_s4s3BkAj%2B9VRY2cgpf8m2mVb3wO9x0MM%3DSumUoLwQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4d7d090e.2459.1707be01a4c.Coremail.zxjlwt%40126.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCUUJ13dZ%3DNpGJZDY56DqbEAY1TgWXYegKM1q%3DwNpehwA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/19fdd0b1.2579.1707c017b99.Coremail.zxjlwt%40126.com.
On 29 Feb 2020, at 14:30, Sladyn Nunes <sladyn...@gmail.com> wrote:
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9091fc97-dfaa-4a4d-9ea4-6534d2428fc3%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FCDDFA92-2EDF-4ED8-A6D7-B9BAB2C84EE1%40chriskilding.com.
Hi Chris,Thanks for the share.Rick
On 02/29/2020 23:06,Chris Kil...@chriskilding.com> wrote:
Another action point from the call yesterday...Regarding the “share your Jenkins configuration” feature, I am talking to our core engineering team at work to see if we can publish at least a snapshot of our shared Jenkins template repo (this is the template that our product development teams clone and then adapt for their purposes). This is to provide a starting point for the discussion of what the feature should look like.ChrisOn 29 Feb 2020, at 14:30, Sladyn Nunes <sladyn...@gmail.com> wrote:
--
As discussed in the meeting yesterday the initial phase for the project would involve building a yaml generator which would generate a YAML file based on the inputs taken from the user. However my question is that while the packager-config.yml involves only
the groupID and artifacID, and version for the plugins. Would that be enough while generating the configuration file, because as Chris mentioned a more robust configuration file would be necessary to build a AWS distro for instance. If yes is there currently any method to pull in all of the necessary configurations for a plugin which could assist in listing out the fields.Example of a packager-config.ymlplugins:- groupId: "org.jenkins-ci.plugins"artifactId: "matrix-project"source:version: 1.9
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9091fc97-dfaa-4a4d-9ea4-6534d2428fc3%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkin...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6c6bbdda-9143-4906-91b3-079839ae7e4f%40googlegroups.com.
Hi team,
For many users, they download Jenkins first, then select some plugins and config them. It might take a lot of time, like hours. But if we can get a perfect Jenkins distribution which contains all we need, it can save that time for us. Yes, I propose an out of the box solution.
The service could be like this, a website offered as https://customize.jenkins.io. Plus, it should be self-host. People can select the following configurations:
- Jenkins core version
- plugins
- common configuration, user/password, update-center site e.g.
- plugin based configuration, Kubernetes, Sonarqube plugin config e.g.
- multi-form package, jenkins.war or docker image
- other things
Two projects are expected backend and frontend. I think https://github.com/jenkinsci/custom-war-packager already did a lot of works. We can reuse it in this project. The backend should provide the modern Restful API. We can start the backend project with SpringBoot, it can save a lot of time.About the frontend project, I don't have too many experiences on it. For example, we can start it by React framework. If you're instrested in it, please help to add more ideas on it.Any feedbacks are very appreciated.Best regards,Rick
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/00a824b5-9dbf-4ae6-8b7d-0307cac3dd17%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/34c9dbcc-086d-45f5-b372-89367114ce6c%40googlegroups.com.
Hello everyone,
Hi everyone,
Hello everyone