Of course the plugin need some explanactions to work.
I will do my best do explain all in the Plugin Page
Em sábado, 14 de março de 2015 18:29:18 UTC-3, Victor Bathke escreveu:
Hi I created a plugin for Display screenshots and stacktraces while your
UI Test Suit builds (like in the
See https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin
to find the maintainer. If you consider to take over the maintenance, first
contact the current maintainer, Tom Huybrechts apparently, to ask him about
it.
Cheers
2015-03-16 12:08 GMT+01:00 Michael R. fussbal...@online.de:
You have to add the action to the build, probably.
Il giorno lun 16 mar 2015 21:14 Thom Ellis teh...@gmail.com ha scritto:
This is probably a bit of a newbie question, but I haven't been able to
find a good answer. What is the proper way to implicitly call an existing
plugin from within one
Thank you for that. Difficult to find out these things by just reading the
API.
tirsdag 17. mars 2015 10.39.58 UTC+1 skrev Daniel Beck følgende:
These functions are not supposed to be called directly, they clearly
handle HTTP requests.
Just call scheduleBuild2 and use the returned
Trying to call doBuild on a project in Groovy. I cannot find any examples
on how to use this method when it comes down to StaplerRequest and
StaplerResponse.
I am tempted to just call newBuild(), but I guess that would not get me a
hook into that build process/result.
I am iterating through a
These functions are not supposed to be called directly, they clearly handle
HTTP requests.
Just call scheduleBuild2 and use the returned QueueTaskFuture.
On 17.03.2015, at 10:34, Sverre Moe sverre@gmail.com wrote:
Trying to call doBuild on a project in Groovy. I cannot find any examples
- your GitHub plugin name: Karma-Jenkins-Plugin
- your personal GitHub ID: jmbrown864
- The existing GitHub repository to
fork: https://github.com/kbonnette/CodeCover-Jenkins-Plugin
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers
I don’t think that this is possible.
Am 17.03.2015 um 16:48 schrieb Kirill yam...@gmail.com:
Hi folks,
I added few mandatory fields to my build step's config.jelly with the
validation that ensures validation errors appearance if mandatory fields are
empty.
Is there a way to prohibit
On 17.03.2015, at 19:04, Richard Bywater rich...@byh2o.com wrote:
a bit hard to contact Tom?
GitHub account (comment on any commit and he'll get an email):
https://github.com/huybrechts
Jira account (with email address):
https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=huybrechts
Hi, i expect that my PR will be reviewed by some maintainer. Code parts
that i changed were written by Kohsuke that has more critical issues for
resolution.
@anyone please
comment/review https://github.com/jenkinsci/port-allocator-plugin/pulls and
raise :+1: . If we will have enough pluses i
Thanks a million, Jesse!
Your suggestion about JenkinsRule being a @ClassRule rather than a @Rule
was a shot in the bulls eye!
I changed @ClassRule to @Rule and it works fine!
Regards,
Kirill.
пятница, 20 февраля 2015 г., 20:40:23 UTC пользователь Jesse Glick написал:
On Thu, Feb 19, 2015 at
Hi folks,
I added few mandatory fields to my build step's config.jelly with the
validation that ensures validation errors appearance if mandatory fields
are empty.
Is there a way to prohibit saving the job if it's configuration contains
validation errors?
Regards,
Kirill.
--
You received
12 matches
Mail list logo