Re: Need some advice on what to put and not to put on repo.jenkins-ci.org

[nicolas de loof]

We also discussed on getting jenkins repo synced to central, any progress
made on this topic ?


2013/8/1 Baptiste MATHUS 

>
> Le 1 août 2013 01:34, "Jesse Glick"  a écrit :
>
> >
> > On Wed, Jul 31, 2013 at 10:55 AM, Sandell, Robert
> >  wrote:
> > > Hosting it on central seems like a big pain compared to keeping it
> here.
> >
> > Get yourself an OSSRH account and publish it on Central; it is not
> > that much work, and it is better for your users.
>
> +1.
>
> --
> 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/groups/opt_out.
>
>
>

-- 
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/groups/opt_out.

Re: Autoinstaller plugin providing directory to the PATH

[Oleg Nenashev]

Hello,

Probably, you could use "Custom Tools 
Plugin". 
Via this plugin you can specify your own tools and installers. Version 0.3 
will add support of the variables and label-specific installation options.

If you need to specify path w/o any installation steps, you can use Extra 
Tool Installers 
Plugin

Best regards,
Oleg Nenashev

среда, 31 июля 2013 г., 2:07:18 UTC+4 пользователь Frédéric Camblor написал:
>
> Hi everyone,
>
> I'm lacking in Jenkins API knowledge to be able to provide a specific 
> directory to the PATH variable during a job execution only.
>
> My need : I'm enhancing the NodeJS plugin with NodeJS & npm 
> auto-installers.
> Once installed, node has a bin/ directory with potentially lots of 
> executables inside it (when a new npm package is installed, it might add 
> new executable to this bin/ folder).
>
> I'd like to provide some build step allowing to add NodeJS installation's 
> bin/ folder to the PATH variable, during a specific build execution.
> It could then make it possible to call some npm executables during shell 
> executed scripts (such as grunt, bower, jasmine and so on...)
>
> I tried appending launcher.env("PATH=/path/to/node/bin: value>"), but it didn't seemed to work (executable not found).
>
> If you have any input/doc to help me, I take it ! :-)
>
> Thanks in advance,
>
> Frédéric Camblor   
> 
> Bordeaux JUG  Leader
> Jenkins  community member & plugin commiter
>
> 

-- 
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/groups/opt_out.

Re: Need some advice on what to put and not to put on repo.jenkins-ci.org

[Baptiste MATHUS]

Le 1 août 2013 01:34, "Jesse Glick"  a écrit :
>
> On Wed, Jul 31, 2013 at 10:55 AM, Sandell, Robert
>  wrote:
> > Hosting it on central seems like a big pain compared to keeping it here.
>
> Get yourself an OSSRH account and publish it on Central; it is not
> that much work, and it is better for your users.

+1.

-- 
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/groups/opt_out.

Dynamically build drop down from XML

[cscott952]

Is it possible to build a drop down box by parsing a XML external to Jenkins?
I'd like to create a job that sets a build version for deployment based on a
drop down dynamically generated by the XML file.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Dynamically-build-drop-down-from-XML-tp4675416.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

-- 
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/groups/opt_out.

Re: Need some advice on what to put and not to put on repo.jenkins-ci.org

[Jesse Glick]

On Wed, Jul 31, 2013 at 10:55 AM, Sandell, Robert
 wrote:
> Hosting it on central seems like a big pain compared to keeping it here.

Get yourself an OSSRH account and publish it on Central; it is not
that much work, and it is better for your users.

-- 
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/groups/opt_out.

Re: Bytecode Compatibility Transformer

[Jesse Glick]

On Tue, Jul 30, 2013 at 7:38 PM, Kohsuke Kawaguchi
 wrote:
> @AdaptField
> protected volatile DescribableList<...> triggers = ...
>
> @AdaptField("DESCRIPTOR")
> @Restricted(NoExternalUse.class)
> public static DescriptorImpl _getDescriptor() {
>return ...;
> }

>From an API design perspective this seems like an overly specific
(inflexible) annotation; there are a bunch of kinds of signature
change that people commonly want to make for which bytecode
transformation of clients would be necessary, and this annotation
seems to cover just two. (Changing field type, and replacing final
field access with a method call.)

Can we instead define a general annotation to be applied to any member
whose signature has changed (or which has a nested element whose
signature has changed or been removed), with a reference to a
transformation? This would let people write modules offering fixes for
other changes like renamed methods, etc.:

@Transformed(by=MethodRenamed.class, info="toURL")
public URL toUrl() {…}

Here @Transformed would be the general marker which class loaders
could scan for (or which could even be indexed during compilation for
runtime efficiency); MethodRenamed would implement the specific
bytecode changes; and the option "toURL" (i.e. previous name) could be
passed to the transformer. Specifically:

@Retention(CLASS)
@interface Transformed {
  Class by();
  String[] info() default {};
}

Maybe too much work to justify the effort, but thought I would put it out there.

-- 
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/groups/opt_out.

Requesting review and/or commit access to rake-plugin

[Olivier Dagenais]

Hi,

Two weeks ago, I submitted pull request 
#13
 to fix JENKINS-18822  that 
is affecting us (and possibly a few more people - see comments added in 
June to JENKINS-7530 ).

After a week, I e-mailed who I thought were the maintainers (3 out of 4 
committers had their e-mail addresses listed) to ask for a code review.  I 
have received no response.

