But there is that fancy 'Release' button that performs mvn release on the
plugin. Why is it there if a plugin owner cant uae it?
I mean, the following workflow seema reasonable:
-- merge a PR
-- click tha button to release the plugin
Its generally useful to have possibility to release them
Hi Dominik,
What exactly do you mean with no release, are you refering to the
hpi-file?
And you can ignore the elboca-plugin since i'm planning to merge it either
today or monday.
It actually depends on what Kutzi thinks about the pubsub-feature and if it
can't be implemented into the jabber
Hey Dannis,
with no release I just mean, that I was not able to find a release in the
update center and also not a repository on GH (the only thing there is is a
Wiki page [1]) - but anyway as you say it seems not relevant.
So lets get some feedback from Kutzi :)
Gruss Domi
[1]
agreed - it would be really great if I could the release plugin to release
itself :-)
--
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
Yay! This is great!
Would you be interested in doing a guest post on
http://jenkins-ci.org/node to talk about this, plans for the future,
and/or perhaps how to gradle-fy your Jenkins plugin project?
I think a lot of people will be interested in this.
On 10/01/2014 01:05 PM, Daniel Spilker
I want to add repeatable properties to the Jenkins plugin I'm developing, and
created a test plugin to make make sure I was using them correctly. My
plugin seems to work fine, I can add as many properties as I want when I
originally edit the config, and it saves and builds. However, when I try to
Hi folks,
I've been using the maven-plugin job for Jenkins for a while now, but due
to various bugs other limitations (can't use Maven 3.2.x for example), I'm
moving to Maven task in freestyle jobs. Frankly, I like how the maven task
treats maven as a blackbox and just deals with the
On Fri, Oct 3, 2014 at 11:29 AM, Scott Wolk scott.w...@gmail.com wrote:
I like
the incremental builds feature of the maven-plugin and think this would be a
useful enhancement to the maven task. We're basically talking about checking
changlog to see which modules are impacted and including them
I've started trying to use (or maybe test is a better description) the
workflow-plugin that is documented
here: https://github.com/jenkinsci/workflow-plugin
It looks like the plugin would definitely address some of the issues that
we have with Jenkins. Unfortunately, my initial attempts to
Almost - the users list would be your best bet as that's most on topic and
possibly has more of an audience than the development list which is meant
for more Jenkins development discussions
Cheers
Richard
On 4/10/2014 9:17 AM, Jason Swager jswa...@alohaoi.com wrote:
I've started trying to use
On Fri, Oct 3, 2014 at 4:17 PM, Jason Swager jswa...@alohaoi.com wrote:
my initial attempts to use it have been very unsuccessful - I can't even get
a Git checkout to work.
Possibly you did not wrap in node {…}. Try running the Docker-based
demo to get started.
Is there a proper forum to ask
I'd argue though that as a maintainer you'd want to download the PR and
test it actually works and doesn't break things which would presumably mean
dragging it down and testing :)
Having said that it does seem silly to have a Jenkins instance that doesn't
give you some of the goodness that
On Fri, Oct 3, 2014 at 3:34 AM, Ivan Kalinin pupss...@gmail.com wrote:
But there is that fancy 'Release' button that performs mvn release on the
plugin. Why is it there if a plugin owner cant use it?
Because we have not figured out yet how to make it work, specifically
how to determine that
Thanks Jesse, I like your ideas. I'll work on a separate simple plugin that
figures out affected modules and populates a build variable that can be
plugged into maven task 'goals and options'.
I'd love to see maven classic builder be moved into its own plugin.
Scott
--
You received this
14 matches
Mail list logo
