Hi Nathan, I think that your plugins are really interesting and may be valued by many here. People here are probably in the launching phase before the Jenkins user conference (23rd). It will be easier after that.
If you start by pushing the plugins to https://github.com/grunzwei, then send an email with the list of plugins, they can be forked into jenkinsci. Thanks, Emeric Le jeudi 3 octobre 2013 22:47:45 UTC+2, nathang a écrit : > > Hi, > > at the company where i work we've created a bunch of jenkins plugins over > the last 2 years. finally, after a long time, i'm starting a process for > contributing to open source (this is not trivial in enterprise companies). > in order to get the managers to push this through quickly, i need to show > them that it's easy to contribute, that a lot of other people contribute > and where exactly the code is hosted and who has access. > > i need to be able to create plugin repositories on jenkinsci account, or > at least to be able to create plugin repositories and submit push/pull > requests easily. > my github username is grunzwei. > > some plugins we have that might be of interest once we "productize" them > and publish: > > * build-stream-tree, shows the flow of job executions. yes i know that > there are similar plugins to this, but frankly, they're not what they're > cracked up to be. the difference is that this one works really really well. > tons of features, including embedding in email, customized columns, > asynchronous downstream jobs - etc... you'll see, i hope. it's the only > reasonable way to navigate in jenkins. > > * recursive-cancel-build, cancels all the jobs in a flow. it finds all the > jobs, and not just some, because the downstream logic is based on > build-stream-tree, so it really stops everything, including asynchronous > jobs etc. > > * views-manager, a javascript tree that allows you to dragndrop views. > ever tried moving a view from one nested view to another? good luck. > supports copy, rename, move, delete. > > * clone-jobs - copies a set of jobs (not just one job) and keeps the links > between them. saves days when you need to clone your pipeline. > > * batch-or-shell - allows you to put in a script per OS, and the correct > script is executed depending on the node where the job is running. > > * builds-filter - allows you to filter the builds list according to the > branch (so if you have a job that executes different branches, you can > choose to see builds for a specific branch) > > these plugins are highly valued here, and i'd love to be able to publish > them. > > in the past we've also patched busted plugins (BlameSubversion, promoted > builds, some email sending logic for useremailresolver extensions) so that > we could use them, but weren't really able to push our bug-fixes back. now > we're trying to contribute our bug-fixes back, as can be seen by the pull > request we opened on dynamic-axis-plugin. > > thanks, > Nathan. > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