Can someone here review my pull request and/or grant me commit access to 
the rake-plugin repository?  My GitHub id is olivierdagenais.

Thanks!
- Oli

-- 
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/groups/opt_out.

Re: Autoinstaller plugin providing directory to the PATH

[Kohsuke Kawaguchi]

You override ToolInstallation.buildEnvVars()

Its Javadoc explains how to add it, and see JDK.buildEnvVars() for a 
concrete example.


On 07/30/2013 03:07 PM, Frédéric Camblor wrote:

Hi everyone,

I'm lacking in Jenkins API knowledge to be able to provide a specific directory
to the PATH variable during a job execution only.

My need : I'm enhancing the NodeJS plugin with NodeJS & npm auto-installers.
Once installed, node has a bin/ directory with potentially lots of executables
inside it (when a new npm package is installed, it might add new executable to
this bin/ folder).

I'd like to provide some build step allowing to add NodeJS installation's bin/
folder to the PATH variable, during a specific build execution.
It could then make it possible to call some npm executables during shell
executed scripts (such as grunt, bower, jasmine and so on...)

I tried appending launcher.env("PATH=/path/to/node/bin:"),
but it didn't seemed to work (executable not found).

If you have any input/doc to help me, I take it ! :-)

Thanks in advance,

Frédéric Camblor  

Bordeaux JUG  Leader
Jenkins  community member & plugin commiter

--
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/groups/opt_out.





--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
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/groups/opt_out.

Re: Bytecode Compatibility Transformer

[Kohsuke Kawaguchi]

On 07/30/2013 09:01 PM, Domi wrote:

In your example, how @AddaptField know to which type he should adapt the field? 
e.g. Why to List instead and not Collection?


The current type of the field is what it adapts to.

@AdaptField
protected volatile DescribableList<...> triggers = ...

The annotation is a sign that whoever refers to this 'triggers' field, 
regardless of what that byte code says as the type, gets adapted to the 
current type DescribableList.




Am 31.07.2013 um 01:38 schrieb Kohsuke Kawaguchi :



I wrote a small bytecode transformation engine so that we can further evolve 
code while maintaining the backward compatibility:

https://github.com/jenkinsci/bytecode-compatibility-transformer


This is a pair of an annotation and a bytecode transformer.

For example, I recently (somewhat inadvertently) changed 
AbstractProject.triggers from List to DescribableList, and this is causing 
various linkage errors when loading plugins. But with this library, I can add:

   @AdaptField
   protected volatile DescribableList<...> triggers = ...

... and the bytecode transformer can rewrite a reference to this field so that 
things will work (unless you try to set something like ArrayList to this field, 
which would fail with ClassCastException.)

Since Jenkins controls classloading of all plugins, installing such a 
transformer can be done in a core without changing plugins.


Another use for this is to get rid of a singleton, for example like in the 
FreeStyleProject class:

   @Restricted(NoExternalUse.class)
   @Extension(ordinal=1000)
   public static final DescriptorImpl DESCRIPTOR = new DescriptorImpl();

   public static final class DescriptorImpl extends AbstractProjectDescriptor {
  
   }

I could change this to:

   @Extension(ordinal=1000)
   public static final class DescriptorImpl extends AbstractProjectDescriptor {
  
   }

   @AdaptField("DESCRIPTOR")
   @Restricted(NoExternalUse.class)
   public static DescriptorImpl _getDescriptor() {
  return ...;
   }


For these benefits, I'd like to integrate this into the main line unless I hear 
some objections.

So far we've relied on bridge method injector [1] to do some code evolutions, 
and I think this will be another valuable tool to push that even further. And 
yes, this is not a tool for an inexperienced. Plugins would be able to use the 
same mechanism, but use this at your own risk.


I haven't thought about how to integrate this into remoting, but we control 
classloading there as well, so it should be doable.

Besides, this is useful enough just on the master, and there are many objects 
in the master that really can't be sent to slaves, like Jenkins, Job, and Run.



[1] http://bridge-method-injector.infradna.com/
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
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/groups/opt_out.







--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins

--
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/groups/opt_out.

Re: New plugin : Accelerated Build Now Plugin

[Anthony Dahanne]

indeed !
thanks Nicolas !
Anthony


On Wed, Jul 31, 2013 at 12:39 PM, nicolas de loof
wrote:

> you should have commit permission now
>
>
> 2013/7/31 Anthony Dahanne 
>
>> my github id is : anthonydahanne
>>
>> thanks !
>>
>>
>> On Wed, Jul 31, 2013 at 12:24 PM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>>
>>>
>>>
>>> 2013/7/31 Anthony Dahanne 
>>>
 Hello Baptiste, Nicolas

 @Nicolas : thank you for  the fork !
 Now, I am wondering if it was something I really needed or not...
 I have 2 questions actually :
 * I thought I needed to have my plugin repo forked to jenkins github
 account before I would able to publish it to Jenkins plugins, but I just
 pushed a new release of my plugin to maven.jenkins-ci.org, having
 origin still set as my original repo. (meaning the forked repo was not
 updated) --> Why do I need a forked repo of my plugin ? It just seems that
 it is extra work for me to maintain both of them ?

