I'm just putting those two things out there as it is better to integrate
credentials from the beginning... and a smart SCM-API implementation can be
leveraged to deliver better polling support for regular job types... which
again calls for early integration.
You probably don't need P4 specific
You probably don't need P4 specific credential type. You should be able
to get away with a Domain requirements/specification and the standard
username/password credentials type
You are right, but such migration requires 1.509.x to be a minimal
supported version.
The proposed PR has been created
For the data binding the names must exactly match:
jelly: field=„isStart“
Java: Constructor: isStart
Java: Getter: getIsStart
Am 18.04.2014 um 05:46 schrieb Code ekkapo...@gmail.com:
This is the builder class which is based on HelloWorldBuilder.
public class LogInfoBuilder extends Builder
Also you need only specify field=isStart on the f:entry. f:checkbox
need have no attributes at all.
--
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
I'm waiting for Rob and Paul to agree on the approach forward. I think
we'd be happy to honor that, since you guys are the ones that are doing
the actual work.
Where Jesse and I are coming from is to try to understand the message to
the existing users, because Perforce plugin is widely
I thought I've sent this but looks like I haven't.
Sorry about the delay, but it should be all set now.
On 04/17/2014 01:48 PM, Suersh Nallamilli wrote:
Can some one give me the required permissions ASAP , please?
On Wed, Apr 16, 2014 at 11:12 AM, Suersh Nallamilli
sureshi...@gmail.com
I didn't realize that you could release two versions of a plugin at the
same time to two different update centers. I think your proposal is
probably the best option here.
On Fri, Apr 18, 2014 at 11:31 AM, Kohsuke Kawaguchi
kkawagu...@cloudbees.com wrote:
I'm waiting for Rob and Paul to agree
On Fri, Apr 18, 2014 at 1:31 PM, Kohsuke Kawaguchi
kkawagu...@cloudbees.com wrote:
We could put both current and the new in the same repo, and call the new one
perforce plugin 2.0. […]
We can have alpha/beta releases of 2.0 in parallel to updates to 1.x
releases. People on the beta update
Hi *Kohsuke,*
I am still getting access denied for
jenkinsci/windows-azure-storage-plugin.git.
Does this take some time , i guess it should be immediate. I am
getting below error
remote: Permission to jenkinsci/windows-azure-storage-plugin.git
denied to snallami.
Hmm, how about now?
2014-04-18 19:05 GMT-07:00 Suersh Nallamilli sureshi...@gmail.com:
Hi *Kohsuke,*
I am still getting access denied for
jenkinsci/windows-azure-storage-plugin.git.
Does this take some time , i guess it should be immediate. I am
getting below error
Thank You. Now i got commit access
On Fri, Apr 18, 2014 at 9:27 PM, Kohsuke Kawaguchi k...@kohsuke.org wrote:
Hmm, how about now?
2014-04-18 19:05 GMT-07:00 Suersh Nallamilli sureshi...@gmail.com:
Hi *Kohsuke,*
I am still getting access denied for
11 matches
Mail list logo
