Hello! I would like to contribute a plugin to the community – a debian
package builder tool. It's created to analyze, build and publish debian
packages.
My github id is *pupssman*, the plugin is at
https://github.com/pupssman/debian-package-builder
Best,
Ivan Kalinin.
This should be ok now
2012/10/22 Phil Rumble philrum...@hotmail.com
Bump... is there anyone who can help?
On Tue, Jul 17, 2012 at 9:19 PM, Phil Rumble philrum...@hotmail.comwrote:
I don't how to do that, is there anything that I need to do?
On Tue, Jul 17, 2012 at 5:07 PM, Ullrich
forked as https://github.com/jenkinsci/debian-package-builder-plugin
CI job on
https://jenkins.ci.cloudbees.com/job/plugins/job/debian-package-builder-plugin/
2012/10/22 Ivan Kalinin pupss...@gmail.com
Hello! I would like to contribute a plugin to the community – a debian
package builder tool.
granted you access, but you just can push commits to github
2012/10/22 Ivan Kalinin pupss...@gmail.com
Great! What do i do next? How do I grigger the job?
On Monday, October 22, 2012 12:32:04 PM UTC+4, nicolas de loof wrote:
forked as
I guess this marker is that the issue is either blocker or critical (+ the
fix has to be in Jenkins for at least cca 2 weeks).
I'm asking because someone could forget to bump the issue to critical (default
is major) or I can miss something (both happened in the past).
On Monday 22 October
I would like to nominate JENKINS-15382 [1]
Not a critical or blocker, but it caused me some intermittent grief. (and I've
been running this in production backported to 1.466.2 thanks to Cloudbees)
/James
[1] https://issues.jenkins-ci.org/browse/JENKINS-15382.
-Original Message-
Hello, let me contribute to jenkins with this plugin please.
https://github.com/advantiss/builds-chain-fingerprinter
I think this should get fixed or reverted and back ported into the new LTS
release.
/Domi
On 18.10.2012, at 21:43, Jeff Maxwell jeff.maxw...@gmail.com wrote:
We have the same requirement.
On Thursday, September 27, 2012 11:02:00 AM UTC-5, liam.j.bennett wrote:
While this is clearly a bug
Just send us the repo location and your github ID so we can for it and add
grant you all the required permissions
/Domi
On 20.10.2012, at 08:13, Jerry Cai n...@qq.com wrote:
Dear all Jenkins-Devs ,
Jenkins CI is my favorite CI system , and I am very interested in it's
opening framework ,
I have updated the documentation:
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Structure#PluginStructure-Classloader
/Domi
On 21.10.2012, at 10:28, Edo Shor edo.s...@whitesourcesoftware.com wrote:
Hi,
My plugin uses velocity engine v 1.7 for creating reports. Can't change that.
HPI
I just submitted JENKINS-15594 (
https://issues.jenkins-ci.org/browse/JENKINS-15594). Ever since we've
upgraded Jenkins to 1.486, we've had intermittent and sporadic failures in
our jobs that use the CopyArtifacts plugin. I've confirmed that the job
supplying the artifact files DOES exist,
On Monday, October 15, 2012 8:09:50 PM UTC+4, R Tyler Croy wrote:
On Sun, 14 Oct 2012, Eugene Seliverstov wrote:
Plugin is hosted at my github account:
https://github.com/theirix/vboxwrapper-plugin
Could you please review an idea and provide an access to host the plugin
at
this should be fixed now
2012/10/22 theirix thei...@gmail.com
On Monday, October 15, 2012 8:09:50 PM UTC+4, R Tyler Croy wrote:
On Sun, 14 Oct 2012, Eugene Seliverstov wrote:
Plugin is hosted at my github account: https://github.com/theirix/**
vboxwrapper-plugin
Done
On Monday 22 October 2012 09:19:45 Nord, James wrote:
I would like to nominate JENKINS-15382 [1]
Not a critical or blocker, but it caused me some intermittent grief. (and
I've been running this in production backported to 1.466.2 thanks to
Cloudbees)
/James
[1]
I am actually trying to develop a Jenkins plugin using maven but I am
unable to test it.
I created my project with the command mvn -cpu hpi:create. I called the project
jenkins-plugin-tutorial. I packaged it with mvn package or mvn install and
run the Jenkins server with mvn hpi:run.
By
I forgot to say that I am using
Maven 2.2.1
Jenkins 1.466
Le mardi 23 octobre 2012 01:32:58 UTC+2, Dimitri CHARLES a écrit :
I am actually trying to develop a Jenkins plugin using maven but I am
unable to test it.
I created my project with the command mvn -cpu hpi:create. I called the
Hi Dimitri,
I created a plug-in last week I think, and run mvn hpi:run and it worked fine
(it was using 1.466 too).
But my Maven is 3.0.4. There are some special settings for Maven 2.x in the
plug-in tutorial, but could you consider updating your Maven to 3.0.4, maybe
installing both, and
I'm flying back to home today, and planning to take a sweep Tuesday afternoon.
2012/10/22 Vojtech Juranek vjura...@redhat.com:
Hi,
as agreed on the last Jenkins meeting [1], next LTS will be based on 1.480.
I identified and backported following bug fixes:
JENKINS-13336 Invalid JSON is
Hi,
I have been using Jenkins for 2 years now and planning to promote Jenkins
to a larger audience out of the workspace where I am working right now. We
are expecting around 25 - 30 comprising of people with no knowledge of
Jenkins and people with some knowledge.
Found about the Jenkins
19 matches
Mail list logo