>>>
>>> don't maintain both, work directly on the jenkinsci one.
>>> benefit being hosted here is to get larger audience/contribution
>>>
>>>
>>>

 * I did git remote add jenkins 
 g...@github.com:jenkinsci/accelerated-build-now-plugin.git
 on my local repo and I could not push anything to it ... Are my rights ok ?
 or did you just add TerracottaOSS (the owner of the plugin repo) to the
 list of committers ?
 $ git push jenkins master
 ERROR: Permission to jenkinsci/accelerated-build-now-plugin.git denied
 to anthonydahanne.
 fatal: Could not read from remote repository.

 Please make sure you have the correct access rights
 and the repository exists.

>>>
>>> what's your github id ?
>>>
>>>

 @Baptiste
 Hum... that's a tempting idea, and , at the same time I'm not sure how
 to best integrate those 2 plugins together. We could at least provide new
 options to the PrioritySorter plugin to enable/disable the
 AcceleratedBuildNow feature.
 I'll think about it for sure !
 Thanks for the suggestion !

 Regards,
 Anthony




 On Wed, Jul 31, 2013 at 3:59 AM, nicolas de loof <
 nicolas.del...@gmail.com> wrote:

> forked as https://github.com/jenkinsci/accelerated-build-now-plugin
>
>
> 2013/7/31 Baptiste MATHUS 
>
>> Hi,
>>
>> Congrats for that plugin, I really like the idea.
>>
>> Did you consider merging it somehow with the Priority Sorter Plugin?
>> I feel this would be great to combine both the feature of your plugin
>> (starting a job anyhow) + use the priority to preferably choose the 
>> lowest
>> priority job/build to stop.
>>
>> In general, I think it's great if plugins become a little bit
>> bigger/different instead of creating brand new one. But not totally sure
>> this would also apply here.
>>
>> WDYT?
>>
>> Thanks
>>
>>
>>
>> 2013/7/30 Anthony Dahanne 
>>
>>> Hello,
>>> I would like the plugin Accelrated Build Now Plugin to be part of
>>> the Jenkins plugins.
>>>
>>> This plugin is hosted on github at:
>>> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>>>
>>> The wiki page is :
>>> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>>>
>>> My github username: anthonydahanne
>>>
>>> Thanks,
>>> Anthony
>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>>
>> --
>> 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/groups/opt_out.
>>
>>
>>
>
>  --
> 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/groups/opt_out.
>
>
>

  --
 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://gr

Re: Log message missing correct SVNExternalDetails.toString() information

[Daniel Beck]

This was fixed a month ago in the Subversion plugin:

https://github.com/jenkinsci/subversion-plugin/commit/5dce1f171869ade40d3558dc187a1cdf246f3d32

No release since, so you could use a snapshot build to fix it in your Jenkins.

On 31.07.2013, at 16:52, Hartmut Kühn  wrote:

> Hi all,
>  
> I don’t know, if this is the right place to send this.
>  
> I am missing correct SVNExternalsDetails.toString() information in my build 
> logs, when using SVN externals:
>  
> AUtools\SetupTools\lib\jdom\jdom-1.1.1.jar
> AUtools\SetupTools\lib\jdom\jdom-1.1.1.zip
> Hole 
> 'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@6156d8'
>  aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
> At revision 627
> AUtools\SetupTools\lib\jtds\jtds-1.2.5.jar
> Hole 
> 'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@11d1c59'
>  aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
> At revision 627
> AUtools\SetupTools\lib\ojdbc\ojdbc6.jar
> Hole 
> 'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@1e4d80b'
>  aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
> At revision 627
>  
> I am using Jenkins 1.518.
>  
> I was not sure which component to use in Jenkins JIRA. Maybe someone familiar 
> with this can post this into the right section.
>  
> Best regards
> 
> i.A. Hartmut Kühn
> Software Developer
> Product Development
>  
> OPTIMAL SYSTEMS GmbH
> - Unternehmenszentrale -
> Cicerostraße 26, 10709 Berlin
> Tel.: +49 30 895708-0
> E-Mail: ku...@optimal-systems.de
> Web: www.optimal-systems.de
>  
> 
> Alle Informationen zum Award finden Sie in unserem Newsroom.
>  
> Lesen Sie den aktuellen OPTIMAL SYSTEMS Newsletter – hier können Sie ihn 
> abonnieren:
> http://www.optimal-systems.de/newsletter
>  
> Folgen Sie uns auf twitter und werden Sie Facebook-Freund:
> Twitter: www.twitter.com/optimalsystems
> Facebook: www.facebook.com/optimalsystems
>  
> Sitz der Gesellschaft: Berlin 
> HRB 38 560 Amtsgericht Charlottenburg - USt-IdNr.: DE 136 722 551 
> Geschäftsführer: Karsten Renz
>  
>  
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

-- 
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/groups/opt_out.

Re: New plugin : Accelerated Build Now Plugin

[nicolas de loof]

you should have commit permission now


2013/7/31 Anthony Dahanne 

