Re: repository-connector plugin maintainence

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

Re: repository-connector plugin maintainence

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

Re: repository-connector plugin maintainence

> On 23. Jan 2018, at 00:54, Jae Gangemi 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

Re: repository-connector plugin maintainence

replace context with status check in the above - context is how it's referred to in the api and not through the website. On Mon, Jan 22, 2018 at 4:54 PM, Jae Gangemi wrote: > > right - but how is the context that is required indicating the build was > successful set? > >

Re: repository-connector plugin maintainence

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? On Mon, Jan

Re: repository-connector plugin maintainence

> On 22. Jan 2018, at 23:41, Jae Gangemi 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

Re: repository-connector plugin maintainence

> On 22. Jan 2018, at 22:19, Jae Gangemi 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

Re: repository-connector plugin maintainence

interesting, i didn't know that existed. 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

Re: repository-connector plugin maintainence

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

Re: repository-connector plugin maintainence

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!!

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

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: > > 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 >

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 >

Re: repository-connector plugin maintainence

thanks! adding original maintainers (as listed in wiki page) to cc list. On Tue, Jan 9, 2018 at 2:36 PM, Baptiste Mathus wrote: > Hello! > > Thank you for your interest! We've documented the process on this page: > https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin > >

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

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