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.
Chris > On 29 Feb 2020, at 14:30, Sladyn Nunes <[email protected]> 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.yml > plugins: > - 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 [email protected]. > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/FCDDFA92-2EDF-4ED8-A6D7-B9BAB2C84EE1%40chriskilding.com.