> my github id is : anthonydahanne
>
> thanks !
>
>
> On Wed, Jul 31, 2013 at 12:24 PM, nicolas de loof <
> nicolas.del...@gmail.com> wrote:
>
>>
>>
>>
>> 2013/7/31 Anthony Dahanne 
>>
>>> Hello Baptiste, Nicolas
>>>
>>> @Nicolas : thank you for  the fork !
>>> Now, I am wondering if it was something I really needed or not...
>>> I have 2 questions actually :
>>> * I thought I needed to have my plugin repo forked to jenkins github
>>> account before I would able to publish it to Jenkins plugins, but I just
>>> pushed a new release of my plugin to maven.jenkins-ci.org, having
>>> origin still set as my original repo. (meaning the forked repo was not
>>> updated) --> Why do I need a forked repo of my plugin ? It just seems that
>>> it is extra work for me to maintain both of them ?
>>>
>>
>> don't maintain both, work directly on the jenkinsci one.
>> benefit being hosted here is to get larger audience/contribution
>>
>>
>>
>>>
>>> * I did git remote add jenkins 
>>> g...@github.com:jenkinsci/accelerated-build-now-plugin.git
>>> on my local repo and I could not push anything to it ... Are my rights ok ?
>>> or did you just add TerracottaOSS (the owner of the plugin repo) to the
>>> list of committers ?
>>> $ git push jenkins master
>>> ERROR: Permission to jenkinsci/accelerated-build-now-plugin.git denied
>>> to anthonydahanne.
>>> fatal: Could not read from remote repository.
>>>
>>> Please make sure you have the correct access rights
>>> and the repository exists.
>>>
>>
>> what's your github id ?
>>
>>
>>>
>>> @Baptiste
>>> Hum... that's a tempting idea, and , at the same time I'm not sure how
>>> to best integrate those 2 plugins together. We could at least provide new
>>> options to the PrioritySorter plugin to enable/disable the
>>> AcceleratedBuildNow feature.
>>> I'll think about it for sure !
>>> Thanks for the suggestion !
>>>
>>> Regards,
>>> Anthony
>>>
>>>
>>>
>>>
>>> On Wed, Jul 31, 2013 at 3:59 AM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
 forked as https://github.com/jenkinsci/accelerated-build-now-plugin


 2013/7/31 Baptiste MATHUS 

> Hi,
>
> Congrats for that plugin, I really like the idea.
>
> Did you consider merging it somehow with the Priority Sorter Plugin?
> I feel this would be great to combine both the feature of your plugin
> (starting a job anyhow) + use the priority to preferably choose the lowest
> priority job/build to stop.
>
> In general, I think it's great if plugins become a little bit
> bigger/different instead of creating brand new one. But not totally sure
> this would also apply here.
>
> WDYT?
>
> Thanks
>
>
>
> 2013/7/30 Anthony Dahanne 
>
>> Hello,
>> I would like the plugin Accelrated Build Now Plugin to be part of the
>> Jenkins plugins.
>>
>> This plugin is hosted on github at:
>> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>>
>> The wiki page is :
>> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>>
>> My github username: anthonydahanne
>>
>> Thanks,
>> Anthony
>>
>>  --
>> 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/groups/opt_out.
>>
>>
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> --
> 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/groups/opt_out.
>
>
>

  --
 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/groups/opt_out.



>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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

Re: New plugin : Accelerated Build Now Plugin

[Anthony Dahanne]

my github id is : anthonydahanne

thanks !


On Wed, Jul 31, 2013 at 12:24 PM, nicolas de loof
wrote:

>
>
>
> 2013/7/31 Anthony Dahanne 
>
>> Hello Baptiste, Nicolas
>>
>> @Nicolas : thank you for  the fork !
>> Now, I am wondering if it was something I really needed or not...
>> I have 2 questions actually :
>> * I thought I needed to have my plugin repo forked to jenkins github
>> account before I would able to publish it to Jenkins plugins, but I just
>> pushed a new release of my plugin to maven.jenkins-ci.org, having origin
>> still set as my original repo. (meaning the forked repo was not updated)
>> --> Why do I need a forked repo of my plugin ? It just seems that it is
>> extra work for me to maintain both of them ?
>>
>
> don't maintain both, work directly on the jenkinsci one.
> benefit being hosted here is to get larger audience/contribution
>
>
>
>>
>> * I did git remote add jenkins 
>> g...@github.com:jenkinsci/accelerated-build-now-plugin.git
>> on my local repo and I could not push anything to it ... Are my rights ok ?
>> or did you just add TerracottaOSS (the owner of the plugin repo) to the
>> list of committers ?
>> $ git push jenkins master
>> ERROR: Permission to jenkinsci/accelerated-build-now-plugin.git denied to
>> anthonydahanne.
>> fatal: Could not read from remote repository.
>>
>> Please make sure you have the correct access rights
>> and the repository exists.
>>
>
> what's your github id ?
>
>
>>
>> @Baptiste
>> Hum... that's a tempting idea, and , at the same time I'm not sure how to
>> best integrate those 2 plugins together. We could at least provide new
>> options to the PrioritySorter plugin to enable/disable the
>> AcceleratedBuildNow feature.
>> I'll think about it for sure !
>> Thanks for the suggestion !
>>
>> Regards,
>> Anthony
>>
>>
>>
>>
>> On Wed, Jul 31, 2013 at 3:59 AM, nicolas de loof <
>> nicolas.del...@gmail.com> wrote:
>>
>>> forked as https://github.com/jenkinsci/accelerated-build-now-plugin
>>>
>>>
>>> 2013/7/31 Baptiste MATHUS 
>>>
 Hi,

 Congrats for that plugin, I really like the idea.

 Did you consider merging it somehow with the Priority Sorter Plugin?
 I feel this would be great to combine both the feature of your plugin
 (starting a job anyhow) + use the priority to preferably choose the lowest
 priority job/build to stop.

 In general, I think it's great if plugins become a little bit
 bigger/different instead of creating brand new one. But not totally sure
 this would also apply here.

 WDYT?

 Thanks



 2013/7/30 Anthony Dahanne 

