Have you looked at this plugin?
https://wiki.jenkins.io/display/JENKINS/Groovy+Events+Listener+Plugin
On Tuesday, June 18, 2019 at 6:15:02 AM UTC-7, selva vignesh wrote:
>
> Hi,
> I am developing one plugin for my internal purpose. I would like to add
> feature that will do some action at the en
> Am 02.07.2019 um 16:12 schrieb Jesse Glick :
>
> Read
>
> https://github.com/jenkinsci/js-libs
>
> and you will know more than I.
>
Yes, I tried to use that approach already without success. I got stuck
somewhere in the middle and nobody is here who can help on UI issues anymore
:-( Se
Yes, you should absolutely create a JIRA.
On Tuesday, July 2, 2019 at 8:46:42 AM UTC-7, Julien HENRY wrote:
>
> Hi Jesse,
>
> Here are 3 PRs to implement the proposed change. I did only Bitbucket so
> far, but if you confirm I'm on the good track, I will submit the same for
> GitHub (I have the
On Tuesday, July 2, 2019 at 12:27:26 PM UTC-4, Joe Hansche wrote:
>
> On Tue, Jul 2, 2019 at 6:49 AM Daniel Beck wrote:
>
>> > On 1. Jul 2019, at 20:50, 'Joe Hansche' via Jenkins Developers wrote:
>> >
>> > I opened a new thread here to request committer access to this plugin:
>> https://groups.g
On Tue, Jul 2, 2019 at 6:49 AM Daniel Beck wrote:
>
>
> > On 1. Jul 2019, at 20:50, 'Joe Hansche' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
> >
> > I opened a new thread here to request committer access to this plugin:
> https://groups.google.com/d/msg/jenkinsci-dev/5LUZT6
okay, thanks.
Done ;)
On Tue, Jul 2, 2019 at 3:36 PM Daniel Beck wrote:
>
>
> > On 2. Jul 2019, at 14:18, Martin Reinhardt
> wrote:
> >
> > sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not
> allowed to publish:
> >
> > [ERROR] Failed to execute goal
> org.apache.maven.plugins
This is a question best asked on the Jenkins users mailing list. The
Jenkins Developers mailing list is used for discussions of development
which extends and enhances Jenkins.
On Tue, Jul 2, 2019 at 10:01 AM chinna obireddy wrote:
> Problem: I have multiple lockable resources at various locatio
Problem: I have multiple lockable resources at various locations with
labels DEVICE_A and DEVICE_B along with Jenkins Slaves labels JS_COUTRYA
and JS_COUNTRYB in the respective countries.
Goal: Jenkins should choose the Jenkins SLave based on the Locked Resource
for example: If Jenkins Master
Hi Jesse,
Here are 3 PRs to implement the proposed change. I did only Bitbucket so
far, but if you confirm I'm on the good track, I will submit the same for
GitHub (I have the changes locally, just haven't tested end-to-end).
https://github.com/jenkinsci/scm-api-plugin/pull/71
https://github.com/j
> On 2. Jul 2019, at 10:31, Oliver Gondža wrote:
>
> JENKINS-57515 Major Jenkins 2.181
> AIX slave start error due to can not found
> /com/sun/jna/aix-ppc64/libjnidispatch.so
> https://issues.jenkins-ci.org/browse/JENKINS-57515
Do
On Tue, Jul 2, 2019 at 4:02 AM Ullrich Hafner wrote:
> In Jenkins core we currently bundle some very old libraries that do not play
> nicely with my packages above. Should core get also some detached plugins for
> the UI part?
I do not think that is possible, as some of them are used in core
fe
> On 2. Jul 2019, at 14:18, Martin Reinhardt wrote:
>
> sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not allowed to
> publish:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
> project log-parser: Failed to
BTW: On Github my account (hypery2k) can also not access the settings tab
of the repo
--
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+unsubs
sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not allowed
to publish:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on
project log-parser: Failed to deploy artifacts: Could not transfer artifact
org.jenkins-ci.plugins:
> On 1. Jul 2019, at 20:50, 'Joe Hansche' via Jenkins Developers
> wrote:
>
> I opened a new thread here to request committer access to this plugin:
> https://groups.google.com/d/msg/jenkinsci-dev/5LUZT6_kU7E/_MuM77kMBgAJ
> The maintainer, João Luís, responded in that thread with no objectio
I'm surprised to see that you seem to have decided to not release to Jenkins
update sites.[1][2]
Could you explain this?
Should we suspend distribution of previous log-parser plugin releases, as its
newest releases are no longer distributed via update sites?
1:
https://github.com/jenkinsci/lo
Hello everyone,
Latest LTS RC was made public and it is ready to be tested. Final
release is scheduled for 2019-07-17. There are five issues backported
and one that was postponed.
Postponed:
JENKINS-33843 Major 2.181
It's not possible to di
Added Leandro to Cc
On Tue, Jul 2, 2019 at 9:22 AM 'Robin Jansohn' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:
> Hi Oleg,
> thanks for the quick reply. I don't really know my way around Google
> mailing lists, how do I CC someone? I've forwarded your reply to the
> maintainer
Currently I’m using a lot of inline JS packages to provide a rich UI for the
warnings plugin. I want to use the same UI modules in another plugin so I am
wondering what would be the best way to provide these features.
Should I create a new API plugin for each of these dependencies?
E.g. I’m us
Hi Oleg,
thanks for the quick reply. I don't really know my way around Google
mailing lists, how do I CC someone? I've forwarded your reply to the
maintainer but I guess that is not what you meant?
Kind regards,
Robin
On Tuesday, 2 July 2019 08:38:43 UTC+2, Oleg Nenashev wrote:
>
> Hi Robin,
>
20 matches
Mail list logo
