On Fri, 22 Aug 2014 17:47:14 +0200, Christian Galsterer
christian.galste...@gmx.de wrote:
Hi,
I created a new plugin which allows to set the build description with
support for macros from the Token Macro Plugin.
My Github ID is:christiangalsterer
The repo is available at
https://github.com
, e.h.
email-ext.
Therefore this new plugin.
Br
Christian
On Friday, August 22, 2014 5:55:35 PM UTC+2, ogondza wrote:
On Fri, 22 Aug 2014 17:47:14 +0200, Christian Galsterer
christian...@gmx.de javascript: wrote:
Hi,
I created a new plugin which allows to set the build description
using a regex expression. Not always the required
information is available in the log output or it is simply easier to use the
macros from the Token Macro Plugin as many other plugins also do, e.h.
email-ext.
Therefore this new plugin.
Br
Christian
On Friday, August 22, 2014 5:55:35
@googlegroups.com
*Sent:* Saturday, August 9, 2014 3:56 PM
*Subject:* Re: New Plugin: SAML Plugin
I don't see my plugin yet in the two sites mentioned on the wiki. It's
been almost 24 hours and it said they should show up within 6, so I think
somethings wrong.
http://repo.jenkins-ci.org/releases/org/jenkins
*To:* jenkinsci-dev@googlegroups.com
*Sent:* Saturday, August 9, 2014 3:56 PM
*Subject:* Re: New Plugin: SAML Plugin
I don't see my plugin yet in the two sites mentioned on the wiki. It's
been almost 24 hours and it said they should show up within 6, so I think
somethings wrong.
http://repo.jenkins
-dev/qkmbl3HrYgk/dWnVU7-nTjoJ
https://groups.google.com/forum/#!searchin/jenkinsci-dev/snapshot/jenkinsci-dev/fyxXO0HXrGc/r1KYltnfzesJ
Hope that helps
Bruno
From: Ben McCann b...@benmccann.com
To: jenkinsci-dev@googlegroups.com
Sent: Saturday, August 9, 2014 3:56 PM
Subject: Re: New Plugin
*To:* jenkinsci-dev@googlegroups.com
*Sent:* Saturday, August 9, 2014 3:56 PM
*Subject:* Re: New Plugin: SAML Plugin
I don't see my plugin yet in the two sites mentioned on the wiki. It's
been almost 24 hours and it said they should show up within 6, so I think
somethings wrong.
http
-plugin), and the new plugin should migrate any old
config where appropriate.
On 08/17/2014 01:51 AM, Rafael Ribeiro Rezende wrote:
Or we could take the chance and fix this one at least... But I don't
know if it would break any reference.
On Aug 16, 2014 3:56 PM, Daniel Beck m...@beckweb.net
the artefactId is taken from the pom.xml (which should not contain -plugin) -
the name of the git repository per convention is like artifactId-plugin
Domi
On 16 Aug 2014, at 00:37, Rafael Ribeiro Rezende rafaelrez...@gmail.com wrote:
Thanks for pointing that out.
I just noticed that the
Agreed, but the old pom.xml already had the -plugin in its artifactId.
If I remove it in this case, the ids won't match anymore.
Ideas?
On Aug 16, 2014 2:47 PM, d...@fortysix.ch d...@fortysix.ch wrote:
the artefactId is taken from the pom.xml (which should not contain
“-plugin) - the name of
More than 150 plugins do it wrong (i.e. have a name ending in -plugin), so
that's not something to be concerned about.
On 16.08.2014, at 14:57, Rafael Ribeiro Rezende rafaelrez...@gmail.com wrote:
Agreed, but the old pom.xml already had the -plugin in its artifactId.
If I remove it in this
Or we could take the chance and fix this one at least... But I don't know
if it would break any reference.
On Aug 16, 2014 3:56 PM, Daniel Beck m...@beckweb.net wrote:
More than 150 plugins do it wrong (i.e. have a name ending in -plugin), so
that's not something to be concerned about.
On
Hello everyone,
I finally managed some time to finish and test the new Play plugin.
The Play!Framework plugin is designed to work with every existing version
of Play, from the first non-sbt-based Play!1.x to the latest versions of
Activator
If the old one is not working anymore, then you should integrate your stuff
into it and try to migrate the old config to the new one, this will keep the
plugin with the same pluginid and
It will keep the users from scratching there head when searching for the right
Play-Plugin
Am 15.08.2014
Thanks for pointing that out.
I just noticed that the artifactId is actually play-autotest-plugin instead
of the play-plugin I assumed at first due to the folder name in the
jenkinsci Github.
Just fixed the artifactId to match the older one.
On Fri, Aug 15, 2014 at 11:54 PM, domi
Hi Christopher,
I agree to most of the points you wrote. but please take a look at the
current version of the plugin. it is currently 0.1.0, which means i'll work
further on the plugin and improve it step by step.
oauth is definitely one of the next features that i'm going to implement.
in
Hi,
i created a google play publisher plugin for android app.
the project is located at github:
https://github.com/DavidHamm/google-play-publisher
my github id is: davidhamm
Thanks
david
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
Hi there,
On 08/13/2014 08:27 PM, David Hamm wrote:
i created a google play publisher plugin for android app.
the project is located at github:
Ah, I have been working on an extended version of this plugin, as
perhaps was somebody else (there was a discussion on the users list
recently).
/fyxXO0HXrGc/r1KYltnfzesJ
Hope that helps
Bruno
--
*From:* Ben McCann b...@benmccann.com
*To:* jenkinsci-dev@googlegroups.com
*Sent:* Saturday, August 9, 2014 3:56 PM
*Subject:* Re: New Plugin: SAML Plugin
I don't see my plugin yet in the two sites mentioned
I just filed two bugs for the https issue. I have to say I am quite
concerned this is an issue and that there are over 50 open items listed as
critical security issues in the bug tracker.
https://issues.jenkins-ci.org/browse/JENKINS-24190
https://issues.jenkins-ci.org/browse/JENKINS-24191
On
I don't see my plugin yet in the two sites mentioned on the wiki. It's been
almost 24 hours and it said they should show up within 6, so I think
somethings wrong.
http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/
http://repo.jenkins-ci.org/releases/org/jvnet/hudson/plugins/
When I ran
Hope that helps
Bruno
From: Ben McCann b...@benmccann.com
To: jenkinsci-dev@googlegroups.com
Sent: Saturday, August 9, 2014 3:56 PM
Subject: Re: New Plugin: SAML Plugin
I don't see my plugin yet in the two sites mentioned on the wiki. It's been
almost 24
Hi,
Any thoughts on this?
Thanks,
Ben
On Aug 7, 2014 11:54 AM, Ben McCann b...@benmccann.com wrote:
Hi,
Just wanted to follow up on this and see if there was anything I needed to
do to have this downloadable from the Jenkins plugin registry. There's no
plugin currently supporting SAML
Great! Thank you so much.
I've made the changes you've requested and released 0.1. I think... It's
not showing up yet as available for download and the wiki
https://wiki.jenkins-ci.org/display/JENKINS/SAML+Plugin still says No
Information For This Plugin. Perhaps it just takes awhile to appear
Hi,
Just wanted to follow up on this and see if there was anything I needed to
do to have this downloadable from the Jenkins plugin registry. There's no
plugin currently supporting SAML 2.0, so I think this will be a very
helpful addition.
Thanks,
Ben
On Wed, Aug 6, 2014 at 1:35 PM, Ben
Hi,
I created a SAML 2.0 Authentication plugin:
https://github.com/connectifier/jenkins-saml-plugin
My GitHub ID is benmccann
Thanks,
Ben
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving
Sounds reasonable! Fine with me :)
--
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 more options, visit
with recent versions of the
Git plugin, I decided to write a new plugin for triggering git polls through
Gitorious WebHooks.
It is currently available on GitHub and is already used in our CI
environment.
Is it possible to host this on jenkins-ci.org? My GitHub ID is belanur.
Regards
Hi crowd,
since the existing Gitorious plugin seems to be dead (one release back in
2012, no activtiy on github) and does not work with recent versions of the
Git plugin, I decided to write a new plugin for triggering git polls
through Gitorious WebHooks https://gitorious.org/gitorious/pages
to publish a new plugin for
executing a build remotely.
The plugin allows you to request a build from the API but it returns a
JSON snippet with a UUID for the job. This allows you to track the status
of a job (using another part of the API) even before it has left the
queue and has been
there,
I'd like to use the official Jenkins repo to publish a new plugin for
executing a build remotely.
The plugin allows you to request a build from the API but it returns a
JSON snippet with a UUID for the job. This allows you to track the status
of a job (using another part of the API
I've not touched this in a while Daniel, but I found that if I was queuing
multiple copies of the same job, I could give it a unique ID - whereas
/build simply gives you the information it's queuing.
That's not to say that the queue API has improved to include information
like this - like I say,
On 31.07.2014, at 12:19, Stuart Davidson stuart.david...@spedge.com wrote:
I've not touched this in a while Daniel, but I found that if I was queuing
multiple copies of the same job, I could give it a unique ID - whereas /build
simply gives you the information it's queuing.
That's not
As I understand it, a build could be queued, cancelled, queued again and
thus end up with the same build id. With this plugin, I'm appending a UUID
to the build in order to identify a unique run no matter what happened in
the queue.
However, you've shown a way of uniquely identifying a build by
On 31.07.2014, at 12:36, Stuart Davidson stuart.david...@spedge.com wrote:
As I understand it, a build could be queued, cancelled, queued again and thus
end up with the same build id. With this plugin, I'm appending a UUID to the
build in order to identify a unique run no matter what
Hello everyone,
I'm new to Jenkins Developers group and I would like to share a plugin i
wrote to connect Jenkins to Octopus Deploy. It is a simple wrapper to
existing tools but still provides a significant UI improvement.
It can be found on my personal Github account:
Hi all,
I have a new jenkins plugin I'd like to be hosted
Its available to clone from here;
https://github.com/daveneedstoknow/JenkinsAutoTrishPlugin
Thanks
Dave.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this
Re-sending the request after changing the subject line.
Hi,
I had developed a new plugin for Jenkins named test-results-analyzer.
Many of us have a requirement of knowing the execution status of a test
package , test class or test-method across multiple builds. This plugin
developed a new plugin for Jenkins named test-results-analyzer.
Many of us have a requirement of knowing the execution status of a test
package , test class or test-method across multiple builds. This plugin is an
implementation of the said requirement and shows a table containing
in the dashboard view?
Welcome aboard! Ulli
Am 18.07.2014 um 14:33 schrieb Varun Menon mr.varu...@gmail.com
javascript::
Re-sending the request after changing the subject line.
Hi,
I had developed a new plugin for Jenkins named test-results-analyzer.
Many of us have a requirement of knowing
Developer List
Subject: Re: Host new plugin - commit access
Added as https://github.com/jenkinsci/vmanager-plugin, you have commit access.
slide
On Wed, Jul 16, 2014 at 10:45 AM, Tal Yanai t...@yanai.org.il
mailto:t...@yanai.org.il wrote:
g...@github.com:tyanai/vManager-Plugin-Jenkins.git
.
*From:* jenkinsci-dev@googlegroups.com [mailto:
jenkinsci-dev@googlegroups.com] *On Behalf Of *Slide
*Sent:* Wednesday, July 16, 2014 10:43 PM
*To:* Jenkins Developer List
*Subject:* Re: Host new plugin - commit access
Added as https://github.com/jenkinsci/vmanager-plugin, you have commit
@googlegroups.com] On
Behalf Of Slide
Sent: Thursday, July 17, 2014 11:06 PM
To: Jenkins Developer List
Subject: Re: Host new plugin - commit access
See this wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
On Thu, Jul 17, 2014 at 12:46 PM, Tal Yanai t...@yanai.org.il
Hi,
I would like to get a commit access to add a new Plugin.
The GitHub plugin name is vManager-Plugin-Jenkins
The GitHub personal name is tyanai
Thanks,
Tal.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from
Do you have a repo it can be cloned from into the jenkins org?
On Wed, Jul 16, 2014 at 10:26 AM, Tal Yanai t...@yanai.org.il wrote:
Hi,
I would like to get a commit access to add a new Plugin.
The GitHub plugin name is vManager-Plugin-Jenkins
The GitHub personal name is tyanai
Thanks
vManager-Plugin-Jenkins is the repo name
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On
Behalf Of Slide
Sent: Wednesday, July 16, 2014 8:33 PM
To: Jenkins Developer List
Subject: Re: Host new plugin - commit access
Do you have a repo it can be cloned from
*To:* Jenkins Developer List
*Subject:* Re: Host new plugin - commit access
Do you have a repo it can be cloned from into the jenkins org?
On Wed, Jul 16, 2014 at 10:26 AM, Tal Yanai t...@yanai.org.il wrote:
Hi,
I would like to get a commit access to add a new Plugin.
The GitHub plugin name
@googlegroups.com [mailto:
jenkinsci-dev@googlegroups.com] *On Behalf Of *Slide
*Sent:* Wednesday, July 16, 2014 8:44 PM
*To:* Jenkins Developer List
*Subject:* Re: Host new plugin - commit access
Yes, what is the URL?
On Wed, Jul 16, 2014 at 10:33 AM, Tal Yanai t...@yanai.org.il wrote:
vManager
Hi,
I had developed a new plugin for Jenkins named test-results-analyzer.
Many of us have a requirement of knowing the execution status of a test
package , test class or test-method across multiple builds. This plugin is
an implementation of the said requirement and shows a table containing
The rebuild infrastructure is all in java -
https://github.com/JeremyMarshall/chuck-norris-axis-plugin/tree/master/src/main/java/org/jenkinsci/complex/axes
I was hoping to have that in its own plugin at some point but it seems
impossible to have databoundconstructors and getters and setters
Hi
I put together an example plugin to simplify matrix job axis creation. This
rebuilds at build time to update the axis builds.
It uses the chucknorris plugin as an optional dependency. I built it with
the gradle plugin and its a combination of java for the scaffolding and
groovy for the
Very cool plugin Christian. Can you merge my PR :)
On Wednesday, July 9, 2014 2:24:25 AM UTC-5, Christian Meyer wrote:
Hi,
I developed a plugin to analyze the usage of Jenkins plugins.
I would like to share this plugin, although it is in an early state at the
moment.
github-id:
Hi,
I developed a plugin to analyze the usage of Jenkins plugins.
I would like to share this plugin, although it is in an early state at the
moment.
github-id: chrissy25
repository: pluginusage
regards
Christian
--
You received this message because you are subscribed to the Google
Created https://github.com/jenkinsci/plugin-usage-plugin
Welcome aboard! Ulli
Am 09.07.2014 um 09:24 schrieb Christian Meyer chrissy.meye...@gmail.com:
Hi,
I developed a plugin to analyze the usage of Jenkins plugins.
I would like to share this plugin, although it is in an early state at
Thanks :)
Am Mittwoch, 9. Juli 2014 15:53:06 UTC+2 schrieb Ullrich Hafner:
Created https://github.com/jenkinsci/plugin-usage-plugin
Welcome aboard! Ulli
Am 09.07.2014 um 09:24 schrieb Christian Meyer chrissy...@gmail.com
javascript::
Hi,
I developed a plugin to analyze the usage of
I'm having issues with my IRC client since I switched machines... somebody
else might be able to help
On 3 July 2014 10:18, Paul Allen pal...@perforce.com wrote:
Hi Stephen,
Please can you create a new plugin entry for 'p4'.
github repo:jenkinsci/p4-plugin
artifactId
...@perforce.com wrote:
Hi Stephen,
Please can you create a new plugin entry for 'p4'.
github repo:jenkinsci/p4-plugin
artifactId: p4
package:com.perforce.jenkins.p4
My GitHub id is 'p4paul'.
I will need to do some refactoring to match the names above
create a new plugin entry for 'p4'.
github repo:jenkinsci/p4-plugin
artifactId: p4
package:com.perforce.jenkins.p4
My GitHub id is 'p4paul'.
I will need to do some refactoring to match the names above, but the code
is currently here
stephen.alan.conno...@gmail.com wrote:
I'm having issues with my IRC client since I switched machines...
somebody else might be able to help
On 3 July 2014 10:18, Paul Allen pal...@perforce.com wrote:
Hi Stephen,
Please can you create a new plugin entry for 'p4'.
github repo
On 3 July 2014 10:18, Paul Allen pal...@perforce.com wrote:
Hi Stephen,
Please can you create a new plugin entry for 'p4'.
github repo:jenkinsci/p4-plugin
artifactId: p4
package:com.perforce.jenkins.p4
My GitHub id is 'p4paul
Kindly requesting the hosting of our new Jenkins plugin:
- plugin name: azure-slave
- my GitHub userid: martinsawicki. Also please give commit access
to snallami
(we do not yet have a Gitub repo for this, but pls create one under the Jenkins
repo)
Thank you!
Martin
Hi,
I have created a chroot plugin, which uses pbuilder and mock to create
isolated build environments (which I found very useful for C and C++
projects with different dependencies) and I would like to host it on
jenkin-ci.org:
Plugin name: chroot-plugin
Github username: rmohr
Github
Sure; thanks for the clarification of the pattern.
Paul
On 30 Jun 2014, at 11:26, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
please do not put `-plugin` in the artifactId.
The pattern is:
github repo name is: X-plugin
artifactId is: X
groupId is: org.jenkins-ci.plugins
Created https://github.com/jenkinsci/chroot-plugin
Welcome aboard!
Ulli
Am 01.07.2014 um 10:15 schrieb Roman Mohr rfenkhu...@googlemail.com:
Hi,
I have created a chroot plugin, which uses pbuilder and mock to create
isolated build environments (which I found very useful for C and C++
Hi Oleg,
On 27 Jun 2014, at 17:11, Oleg Nenashev o.v.nenas...@gmail.com wrote:
I would need to learn about configuration migration, if you know of another
tool or example that performs this task please let me know.
please do not put `-plugin` in the artifactId.
The pattern is:
github repo name is: X-plugin
artifactId is: X
groupId is: org.jenkins-ci.plugins
package name is one of:
* org.jenkinsci.plugins.X; or
* jenkins.plugins.X; or
* com.mycompany.jenkins.X (if you want to credit a company providing
I would need to learn about configuration migration, if you know of
another tool or example that performs this task please let me know.
https://wiki.jenkins-ci.org/display/JENKINS/Hint+on+retaining+backward+compatibility
describes common cases, which may be used. When you finish the
plans, hence I would like to keep plugins separately.
If the new plugin becomes a mainline, we can always deprecate the existing
plugin or to replace it by the migration assistant (which will depend from
the new plugin).
2014-06-24 20:09 GMT+04:00 Rob Petti rob.pe...@gmail.com:
Let's
to keep plugins separately.
If the new plugin becomes a mainline, we can always deprecate the
existing plugin or to replace it by the migration assistant (which will
depend from the new plugin).
2014-06-24 20:09 GMT+04:00 Rob Petti rob.pe...@gmail.com:
Let's start with actually uploading
Hi Oleg,
On 26 Jun 2014, at 15:53, Oleg Nenashev o.v.nenas...@gmail.com wrote:
My managers don't want to invest into such migration without a middle-term
advantage.
They think that Perforce guys should be responsible for the compatibility
since we pay you money ;)
I definitely don't want
for the
user guide and details of the new plugin.
Thanks,
Paul
On 12 Jun 2014, at 21:20, Oleg Nenashev o.v.ne...@gmail.com javascript:
wrote:
2.0 should be indicate it, but the additional entry on Wiki is required
to explicitly describe the situation.
However, the 1.x version
, hence I would like to keep plugins separately.
If the new plugin becomes a mainline, we can always deprecate the existing
plugin or to replace it by the migration assistant (which will depend from
the new plugin).
2014-06-24 20:09 GMT+04:00 Rob Petti rob.pe...@gmail.com:
Let's start
On Thu, Jun 12, 2014 at 4:20 PM, Oleg Nenashev o.v.nenas...@gmail.com wrote:
I'm not sure about the behavior for
common update centers if the 2.x version goes to the main repo.
This might be an issue—1.x updates would not be offered to anyone
(assuming the core baselines for 1.x and 2.x are the
On Jun 16, 2014, at 22:32 , Jesse Glick jgl...@cloudbees.com wrote:
On Thu, Jun 12, 2014 at 4:20 PM, Oleg Nenashev o.v.nenas...@gmail.com wrote:
I'm not sure about the behavior for
common update centers if the 2.x version goes to the main repo.
This might be an issue--1.x updates would not
Keith, the component in JIRA is created now
regards Domi
On 05 May 2014, at 18:46, Keith keithc...@gmail.com wrote:
Domi,
are you planning an integration with the credentials plugin?
I hadn't considered it, but certainly I can see why it should. Mainly I've
just been exploring Jenkins
Hi,
I want to share new plugin with community.
The plugin allows to use Xamarin Studio Build Tool from Xamarin Studio Tool
Runner (mdtool).
The name of the plugin is *mdtool-plugin*.
My GitHub user name is *fen-x*.
Ivan Nikitin
--
You received this message because you are subscribed
Created: https://github.com/jenkinsci/mdtool-plugin
Welcome aboard!
Ulli
Am 13.06.2014 um 16:24 schrieb Иван Никитин fenix...@gmail.com:
Hi,
I want to share new plugin with community.
The plugin allows to use Xamarin Studio Build Tool from Xamarin Studio Tool
Runner (mdtool
plugin and to look at a way
to ease the migration process.
With some maturing of the new plugin, I still hope to be able to release it
under the Jenkins community. If you have identified missing features or have
suggestions on the migration please let me know. I am keen to bring
of the new plugin, I still hope to be able to release
it under the Jenkins community. If you have identified missing features or
have suggestions on the migration please let me know. I am keen to bring
in as much help as possible.
Kind regards,
Paul
On 20 May 2014, at 20:22, Oleg
On 12.06.2014, at 18:07, Jesse Glick jgl...@cloudbees.com wrote:
just merge to master, change
2.0-beta-n-SNAPSHOT to 2.0-SNAPSHOT, and release
And maybe indicate incompatibility of existing configurations.
--
You received this message because you are subscribed to the Google Groups
Jenkins
2.0 should be indicate it, but the additional entry on Wiki is required to
explicitly describe the situation.
However, the 1.x version is not dead. I'm not sure about the behavior for
common update centers if the 2.x version goes to the main repo.
2014-06-12 23:58 GMT+04:00 Daniel Beck
Hi,
I made a new plugin for .Net in Jenkins.
The plugin change the version of AssemblyInfo.cs from .Net Projects.
I have searched and don't find anything like this, so I made a plugin for
change default assemblyversion files.
I want to share my plugin with Jenkins community and like I read
Created https://github.com/jenkinsci/change-assembly-version-plugin
Welcome aboard!
Ulli
Am 06.06.2014 um 14:29 schrieb Leonardo Kobus leonardo.ko...@gmail.com:
Hi,
I made a new plugin for .Net in Jenkins.
The plugin change the version of AssemblyInfo.cs from .Net Projects.
I have
Hi,
I made a new plugin for .Net in Jenkins.
The plugin change the version of AssemblyInfo.cs from .Net Projects.
I have searched and don't find anything like this, so I made a plugin for
change default AssemblyInfo.cs files.
I want to share my plugin with Jenkins community and like I read
Good point, Richard. Thank you! I'll see if we can send a pull-request to
Notification Plugin instead.
Warm regards,
Evgeny
On Wed, Jun 4, 2014 at 2:22 AM, Richard Bywater rich...@byh2o.com wrote:
Just a query - is there a particular reason not to extend the
functionality of the existing
Hi,
We're working on jenkins-notify-plugin
https://github.com/cloudnative/jenkins-notify-plugin submitting a
configurable JSON payload in a POST request as as post-build action.
Project description provides all further details.
So we'd love to have the project forked and hosted at
Just a query - is there a particular reason not to extend the functionality
of the existing Notification Plugin? (
https://wiki.jenkins-ci.org/display/JENKINS/Notification+Plugin) I see your
one is a lot more customisable but it seems to me that the use-cases are
similar?
Richard.
On Wed, Jun
Hi there,
P4Java 2013.1 (and 2013.2) supports Perforce servers as old as 2005.2:
ftp://ftp.perforce.com/perforce/r13.1/doc/user/p4javanotes.txt
Requirements
* Perforce server at Release 2005.2 or higher.
Hope this helps!
-Marc
On Monday, May 26, 2014 4:39:58 AM UTC-7, Kanstantsin Shautsou
Does the p4java support all perforce server versions?
For example, will 2013.1 p4java support connections with 2009.1 server?
Because with current wrapper i can select different binaries.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To
parade with the old plugin and to look at a way to ease
the migration process.
With some maturing of the new plugin, I still hope to be able to release it
under the Jenkins community. If you have identified missing features or have
suggestions on the migration please let me know. I am keen
пользователь pallen написал:
Hi Guys,
I know there has been a lot of discussion around the new plugin, but
referring to Kawaguchi-san's email (below) I am happy to go with option 3
and distribute through the beta update centre for the time being.
Please let me know where to deploy the code
Hi Ulli,
Thanks a lot!
I will upload the sources and create the wiki page for the plugin.
Regards,
Cees
On Mon, May 12, 2014 at 10:14 AM, Ulli Hafner ullrich.haf...@gmail.comwrote:
https://github.com/jenkinsci/send-stacktrace-to-eclipse-plugin
Welcome aboard!
Ulli
Am 08.05.2014 um
https://github.com/jenkinsci/send-stacktrace-to-eclipse-plugin
Welcome aboard!
Ulli
Am 08.05.2014 um 21:19 schrieb Cees Bos cbos...@gmail.com:
Hi Ulli,
Thanks for the reply.
It is not on Github yet. I read on the wiki page
(https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins)
Hi Ulli,
Thanks for the reply.
It is not on Github yet. I read on the wiki page (
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins) that is not
necessary.
If that is easier for you I can create a repo and push it to there, so you
can clone it.
I don't know what is easier to do for
Can someone reply on the mail below I send earlier?
Regards,
Cees
On Fri, Apr 25, 2014 at 11:00 AM, Cees Bos cbos...@gmail.com wrote:
We have developed a plugin which can send a stacktrace of a failing
testcase to Eclipse.
In Eclipse you need a plugin, which can receive the request.
The
Is your plugin already in GitHub so we can fork it?
Am 25.04.2014 um 11:00 schrieb Cees Bos cbos...@gmail.com:
We have developed a plugin which can send a stacktrace of a failing testcase
to Eclipse.
In Eclipse you need a plugin, which can receive the request.
The Eclipse plugin can be
Domi,
are you planning an integration with the credentials plugin?
I hadn't considered it, but certainly I can see why it should. Mainly
I've just been exploring Jenkins plugin architecture, as this is my
first Jenkins plugin.
any idea when do cut the first release of this plugin?
I
Hi domi,
I merged the 2 plugins, as discussed almost 2 years ago :)
Any chance that you merge the pull request and release a new version of the
repository-connector-plugin any timme soon?
After the merge I would remove my repoclient-plugin Wiki page and update
the Wiki page of the
Hi Guys,
I know there has been a lot of discussion around the new plugin, but referring
to Kawaguchi-san's email (below) I am happy to go with option 3 and distribute
through the beta update centre for the time being.
Please let me know where to deploy the code and any changes that are need
That did the trick -- many thanks!
~ Keith
On Saturday, April 26, 2014 3:19:01 AM UTC-7, Ullrich Hafner wrote:
Sorry, due to the renaming of the repo the granted group has been renamed
too.
Can you please retry?
Am 25.04.2014 um 23:27 schrieb Keith Collison keit...@gmail.comjavascript:
601 - 700 of 1229 matches
Mail list logo