> Hello,
> I would like the plugin Accelrated Build Now Plugin to be part of the
> Jenkins plugins.
>
> This plugin is hosted on github at:
> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>
> The wiki page is :
> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>
> My github username: anthonydahanne
>
> Thanks,
> Anthony
>
>  --
> 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/groups/opt_out.
>
>
>



 --
 Baptiste  MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !

 --
 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/groups/opt_out.



>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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/groups/opt_out.
>>
>>
>>
>
>  --
> 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/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop rec

Re: New plugin : Accelerated Build Now Plugin

[nicolas de loof]

2013/7/31 Anthony Dahanne 

> Hello Baptiste, Nicolas
>
> @Nicolas : thank you for  the fork !
> Now, I am wondering if it was something I really needed or not...
> I have 2 questions actually :
> * I thought I needed to have my plugin repo forked to jenkins github
> account before I would able to publish it to Jenkins plugins, but I just
> pushed a new release of my plugin to maven.jenkins-ci.org, having origin
> still set as my original repo. (meaning the forked repo was not updated)
> --> Why do I need a forked repo of my plugin ? It just seems that it is
> extra work for me to maintain both of them ?
>

don't maintain both, work directly on the jenkinsci one.
benefit being hosted here is to get larger audience/contribution



>
> * I did git remote add jenkins 
> g...@github.com:jenkinsci/accelerated-build-now-plugin.git
> on my local repo and I could not push anything to it ... Are my rights ok ?
> or did you just add TerracottaOSS (the owner of the plugin repo) to the
> list of committers ?
> $ git push jenkins master
> ERROR: Permission to jenkinsci/accelerated-build-now-plugin.git denied to
> anthonydahanne.
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>

what's your github id ?


>
> @Baptiste
> Hum... that's a tempting idea, and , at the same time I'm not sure how to
> best integrate those 2 plugins together. We could at least provide new
> options to the PrioritySorter plugin to enable/disable the
> AcceleratedBuildNow feature.
> I'll think about it for sure !
> Thanks for the suggestion !
>
> Regards,
> Anthony
>
>
>
>
> On Wed, Jul 31, 2013 at 3:59 AM, nicolas de loof  > wrote:
>
>> forked as https://github.com/jenkinsci/accelerated-build-now-plugin
>>
>>
>> 2013/7/31 Baptiste MATHUS 
>>
>>> Hi,
>>>
>>> Congrats for that plugin, I really like the idea.
>>>
>>> Did you consider merging it somehow with the Priority Sorter Plugin?
>>> I feel this would be great to combine both the feature of your plugin
>>> (starting a job anyhow) + use the priority to preferably choose the lowest
>>> priority job/build to stop.
>>>
>>> In general, I think it's great if plugins become a little bit
>>> bigger/different instead of creating brand new one. But not totally sure
>>> this would also apply here.
>>>
>>> WDYT?
>>>
>>> Thanks
>>>
>>>
>>>
>>> 2013/7/30 Anthony Dahanne 
>>>
 Hello,
 I would like the plugin Accelrated Build Now Plugin to be part of the
 Jenkins plugins.

 This plugin is hosted on github at:
 https://github.com/Terracotta-OSS/accelerated-build-now-plugin

 The wiki page is :
 https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin

 My github username: anthonydahanne

 Thanks,
 Anthony

  --
 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/groups/opt_out.



>>>
>>>
>>>
>>> --
>>> Baptiste  MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor !
>>>
>>> --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>  --
>> 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/groups/opt_out.
>>
>>
>>
>
>  --
> 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/groups/opt_out.
>
>
>

-- 
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/groups/opt_out.

Re: Disk usage plugin

[Vojtech Juranek]

Hi,

> I am not very satisfied how Disk usage plugin works, so I am going to
> rewrite it according to my needs and jiras which are created. 

I've assigned you recently created JENKINS-18962 [1]. Feel free to assign 
yourself any other feature request from disk-usage plugin component [2], e.g.
JENKINS-3433 or JENKINS-18555 are IMHO good candidates to be included in next 
generation of disk-usage plugin.

Cheers
Vojta

[1] https://issues.jenkins-ci.org/browse/JENKINS-18962
[2] 
https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+disk-usage

signature.asc
Description: This is a digitally signed message part.

Re: New plugin : Accelerated Build Now Plugin

[Anthony Dahanne]

Hello Baptiste, Nicolas

@Nicolas : thank you for  the fork !
Now, I am wondering if it was something I really needed or not...
I have 2 questions actually :
* I thought I needed to have my plugin repo forked to jenkins github
account before I would able to publish it to Jenkins plugins, but I just
pushed a new release of my plugin to maven.jenkins-ci.org, having origin
still set as my original repo. (meaning the forked repo was not updated)
--> Why do I need a forked repo of my plugin ? It just seems that it is
extra work for me to maintain both of them ?

* I did git remote add jenkins
g...@github.com:jenkinsci/accelerated-build-now-plugin.git
on my local repo and I could not push anything to it ... Are my rights ok ?
or did you just add TerracottaOSS (the owner of the plugin repo) to the
list of committers ?
$ git push jenkins master
ERROR: Permission to jenkinsci/accelerated-build-now-plugin.git denied to
anthonydahanne.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

