Re: Can't get access to the release button of the debian-package-builder-plugin in cloudbees
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 changes without having to check out the source code and perform manual mvn operations. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Need of access to upload new plugin.
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 plugin. This does require that the elOyente plugin will remain seperate. Mainly since this is an implementation of the pubsub-feature, and therefore no standard. Regarding the ownership, I don't mind taking up the responsibility. However if i can avoid it by merging it into the jabber-plugin I probably will. Regards, Dennis Jacobs. On Thursday, October 2, 2014 5:30:43 PM UTC+2, Dominik Bartholdi wrote: Hi Dennis, The el-boca plugin seems not to have a release - or at least I can’t find it… In terms of how these plugins interact/integrate, I’m probably the wrong guy to ask - I think Kutzi would be the right person, he is the maintainer of the Jabber plugin. About the maintaining of your plugin - yes the idea would be that you take over the ownership/maintenance of the plugin. You will then also be added as the component owner in JIRA to get tickets assigned by users if any problems come up. This is a very important part about the plugins and a reason why we take care and ask about the need for the new plugins - releasing a new plugin is easy but taking responsibility for it is something else. regards Domi On 02.10.2014, at 14:31, Dennis Jacobs jcbs...@gmail.com javascript: wrote: el-boca -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Need of access to upload new plugin.
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] https://wiki.jenkins-ci.org/display/JENKINS/elboca On 03.10.2014, at 09:52, Dennis Jacobs jcbs.d...@gmail.com wrote: 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 plugin. This does require that the elOyente plugin will remain seperate. Mainly since this is an implementation of the pubsub-feature, and therefore no standard. Regarding the ownership, I don't mind taking up the responsibility. However if i can avoid it by merging it into the jabber-plugin I probably will. Regards, Dennis Jacobs. On Thursday, October 2, 2014 5:30:43 PM UTC+2, Dominik Bartholdi wrote: Hi Dennis, The el-boca plugin seems not to have a release - or at least I can't find it... In terms of how these plugins interact/integrate, I'm probably the wrong guy to ask - I think Kutzi would be the right person, he is the maintainer of the Jabber plugin. About the maintaining of your plugin - yes the idea would be that you take over the ownership/maintenance of the plugin. You will then also be added as the component owner in JIRA to get tickets assigned by users if any problems come up. This is a very important part about the plugins and a reason why we take care and ask about the need for the new plugins - releasing a new plugin is easy but taking responsibility for it is something else. regards Domi On 02.10.2014, at 14:31, Dennis Jacobs jcbs...@gmail.com wrote: el-boca -- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Can't get access to the release button of the debian-package-builder-plugin in cloudbees
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 jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Gradle JPI Plugin Released
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 wrote: I released a new version of the Gradle JPI plugin: https://github.com/jenkinsci/gradle-jpi-plugin/blob/0.6.0/CHANGELOG.md Please give it a try and report any problems: https://issues.jenkins-ci.org/browse/JENKINS/component/16321 Daniel -- 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 mailto:jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi http://kohsuke.org/ -- 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. For more options, visit https://groups.google.com/d/optout.
repeatableProperty with Groovy, Loading overlay not dissapearing on config screen
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
edit the config a second time, the config screen shows the loading overlay
endlessly. If I scroll down, I can see the properties I saved earlier are
still there, but I can't edit anything.
My class looks like this:
public class RepeatableTest extends Builder {
private ListProp property = new ArrayListProp();
@DataBoundConstructor
public RepeatableTest(ListProp property) {
this.property = property;
}
public ListProp getProperty() {
return property;
}
@Override
public boolean perform(AbstractBuild build, Launcher launcher,
BuildListener listener) throws IOException {
listener.getLogger().println(property.get(0).name);
listener.getLogger().println(property.size());
return true;
}
@Override
public DescriptorImpl getDescriptor() {
return (DescriptorImpl)super.getDescriptor();
}
public static class Prop extends AbstractDescribableImplProp {
public String name;
public String getName(){
return name;
}
@DataBoundConstructor
public Prop(String name) {
this.name = name;
}
@Extension
public static class DescriptorImpl extends DescriptorProp {
@Override
public String getDisplayName() {
return ;
}
}
}
@Extension // This indicates to Jenkins that this is an implementation
of an extension point.
public static final class DescriptorImpl extends
BuildStepDescriptorBuilder {
private String phpLoc;
public DescriptorImpl() {
load();
}
public boolean isApplicable(Class? extends AbstractProject aClass)
{
// Indicates that this builder can be used with all kinds of
project types
return true;
}
public String getDisplayName() {
return Repeatable Test;
}
@Override
public boolean configure(StaplerRequest req, JSONObject formData)
throws FormException {
phpLoc = formData.getString(phpLoc);
save();
return super.configure(req,formData);
}
public String getPhpLoc() {
return phpLoc;
}
}
}
My config.groovy looks like this:
package uitestplugin.uitest.RepeatableTest;
import lib.JenkinsTagLib
import lib.FormTagLib
def f = namespace(lib.FormTagLib)
t=namespace(JenkinsTagLib.class)
f.form{
f.entry(title:Properties){
f.repeatableProperty(field:property)
}
}
and my prop/config.groovy looks like this:
package uitestplugin.uitest.RepeatableTest.Prop;
def f = namespace(lib.FormTagLib)
f.entry(title:Name, field:name) {
f.textbox()
}
The config.xml:
?xml version='1.0' encoding='UTF-8'?
project
actions/
description/description
keepDependenciesfalse/keepDependencies
properties/
scm class=hudson.scm.NullSCM/
canRoamtrue/canRoam
disabledfalse/disabled
blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding
blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding
triggers/
concurrentBuildfalse/concurrentBuild
builders
uitestplugin.uitest.RepeatableTest plugin=ui-test@1.0-SNAPSHOT
property
uitestplugin.uitest.RepeatableTest_-Prop
nameProp1/name
/uitestplugin.uitest.RepeatableTest_-Prop
uitestplugin.uitest.RepeatableTest_-Prop
nameProp2/name
/uitestplugin.uitest.RepeatableTest_-Prop
/property
/uitestplugin.uitest.RepeatableTest
/builders
publishers/
buildWrappers/
/project
Any ideas as to what could cause this? I based a lot of the code from the
ui-samples plugin
(https://wiki.jenkins-ci.org/display/JENKINS/UI+Samples+Plugin).
Also, using the web developer toolbar for Firefox, I can see that there is a
Javascript error on the page. The error is:
Timestamp: 10/3/2014 12:58:49 PM
Error: TypeError: prototypes is undefined
Source File:
http://localhost:8080/adjuncts/e58fb488/lib/form/hetero-list/hetero-list.js
Line: 16
And the code this relates to is(I've marked line 16 with a comment at the
end of the line):
// @include lib.form.dragdrop.dragdrop
// do the ones that extract innerHTML so that they can get their original
HTML before
// other behavior rules change them (like YUI buttons.)
Behaviour.specify(DIV.hetero-list-container, 'hetero-list', -100,
function(e) {
e=$(e);
if(isInsideRemovable(e))return;
// components for the add button
var menu = document.createElement(SELECT);
var btns = findElementsBySelector(e,INPUT.hetero-list-add),
btn = btns[btns.length-1]; // In case nested
Maven Task for Freestyle job Enhancements
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 input/output. But, 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 in maven -pl and -amd flags. Another enhancement that I would like to make is to make use of maven 3.1+ ability to append thread id to the log output so it's easier to separate log output for each module when building with multiple threads. Seems it would be able to do some console filtering based on this. So, from the experienced developers/contributors here, some guidance on best route to take and where to start would be greatly appreciated. I mean, should I start a new plugin that extends on Maven core task, could I just extend the core task, or is there other options? Thanks, Scott -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Maven Task for Freestyle job Enhancements
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 in maven -pl and -amd flags. Yes, this would be very useful. should I start a new plugin that extends on Maven core task, could I just extend the core task, or is there other options? The most conservative option for the incremental builds feature would be a new plugin that adds a separate build step which inspects your changelog, computes the right -pl/-amd flags (possibly empty, for example for an initial build), and defines this as a build variable. Then you could just pass this variable to the “goals and options” of the existing Maven build step. What I would really like to see [1] is for the existing Maven task to be moved to a plugin with its own lifecycle. This would make it easier and safer to add significant new features to it directly, especially if you need to do things like link against Maven core libraries to parse POMs. (You might not need to do that; for -pl you can pass directory names, so you would just need to pay attention to what subdirs contain a pom.xml.) I believe this is a pretty easy refactoring and could work on it if there is interest (CC @domi). [1] https://trello.com/c/ImfSSGkj/4-classic-maven-builder-into-maven-builder-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 email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Proper forum for questions about the Workflow plugin?
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 use it have been very unsuccessful - I can't even get a Git checkout to work. Is there a proper forum to ask questions about this plugin or seek help and advice? Thanks in advance, Jason Swager -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Proper forum for questions about the Workflow plugin?
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 (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 use it have been very unsuccessful - I can't even get a Git checkout to work. Is there a proper forum to ask questions about this plugin or seek help and advice? Thanks in advance, Jason Swager -- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Proper forum for questions about the Workflow plugin?
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 questions about this plugin or seek help and
advice?
Given its early condition, this list is fine.
--
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.
For more options, visit https://groups.google.com/d/optout.
Re: Can't get access to the release button of the debian-package-builder-plugin in cloudbees
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 Jenkins provides. Richard On 3/10/2014 8:34 PM, 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 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 changes without having to check out the source code and perform manual mvn operations. -- 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. For more options, visit https://groups.google.com/d/optout. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Can't get access to the release button of the debian-package-builder-plugin in cloudbees
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 you (the web user) are the authorized plugin maintainer, or at least that you have push permission to the repository. Of course we would like it to work as you describe. -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Maven Task for Freestyle job Enhancements
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 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. For more options, visit https://groups.google.com/d/optout.
