I am getting issues with this implementation:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/319
I have been debugging it and I can see that if I
1. Create a multibranch pipeline
2. Configure it with Git source and using
g...@github.com:tomasbjerre/gwt-issue-314.git
3. Scan t
anges). But suggestions
on that are very welcome.
måndag 15 april 2024 kl. 19:06:38 UTC+2 skrev jgl...@cloudbees.com:
> On Sat, Apr 13, 2024 at 1:13 AM Tomas Bjerre wrote:
>
>> - Is there a faster way
>> to Jenkins.getInstance().getAllItems(ParameterizedJob.class);
10771
>
> You could also investigate making your plugin extensible via an
> ExtensionPoint. So when others see the need for a different implementation,
> they could write their own plugin that just implements the ExtensionPoint
>
>
>
>
>
> *From:* jenkinsci-dev@googlegroup
It was reported here:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/issues/272
That the Generic Webhook Trigger Plugin is slow in large installations.
I "solved" that by adding a cache and having it configurable in the global
config here:
https://github.com/jenkinsci/generic-webhoo
I was unable to release my plugin:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/release.sh
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:3.1.1:deploy (default-deploy)
on project generic-webhook-trigger: Failed to deploy artifacts: C
You can probably do this with Generic Webhook Trigger:
https://plugins.jenkins.io/generic-webhook-trigger/
lördag 26 september 2020 kl. 18:33:25 UTC+2 skrev Léon Hagenaars-Keus:
> The thing this plugin does is provide a global 'build now' url for a json
> post, where the plugin looks at all
You can probably do it with Generic Webhook Trigger Plugin:
https://plugins.jenkins.io/generic-webhook-trigger/
A quick look at the docs:
https://developer.github.com/webhooks/event-payloads/
Tells me you should trigger when action has value rerequested.
There are examples of github usage here:
I have a couple of PR:s open on Lockable Resource Plugin:
* Adding skipIfLocked:
https://github.com/jenkinsci/lockable-resources-plugin/pull/184
* Returning a lock-object:
https://github.com/jenkinsci/lockable-resources-plugin/pull/185
I think this will help many users. But it does not look l
I prefer setting up a webhook from the Git service to Jenkins. And in
Jenkins I recognize type. Type of repo in combination with the webhook
content tells me what should be done. Zero code duplication. I wrote about
it here:
https://jenkins.io/blog/2019/12/14/generic-webhook-trigger-plugin/
, but this does not mean I don’t have to start the build at
> least once to make the webhooks work.
> /Domi
>
> On 3 Dec 2018, at 09:25, Tomas Bjerre wrote:
>
> Regarding configuration of webhooks with pipelines. This is why I always
> configure that with Job DSL. I configure
Regarding configuration of webhooks with pipelines. This is why I always
configure that with Job DSL. I configure the Jenkins job and the Git
service (usually some rest-call) in the same Groovy (Job DSL) script.
Den måndag 3 december 2018 kl. 09:15:05 UTC+1 skrev domi:
>
> Thanks Jesse, it proba
Thanks =)
Den fredag 31 augusti 2018 kl. 19:33:56 UTC+2 skrev Daniel Beck:
>
>
>
> > On 31. Aug 2018, at 19:32, Tomas Bjerre > wrote:
> >
> > curl -v
> http://localhost:8080/jenkins/generic-webhook-trigger/invoke?param1=value1¶m2=value2
>
> >
>
I have a class like this:.
...
@Extension
public class GenericWebHookRequestReceiver extends CrumbExclusion
implements UnprotectedRootAction {
private static final Logger LOGGER =
Logger.getLogger(GenericWebHookRequestReceiver.class.getName());
public HttpResponse doInvoke(final Stapl
Google has a brilliant tool for formatting java code:
https://github.com/google/google-java-format
I use it in all my projects. There are Gradle and Maven plugins:
https://github.com/jenkinsci/generic-webhook-trigger-plugin/blob/master/pom.xml#L148
If you want to force something to appear
You can read the JSON with this plugin:
https://wiki.jenkins.io/display/JENKINS/Generic+Webhook+Trigger+Plugin
Den onsdag 7 december 2016 kl. 14:15:12 UTC+1 skrev Oli Spicer:
>
> I work in a .NET environment with Team Foundation Server on premises for
> version control. I recently configured
The ones that I know of are:
https://wiki.jenkins-ci.org/display/JENKINS/Warnings+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+Bitbucket+Server+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Violation+Comments+to+GitHub+Plugin
And you may want to have a look at:
ht
t supported by the warnings plug-in to the
> warnings plug-in? Then the violations plug-in would be obsolete. Otherwise
> we basically have two plug-ins with the same UI but a different set of
> parsers. This will confuse users ...
>
> Am 13.11.2016 um 21:00 schrieb Tomas Bjer
o
> made you the lead of that plugin.
> https://issues.jenkins-ci.org/projects/JENKINS?selectedItem=
> com.atlassian.jira.jira-projects-plugin:components-
> page&contains=violations
>
> If you don't know how to release, please refer to the documentation
> <https://wiki.
eline and also 4 new formats.
Den söndag 13 november 2016 kl. 19:30:00 UTC+1 skrev Daniel Beck:
>
> Hi Tomas,
>
> It's unclear what you're asking for. You should already have commit access
> to this repo.
>
> Daniel
>
> > On 05.11.2016, at 09:12, Tomas
Is anyone looking into this?
--
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.
To view this discussion on the web
https://github.com/jenkinsci/violations-plugin
github id: tomasbjerre
jenkins id: tomasbjerre
--
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-de
solution published anywhere? While we do
encourage people to fix issues in existing plugins or add features to
existing plugins, we don't keep people from contributing. I'm saying this
as a member of the hosting team that reviews plugin submissions.
On Sat, Jun 18, 2016, 01:11 Tomas Bjerre
Have you seen Jucies? And this
issue: https://github.com/jucies/releases/issues/15 ?
I think it would be much better if competition among plugins were allowed.
Many times I've lost interest in fixing a problem when I've browsed the
code of plugins. Simply because there are too many bad decision
om grouping, etc.
> Instead of using above jsonp source I would rather use a REST/CORS server
> that provides thus data.
>
> salu2
>
> On Monday, May 2, 2016 at 3:08:42 PM UTC+2, Tomas Bjerre wrote:
>>
>> This is great!
>>
>> I tried to come up with a solutio
GMT+02:00 Daniel Beck :
>
> > On 02.05.2016, at 15:08, Tomas Bjerre wrote:
> >
> > Competition is a good thing. But competition is not allowed among
> Jenkins plugins. Its very frustrating when you dont want to contribute to
> an existing plugin. Perhaps because of the wa
This is great!
I tried to come up with a solution for this myself. The plugins are (in my
opinion) the only good thing about Jenkins. I would never use it if it was
not for the plugins. A solution like this is needed, so that plugin
developers can avoid situations like this:
https://groups.goo
You may want to have a look
at https://wiki.jenkins-ci.org/display/JENKINS/Git+Changelog+Plugin
Den tisdag 22 mars 2016 kl. 16:00:40 UTC+1 skrev Nickolay Rumyantsev:
>
> Hi,
>
> In my company we use Atlassian Stash (now Bitbucket Server) to serve our
> sources. We use pull requests to merge our
ilure Analyzer plugin - and
> https://github.com/switchgears/gerrit-review-buddy/blob/master/src/main/java/org/jenkinsci/plugins/gerritreviewbuddy/MessageProvider.java
>
>
> /James
>
> On Saturday, March 5, 2016 at 7:34:06 PM UTC, Daniel Beck wrote:
>>
>>
>> On 05.03.20
I'm getting an error when trying to use the new plugin parent 2.3.
The PR with the
change: https://github.com/jenkinsci/violation-comments-to-github-plugin/pull/1
And the log from that
build:
https://jenkins.ci.cloudbees.com/job/plugins/job/violation-comments-to-github-plugin/16/console
Apache
Plugin Name: Violation Comments To GitHub
My GitHub username: tomasbjerre
Existing
repo: https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin
Doc: https://github.com/tomasbjerre/violation-comments-to-github-jenkins-plugin
This plugin will find report files from static code a
is, there are already a couple of bitbucket plugins and
> all of these address the hosted service bitbucket.
> /Domi
>
>
> On 04 Feb 2016, at 16:38, Tomas Bjerre wrote:
>
> Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket
> Server", perha
Now that "Atlassian Stash" has changed name to "Atlassian Bitbucket
Server", perhaps some of the plugins
(https://github.com/jenkinsci?utf8=%E2%9C%93&query=stash) should also
change name. Or they can all be merged into 1 single plugin "Bitbucket
Server plugin". What do you think?
--
You recei
I am also developing plugins for Stash/Bitbucket Server and I must say that
their approach is much better. They have the Atlassian Marketplace where
plugins are published if they have a clear use case, the people at Atlassia
can successfully test that use case and it is documented properly.
Having
I dont want to maintain this plugin.
I tried to but in my opinion it should be re-written completely. A library for
parsing reports should be developed in a separate project and used in that new
plugin.
The code quality is poor and alot of time is needed to manage all the submitted
issues.
So
The JIRA-Filter-feature
> seems to be the difference.
>
> Regards
> Paul.
>
>
> On Tuesday, December 8, 2015 at 7:59:54 PM UTC+1, Tomas Bjerre wrote:
>>
>> I created a pull request here:
>> https://github.com/jenkinsci/git-changelog-plugin/pull/1
>>
>> L
I created a pull request here:
https://github.com/jenkinsci/git-changelog-plugin/pull/1
Lets wait and see what he thinks about merging the plugins.
Den fredag 20 november 2015 kl. 22:56:26 UTC+1 skrev Tomas Bjerre:
>
>
> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin
&
ense? It looks like
> you actually made the name more similar to the existing plugin.
>
> On 07.12.2015, at 07:33, Tomas Bjerre >
> wrote:
>
> > Any chance of getting this one forked soon? =)
> >
> > Den tisdag 1 december 2015 kl. 22:04:57 UTC+1 skrev Tomas Bjer
Any chance of getting this one forked soon? =)
Den tisdag 1 december 2015 kl. 22:04:57 UTC+1 skrev Tomas Bjerre:
>
> No I dont want to merge them.
> I changed the name:
> https://github.com/tomasbjerre/git-publisher-plugin
> And the artifactid: git-changelog-publisher
>
> -T
No I dont want to merge them.
I changed the name:
https://github.com/tomasbjerre/git-publisher-plugin
And the artifactid: git-changelog-publisher
-Tomas
Den tisdag 1 december 2015 kl. 21:39:00 UTC+1 skrev Christopher:
>
> Hi there,
>
> On 20/11/15 22:56, Tomas Bjerre wrote:
>
I have been waiting since 20 nov for my plugin to be forked:
https://github.com/tomasbjerre/git-releasenotes-plugin
I already have another plugin hosted and it looks like I can fork the new
plugin by myself. Perhaps I am suppose to do that?
-Tomas
--
You received this message because you are s
I do that in the expand method here:
https://github.com/jenkinsci/violation-comments-to-stash-plugin/blob/master/src/main/java/org/jenkinsci/plugins/jvcts/perform/JvctsPerformer.java#L122
Den tisdag 1 december 2015 kl. 06:22:04 UTC+1 skrev Thilina Madhusanka:
>
> Hi
>
> I need to get input from u
Anything happening here? =)
Den fredag 20 november 2015 kl. 22:56:26 UTC+1 skrev Tomas Bjerre:
>
>
> Repo: https://github.com/tomasbjerre/git-releasenotes-plugin
> Username: tomasbjerre
> JenkinsCI username: tomasbjerre
>
> I made a pre-release here with some screenshots:
Repo: https://github.com/tomasbjerre/git-releasenotes-plugin
Username: tomasbjerre
JenkinsCI username: tomasbjerre
I made a pre-release here with some screenshots:
https://github.com/tomasbjerre/git-releasenotes-plugin/releases
This plugin may look similar to Git Changelog Plugin, and I actually
s a Jenkins-bug? See the ip
variable is undefined here.
Den söndag 15 november 2015 kl. 21:51:35 UTC+1 skrev Tomas Bjerre:
>
> How to add list of configurable elements to a Jenkins plugin configuration
> page?
>
> I h
How to add list of configurable elements to a Jenkins plugin configuration
page?
I have a list of configurable items. It should be able to grow dynamically
and each item has 3 fields. There is initially one row, if that is
populated I want to add a new empty row.
I have 2 Java files to store t
u are
> confident enough
>
> An -alpha- version number will only show in the experimental update centre
> which needs to be added explicitly by adventurous users.
>
> On Monday, June 1, 2015, Tomas Bjerre wrote:
>
>> I totally agree! I just dont see it happen. Its been almos
gt; Richard
>
> On 10:30AM, Mon, 1/06/2015 Tomas Bjerre > wrote:
>
>> Plugin Name: Violations Reboot
>> My GitHub username: tomasbjerre
>> Existing repo: https://github.com/tomasbjerre/violations-reboot-plugin
>> Doc: https://github.com/tomasbjerre/violat
gst users.
>
> My 2 cents...
> Richard
>
> On 10:30AM, Mon, 1/06/2015 Tomas Bjerre > wrote:
>
>> Plugin Name: Violations Reboot
>> My GitHub username: tomasbjerre
>> Existing repo: https://github.com/tomasbjerre/violations-reboot-plugin
>> Doc: https://gith
Plugin Name: Violations Reboot
My GitHub username: tomasbjerre
Existing repo: https://github.com/tomasbjerre/violations-reboot-plugin
Doc: https://github.com/tomasbjerre/violations-reboot-plugin
This is very similar to Violations
(https://github.com/jenkinsci/violations-plugin). The Violations pl
I'm trying to update the wiki page of my plugin:
https://wiki.jenkins-ci.org/display/JENKINS/violation-comments-to-stash-plugin
The changes does not have any effect on the published page. If I edit the
page, I can see my changes. Same thing if I preview and after save. But
then when I browse to
Hi,
I’d like to host a new Jenkins plugin at Jenkins-ci. The plugin will enable
comments from static code analyzer reports to be used to comment Atlassian
Stash pull requests.
GitHub plugin name: jenkins-violation-comments-to-stash-plugin
Personal GitHub ID: tomasbjerre
Existing GitHub
reposi
51 matches
Mail list logo