@Baptiste
Hum... that's a tempting idea, and , at the same time I'm not sure how to
best integrate those 2 plugins together. We could at least provide new
options to the PrioritySorter plugin to enable/disable the
AcceleratedBuildNow feature.
I'll think about it for sure !
Thanks for the suggestion !

Regards,
Anthony




On Wed, Jul 31, 2013 at 3:59 AM, nicolas de loof
wrote:

> forked as https://github.com/jenkinsci/accelerated-build-now-plugin
>
>
> 2013/7/31 Baptiste MATHUS 
>
>> Hi,
>>
>> Congrats for that plugin, I really like the idea.
>>
>> Did you consider merging it somehow with the Priority Sorter Plugin?
>> I feel this would be great to combine both the feature of your plugin
>> (starting a job anyhow) + use the priority to preferably choose the lowest
>> priority job/build to stop.
>>
>> In general, I think it's great if plugins become a little bit
>> bigger/different instead of creating brand new one. But not totally sure
>> this would also apply here.
>>
>> WDYT?
>>
>> Thanks
>>
>>
>>
>> 2013/7/30 Anthony Dahanne 
>>
>>> Hello,
>>> I would like the plugin Accelrated Build Now Plugin to be part of the
>>> Jenkins plugins.
>>>
>>> This plugin is hosted on github at:
>>> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>>>
>>> The wiki page is :
>>> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>>>
>>> My github username: anthonydahanne
>>>
>>> Thanks,
>>> Anthony
>>>
>>>  --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>>
>> --
>> 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/groups/opt_out.
>>
>>
>>
>
>  --
> 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/groups/opt_out.
>
>
>

-- 
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/groups/opt_out.

Re: Need some advice on what to put and not to put on repo.jenkins-ci.org

[nicolas de loof]

no problem for me to keep it hosted on jenkins-ci.org


2013/7/31 Sandell, Robert 

> Hi,
>
> The Gerrit Trigger plugin is a multi module project, the plugin, a library
> for connecting and receiving stream events from Gerrit and one module that
> contains common build config stuff.
>
> I originally intended for the events module to be standalone and I’ve
> recently been asked to extract it into a complete separate project to
> remove any dependencies to Jenkins so that it can be easier used in other
> projects. It is already used by some other projects today but they need to
> suffer with all the dependencies that the parent pom inherits from the
> Jenkins plugin defaults.
>
> ** **
>
> So I intend to do it, since it would also cut down a bit of the complexity
> of the plugin itself by having separate release cycles for the two modules.
> 
>
> ** **
>
> But the question is where and how to host it?
>
> Is anyone opposed to me still hosting the released binaries in the Jenkins
> repo? Even though it technically has no dependency left to Jenkins, besides
> its biggest user is a Jenkins plugin J
>
> The reason I’m thinking of keeping it there is because that’s where the
> old versions of the module are, and convenience; I already have an account
> and I’m familiar with the repo. Hosting it on central seems like a big pain
> compared to keeping it here.
>
> On the other hand it is meant to be used by other unrelated projects and
> why should they add the Jenkins repo to their poms just for my little
> library?
>
> ** **
>
> Maybe a similar argument could be made for stapler that has up until
> recently always been hosted on the Jenkins repo even though it’s a
> standalone project, but I guess kk started to host it on central for that
> reason?
>
> ** **
>
> Same question about the git repo. I can create a new repo on my company´s
> GitHub account and take pull requests from there, or could I create a new
> repo in the Jenkins org for convenience’s sake?
>
> ** **
>
> As you might see I’m torn between doing the right thing and not needing to
> put too much work into it.
>
> ** **
>
> Looking forward to your opinions!
>
> ** **
>
> /B
>
> ** **
>
> ** **
>
> *Robert Sandell***
>
> Software Tools Engineer
>
> SW Environment and Product Configuration
>
> Development Environment
>
>  
>
> Sony Mobile Communications
>
> Tel: +46 (0)10 80 12721
>
> sonymobile.com
>
>  
>
> [image: SONY make.believe]
>
> ** **
>
> ** **
>
> --
> 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/groups/opt_out.
>
>
>

-- 
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/groups/opt_out.


<>

Need some advice on what to put and not to put on repo.jenkins-ci.org

[Sandell, Robert]

Hi,
The Gerrit Trigger plugin is a multi module project, the plugin, a library for 
connecting and receiving stream events from Gerrit and one module that contains 
common build config stuff.
I originally intended for the events module to be standalone and I've recently 
been asked to extract it into a complete separate project to remove any 
dependencies to Jenkins so that it can be easier used in other projects. It is 
already used by some other projects today but they need to suffer with all the 
dependencies that the parent pom inherits from the Jenkins plugin defaults.

So I intend to do it, since it would also cut down a bit of the complexity of 
the plugin itself by having separate release cycles for the two modules.

But the question is where and how to host it?
Is anyone opposed to me still hosting the released binaries in the Jenkins 
repo? Even though it technically has no dependency left to Jenkins, besides its 
biggest user is a Jenkins plugin :)
The reason I'm thinking of keeping it there is because that's where the old 
versions of the module are, and convenience; I already have an account and I'm 
familiar with the repo. Hosting it on central seems like a big pain compared to 
keeping it here.
On the other hand it is meant to be used by other unrelated projects and why 
should they add the Jenkins repo to their poms just for my little library?

