On Fri, May 20, 2016 at 4:12 PM, Daniel Beck wrote:
>
> > On 20.05.2016, at 03:35, Roshan Dawrani wrote:
> >
> > I couldn't update to v2.5 though, due to
> https://issues.jenkins-ci.org/browse/JENKINS-34013, which is still open
> &
Thank you for replying, Daniel. This is how I finally did it y'day -
downloaded the HPI files of the plugins that were not being shown due to
their dependency on a minimum version of Jenkins and uploaded them to
Jenkins /plugins directory using the "Advanced" UI of the plugin manager.
After manuall
On Tue, Jun 5, 2012 at 9:42 AM, Roshan Dawrani wrote:
>
> I am using Jenkins 1.461 with "git" plugin 1.1.18 (confirmed using
> /pluginManager).
>
> I have run Tomcat with "-Dhudson.plugins.git.GitSCM.verbose=true", but
> nowhere in the Jenkins job specif
Hi,
I am using Jenkins 1.461 with "git" plugin 1.1.18 (confirmed using
/pluginManager).
I have run Tomcat with "-Dhudson.plugins.git.GitSCM.verbose=true", but
nowhere in the Jenkins job specific logs I am seeing the verbose output
coming from the "git" plugin classes.
Could someone please let me
Revision 2a7562a91b2862fbb34c739138fe569b49476d7f
(origin/master)
===
Cheers.
On Mon, Jun 4, 2012 at 7:43 PM, Roshan Dawrani wrote:
> Hi,
>
> I am using Jenkins 1.461 and investigating an issue that Jenkins picks up
&
Hi,
I am using Jenkins 1.461 and investigating an issue that Jenkins picks up
for us the wrong revision to build, when it scans multiple branches that we
have in our "git" repository.
The Jenkins job is currently defined as:
==