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?
>
>
22, 2018 at 4:08 PM, Daniel Beck wrote:
>
> > 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 m
-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:
>>
>>
>> would it be possib
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 :
>
>>
>> awesome!
>>
>> jenkins: jgangemi (jgangemi at
ail 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 >
> wrote:
>
>
> thanks!
>
> adding original maintain
gt;
> 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-
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 G
