Thanks to Perforce themselves wading in with their size 12's you would come
to the conclusion the current plugin has gone stale.
It's easy to set up a test mechanism though, even easier if you use the
free version of IntelliJ.
--
You received this message because you are subscribed to the
Nevermind, I decided to give Intellij CE a go, and I don't know what kind
of voodoo magic it does, but it makes things a lot simpler. :)
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving
1.7?
BTW: you would get more answers in the dev-list (CC)
Am 23.04.2014 um 14:25 schrieb Niksan sumo...@googlemail.comjavascript:
:
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving
Unless I've missed a post, can someone tell me what's currently wrong with
the current plugin that warrants a pretty much from the ground up new
plugin? Speaking as a heavy user of Perforce if people are currently using
the existing plugin what issues are people having?
What worries me is
be in a minority on the point above, I just have concerns that when
it comes to new features, P4Api will get in the way.
On Wednesday, April 23, 2014 2:58:32 PM UTC+1, pallen wrote:
Hi Niksan,
The Jenkins plugin had popped up on Perforce's radar a few times; often
for performance issues. With our new
I meant point 1 and 4 are the same, not point 1 and 3. :)
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
For
