Hey Jae, I don’t know why my last email did not reach you, but I did answer you a few days ago… Here is a copy:
Hi Jae, There is no need to enable travis, as every Jenkins Plugin hosted in the Jenkins GH Org, we can make use of the Jenkins Project Infrastructure - also it would be very strange to have a Jenkins project to need Travis to build there PRs… The Repository Connector seem not yet integrated into this env, but I think we should aim for this solution. Most probably the only thing missing is the “Jenkinsfile”: https://github.com/jenkinsci/config-file-provider-plugin/blob/master/Jenkinsfile <https://github.com/jenkinsci/config-file-provider-plugin/blob/master/Jenkinsfile> Here is an example of an other plugin of mine: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfig-file-provider-plugin/activity <https://ci.jenkins.io/blue/organizations/jenkins/Plugins/config-file-provider-plugin/activity> In terms of the future… I think the first would be to upgrade the parent pom to org.jenkins-ci.plugins:plugin this would ease a lot of things and should keep us up to date with the latest requirements when it comes to plugin maintenance. Other things: - pipeline support, I did not have the time to check https://github.com/jenkinsci/repository-connector-plugin/pull/21 <https://github.com/jenkinsci/repository-connector-plugin/pull/21> - upgrade/replace of aether, aether is no longer an active project and is now (as far as I understand) replaced by https://maven.apache.org/resolver/ <https://maven.apache.org/resolver/> PRs: unfortunate I’m very limited in terms of time right now - but I fully trust you and you can move things forward! If you want me to have a look to, just mention me in the PR comments (@imod) and I will do my best. Releases: the same rule as with PRs: I trust you! If you think a release is ready, go for it or ask me to do one. The only thing I ask you for here, is that you try to update the release notes on the wiki too - as a user, I hate releases where I have no idea what changed. …in general: I trust you and I think that we only can move forward if we both do so. Regards Domi > On 22 Jan 2018, at 22:19, Jae Gangemi <[email protected]> wrote: > > > would it be possible to get admin access to this repo? i'd like to set up > travis to build pull requests but i don't currently have access. > > i have cc-ed domi here. i tried reaching out to touch base and discuss this > last week but i have not heard back and wanted to cover my bases. > > thanks!! > > > On Sun, Jan 14, 2018 at 1:21 PM, Baptiste Mathus <[email protected] > <mailto:[email protected]>> wrote: > Thanks for your patience. > Just added you as a committer Jae. > > Obviously you will want to go through PRs for changes, and leave some time to > Domi to review it as much as possible. > > When/if you wish to release, you'll need to file a PR against the permissions > repo, but that's probably not needed yet at that point. > > Cheers and welcome! > > 2018-01-10 16:38 GMT+01:00 Jae Gangemi <[email protected] > <mailto:[email protected]>>: > > awesome! > > jenkins: jgangemi (jgangemi at gmail) > github: jgangemi > > On Tuesday, January 9, 2018 at 11:39:56 PM UTC-7, domi wrote: > Hi Jae, > > I’m more then happy if you want to help out with the repository-connector! > The reason why I did not answer to your first mail is, that my subscription > to the jerkins-dev googlegroup does not work anymore - I’m fighting with it > since months and have no idea why it does not work… > /Domi > >> On 10 Jan 2018, at 00:22, Jae Gangemi <[email protected] <>> wrote: >> >> >> thanks! >> >> adding original maintainers (as listed in wiki page) to cc list. >> >> On Tue, Jan 9, 2018 at 2:36 PM, Baptiste Mathus <[email protected] <>> wrote: >> Hello! >> >> Thank you for your interest! We've documented the process on this page: >> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin >> <https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin> >> >> To sum up, you want to put them in CC (hint: use git history, there should >> be a bunch of emails there in commits) here, and either they answer, or we >> have a typical 2 weeks timeout before giving you the necessary permissions >> to take over. >> >> Thanks again >> >> 2018-01-08 18:59 GMT+01:00 Jae Gangemi <[email protected] <>>: >> i'm trying to reach the maintainers of the repostitory-connector plugin to >> see if they are still interested in maintaining it and if not, what steps i >> need to do in order to take over and provide support. >> >> thanks!! >> >> -- >> -jae >> >> -- >> 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/cec61c51-0840-4dd8-ab7a-57136056cd49%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/cec61c51-0840-4dd8-ab7a-57136056cd49%40googlegroups.com?utm_medium=email&utm_source=footer>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> -- >> 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/X3nHpfaeD9M/unsubscribe >> <https://groups.google.com/d/topic/jenkinsci-dev/X3nHpfaeD9M/unsubscribe>. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS62Kvt8Y76s4h8ep3yirks9dye1FuiCncFfPY1ODHv_qg%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS62Kvt8Y76s4h8ep3yirks9dye1FuiCncFfPY1ODHv_qg%40mail.gmail.com?utm_medium=email&utm_source=footer>. >> >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> >> -- >> -jae > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/e5755176-9209-43ad-8b50-db4f7b93121e%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/e5755176-9209-43ad-8b50-db4f7b93121e%40googlegroups.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > 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/X3nHpfaeD9M/unsubscribe > <https://groups.google.com/d/topic/jenkinsci-dev/X3nHpfaeD9M/unsubscribe>. > To unsubscribe from this group and all its topics, send an email to > [email protected] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7DtV529r5jvroKu-um3tWCjCQzFmcVg17szQiJ90P96g%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7DtV529r5jvroKu-um3tWCjCQzFmcVg17szQiJ90P96g%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > > -- > -jae -- 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/6477EE86-E2F9-4EB0-993F-64D241D5B9A4%40fortysix.ch. For more options, visit https://groups.google.com/d/optout.
