Hi Robert,
Thanks for your reply. I was NOT able to figure out how to use BuildChooser
to get all configuration properties of a Job (not Build). I would greatly
appreciate if you can provide a sample code snippet.
Thanks
Quadir
On Monday, June 30, 2014 1:33:36 PM UTC+5:30, Robert Sandell
My apologies for the delay due to travel. 1.554.3 is released.
2014-06-25 10:47 GMT-07:00 oliver gondža ogon...@gmail.com:
RC testing is over. We can proceed with the release.
Thanks everyone who helped with manual testing.
--
oliver
--
You received this message because you are
Hi,
I have a describable/descriptor class that will be used at multiple
locations and i don't want to repeat the jelly code everywhere. But from i
can see on the jelly Taglib references page there are only options to
include a list of descriptors and not a single descriptor.
Is it possible?
1.565 works for me.
Workflow needs a really cutting-edge releases of Jenkins and we are still
planning on making more changes to the core for interop with BuildStep,
etc. So I don't think it should affect our LTS conversation for now.
2014-06-30 13:16 GMT-07:00 teilo teilo+goo...@teilo.net:
Hi,
About 10 days ago, I submitted a patch (with additional tests) for the
Build Pipeline Plugin in order to fix JENKINS-22146 (view faces an infinite
recursion under certain circumstances).
Successful pull request is here:
https://github.com/jenkinsci/build-pipeline-plugin/pull/41
May I get
Hi,
About 2 weeks ago, I submitted a trivial patch for the Display Upstream
Changes Plugin in order to fix JENKINS-23309 (changes from upstream jobs
residing in same CloudBees Folder didn't show).
Successful pull request is here:
If i use the dropdownDescriptorSelector everything works but I don't want
to have a dropdown list with only one element inside it, it looks terrible.
I can make it so that only the actual content of the descriptor's jelly
file is displayed by doing:
st:include
Hi,
I have created a chroot plugin, which uses pbuilder and mock to create
isolated build environments (which I found very useful for C and C++
projects with different dependencies) and I would like to host it on
jenkin-ci.org:
Plugin name: chroot-plugin
Github username: rmohr
Github
If there is a bug in your little library that is fixed and released, all
plugins using it will probably have to update the dependency and release a new
version of the plugin, until it appears in core.
If the library was a plugin all plugins would get the bugfix when the new icon
plugin version
It’s a bit hard to guess without a context to look at.
But try a div tag around the include with a name attribute of the contructor
parameter the object is going in to and/or provide the “it” attribute to the
include tag.
Robert Sandell
Software Tools Engineer - SW Environment and Product
how does this plugin compare to the existing gitlab plugin?
https://wiki.jenkins-ci.org/display/JENKINS/Gitlab+Hook+Plugin
/Domi
On 01.07.2014, at 07:44, Daniel Brooks daniel_bro...@dabsquared.com wrote:
Hi,
I have a new Gitlab Jenkins plugin currently on GitHub here:
Sure; thanks for the clarification of the pattern.
Paul
On 30 Jun 2014, at 11:26, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
please do not put `-plugin` in the artifactId.
The pattern is:
github repo name is: X-plugin
artifactId is: X
groupId is: org.jenkins-ci.plugins
I added you as a committer, welcome aboard!
Ulli
Am 01.07.2014 um 01:59 schrieb Tom Dunstan t...@tomd.cc:
Hi all
I've submitted a small patch for the Promoted Builds Plugin that makes it
useful when also using the Version Number Plugin. It has a unit test update
and has passed the
Interested in merging the changes by yourself?
Then please let us know your GitHub user name and the plugin names you would
like to contribute.
Am 01.07.2014 um 09:27 schrieb Regis Desgroppes regis.desgrop...@here.com:
Hi,
About 2 weeks ago, I submitted a trivial patch for the Display
Created https://github.com/jenkinsci/chroot-plugin
Welcome aboard!
Ulli
Am 01.07.2014 um 10:15 schrieb Roman Mohr rfenkhu...@googlemail.com:
Hi,
I have created a chroot plugin, which uses pbuilder and mock to create
isolated build environments (which I found very useful for C and C++
Maybe there's a misunderstanding ... I created a jenkins-icon module
(a simple java jar containing just the icon taglib). It doesn't depend
on anything in Jenkins - it just depends on Stapler. Jenkins core
depends on this module to get the icon tag. Plugins can also
independently depend on
I got help from elsewhere, the solution is to use f:property:
f:property field=jarFilePaths /
Now everything works as I want.
On Tuesday, 1 July 2014 10:47:13 UTC+2, Robert Sandell wrote:
It’s a bit hard to guess without a context to look at.
But try a div tag around the include with a name
But wouldn't that be the case anyway if we defined the base tag in the
normal way inside Jenkins core i.e. plugins using the tag would need to
wait for a core update to get fixes on that tag?
On 01/07/2014 09:19, Sandell, Robert wrote:
If there is a bug in your little library that is fixed
Ah ok. Yeah that will work
On Tuesday, 1 July 2014, Tom Fennelly tom.fenne...@gmail.com wrote:
Maybe there's a misunderstanding ... I created a jenkins-icon module (a
simple java jar containing just the icon taglib). It doesn't depend on
anything in Jenkins - it just depends on Stapler.
Hi Friends Colleagues!
For all of you who attended the JUC Berlin, thanks for a great day! For
those of you who weren't able to attend, here are some great news!
For the 3rd consecutive year Jenkins CI users and developers are invited to
come to Copenhagen, Denmark for the Jenkins CI Code Camp
Yes, that’s true, but a bit confusing. In the scenario where many plugins are
using the lib in a Jenkins core that doesn’t have it; the plugin that loads
first would dictate what version of the lib to use for the other plugins, even
though it is bundled in each plugin (unless they use
Thanks Robert. Good point!!
So maybe what we could do then is a cross between what I was referring
to, and shim plugin i.e. a jenkins-icons plugin that just depends on
the jenkins-icons module (in the same way as Jenkins core would depend
on it) and nothing more i.e. doesn't define any new
Hello guys,
Yesterday I had a problem with the EC2 Plugin, caused by a modification
made to use the proxy configuration that didn't checked for null config.
That pointed me to some ideas. First of all, I think the Jenkins.proxy
attribute shouldn't be null. Maybe when no proxy configuration
yep... only now you are back to doing a shim plugin See... I told you
there was no escape!
OTOH you now do not need to get the changes into core to release your module
On 1 July 2014 13:20, Tom Fennelly tom.fenne...@gmail.com wrote:
Thanks Robert. Good point!!
So maybe what we could
Hi!
My github account is mindjiver if it would help with getting access to maintain
the wonderful swarm plugin :)
On 24 Jun 2014 at 20:13:36, Peter Jönsson (peter.jons...@klarna.com) wrote:
Hello!
We here at Klarna [0] are big users of the Swarm plugin. It seems to have a
number of
Hi Ulli,
Sure!
My GitHub user name: rdesgroppes
Plugins I have to contribute for the time being: robot-plugin,
display-upstream-changes-plugin, build-pipeline-plugin .
MfG,
Regis
Le mardi 1 juillet 2014 12:05:12 UTC+2, Ullrich Hafner a écrit :
Interested in merging the changes by yourself?
Your commit rights are all set.
Welcome aboard!
Ulli
Am 01.07.2014 um 15:32 schrieb Peter Jönsson peter.jons...@klarna.com:
Hi!
My github account is mindjiver if it would help with getting access to
maintain the wonderful swarm plugin :)
On 24 Jun 2014 at 20:13:36, Peter Jönsson
Done.
Welcome aboard!
Ulli
Am 01.07.2014 um 15:44 schrieb Regis Desgroppes regis.desgrop...@here.com:
Hi Ulli,
Sure!
My GitHub user name: rdesgroppes
Plugins I have to contribute for the time being: robot-plugin,
display-upstream-changes-plugin, build-pipeline-plugin .
MfG,
Regis
Thanks! :)
// peter
On 1 Jul 2014 at 15:55:20, Ulli Hafner (ullrich.haf...@gmail.com) wrote:
Done.
Welcome aboard!
Ulli
Am 01.07.2014 um 15:44 schrieb Regis Desgroppes regis.desgrop...@here.com:
Hi Ulli,
Sure!
My GitHub user name: rdesgroppes
Plugins I have to contribute for the time
OK after talking to Stephen again we're heading back in the old
shim direction (he has beaten me into submission lol).
On 01/07/2014 13:53, Stephen Connolly wrote:
yep... only now you are back to doing a shim plugin See... I told
you there was no escape!
OTOH you now do not need to
Not at all... I just pointed out that if you go the way I originally
suggested you get a nice clean tag in core and all the mess in a shim
plugin that will go away eventually...
On 1 July 2014 16:18, Tom Fennelly tom.fenne...@gmail.com wrote:
OK after talking to Stephen again we're
You did that too ;) Ah I'm just kidding... thanks Stephen !!!
On 01/07/2014 16:29, Stephen Connolly wrote:
Not at all... I just pointed out that if you go the way I originally
suggested you get a nice clean tag in core and all the mess in a shim
plugin that will go away eventually...
On 1
This plugin emulates Jenkins to act like Gitlab CI to Gitlab. This allows
those using GitLab CE to use Jenkins normally faked as GitLab CI. This
plugin also doesn't use a single web hook which triggers a polling of the
repo. It is also coded in Java instead of Ruby.
On Tuesday, July 1, 2014
Thanks! It definitely has some things I would like to change, like having
to enter the merge info with a targetBranch and sourceBranch as a build
parameter. But i think it's good for a V1.0!
On Tuesday, July 1, 2014 9:44:04 AM UTC-7, slide wrote:
This looks great, I'll give it a shot when its
As discussed on IRC sometime back about writing a plugin that lets you add
new build environment variables or override a pre-defined or existing
variables at each build step.
I have a plugin implemented with these functionalities.
Basically you can add set of variables at a build step and these
I'm not a fan of env-inject, but isn't that what its build step basically does
when loading env vars from a .properties file?
On 01.07.2014, at 20:30, Vivek Pandey vivek.pan...@gmail.com wrote:
As discussed on IRC sometime back about writing a plugin that lets you add
new build environment
AFAICT, Env-inject plugin injects vars in to a build, it does not get across to
other build steps and it doesn't let you modify existing build vars etc.
Vivek
Sent from my iPhone
On Jul 1, 2014, at 12:02 PM, Daniel Beck m...@beckweb.net wrote:
I'm not a fan of env-inject, but isn't that
Hi,
I have problems editing the Confluence page
https://wiki.jenkins-ci.org/display/JENKINS/Delivery+Pipeline+Plugin, I
just get An error occured while trying to save the requested page.
This has worked for before. I have tried to clear browser cache, removed
all text in page and then try to
As Daniel, i think the env-inject plugin is a pain - but I don't see a clear
differentiation to this new one, do we really need an other or would it make
sense to combine the two?
Domi
Am 01.07.2014 um 21:25 schrieb Vivek Pandey vivek.pan...@gmail.com:
AFAICT, Env-inject plugin injects vars
This plugin is currently in my github repo
https://github.com/vivek/build-env-propagator.
vivek.
On Tue, Jul 1, 2014 at 12:25 PM, Vivek Pandey vivek.pan...@gmail.com
wrote:
AFAICT, Env-inject plugin injects vars in to a build, it does not get
across to other build steps and it doesn't let
I agree there is competing feature of variable injection in a build step,
other than that there is not much overlap. Maybe keep them separate to
start and merge/add functionalities in to either based on what makes sense
after actual usage?
On Tue, Jul 1, 2014 at 1:30 PM, domi d...@fortysix.ch
Just wanted to make you aware of the overlap. Having more plugins lets admins
pick and choose, so adding a new one for related but different functionality is
preferable from my POV.
On 01.07.2014, at 22:40, Vivek Pandey vivek.pan...@gmail.com wrote:
I agree there is competing feature of
I'm actually of the opposite view in that if we start having lots of
plugins with similar functionality, it actually makes things more
confusing. Especially if you need to have multiple plugins installed to get
the breadth of functionality you want and even more so if they use similar
labels on
Please view this confidential document I shared with you. Click Here
http://www.diamondandlife.com/private/locked to view the document.
*Geoff Bullen *
Centrum Systems
Level 8, 5 Elizabeth Street
Sydney
http://www.centrumsystems.com.au
--
You received this message because you are
Apartments simplicity or understood do it we. Song such eyes had and off.
Removed winding ask explain delight out few behaved lasting. Letters old
hastily ham sending not sex chamber because present. Oh is indeed twenty
entire figure. Occasional diminution announcing new now literature
45 matches
Mail list logo