Maybe a similar argument could be made for stapler that has up until recently 
always been hosted on the Jenkins repo even though it's a standalone project, 
but I guess kk started to host it on central for that reason?

Same question about the git repo. I can create a new repo on my company´s 
GitHub account and take pull requests from there, or could I create a new repo 
in the Jenkins org for convenience's sake?

As you might see I'm torn between doing the right thing and not needing to put 
too much work into it.

Looking forward to your opinions!

/B


Robert Sandell
Software Tools Engineer
SW Environment and Product Configuration
Development Environment

Sony Mobile Communications
Tel: +46 (0)10 80 12721
sonymobile.com

[cid:image001.jpg@01CE8E0C.4D38C180]


-- 
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/groups/opt_out.


<>

Log message missing correct SVNExternalDetails.toString() information

[Hartmut Kühn]

Hi all,

I don't know, if this is the right place to send this.

I am missing correct SVNExternalsDetails.toString() information in my build 
logs, when using SVN externals:

AUtools\SetupTools\lib\jdom\jdom-1.1.1.jar
AUtools\SetupTools\lib\jdom\jdom-1.1.1.zip
Hole 
'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@6156d8' 
aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
At revision 627
AUtools\SetupTools\lib\jtds\jtds-1.2.5.jar
Hole 
'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@11d1c59' 
aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
At revision 627
AUtools\SetupTools\lib\ojdbc\ojdbc6.jar
Hole 
'hudson.scm.subversion.SubversionUpdateEventHandler$SVNExternalDetails@1e4d80b' 
aus Revision 627 in Datei 'D:\Programme\Jenkins\jobs\...
At revision 627

I am using Jenkins 1.518.

I was not sure which component to use in Jenkins JIRA. Maybe someone familiar 
with this can post this into the right section.

Best regards

i.A. Hartmut Kühn
Software Developer
Product Development

OPTIMAL SYSTEMS GmbH
- Unternehmenszentrale -
Cicerostraße 26, 10709 Berlin
Tel.: +49 30 895708-0
E-Mail: ku...@optimal-systems.de
Web: www.optimal-systems.de

[Beschreibung: 
HDJ--mailsignatur]
Alle Informationen zum Award finden Sie in unserem 
Newsroom.

Lesen Sie den aktuellen OPTIMAL SYSTEMS Newsletter - hier können Sie ihn 
abonnieren:
http://www.optimal-systems.de/newsletter

Folgen Sie uns auf twitter und werden Sie Facebook-Freund:
Twitter: www.twitter.com/optimalsystems
Facebook: 
www.facebook.com/optimalsystems

Sitz der Gesellschaft: Berlin
HRB 38 560 Amtsgericht Charlottenburg - USt-IdNr.: DE 136 722 551
Geschäftsführer: Karsten Renz


-- 
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/groups/opt_out.


<>

Re: Resources in src/main/webapp is missing when plugin is deployed

[Jesse Glick]

On Wed, Jul 31, 2013 at 4:58 AM, Daniel Olausson  wrote:
> What do you mean with "Cf. Plugin.doDynamic"?

Just a reference to core sources in case you needed to debug further.

-- 
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/groups/opt_out.

RE: cucumber-reports-plugin

[James Nord (jnord)]

I've created a pull request[1] for the jenkinsci repo so that others can 
comment on this rather than just pulling the trigger.

/James

[1] https://github.com/jenkinsci/cucumber-reports-plugin/pull/1

From: Kingsley Hendrickse [mailto:kings...@masterthought.net]
Sent: 31 July 2013 13:44
To: James Nord (jnord)
Cc: jenkinsci-dev@googlegroups.com; Alex Thomson (alethoms)
Subject: Re: cucumber-reports-plugin

Hi

The maintained code is 
https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java and 
this is where all releases come from. I didn't create the jenkinsci repo or the 
wiki page - but I will update it to point at the masterthought repo.

The cucumber-reports plugin is in the update centre or you can download it from 
http://www.masterthought.net/section/cucumber-reporting

Thanks

--Kingsley

On 31 Jul 2013, at 15:24, "James Nord (jnord)" 
mailto:jn...@cisco.com>> wrote:


Hi Kingsley,

Just wondering why the cucumber reports plugin is being developed and released 
from the masterthought repo[1] rather than the Jenkins repo[2] - which is 
listed as the official[3] repo in the wiki?

Is there any plans to move back to the Jenkins repo - or should all the source 
in the Jenkins repo be replaced by a notice saying where the source is and the 
wiki be updated?

Regards
/James

[1] https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java
[2] https://github.com/jenkinsci/cucumber-reports-plugin
[3] https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Reports+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/groups/opt_out.

Re: cucumber-reports-plugin

[Kingsley Hendrickse]

 

Hi


The maintained code is 
https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java and 
this is where all releases come from. I didn't create the jenkinsci repo or 
the wiki page - and I don't have write access to the repo on jenkins - but 
the links should all go to the masterthought repo.

The cucumber-reports plugin is in the update centre or you can download it 
from http://www.masterthought.net/section/cucumber-reporting


Thanks


--Kingsley

