Hi,
I understood, looking at some plugins that a good extension point
is hudson.model.RootAction.
Looking at the ui-samples plugin, I implemented an extension such as:
@Extension
public class MyMenuExtension implements RootAction {
public String getIconFileName() {
return "gear
In src/main/resources create a package called the same as your class
my.package.MyMenuExtension
in that package create a index.jelly file and fill that with content.
Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications
From: jenkinsci-dev
https://wiki.jenkins-ci.org/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkins
is a good start
--
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 jenkins
Jesse, slide & Kevin,
Thank you all for your input. My understanding is that the terms of use in
the license for Rational Team Concert does not allow for redistribution. I
am getting clarification on that, and whether or not deploying it to the
Jenkins repository constitutes redistribution.
Hi,
Trying to debug JENKINS-15156 it seems that after creating a new job,
the 'dir' member of its 'AbstractLazyLoadRunMap' of builds is null
until Jenkins is restarted/reload. After the map's members get
garbage-collected, reloading them fails because dir is null, giving
the missing builds.
Below
Thanks,
can you create a Github pull request for this?
That would be much easier to handle.
Gesendet: Donnerstag, 31. Januar 2013 um 17:19 Uhr
Von: "Julian Schmidt"
An: jenkinsci-dev@googlegroups.com
Betreff: Possible fix for JENKINS-15156 (builds d
2013/1/31 Scott Cowan
> Jesse, slide & Kevin,
>
> Thank you all for your input. My understanding is that the terms of use
> in the license for Rational Team Concert does not allow for
> redistribution. I am getting clarification on that, and whether or not
> deploying it to the Jenkins reposito
Hi,
I've extracted MailAddressResolver out of cvs-plugin according to
JENKINS-16389. Please fork.
https://github.com/olivergondza/cvs-mail-address-resolver-plugin
--
oliver
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe
All right, I created one such pull request:
https://github.com/jenkinsci/jenkins/pull/688
--
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+un
Heya,
Jenkins' Jira contains a component 'libvirtslave' which is redundant for
'libvirt-slave'. Can someone delete the former one, I already moved all
existing tickets over to the latter.
Is it furthermore possible to create versions for the different
components? It would be helpful if you can as
Hi,
The StarTeam plugin has similar problem.
Jar of the Starteam client is not freely redistributable
For same reason the plugin was grandfathered into repository.
The issue is worked around by having the StarTeam jars only in local private
repository.
Is this still acceptable solution?
Jan
On 01/31/2013 11:19 AM, Julian Schmidt wrote:
Below is a patch against revision ce170a60be which for me seems to
solve this.
Please submit a pull request—that is the best way to get your changes reviewed.
(If you are reluctant to do that, at least attach the patch to JIRA.)
Also, do you know
On 01/31/2013 06:59 PM, Jan Ruzicka wrote:
The issue is worked around by having the StarTeam jars only in local private
repository.
Another solution would be to create a sister jar-packaging Maven project (under a pom-packaging parent) containing stubs for all the classes/methods you use from
On 01/31/2013 01:10 PM, oliver gondža wrote:
Please fork.
https://github.com/olivergondza/cvs-mail-address-resolver-plugin
Done.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails f
Hi, I work with Scott on Rational Team Concert. I'm the RTC Build
component lead.
That's an interesting suggestion, Jesse. Currently we're compiling against
the RTC client libraries using Eclipse Tycho, with our plugin POM
configured to point to an Eclipse P2 repository containing the client
Thanks. I'll look at what Robert and ogondza proposed!
On Thursday, January 31, 2013 4:03:38 PM UTC+1, ogondza wrote:
>
>
> https://wiki.jenkins-ci.org/display/JENKINS/Basic+guide+to+Jelly+usage+in+Jenkinsis
> a good start
--
You received this message because you are subscribed to the Google Gr
16 matches
Mail list logo
