repository-connector plugin maintainence
Locked
repository-connector plugin maintainence
 
|
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/cec61c51-0840-4dd8-ab7a-57136056cd49%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
Hello! Thank you for your interest! We've documented the process on this page: 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 <[hidden email]>:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS62Kvt8Y76s4h8ep3yirks9dye1FuiCncFfPY1ODHv_qg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
On Tue, Jan 9, 2018 at 2:36 PM, Baptiste Mathus <[hidden email]> wrote:
-- -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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMshyruVRB3t14Oht9LQ_xmP%3DP34Z7k2PU0_mmJSsb3VPuXs0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
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
-- 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/7DEC60E3-A73A-4FAE-B104-E4F8188D9D9C%40fortysix.ch. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
awesome! jenkins: jgangemi (jgangemi at gmail) github: jgangemi On Tuesday, January 9, 2018 at 11:39:56 PM UTC-7, domi 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e5755176-9209-43ad-8b50-db4f7b93121e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
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 <[hidden email]>:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS7DtV529r5jvroKu-um3tWCjCQzFmcVg17szQiJ90P96g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
On Sun, Jan 14, 2018 at 1:21 PM, Baptiste Mathus <[hidden email]> wrote:
-- -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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMshyrsXBQWCmaCXwVK5gYhH%3D-GAt4DmeVOP%3DJkko6GK8e_gMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
|
|
I suggest you take a look at the Jenkinsfile there are a few options:
-- https://github.com/jenkinsci/accurev-plugin/blob/master/Jenkinsfile https://github.com/jenkinsci/git-client-plugin/blob/master/Jenkinsfile You get automatic builds then on ci.jenkins.io https://ci.jenkins.io/job/Plugins/job/accurev-plugin/ /Joseph Den mandag den 22. januar 2018 kl. 22.19.28 UTC+1 skrev Jae Gangemi:
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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ebab169e-ba98-4e29-b9f8-6291a88c610d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
On Mon, Jan 22, 2018 at 3:19 PM, Joseph P <[hidden email]> wrote:
-- -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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMshyrvg2msfhWih2%3D%2B%2BjTVWo10%2B%3Dr6ns6o15tPFKyonZyGroA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
In reply to this post by Jae Gangemi
> On 22. Jan 2018, at 22:19, Jae Gangemi <[hidden email]> 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 changed the accurev-plugin Developers team to admin access. -- 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2513757E-E03A-4949-B9EF-5CDCDCD7BEB1%40beckweb.net. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
In reply to this post by Jae Gangemi
> On 22. Jan 2018, at 23:41, Jae Gangemi <[hidden email]> wrote: > > unfortunately it doesn't look like it will block merging if the build fails or post back status updates to the PR which would be useful in preventing some mistakes (i opened a PR the other day and missed a commit/push that i only found out about after someone tried to pull the PR and build it locally). It's unclear what you mean. https://github.com/jenkinsci/repository-connector-plugin/settings/branches allows you to protect branches to prevent merges while PR checks are failing. It has nothing to do with the tool that posts commit statuses. -- 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/48EAB1D9-875B-47D7-A150-27AB283A3FBD%40beckweb.net. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
On Mon, Jan 22, 2018 at 4:08 PM, Daniel Beck <[hidden email]> wrote:
-- -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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMshyrtMOZ9Gq9oGUMVN5fy7JLSdvCyhSbR-XFmCeWwwKyzNzA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
On Mon, Jan 22, 2018 at 4:54 PM, Jae Gangemi <[hidden email]> wrote:
-- -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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMshyrtO3Nr%2B%3D0bYvt6K7USRWL-nd%2BN-rpdL23T17dSqLG%2BKzQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
In reply to this post by Jae Gangemi
> On 23. Jan 2018, at 00:54, Jae Gangemi <[hidden email]> wrote: > > right - but how is the context that is required indicating the build was successful set? > > oh wait...is that handled by some special internal magic by whatever plugin is being used to do the builds vs having to call some step/publisher in the Jenkinsfile itself to set the context? That's built in to GitHub Branch Source Plugin. Docs here: https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#_github_pull_requests Look at any plugin repo that has a Jenkinsfile and you're going to see plenty of commit statuses, linking back to ci.jenkins.io. -- 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/985D4CEB-71A5-437A-863D-567668C32401%40beckweb.net. For more options, visit https://groups.google.com/d/optout. |
Re: repository-connector plugin maintainence
|
|
In reply to this post by Jae Gangemi
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 Here is an example of an other plugin of mine: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfig-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 - 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/ 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
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 [hidden email]. 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. |
Re: repository-connector plugin maintainence
|
|
In reply to this post by Daniel Beck
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 Here is an example of an other plugin of mine: https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fconfig-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 - 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/ 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
-- 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 [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8F25043B-4151-435A-BA45-4B2CD82CE31D%40fortysix.ch. For more options, visit https://groups.google.com/d/optout. |
«
Return to Jenkins dev
|
1 view|%1 views
| Free forum by Nabble | Edit this page |