On Wednesday, 31 July 2013 15:24:54 UTC+3, James Nord (jnord) wrote:
>
>  Hi Kingsley,
>
>  
>
> Just wondering why the cucumber reports plugin is being developed and 
> released from the masterthought repo[1] rather than the Jenkins repo[2] – 
> which is listed as the official[3] repo in the wiki?
>
>  
>
> Is there any plans to move back to the Jenkins repo – or should all the 
> source in the Jenkins repo be replaced by a notice saying where the source 
> is and the wiki be updated?
>
>  
>
> Regards
>
> /James
>
>  
>
> [1] 
> https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java
>
> [2] https://github.com/jenkinsci/cucumber-reports-plugin
>
> [3] https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Reports+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/groups/opt_out.

cucumber-reports-plugin

[James Nord (jnord)]

Hi Kingsley,

Just wondering why the cucumber reports plugin is being developed and released 
from the masterthought repo[1] rather than the Jenkins repo[2] - which is 
listed as the official[3] repo in the wiki?

Is there any plans to move back to the Jenkins repo - or should all the source 
in the Jenkins repo be replaced by a notice saying where the source is and the 
wiki be updated?

Regards
/James

[1] https://github.com/masterthought/jenkins-cucumber-jvm-reports-plugin-java
[2] https://github.com/jenkinsci/cucumber-reports-plugin
[3] https://wiki.jenkins-ci.org/display/JENKINS/Cucumber+Reports+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/groups/opt_out.

Re: Resources in src/main/webapp is missing when plugin is deployed

[Daniel Olausson]

Thanks, it worked.

What do you mean with "Cf. Plugin.doDynamic"?

On Tuesday, 30 July 2013 17:41:21 UTC+2, Jesse Glick wrote:
>
> On Tue, Jul 30, 2013 at 8:50 AM, Daniel Olausson 
> > 
> wrote: 
> >  
>
> Try: ${resURL}/plugin/myArtifactId/js/myJavascript.js 
>
> Cf. Plugin.doDynamic, and use 1.460 or later. 
>

-- 
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/groups/opt_out.

Re: New plugin : Accelerated Build Now Plugin

[nicolas de loof]

forked as https://github.com/jenkinsci/accelerated-build-now-plugin


2013/7/31 Baptiste MATHUS 

> Hi,
>
> Congrats for that plugin, I really like the idea.
>
> Did you consider merging it somehow with the Priority Sorter Plugin?
> I feel this would be great to combine both the feature of your plugin
> (starting a job anyhow) + use the priority to preferably choose the lowest
> priority job/build to stop.
>
> In general, I think it's great if plugins become a little bit
> bigger/different instead of creating brand new one. But not totally sure
> this would also apply here.
>
> WDYT?
>
> Thanks
>
>
>
> 2013/7/30 Anthony Dahanne 
>
>> Hello,
>> I would like the plugin Accelrated Build Now Plugin to be part of the
>> Jenkins plugins.
>>
>> This plugin is hosted on github at:
>> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>>
>> The wiki page is :
>> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>>
>> My github username: anthonydahanne
>>
>> Thanks,
>> Anthony
>>
>>  --
>> 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/groups/opt_out.
>>
>>
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
>
> --
> 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/groups/opt_out.
>
>
>

-- 
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/groups/opt_out.

Re: Disk usage plugin

[Baptiste MATHUS]

+1.

I don't know if you had that kind of thing in mind, but I think this would
be great to be able to dig into details recursively and maybe in some
period, but I'm also conscious this would need a lot of disk space to store
all those details. I can create the corresponding JIRA if you feel this
goes in the right direction.

Thanks


2013/7/30 Domi 

> Just One: rewrite the existing, instead of a new one.
> /Domi
>
> Am 30.07.2013 um 15:08 schrieb "lvoty...@redhat.com"  >:
>
> Hi,
> I am not very satisfied how Disk usage plugin works, so I am going to
> rewrite it according to my needs and jiras which are created. If you have
> some problems which is not described (or do not have assigned disk-usage
> component) in jiras or some suggestions please share it to help me do it
> this plugin more useful.
>
> Thanks for any contribution!
>
> Lucka
>
>
>
>  --
> 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/groups/opt_out.
>
>
>
>  --
> 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/groups/opt_out.
>
>
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
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/groups/opt_out.

Re: New plugin : Accelerated Build Now Plugin

[Baptiste MATHUS]

Hi,

Congrats for that plugin, I really like the idea.

Did you consider merging it somehow with the Priority Sorter Plugin?
I feel this would be great to combine both the feature of your plugin
(starting a job anyhow) + use the priority to preferably choose the lowest
priority job/build to stop.

In general, I think it's great if plugins become a little bit
bigger/different instead of creating brand new one. But not totally sure
this would also apply here.

WDYT?

Thanks



2013/7/30 Anthony Dahanne 

> Hello,
> I would like the plugin Accelrated Build Now Plugin to be part of the
> Jenkins plugins.
>
> This plugin is hosted on github at:
> https://github.com/Terracotta-OSS/accelerated-build-now-plugin
>
> The wiki page is :
> https://wiki.jenkins-ci.org/display/JENKINS/Accelerated+Build+Now+Plugin
>
> My github username: anthonydahanne
>
> Thanks,
> Anthony
>
>  --
> 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/groups/opt_out.
>
>
>



-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

-- 
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/groups/opt_out.