erence the plugin with a different name, one
uses the postfix ‘-plugin’, but the new one does not.
Did I miss anything? Is this script discarded? What should be used instead?
Many Thanks
Domi
btw.
I have the same problem for all these plugins:
Some plugins failed to download! Not downloaded: gree
s of Bitbucket, I think the best would be if Atlassian
could step in.
Sorry for misusing this thread, but the topic just happened to raise this issue
for me again and I’m sure I’m not the only one feeling this way...
/Domi
> On 6 Nov 2019, at 05:24, Mark Waite wrote:
>
> We don
Nice!!! +1
> On 5 Nov 2019, at 00:29, Daniel Beck wrote:
>
> Thanks everyone for the suggestions addressing my concerns around minor
> changes. I think with a list of "additional contributors" we'd properly take
> care of them without bloating the changelog.
>
>> On 4. Nov 2019, at 23:35, Ba
quite complicated and
many maintainers will not do it and therefore not get any info about new
issues. So I think there should be some kind of easy way to at least inform the
official maintainer - maybe we can even create these filters automatically…
/Domi
> On 6 Sep 2019, at 01:37, Ullrich Haf
Hey James,
No, I I’m not using - its years since the last time I did...
So yes, please feel free to put it up for adoption.
/Domi
> On 16 Jul 2019, at 15:19, James Nord wrote:
>
> Hi Dominik,
>
> I have not used the m2release plugin for over 4 years now and have not b
. Local).
Is there any way I can do this? (Beside using groovy initscripts instead of the
CasC configuration files)
Thanks Domi
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emai
Thanks for the explanation Jesse! I created an issue for the
workflow-cps-plugin at https://issues.jenkins-ci.org/browse/JENKINS-54996
/Domi
> On 3 Dec 2018, at 15:25, Jesse Glick wrote:
>
> On Mon, Dec 3, 2018 at 7:49 AM Tony Noble wrote:
>> Would it not make sense to fo
}
branches('develop')
scriptPath(’install.groovy')
lightweight(true)
extensions {
localBranch()
cleanCheckout()
}
}
}
}
}
}
/Domi
> On 3 Dec 2018, at 13:38, Tomas Bjerre wrote:
>
>
Hi Tomas,
I do this too, 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.
not listen on the one I have
defined on the I have defined to load the "Pipeline from SCM”?
/Domi
> On 30 Nov 2018, at 17:59, Jesse Glick wrote:
>
> The simplest approach, starting from what you are doing now, would be
> to keep the build records and other state files
cloud foundry)
and I would say that running jenkins-x cost us more then our production
environment, because of the number of pods (yes, we don’t have a micro service
architecture)
/Domi
> On 30 Nov 2018, at 15:02, James Strachan wrote:
>
> we solved this in Jenkins X through the us
hope someone
else has a better idea on how to do this stuff properly.
Many thanks
Domi
--
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 jen
gt; authentication.
>
>
> On Mon, 19 Nov 2018, at 13:29, domi wrote:
> > Unfortunately this does not seem to work :(
> >
> > > On 16 Nov 2018, at 20:18, Jesse Glick > > <mailto:jgl...@cloudbees.com>> wrote:
> > >
> > > On Fri, Nov 16
Unfortunately this does not seem to work :(
> On 16 Nov 2018, at 20:18, Jesse Glick wrote:
>
> On Fri, Nov 16, 2018 at 8:12 AM domi wrote:
>> I really like the way I can validate my Jenkinsfile from within VS Code now:
>> https://jenkins.io/blog/2018/11/07/Validate-Jenkin
bucket [2]?
/Domi
[1] https://plugins.jenkins.io/github-oauth
<https://plugins.jenkins.io/github-oauth>
[2] https://plugins.jenkins.io/bitbucket-oauth
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe fr
Actually, there was a glitch in the update center job just until a couple of
minutes ago - Daniel just fixed it and it should be ok again now…
/Domi
> On 2 Nov 2018, at 08:32, Sameer wrote:
>
> Hi,
>
> I have released the next version of Nirmata-Plugin a couple of hours back a
):
https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/
What do I have to do to make Scripler appear on https://plugins.jenkins.io
again?
Regards
Domi
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To u
…in general: I trust you and I think that we only can move forward if we both
do so.
Regards Domi
> On 22 Jan 2018, at 22:19, Jae Gangemi wrote:
>
>
> would it be possible to get admin access to this repo? i'd like to set up
> travis to build pull requests but i don&
d.
…in general: I trust you and I think that we only can move forward if we both
do so.
Regards Domi
> On 23 Jan 2018, at 00:07, Daniel Beck wrote:
>
>
>> On 22. Jan 2018, at 22:19, Jae Gangemi wrote:
>>
>> would it be possible to get admin access to this repo? i
Hi Jae,
I’m more then happy if you want to help out with the repository-connector!
The reason why I did not answer to your first mail is, that my subscription to
the jerkins-dev googlegroup does not work anymore - I’m fighting with it since
months and have no idea why it does not work…
/Domi
/config-file-provider-plugin/commit/679be2283e7bf812745d6278edcfdf5533a0b4d9
<https://github.com/jenkinsci/config-file-provider-plugin/commit/679be2283e7bf812745d6278edcfdf5533a0b4d9>
Thanks!
/Domi
--
You received this message because you are subscribed to the Google Groups
"Jenkin
/plugins/config-file-provider/2.15.3/config-file-provider-2.15.3.hpi
<https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/config-file-provider/2.15.3/config-file-provider-2.15.3.hpi>
has any one any idea whats wrong?
thanks Domi
--
You received this message because you are subscribed
This is exactly what 'repository connector' does - it downloads artifacts from
a maven repository (which artifactory is just one of, an other could be nexus
or archiva)
/domi
> Am 30.03.2016 um 20:05 schrieb sara_jenkins :
>
> Hello Dominik,
>
> Thank you for your
ory
https://wiki.jenkins-ci.org/display/JENKINS/Repository+Connector+Plugin
—> use the parameters set by the previous plugin to download the artifact to
the workspace
/Domi
> On 28 Mar 2016, at 15:13, Oleg Nenashev wrote:
>
> I've added jenkinsci-users to Cc.
> Most likely
Really nice work!!!
/Domi
> On 24 Mar 2016, at 07:02, R. Tyler Croy wrote:
>
> I finished up the final work for migration from https://jenkins-ci.org to
> https://jenkins.io today. The final step of the switchover was to redirect
> non-mapped URLs from jenkins-ci.org ove
Thanks!
For now I go with this (I hate whitelisting...):
if(currentBuild.result != null && !"SUCCESS".equals(currentBuild.result)) {
...
}
> On 22 Mar 2016, at 09:42, Robert Sandell wrote:
>
> Pro tip, requires some "custom whitelisting":
>
> AbstractTestResultAction testResultA
ll -B -Dmaven.test.failure.ignore'
step([$class: 'JUnitResultArchiver', testResults:
'**/target/surefire-reports/*.xml’])
if(testFailure) {
// send notification
}
regards Domi
--
You received this message because you are subscribed to the Google Groups
"Jenkins Dev
You can define some restrictions on where a job is allowed to be executed with
this https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin
<https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin>
/Domi
> On 16 Mar 2016, at 16:12, Brian Stinson wrote:
>
&g
there are others on the marked too and they have the exact same concept
- so if thing like this get implemented, then it would be wise to have some
kind of abstraction.
my 2cents…
/Domi
> On 07 Mar 2016, at 13:01, Robert Sandell wrote:
>
> and IIRC GitLab calls an Organisation/Team for
being independent of
any vendor stuff. How about being able to switch from BB to GH or anywhere else
but not having to change anything in the build pipeline except the repo url?
/Domi
> Am 05.03.2016 um 10:54 schrieb Manuel Jesús Recena Soto :
>
> Hello Domi,
>
> GitHub uses: Orga
Would it be possible to generalize this GH stuff a bit more? From what I know,
most git hosting services have the notion of organizations,repos,PRs... eg.
GH,Bitbucket,gitlab?,gitblit?
I know GH is the most prominent, but ... yeah...
/Domi
> Am 05.03.2016 um 01:12 schrieb Daniel B
e too…
...oh and there is the Job DSL plugin, it has a totally different purpose, but
I think people will mix up this one into the game too
..confusing
/Domi
> On 18 Feb 2016, at 08:58, Michael Neale wrote:
>
> I mentioned some time back
> <https://groups.google.com/forum/#!se
Maybe worth to take a look at this:
https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over
/Domi
> On 12 Feb 2016, at 15:52, 'konrad' via Jenkins Developers
> wrote:
>
> I'm about to develop a plugin for Jenkins which should post some build
> artifacts of
ing should be fine (this was done for other plugins
too) - maybe add a comment to the docu about the original name.
Domi
> Am 04.02.2016 um 20:02 schrieb Tomas Bjerre :
>
> When responding to this, you should know that "Bitbucket" and "Bitbucket
> Server" are tw
not sure about this, 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",
I guess you already tried to prove the required calls in the script security
plugin?
https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin
/Domi
> On 04 Feb 2016, at 09:07, Michael Neale wrote:
>
> Inspired by Jesse's example
> <https://github.com/jenkins
+100
> Am 18.01.2016 um 10:35 schrieb arodrig...@cloudbees.com:
>
> Hi all,
>
> Please find below a proposal for a new parent POM for Jenkins Plugins.
>
> Motivation
>
> The main driver to propose a revision of the parent plugin POM is to decouple
> this artifact from the Jenkins Core:
> Simp
This might be an interesting one:
http://technologyconversations.com/2015/12/08/blue-green-deployment-to-docker-swarm-with-jenkins-workflow-plugin/
<http://technologyconversations.com/2015/12/08/blue-green-deployment-to-docker-swarm-with-jenkins-workflow-plugin/>
/Domi
> On 10 Dec 20
I think thats a good idea - and yes I think we should not tweet about such
plugins either.
Actually the @ejnkins_release should be cleaned up a bit to, it tweets every
release twice with just some minutes difference.
/Domi
> On 04 Dec 2015, at 10:24, Baptiste Mathus wrote:
>
>
Also the DigitalOcean plugin has no wiki page, but has successfully done a
release…
/Domi
> Begin forwarded message:
>
> From: Dominik Bartholdi
> Date: 3 December 2015 at 21:09:15 GMT+1
> To: d...@fortysix.ch
> Subject: Tweet by Jenkins releases on Twitter
>
>
there is also the repos for all kind of scripts:
https://github.com/jenkinsci/jenkins-scripts
<https://github.com/jenkinsci/jenkins-scripts>
/Domi
> On 24 Nov 2015, at 20:56, R. Tyler Croy wrote:
>
> (replies inline)
>
> On Tue, 24 Nov 2015, Jorge Castro wrote:
>
&g
+1 for merging and adding a feature flag in the global configuration to enable
one or/and the other functionality
/Domi
> On 22 Nov 2015, at 21:27, Daniel Beck wrote:
>
> Would it make sense to integrate this into the Slack Plugin? I mean, it's in
> the other direction, b
To be honest, the whole list of jenkins docker plugins feels like a zoo and
there is no way a normal user can keep up and make the right choice.
I think this work should be coordinated better and an uptodate comparison
should be kept at a central place.
..my 2cents
/Domi
> On 18 Nov 2015,
There are still tweets about plugin releases without a correct link to the
documentation, the following Tweet leads to the “Plugin Documentation Missing”
page
Domi
> Begin forwarded message:
>
> From: domi
> Date: 4 November 2015 at 08:41:09 GMT+1
> To: d...@fortysix.ch
>
or use the token-macro plugin - it also expands environment variables:
https://wiki.jenkins-ci.org/display/JENKINS/Token+Macro+Plugin
/Domi
> On 29 Oct 2015, at 11:57, Ullrich Hafner wrote:
>
> See
> https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Ut
please also consider good workflow integration and think about this can be
easily configured in a DSL style
Domi
> On 27 Oct 2015, at 23:58, Ikedam wrote:
>
> Hello.
>
> I'm developing a big change for copyartifact plugin, which I plan to release
> as copyartifact-2.
would love to have them defined in a central place.
Domi
> On 26 Oct 2015, at 23:53, Mark Waite wrote:
>
>
>
> On Mon, Oct 26, 2015 at 4:24 PM Nigel Magnay <mailto:nigel.mag...@gmail.com>> wrote:
> Both will be acceptable in styling. That lines are about logic that a
I don’t agree on that; backup, restore, history and adjusting fields (e.g. via
script) will not be as easy anymore…
Domi
> On 24 Oct 2015, at 15:40, Kanstantsin Shautsou
> wrote:
>
> -1, DBs are used everywhere and good API with good library should solve such
> problems.
&g
Yes, and that's also the reason why I think Jenkins should not get a database
backend for any configuration but only for build results and tracking
Domi
> On 24.10.2015, at 12:37, Christopher Orr wrote:
>
> It seems they're talking about both system configuration and job
&
Yes, I also think it's more about the system configuration then about projects.
Domi
> On 23.10.2015, at 23:39, Richard Bywater wrote:
>
> My impression was that they were talking about system configuration which
> presumably isn't touched in the areas you mention?
>
and by the way: it also tweet every release twice…
/Domi
> On 20 Oct 2015, at 15:07, Christopher Orr wrote:
>
> Hi all,
>
> I just saw this, which claims Log Parser 2.0 is a new plugin:
> https://twitter.com/jenkins_release/status/656450179571150849
>
> I know it
Do you have the credentials for the maven repo defined in your settings.xml as
described here?
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org
Domi
> On 19 Oct 2015, at 08:34, Joachim Kuhnert wrote:
>
> Hello everybody,
>
going now is the right
one, I sometimes would wish for more courage - I’m sure the v2.0 label will be
accepted by our users to take some extra effort when upgrading.
/Domi
> On 07 Oct 2015, at 21:57, Andrew Bayer wrote:
>
> So looking back over the thread - my concerns have pretty much
and specially in big organisations where things are to be setup
in a more controlled manner.
Also I could imagine that this wold also be very helpful in the scope of
testing jenkins itself, e.g. integration tests or even unit tests.
/Domi
> On 07 Oct 2015, at 22:05, Baptiste Mathus wr
These are some really good hints, they should be added to the workflow
documentation
Domi
> On 15.09.2015, at 20:28, Jesse Glick wrote:
>
>> On Tue, Sep 15, 2015 at 9:24 AM, jcsirot wrote:
>> I am currently working on the support of the workflow plugin for the ansible
>From an enduser perspective I think these two things provide similar
>information (one just more fine grained) and I would rather have both in the
>same plugin - the name DiskUsage Plugin just screens for this functionality
…just my 2 cents
/Domi
On 02 Sep 2015, at 16:31, Victor
would this not make more sense to be included in
https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin ?
/Domi
On 02 Sep 2015, at 11:58, Victor Martinez wrote:
> I've already created the wiki page:
> https://wiki.jenkins-ci.org/display/JENKINS/PercentageColumn+Plugin
yes, just follow the presented link
On 31 Aug 2015, at 13:38, Gilad Baruchian wrote:
> is it because I need to go to localhost:8080/jenkins/ ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and
also inform the users with
an info message right within Jenkins after he updated to a version where no
plugins are bundled anymore.
...just my 2cents...
/Domi
> Am 18.08.2015 um 23:03 schrieb Tom Fennelly :
>
>
>> On Tuesday, August 18, 2015 at 10:01:28 PM UTC+1, Tom Fennelly wrote
IMO, History has shown that maintenance will more likely not been maintained.
…sure, everyone wants his own plugin, but its not the best for the community
and the endusers too
my 2 cents...
On 24 Jul 2015, at 08:03, Jochen-A-Fuerbacher wrote:
> Does ist really reduce the risk of bad maintained
I think this should better be integrated with
https://wiki.jenkins-ci.org/display/JENKINS/testng-plugin
/Domi
On 22 Jul 2015, at 19:08, Carlos Gonzales wrote:
> Name: summarize-testng-reports
> Github: https://github.com/carledriss/summarize-testng-reports
> Github User: carledriss
+1 for an integration/merge
On 22 Jul 2015, at 10:19, Jochen-A-Fuerbacher wrote:
> The FailedJobDeactivator plugin was developed as part of a bachelor thesis.
> It not just detects wrong configured jobs, it also detects well configured
> jobs, which are orphaned.
> Example: A job gets nightly b
on different levels:
- global
- folder
- user
- job
Domi
On 17 Jul 2015, at 07:05, Daniel Beck wrote:
>
> On 17.07.2015, at 01:13, John Tatum wrote:
>
>> It seems like I had trouble finding good information about entry points.
>
> What do you mean by entry point
seems like a very specific use case - I would not write a plugin, but use the
“managed scripts plugin” to share the script within different jobs:
https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin
/Domi
On 13 Jul 2015, at 14:07, Vince Webb wrote:
> I want a plugin that will r
coming from a CB employee. I think many people will actually start to use these
icons just because they have seen it on any jenkins PR and think it a common
thing to do in this organisation.
/Domi
On 02 Jul 2015, at 22:32, Stephen Connolly
wrote:
> To give some background.
>
> I initial
The “create job advanced plugin” does something like this - you can check its
sources
https://wiki.jenkins-ci.org/display/JENKINS/Create+Job+Advanced+Plugin
/Domi
On 24 Jun 2015, at 16:28, Cletus D'Souza wrote:
> Hello All,
>
> Is it possible to (by configuration or programmati
I fully agree with Chris, we should remove the suffix, as the plugin names are
always shown in a context where its clear its nothing else.
/Domi
On 18 Jun 2015, at 16:26, Christopher Orr wrote:
> Yeah, I don't have too strong an opinion either way on removing "plugin".
>
+1 for Stephens suggestion.
in the long run this would hopefully even allow to finally remove deprecated
stuff…
/Domi
On 09 Jun 2015, at 11:28, Stephen Connolly
wrote:
> On 9 June 2015 at 09:37, Vincent Latombe wrote:
> You might get compilation errors because of plugin extracted fro
-1
I think its very strange to complain about the maintenance state of a plugin
and therefore fork the same and release it with the reason to mark it as
unstable…
this will simple just lead to an other unmaintained plugin with no additional
value for any user.
my 2c
Domi
On 01 Jun 2015, at
I also don’t like it - the left navigation is a really cluttered menu which I
think needs some more thinking too
/Domi
On 28 May 2015, at 10:40, Marius Gedminas wrote:
> On Thu, May 28, 2015 at 10:03:03AM +0200, oliver gondža wrote:
>> One of the things that bothers me about Jenkins
This is actually a subject a couple of user wanted to come up with, but at the
end I think all discarded the idea…
If still wanna do this, then you also have to think about scheduled jobs, these
are triggered by no user interaction, which JAAS subject would you use in these
cases?
/Domi
On 27
The I guess its about the same as:
https://wiki.jenkins-ci.org/display/JENKINS/Envfile+Plugin
/Domi
On 25 May 2015, at 21:07, Daniel Olausson wrote:
> Hi,
>
> GitHub:
> https://github.com/rednuht/retainenvironment
>
> Description can be found at:
> https://github.com/redn
(please make
sure to read the README on GH).
Actually I have not looked at scritlerweb for about a year and I’m quite
surprised it still has activity :)
regards Domi
On 19 May 2015, at 19:31, Scott Hebert wrote:
> Hi,
>
> Does anyone know who runs and maint
I think this is irritating for the users…
Also you should include “serena” in the name of the new plugin, as SDA is not a
well known acronym and users not familiar with serena should know by the name
whether the plugin is interesting for them or not.
/Domi
On 18 May 2015, at 21:33, PoisoN
Just to bring this up again… an other plugin without a correct
configuration/url
Jenkins releases (@jenkins_release)
12.05.15 23:57
S3 package parameter plugin 1.6 (new) dlvr.it/9nNJpt #jenkinsci
/Domi
On 01 May 2015, at 09:40, nicolas de loof wrote:
> My bad, this plugin is
://wiki.jenkins-ci.org/display/JENKINS/Instant+Messaging+Plugin
/Domi
On 29 Apr 2015, at 07:47, domi wrote:
> You need to update the in the plugins pom.xml and do a new release.
> /Domi
>
>
> On 29 Apr 2015, at 07:37, anitha vivedhan wrote:
>
>> Respected,
>>
You need to update the in the plugins pom.xml and do a new release.
/Domi
On 29 Apr 2015, at 07:37, anitha vivedhan wrote:
> Respected,
>
> I created a wiki page for Chat Room jenkins plugin.But that wiki page not
> listed in jenkins Update center .can You please suggest
does anyone know what the “Jenkins Chat Room Plugin” is?
There was a release announced (see tweet below), but the link to the wiki is
wrong (again one of these plugins!) and i can’t find a repository for it either…
/Domi
Begin forwarded message:
> From: domi
> Subject: Tweet von J
open source plugins can
> use the community infrastructure.
>
> If we want to host a "closed source plugins" wiki page to maintain links to
> non-OSS plugins then I think that would be a reasonable compromise.
>
> On 21 April 2015 at 13:39, domi wrote:
> how do we
something like: “for now its better to release it that way” - we hear this a
lot, but experience clearly shows: in most of the cases plugins will never be
merged again after they are separated
my 2cent
Domi
On 21 Apr 2015, at 14:19, Nguyen Anh Phu wrote:
> Hi Ullrich,
> A name of
how do we deal with closed source plugins which only have the documentation on
the jenkins wiki?
e.g.: https://wiki.jenkins-ci.org/display/JENKINS/CxSuite+Jenkins+Plugin
Domi
On 21 Apr 2015, at 12:10, Stephen Connolly
wrote:
> If you come across a plugin on the OSS update center that is
What makes this plugin different from
https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Test+Result+Plugin ?
/Domi
On 15 Apr 2015, at 09:58, Chaitanya Channella wrote:
> Bump
>
> On Wednesday, February 25, 2015 at 12:51:21 PM UTC+1, Chaitanya Channella
> wrote:
> Hi,
>
I agree with Daniel and Oleg, I also think it is misleading - maybe not to he
ones how know this tool - but to everyone else and I would say thats about 90%
..my 2cents
/Domi
On 25 Mar 2015, at 14:42, advinst caphyon wrote:
> Hi,
>
> Advanced Installer is a recognized name in the
information will be kept in sync.
/Domi
On 23 Mar 2015, at 09:33, Nathan McC wrote:
> Thanks. Updated the wiki with how to.
>
> Would it be possible to get this into the jenkins ci on github to make this
> official.
>
> I'm assuming once I have a repo and permiss
Thats about the info I would expect on the plugins wiki page…
Domi
On 23 Mar 2015, at 01:24, Nathan McC wrote:
> Add a blog post with some screenshots; http://blog.nemccarthy.me/?p=387
>
> On Sunday, March 22, 2015 at 9:08:59 PM UTC+11, Nathan McC wrote:
> Hey guys,
>
> I&
to an existing page
WDYT?
/Domi
[1] https://wiki.jenkins-ci.org/display/JENKINS/Credentials+Plugin
--
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
Nice!
I was thinking about implementing this one my self…
Things I would like to see:
- integration with the credentials plugin (no need to repeat the API key
allover)
- support for notifications of multiple applications in on build
/Domi
On 02 Mar 2015, at 21:02, Mads Mohr Christensen wrote
/main/java/org/jenkinsci/plugins/buildtriggerbadge/IconFinder.java#L67-L81
/Domi
On 02 Mar 2015, at 18:27, Peter Rader wrote:
> Hi,
>
> i build a internal plugin (extends hudson.tasks.Builder) that parses
> svn-commit-comments.
> How can i programatically findout if the buil
To be honest, the “Uno” in the name stopped my from looking closer into it -
because the name was just confusing…
…my 2cents
Domi
On 19 Feb 2015, at 08:05, Daniel Beck wrote:
>
> On 18.02.2015, at 22:01, Jesse Glick wrote:
>
>> I would pick a plugin named “Dynamic Paramet
There is even one more to the list:
https://wiki.jenkins-ci.org/display/JENKINS/Oki+Docki+Plugin
regards Domi
On 08 Jan 2015, at 10:17, James Nord wrote:
> Hi David,
>
> How is this different from the other docker plugins that already exist and
> would seem to achieve the s
Shared Library for CPS workflow
1.0
Workflow: Durable Task Step
1.0
Workflow: Job
1.0
Workflow: SCM Step
1.0
Workflow: Step API
1.0
Workflow: Execution Support
Is there any other location with some details about these?
regards Domi
--
You received this
There is also a plugin implementing a master-to-master communication contract -
maybe that could help you some how too…
https://github.com/jenkinsci/master-to-master-api-plugin
Domi
On 20.11.2014, at 21:14, oliver gondža wrote:
> On Thu, 20 Nov 2014 20:53:35 +0100, rakesh ranjan
>
ah soory, sure - you’r right!
…sorry for the noise...
On 10.11.2014, at 17:21, Daniel Beck wrote:
> This is just about the Jira component. Independent of plugin artifactId, repo
> name, wiki page name, or anything else.
>
> On 10.11.2014, at 16:58, domi wrote:
>
>&
+1 for the rename,
but would we not need some kind of aliasing in the core for to ease renaming.
after all, there are plugins which have dependencies to others in the code by
there name like this (or similar): updateCenter.getPlugin(“ghprb”)
Domi
On 10.11.2014, at 14:38, Daniel Beck wrote
This change might have caused issues with the plugin-info-macro on confluence.
Cannot Load Update Center
error 404 loading update-center.json
https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin
Domi
On 06.11.2014, at 07:19, Kohsuke Kawaguchi wrote:
> I've just
Feel free to sen PullRequests…
Domi
On 06.11.2014, at 12:29, martoe wrote:
> Thanks Dominik for your reply.
> I already found the pages you mentioned - but they do not display all the
> information I am looking for... I guess I will create my own statistics then.
>
> C
I see, so it makes sense then...
I'm currently online via mobile only, so maybe someone else could fork this
repo?
Domi
> Am 26.10.2014 um 04:35 schrieb Ali Raza :
>
> I see what you mean. Bumblebee is a product of our company that is why we
> need to add it in the plug
Hi Ali,
The question is just whether bumblebee should really be used in the name or
not, I don't think it adds any value to the user, as it does not point out the
purpose of the plugin. I would just call it hp-alm-plugin, that's more compact
and clear.
...just my 2cent...
Regards Dom
I don't know the HP-ALM suite, but is "bumblebee" adding any value for the user
to identify the purpose of the plugin?
If not, I would skip it.
Domi
> Am 24.10.2014 um 10:08 schrieb Sergey Oplavin :
>
> Hello,
>
> We would like to put our plugin into Jenk
done, welcome a board!
Domi
On 06.10.2014, at 07:49, Krishna Kishore wrote:
> Hi Domi,
>
> Thanks for creating the repository. I just signed up in the issue tracker
> and my userid in JIRA is "clkkishore", please created the required component.
>
> Thanks,
1 - 100 of 303 matches
Mail list logo
