I've seen inconsistent results from the "Recent Changes" links on my
various Jenkins jobs which use the Git plugin 2.0 beta.
One of the jobs stopped showing history, even though I know the changes
were arriving because that job was merging them and pushing the merge
results to the central repos
Waite
>
> From: Kohsuke Kawaguchi
>To: jenkinsci-users@googlegroups.com
>Cc: Mark Waite ; Jenkins Dev
>
>Sent: Friday, July 26, 2013 11:04 AM
>Subject: Re: [ANN] Beta testing of Git plugin 2.0
>
>
>
>I guess I've sent out this announcement too soon out of th
er.json ?
Mark Waite
*From:* Kohsuke Kawaguchi
*To:* Jenkins Users ; Jenkins Dev
*Sent:* Thursday, July 25, 2013 4:40 PM
*Subject:* [ANN] Beta testing of Git plugin 2.0
Hi,
te for how long it will be before Git Client plugin 1.1.1 is
visible from http://updates.jenkins-ci.org/update-center.json ?
Mark Waite
>
> From: Kohsuke Kawaguchi
>To: Jenkins Users ; Jenkins Dev
>
>Sent: Thursday, July 25, 2013 4:40 PM
>Su
It supports per-project credential.
The only problem is that there's currently no implementation of the HTTP
BASIC auth credential. So I'm reusing the credential for SSH password
authentication for this purpose.
If you are at at it, please add that in the credentials plugin.
The branch in q
Did you get credentials integration in yet...
If not I would like to try and get it in for the next beta... and which
branch is it so I can try to start tomorrow
On 25 July 2013 23:40, Kohsuke Kawaguchi wrote:
>
> Hi,
>
> We've been working on a major improvement on Git plugin, and it's now at
Hi,
We've been working on a major improvement on Git plugin, and it's now at
the point that it's ready for general consumption.
As Git plugin is used by many and we want to reduce the chance of
regressions, I'm calling for people to try out this unreleased Git 2.0
plugin.
Please see [1] f
