Auto Deploy Code into Dynamically Provisioned VM

[teilo]

It all depends on what is your target server is running, and what you want to 
transfer.


If the slave and target server are unix like then scp is your friend.  For 
windows things get a little more complex but if you can expose a share on the 
target you can just copy (windows to windows with unc paths) or for unix to 
windows use something like smbclient.

With windows the harder part may be getting your software to run depending what 
your deployment model is.

-- 
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: Further component renames/deletions in Jira

[teilo]

The is at least one (probably more) plugins where the source is not in 
jenkinsci github.

Should these plugins be removed from jira to avoid confusion?

Cucumber html reports - I'm looking at you...

-- 
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: Request for new "Jenkins" mark usage

[teilo]

IMHO xxx jenkins bar really looses the Jenkins and dilutes the mark.

'Xxx bar for Jenkins' I think would be cleaner and make it more separate from 
jenkins.  

My 2p.

-- 
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.

Slave To Master Access Control

[teilo]

Hi all,

Sorry if this is a duplicate but I never saw this posted.

The recent security announcement (CVE-2014-3665) has some implications that 
plugins need to adhere to to be able to run correctly in a locked down 
environment.

See 
https://wiki.jenkins-ci.org/display/JENKINS/Slave+To+Master+Access+Control#SlaveToMasterAccessControl-I%27maplugindeveloper.WhatshouldIdo%3F
 
for the implications and what needs to be done (or not done).

/James

-- 
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: Framework to make periodic method calls inside of Jenkins java sdk?

[teilo]

Hi Robert,

take a look at PeriodicWork

http://javadoc.jenkins-ci.org/hudson/model/PeriodicWork.html

Regards,

/James

On Tuesday, 4 November 2014 15:52:14 UTC, Robert Langenfeld wrote:
>
> I'm looking for a way to have Jenkins automatically call a method every 
> hour or so and have it be executed. I rather not create a new framework to 
> do this as it can become CPU intensive. Instead I'd rather have Jenkins 
> make the calls. Below is an example of what I'm talking about.
>
>
> public class MyClass extends JenkinsClass{
>
> @Override
>
> public void methodThatJenkinsCallsPeriodically(){
>
> myMethod()
>
>  }
>
>  
>
> public void myMethod(){
>
> //TODO Implementation
>
> } 
>
> }
>
>
> I'm assuming this class will have to get added to some kind of list of 
> triggers or something that jenkins will fire off periodically. So does 
> anyone have any good examples of this?
>

-- 
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: Plugin Logging - Showing in Build Console

[teilo]

Hi,

Loggers will be shared by the JVM - so even if Roberts suggestion worked (I 
see no reason why not) this will likeley cause a build console to contain 
spam from other builds.
If your slaves only have a single executor then you will probably get lucky 
- but anyone who uses more than 1 exectutor per slave may get into trouble.

/James



On Tuesday, 4 November 2014 13:45:25 UTC, Robert Sandell wrote:
>
> That depends a bit on what "log-bridge" your slf4j logger is using, I 
> believe the standard in Jenkins is java.util.logging.
>
> I don't know if this would work, but I would try something like this:
>
> Logger l = Logger.getLogger("name.of.your.pojos.logger");
> StreamHandler handler = new StreamHandler(listener.getLogger());
> l.addHandler(handler);
> try {
>   pojo.execute()
> } finally {
>   l.removeHandler(handler)
> }
>
>
> /B
>
> On Tue, Nov 4, 2014 at 12:17 PM, jwa > 
> wrote:
>
>> Good Morning All,
>>
>> I have written a Jenkins plugin which exposes a custom Builder, which may 
>> be added as a build step within jobs.
>>
>> The builder invokes some POJO code from another one of my projects. This 
>> project writes progress information out via slf4j. I have found that these 
>> log statements are being directed to the jenkins log file, which is cool, 
>> but it means that there is no visible progress statements placed in the 
>> console output for the job.
>>
>> Is there any advice on how best I can re-configure Jenkins' logger so it 
>> will take my logged statements via slf4j and direct them to both the 
>> console output as well as the Jenkins log file?
>>
>> Thanks,
>>
>> jwa.
>>
>> -- 
>> 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-de...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Robert Sandell
> *Software Engineer*
> *CloudBees Inc.*
>  

-- 
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: Release of claim plugin 2.4 not published

[teilo]

Hi Christian,

It looks like the tag that was made was a snapshot - not a release - so no 
release has been made.

This is most likley caused by either
1) user error
or
2) using a newish git client in a non english locale, and an old version of 
the maven-release-plugin.

Assuming you didn't give the release a "-SNAPSHOT" version then most likely 
you are falling into option 2 
(http://jira.codehaus.org/browse/MRELEASE-812).

in this case I would override the version of the release pluigin in your 
pom to 2.5 - that way you won't forget the workaround next time
  org.apache.maven.plugins maven-release-plugin  <
version>2.5   





On Tuesday, 4 November 2014 13:54:02 UTC, Christian wrote:
>
> I have already read Working around common issues but it did not help me.
>
> I do not have the build log left since I thought that everything wen't 
> fine and it got published to github as it used to.
>
> Is there some way to trigger the update center to retrieve the information 
> from github?
>
> On Mon, Nov 3, 2014 at 11:49 AM, Kanstantsin Shautsou <
> kanstan...@gmail.com > wrote:
>
>> Post build log and check  Working around common issues
>>
>> On Monday, November 3, 2014 1:34:09 PM UTC+3, Christian wrote:
>>>
>>> Hi,
>>>
>>> I made a release the same way as I always do for the claim-plugin and 
>>> the plugin got published to github 20 days ago:
>>> https://github.com/jenkinsci/claim-plugin/releases/tag/claim-2.4
>>>
>>> Although it does not show up in the Jenkins repo:
>>> http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/claim/
>>>
>>> Following point #5 in the Help my plugin do not show up in the update 
>>> center 
>>> 
>>>  I 
>>> now contact this list for further assistance.
>>>
>>> Thanks,
>>> Christian 
>>>
>>  -- 
>> 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-de...@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: 1.565.3 LTS RC testing started

[teilo]

The faulty plugin is bundled by default with the new lts - so I am saying the 
fix should be pulled from the plugin and then released and updated in the 580.1 
war.

-- 
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: 1.580.1 LTS RC Testing

[teilo]

Definite regression over 1.565.2 (introduced in 1.565.3) which is now 
reported by users and causes a loss in functionality.

https://issues.jenkins-ci.org/browse/JENKINS-25340.

I do not coniser the scenario that causes this to happen to be an edge case 
(it is normal for builds to be aborted).
Whereas having lots of build history and slow disks is an edge case (hence 
why it took from introducing lazy builds for it to be reported vs a short 
amount of time for that "fix" to be reported as causing a regression).

On Tuesday, 28 October 2014 11:00:02 UTC, ogondza wrote:
>
> Hi, LTS RC testing is on. 
>
> Bits are on usual location:   
> http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war 
> So does test plan:   
> https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.580.x+RC+Testing 
>
> Sorry for the late notice 
> -- 
> oliver 
>

-- 
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: 1.565.3 LTS RC testing started

[teilo]

Regression[1] has now been filed by an user - and this is a major loss in 
functionality.
This is present also in 1.580.1.

As such I think the fix should be pulled until a proper fix is written

/James

[1] https://issues.jenkins-ci.org/browse/JENKINS-25340

On Tuesday, 23 September 2014 08:03:49 UTC+1, James Nord (jnord) wrote:
>
> I've commented on 
> https://github.com/jenkinsci/jenkins/commit/8d8102036f4e52aada39db37c05025b9bb31516d
>  
> I'm pretty sure this introduces a regression but not tested when log 
> rotation is involved and all builds are unstable apart from a very old 
> one.) 
>
> /James 
>
> > -Original Message- 
> > From: jenkin...@googlegroups.com  [mailto:jenkinsci- 
>  
> > d...@googlegroups.com ] On Behalf Of oliver gondža 
> > Sent: 22 September 2014 17:25 
> > To: jenkin...@googlegroups.com  
> > Subject: 1.565.3 LTS RC testing started 
> > 
> > Hello everyone, 
> > 
> > Latest RC was made public and it is ready to be tested. 
> > 
> > We have 10 days to make sure that all the fixes[1] are in place and no 
> new 
> > regressions ware introduced. 
> > 
> > Report your findings in this thread or in the test plan wiki. 
> > 
> > Also, make sure to use linked war as this is the only build that 
> contains 
> > security fixes for 1.565.3. 
> > 
> > Download bits from: 
> > http://mirrors.jenkins-ci.org/war-stable-rc/latest/jenkins.war 
> > 
> > Check community maintained LTS test plan: 
> > https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.565.x+RC+Testing 
> > 
> > [1] 
> > https://issues.jenkins- 
> > ci.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+1017 
> > 2+AND+labels+%3D+%221.565.3-fixed%22 
> > 
> > Thanks for helping us 
> > -- 
> > oliver 
> > 
> > -- 
> > 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-de...@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.

build content in plugins - good security practices?

[teilo]

Hi all,

Cucumber has a way to add abitrary content into the test report.  It embeds 
base64 encoded content and a mime type.

The majority of the time this is used for images which could then be embedded 
into the report.

However it may not be images and could be HTML with links to evil.js

In some respects this is no different to browsing the workspace - however with 
the WS what you are going to get is obvious ahead of time.

At the moment all I can think of is dispokay anything that is image/* inline 
and everything else serve as application/octect-stream via a link to force non 
display in the browser.

Any other suggestions?

/james

-- 
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.

Updating the last stable build permalink?

[teilo]

Hi 


That sounds like the use case for build promotion[1].  Have you checked that to 
see if it fulfills your needs.

HTH 

/James 

[1]https://wiki.jenkins-ci.org/display/JENKINS/Promoted+Builds+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.

Re: Can't get access to the "release" button of the debian-package-builder-plugin in cloudbees

[teilo]

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: Proposal : Jenkins to require Java 8

[teilo]

Hmm - even my raspberry pi has jdk 8 support[1]

Doesn't the openJDK support AIX now[2]?  (not that I would run my jenkins 
cluster on openJDK[3] - but it does provide hope for those that need it)

This would just leave HP-UX out in the cold.

/James

[1] 
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-arm-downloads-2187472.html
[2] http://cr.openjdk.java.net/~simonis/ppc-aix-port/
[3] been bitten by OpenJDK 7s buggyness and it has taineted be - even though 8 
is far supperior in quatlity

-- 
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: gerrit-trigger plugin

[teilo]

Hi Robert,

I just noticed your sig change!

The an open pull request from Jesse on this linked to a commercial support 
issue :-)
Would be great to get this finally sorted.

/James

-- 
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: dynamically registering listeneners.

[teilo]

Scalability.

You could argue this is premature optimisation but run listener is on the 
master and called a he'll of slot, so if there is a way it would be better to 
use it
.

-- 
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.

Next LTS candidate chosen: 1.565

[teilo]

So no workflow support in an lts release for a while then :-(

Big shame..

-- 
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: jira cucumber-testresult ownership

[teilo]

Thanks Ulli

On Wednesday, 11 June 2014 09:05:28 UTC+1, Ullrich Hafner wrote:
>
> Done.
>
> Am 11.06.2014 um 09:59 schrieb teilo >:
>
> Hi all,
>
> could someone please set the default owner of issues on the 
> cucumber-testresult plugin to me (teilo) please.
>
> https://issues.jenkins-ci.org/browse/JENKINS/component/18324
>
> /James
>
> -- 
> 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-de...@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.

jira cucumber-testresult ownership

[teilo]

Hi all,

could someone please set the default owner of issues on the 
cucumber-testresult plugin to me (teilo) please.

https://issues.jenkins-ci.org/browse/JENKINS/component/18324

/James

-- 
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: Refreshing the Jenkins UI

[teilo]

Just so people are aware IE has no support for SSE[1].

IE is still commonly used in enterprises despite it many and continuous 
flaws.

So far Jenkins has been pretty browser agnostic.

/James

[1] http://status.modern.ie/serversenteventseventsource

On Thursday, 29 May 2014 08:26:38 UTC+1, Tom Fennelly wrote:
>
>  
> On 29/05/2014 02:57, Michael Neale wrote:
>  
>
>  On Thu, May 29, 2014 at 11:33 AM, Christopher Orr 
> 
> > wrote:
>
>>
>>  It may also be worth considering Server Sent Events — basically one-way 
>> "push" from the server, without all the handshaking and protocol upgrade 
>> fun of WebSockets.  Could be useful if clients are just listening for 
>> server updates, without sending anything (as is generally the case today).
>>
>> Last week I wrote a quick experimental plugin to stream log events as 
>> they happen via SSE to remote JavaScript clients for any running build; I 
>> was surprised how simple it was to build..
>>
>> (Though I just noticed that it has less support than WebSockets (thanks, 
>> Microsoft): http://caniuse.com/eventsource)
>>
>> Chris 
>>
>>
>>
>>   
>  +1 on SSE. I have a fair bit of experience with websockets on servers - 
> enough to know that almost no one gets their proxies right - and it is a 
> source of complaints. SSE seems to work better out of the box, 
> alternatively long polling/comet can also work (a given jenkins master 
> doesn't have to scale to 10s of thousands concurrent users, which is the 
> assumption for a lot of other web choices). 
>
>  Having said that, nearly halfway through 2014 websockets is probably not 
> a controversial choice and does open up a lot of other options. If someone 
> is accessing their jenkins via a proxy, ssl and careful configuration is 
> required to support http upgrade and not break websocket too.  
>   
> AFAIK... any proxy/gateway between the websocket client and server needs 
> to be pretty much websocket aware.  SSE would seem like a perfect fit for 
> Jenkins since the client is listening only (not sending back to the server 
> - could implement that on top anyway if needed).  As far as I know SSE is a 
> fancy long poll/comet style protocol and so would require the same 
> considerations re number of concurrent 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/d/optout.

Request : Delete version from release repository.

[teilo]

Deleting releases from maven repositories is considered bad practice, and only 
a few people have rights to do that.
Given that you would be better off just trying again with a new version 0.0.4-1 
or 0.0.5

/James

-- 
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: Requiring Java8 for acceptance-test?

[teilo]

I was only mildly concerned that you couldn't run the tests against Jenkins on 
AIX, so no issue exists then.

-- 
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: Requiring Java8 for acceptance-test?

[teilo]

Would this preclude running the tests on AIX.
Not that we do - but AIX users do pop their heads up on the list from time 
to time.

That said I am not involved - nor do I have AIX so just wanted to throw 
this out there.

On Wednesday, 19 March 2014 00:26:35 UTC, Kohsuke Kawaguchi wrote:
>
> Now that Java8 came out, what do people think about requiring Java8 for 
> https://github.com/jenkinsci/acceptance-test-harness/ ?
>
> I could really use closures in a number of places, and I think this is one 
> of the few places where this kind of cutting-edge dependencies are OK, 
> since you can launch Jenkins-under-test with arbitrary versions of JVM.
>
> -- 
> Kohsuke Kawaguchi 
>

-- 
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.

Publishing cucumber test results

[teilo]

I was actually thinking of having am extension point that was called after the 
test parsing so you can interact with the Jenkins test model and then push to 
your chosen external service.

Probably as that was how I was going to implement pushing results to our 
internal system and there are things you need to do to parse the files (make 
sure they are from this run not relics, scan workspace etc..).  That said that 
would only work for this plugging and then we will at some point want to push 
other test results as well, so it's just another publisher with a lower ordinal.

-- 
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: Where are Jenkins users?

[teilo]

There's something very wrong with those statistics.

I know there are huge amounts of installations in the Maldives :-) 

-- 
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.

Running multiple executors - considerations and pitfalls?

[teilo]

Can you not virtualize your slaves so you can then run multiple slaves on the 
same hardware?


Otherwise you are always at the behest of the jobs running and then need to 
hook everything up to something like the port reservation 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: Beta release of Gerrit Trigger plugin 2.11.0

[teilo]

sorry trigger happy that should read "from an earlier post 2.10.1 release 
(aka 2.10.2-snapshot)"

On Wednesday, 11 December 2013 16:43:32 UTC, teilo wrote:
>
> Not sure this is still the case (as its from an early post but the plugins 
> assumptions about project types appears incorrect and results in the 
> following error
>
> javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
> file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
>   Can't convert 
> com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4 
> to class hudson.model.AbstractProject
>
>
> I don't think this is a regression in the Cloudbees templates (although they 
> may have been upgraded at similar times).
>
>
>
> On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
>>
>> Did some fixes in this area and released 2.11-beta-2
>>
>>  
>>
>>  
>>
>> *Robert Sandell*
>>
>> Software Tools Engineer - SW Environment and Product Configuration
>>
>> Sony Mobile Communications
>>
>>  
>>
>> *From:* jenkin...@googlegroups.com [mailto:jenkin...@googlegroups.com] *On 
>> Behalf Of *Sandell, Robert
>> *Sent:* den 9 december 2013 16:48
>> *To:* jenkin...@googlegroups.com
>> *Subject:* RE: Beta release of Gerrit Trigger plugin 2.11.0
>>
>>  
>>
>> Ah,
>>
>> It’s because the server config is retrieved via the serverName field of 
>> the trigger and not from the provider of the event. I noticed some other 
>> places where I’ve missed that particular issue.
>>
>>  
>>
>> I’ll start a 2.11-beta branch to work on these.
>>
>>  
>>
>>  
>>
>> *Robert Sandell*
>>
>> Software Tools Engineer - SW Environment and Product Configuration
>>
>> Sony Mobile Communications
>>
>>  
>>
>> *From:* jenkin...@googlegroups.com [mailto:jen...@googlegroups.com] *On 
>> Behalf Of *Jyrki Puttonen
>> *Sent:* den 7 december 2013 18:00
>> *To:* jenkin...@googlegroups.com
>> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>>
>>  
>>
>> I found out one problem, using "Any Server" prevents Jenkins from 
>> reporting result to Gerrit. This happens from retriggering, pushing and 
>> from the search and trigger -page. Log has following line in every case:
>>
>>  
>>
>> Caused by: java.lang.NullPointerException
>>
>>   at 
>> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)
>>
>>  
>>
>> At that line, there's 
>>
>>  
>>
>>   
>>   
>> PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()
>>
>>  
>>
>> I would guess that getServer return null when "Any Server" is selected. 
>> I'm not sure what should be done when the returned server is null, so I 
>> couldn't fix this myself :)
>>
>>  
>>
>>  
>>
>>  
>>
>> On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen  wrote:
>>
>> Hi,
>>
>>  
>>
>> I just installed the beta version, and had few problems.
>>
>>  
>>
>> 1. Gerrit configuration was lost, and I had to add a new server.
>>
>>  
>>
>> 2. Manual triggering from search didn't work. After following steps and 
>> testing after everyone it started to work
>>
>> - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
>>
>> - Changed server from Any Server to specific one
>>
>> - Touched every field in Project configuration (pattern, branch)
>>
>> Then it started to work. After it started to work, I changed server back 
>> to Any Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to 
>> be working.
>>
>>  
>>
>> Pushing to gerrit seems to be working, at least after I did those 
>> previous steps.
>>
>>  
>>
>> I'll keep the beta version running and report if there's other problems.
>>
>>  
>>
>> On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert <
>> robert@sonymobile.com> wrote:
>>
>> The notify parameter is not something you can set (yet), there is 
>> probably still much that can be done to enhance the usage of the REST API.
>>
>> The only thing that is used from the command

Re: Beta release of Gerrit Trigger plugin 2.11.0

[teilo]

Not sure this is still the case (as its from an early post but the plugins 
assumptions about project types appears incorrect and results in the 
following error

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: 
file:/opt/jenkins/data/plugins/gerrit-trigger/WEB-INF/classes/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly:6:68:
  Can't convert 
com.cloudbees.hudson.plugins.modeling.controls.DescriptorListControl@3e0dfca4 
to class hudson.model.AbstractProject


I don't think this is a regression in the Cloudbees templates (although they 
may have been upgraded at similar times).



On Monday, 9 December 2013 18:45:07 UTC, Robert Sandell wrote:
>
> Did some fixes in this area and released 2.11-beta-2
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com  [mailto:
> jenkin...@googlegroups.com ] *On Behalf Of *Sandell, Robert
> *Sent:* den 9 december 2013 16:48
> *To:* jenkin...@googlegroups.com 
> *Subject:* RE: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> Ah,
>
> It’s because the server config is retrieved via the serverName field of 
> the trigger and not from the provider of the event. I noticed some other 
> places where I’ve missed that particular issue.
>
>  
>
> I’ll start a 2.11-beta branch to work on these.
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com  [
> mailto:jen...@googlegroups.com ] *On Behalf Of *Jyrki 
> Puttonen
> *Sent:* den 7 december 2013 18:00
> *To:* jenkin...@googlegroups.com 
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> I found out one problem, using "Any Server" prevents Jenkins from 
> reporting result to Gerrit. This happens from retriggering, pushing and 
> from the search and trigger -page. Log has following line in every case:
>
>  
>
> Caused by: java.lang.NullPointerException
>
>   at 
> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTrigger.schedule(GerritTrigger.java:531)
>
>  
>
> At that line, there's 
>
>  
>
>   
>   
> PluginImpl.getInstance().getServer(serverName).getConfig().isGerritBuildCurrentPatchesOnly()
>
>  
>
> I would guess that getServer return null when "Any Server" is selected. 
> I'm not sure what should be done when the returned server is null, so I 
> couldn't fix this myself :)
>
>  
>
>  
>
>  
>
> On Sat, Dec 7, 2013 at 3:55 PM, Jyrki Puttonen 
> > 
> wrote:
>
> Hi,
>
>  
>
> I just installed the beta version, and had few problems.
>
>  
>
> 1. Gerrit configuration was lost, and I had to add a new server.
>
>  
>
> 2. Manual triggering from search didn't work. After following steps and 
> testing after everyone it started to work
>
> - I had $GERRIT_REFSPEC as Branch Specifier, changed to $GERRIT_BRANCH
>
> - Changed server from Any Server to specific one
>
> - Touched every field in Project configuration (pattern, branch)
>
> Then it started to work. After it started to work, I changed server back 
> to Any Server and Branch Specifier back to $GERRIT_REFSPEC and it seems to 
> be working.
>
>  
>
> Pushing to gerrit seems to be working, at least after I did those previous 
> steps.
>
>  
>
> I'll keep the beta version running and report if there's other problems.
>
>  
>
> On Thu, Nov 28, 2013 at 5:40 PM, Sandell, Robert <
> robert@sonymobile.com > wrote:
>
> The notify parameter is not something you can set (yet), there is probably 
> still much that can be done to enhance the usage of the REST API.
>
> The only thing that is used from the command settings is the contents of 
> the message.
>
>  
>
>  
>
> *Robert Sandell*
>
> Software Tools Engineer - SW Environment and Product Configuration
>
> Sony Mobile Communications
>
>  
>
> *From:* jenkin...@googlegroups.com  [mailto:
> jenkin...@googlegroups.com ] *On Behalf Of *Øyvind Harboe
> *Sent:* den 28 november 2013 10:24
> *To:* jenkin...@googlegroups.com 
> *Cc:* jenkins...@googlegroups.com 
> *Subject:* Re: Beta release of Gerrit Trigger plugin 2.11.0
>
>  
>
> Hi Robert,
>
> I installed the beta because I would like to switch from the ssh commands 
> to REST API commands in order to more carefully manage which email 
> notifications are sent out.
>
>
> Is there any documentation or pointers on how I can change the line below, 
> which adds a comment that a build was started, to the REST API command to 
> do the same, but set notify=NONE?
>
>  gerrit approve , --message 'Build Started 
>  ' --verified  --code-review 
> 
>
>
>
> REST API feature that I would like to use:
>
>
> https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#review-input
>
>
>
>
>
>
>
> On Tuesday, November 26, 2013 4:15:19 PM UTC+1, Robert Sandell wrote:
>
> I just released version 2.11.0-beta-1

Re: Getting access to https://github.com/jenkinsci

[teilo]

How is this plugin different from 
https://wiki.jenkins-ci.org/display/JENKINS/All+Changes+Plugin ?

/James

On Monday, 9 December 2013 07:29:45 UTC, Henrik Johnson wrote:
>
>  Hello,
>
>  
>
> I am in the final parts of completing a plugin for Jenkins (The plugin 
> itself is to copy change history from parent jobs). I would like to request 
> access to the jenkinscs GitHub group in anticipation of finishing up the 
> final loose end of my plugin so that once finished I can publish it.
>
>  
>
> My GitHub account is henrik...@software.dell.com . Thank you!
>
>  
>
> /Henrik Johnson
>
> Software Development Principal Engineer
>
> Dell Software Group
>  

-- 
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: example snippet collection...

[teilo]

Bingo!

Thanks.

/James

On Tuesday, 15 October 2013 14:43:12 UTC+1, Vincent Latombe wrote:
>
> Maybe https://wiki.jenkins-ci.org/display/JENKINS/Recipe+Plugin ?
>
> Vincent
>
>
> 2013/10/15 teilo >
>
>> nope not that one :-(
>>
>>
>> On Tuesday, 15 October 2013 13:32:31 UTC+1, ogondza wrote:
>>>
>>> Just a wild guess but could it be ui-samples-plugin[1]? Formerly a part 
>>> of   
>>> core repo. 
>>>
>>> [1] 
>>> https://github.com/jenkinsci/**ui-samples-plugin<https://github.com/jenkinsci/ui-samples-plugin>
>>>  
>>>
>>> -- 
>>> oliver 
>>>
>>  -- 
>> 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-de...@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: example snippet collection...

[teilo]

nope not that one :-(

On Tuesday, 15 October 2013 13:32:31 UTC+1, ogondza wrote:
>
> Just a wild guess but could it be ui-samples-plugin[1]? Formerly a part of 
>   
> core repo. 
>
> [1] https://github.com/jenkinsci/ui-samples-plugin 
>
> -- 
> oliver 
>

-- 
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.

example snippet collection...

[teilo]

Hi all, 

Earlier in the year Kohsuke asked me to share some of my configuration for 
some for of snippet/example plugin/section.  Not sure if this was a plugin 
or what - but as the JUC rolls around I've been reminded that I should 
probably start to kick off this action. Problem is I can;t for the life of 
me use my google skills to locate what he was referring to...

Anyone (or Johsuke if you are out there!) any ideas on what/where this 
thing is?

/James

-- 
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.

sortable tables with footers?

[teilo]

HI all,

Is it possible to generate a sortable table that has a footer as well as a 
header?

I had a quick look at the source and it appears the sorter code treats all 
rows apart from the first as sortable but wondered if there was any tricks 
to get this working?

I've tried putting the footer in a  but that doesnkt work in IE or 
chrome :-(

example of what I am trying to do


  
  
Header1
Header1
  
   
  


  
${p.desc}
${p.value}
  

  
  


  Total
  ${it.totalString}
  
  


Thanks in advance.

/James

-- 
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: Tapping into Test Results

[teilo]

I don't think there is anything documented as this is done via plugin 
extensions.
if you grabbed all source from githun (including plugins) you could grep 
for "extends AbstractTestResultAction" and that may give you an idea (but 
I'm not sure that the ones that exist are open source.

The prefixes (I believe) need to be unique for the different types. The one 
I am working on at the moment is "cucumber" and I hope to be able to open 
source it shortly.

/James

On Friday, 4 October 2013 16:50:58 UTC+1, Cletus D'Souza wrote:
>
> Good to know that there will be more than just junit test results.  Where 
> can I find a list of these test types documented?  Will the test id contain 
> a different prefix (ex: junit/ for junit tests)?
>  
> Thanks!
> Cletus
>
>  
> > Date: Thu, 3 Oct 2013 14:47:13 -0700
> > From: teilo+...@teilo.net 
> > To: jenkin...@googlegroups.com 
> > Subject: RE: Tapping into Test Results
> > 
> > eep in mind that not all test results are of the junit type. You may be 
> able to get all this information with the test.* classes
> > 
> > GetFailedTests is broken so you would likely want to getResult and take 
> Avon depending on the type if object returned
> > 
> > -- 
> > 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-de...@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: Adventurous users wanted! Literate multi-branch project type

[teilo]

> I think the idea is great and can see this being fantastic for open 
>> source, or where you have a smaller company/team where you can check every 
>> commit to the build settings, I'm just not sure I could use it in an 
>> enterprise without being bitten by its ultimate flexibility (which is one 
>> reason why we use templates - but that gets us a plethora of jobs for the 
>> dozens of branches in each project!)
>>
>
> Oh way cool you've just given me an idea for another enterprise 
> plugin: multi-branch-templates plugin
>
> That should be easy... and because it's templates we don't have the UI 
> glitches we see with my (currently closed source) free-style multi-branch 
> plugin
>
> https://rm.cloudbees.com/issues/2111
>
> That should make you happy... now just to convince Harpreet to put it on 
> the backlog... feel free to file a ZD ;-)
>

Raised ZD#13606
 

-- 
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: Adventurous users wanted! Literate multi-branch project type

[teilo]

> But you are assuming my maven enforcer rules etc. are the only line of 
>> defence here.  The MRM can also play an important part :-)
>>
>
> Yes which is why I have another trick up my sleeve as part of my "make 
> maven better on jenkins and get rid of the ugly aberration that is the 
> Maven project type" plan...
>


I guess that is the trick I have been waiting for for a while...
You've made a lot out of this - I'm expecting the moon on a stick solution 
:-)

 

>  
>
>>
>> Besides that can you configure things that are not reporters?
>> e.g. wipe out workspace, 
>>
>
> That is something that does not make sense in SCM, so that is configured 
> from Jenkins
>  
>
>> always checkout a fresh copy, 
>>
>
> As for wipe out workspace
>  
>
>> enable a release plugin...
>>
>
> That is awaiting the "tasks" support that KK has said he will help 
> write... basically the way this will work is you will enable a branch 
> property that defines the promotion tasks to support for that branch... you 
> will specify the heading keyword to identify the steps for that task and 
> the environment to run the task on... so to enable releasing from Maven you 
> would do something like
>
> # To make a release
>
> mvn release:prepare release:perform -B
>
> and then in jenkins you just tell jenkins that, e.g. the master branch has 
> a release task with the keyword "release" in the heading
>
> Thus you will only be able to cut releases from the master branch.
>  
>
>>
>>  
>>
>>> Plus you can just watch what shit they are committing... You need to do 
>>> that with the poms anyway
>>>
>>
>> No I can't (and actually I don't).  If I could do that then we wouldn't 
>> need the Template plugin as I could watch all Jenkins job creation :-)
>>
>> You are correct in that there is a little bit of an arms race going on - 
>> but most of this is not actively trying to create non-repeatable builds - 
>> it's just people not always thinking things through and the system can 
>> probably automatically pick up 95+% of that.
>>
>
> What is a non-repeatable build in this context?
>

I should have also included traceable so replace with "non-repeatable 
non-traceable"

it is a build that we can't trace back to the source code, or for which if 
we checked it out onto a clean machine setup with the correct OS/java/maven 
could not run "mvn install" and have identical binaries in the future (we 
record the JDK version and maven version used to build as well as the build 
host which will tell us the OS).  Obviously there could be cases where some 
bad unit tests have some dates in them and these could fail if time has 
moved on - but they should be easily identifiable)

 

> The SCM revision will still be buildable if Jenkins built it once before.
>
>
Not true.  If you change the settings, or disable enforcer rules etc you 
can add a external repository.  As we all know some of these external maven 
repositories have a habit of being here one day and gone the next.  That is 
why we force everything via our MRM which will keep every single release it 
downloads forever to handle just this case.
There are also times when the upstream repo replaces a release version 
(even sonatype has let this happen on their hosted repositories in the 
past!) 

So just because you built something today doesn't mean that the 
dependencies/plugins you need to build it tomorrow will still be around and 
at the same place.

There are also occasions where someone sets a "release version" on trunk 
and would let jenkins "mvn deploy" - this could be ok as far as the MRM is 
concerned yet there is no tag in SCM.
As there is no tag there it may be on a branch that is a personal branch or 
a throwaway branch that can be deleted (e.g. you allow deleteion of 
personal/** but not releases/** - but don;t allow deletion/redefinition of 
tags)


Or is it that you are worries about people injecting alternative 
> settings.xml in the build command?
>

That would be one of my big concerns with this.

(Sonar being another root of all evil..)

this setup would also allow users to have jars in SCM that they mvn 
install:installFile...  
(with maven2 you could have done this with system scope - but the enforcer 
rules should have prevented this).
The above isn't about reproduceability - but to make sure that people don;t 
check in jars to SCM - and that they go via the 3rd party reposiroty and 
have their licence/useage tracked.

All our main source build jobs use the same template that allows you to 
specify the following,

1) source location
2) users to email
3) java version
4a) maven version
4b) number of threads (-T...)
5) If you want any findbugs violations to mark the build as unstable
6) if you want any checkstyle violations to mark the build as unstable
7) slave restriction

With just that you have a whole host of plugins configured - and just 
managed.  You get reports even if you choose to ignore them so the commands 
to run are (for a ommit build) always the same
mvn i

Re: Adventurous users wanted! Literate multi-branch project type

[teilo]

On Thursday, 3 October 2013 20:37:27 UTC+1, Stephen Connolly wrote:
>
>
>
> On Thursday, 3 October 2013, teilo wrote:
>
>> Hi Stephen,
>>
>> Is the literate plugin going to be the only route into the multi-branch 
>> job?
>>
>>
> I am sure somebody may use the branch api to implement other types... I 
> have a freestyle multi branch but there is just too many build differences 
> for it to be useful and a ton of UI glitches because plugins assume they 
> are owned by 
>
>  
>
>> Reason being for enterprisy software we need to enforce things in a 
>> build/release so I can't let my users run abitrary maven invocations that 
>> change the build (and make it unreproduceable).
>>
>> e.g. they should not be able to change the settings by using mvn -s 
>> $workspace/some_setting_with_external_repo.xml -DskipTests=true
>>
>
> But they can just change the pom to skip tests anyway... You have a false 
> sense of security...
>

That was a bit of a bad example - but actually if they want to skip tests 
in the POM then that is 100% ok - as we know that the tests were not run on 
a specific build.
 

>
> And if they want to use a different settings... Invoker and an alternative 
> pom file.
>
>
But you are assuming my maven enforcer rules etc. are the only line of 
defence here.  The MRM can also play an important part :-)

Besides that can you configure things that are not reporters?
e.g. wipe out workspace, always checkout a fresh copy, enable a release 
plugin...

 

> Plus you can just watch what shit they are committing... You need to do 
> that with the poms anyway
>

No I can't (and actually I don't).  If I could do that then we wouldn't 
need the Template plugin as I could watch all Jenkins job creation :-)

You are correct in that there is a little bit of an arms race going on - 
but most of this is not actively trying to create non-repeatable builds - 
it's just people not always thinking things through and the system can 
probably automatically pick up 95+% of that.

There are several thousand projects+branches - it would take a full time 
person to watch all of that - you could say that this could be somewhat 
automated - but even that has human overhead to setup these jobs when new 
projects are added, maintain mapping of project/branch to user+manager 
mapping etc...

 

>  
>
>>
>> but at the same time its nice that you just branch and get a job (from 
>> say a job that's created from some kind of template, and that should allow 
>> the user to specify the properties exposed by that template only...)
>>
>> (you haven't yet beaten my addiction to the maven job type...)
>>
>
> I'm not done... There are more tricks up my sleeve
>

 

-- 
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: Tapping into Test Results

[teilo]

eep in mind that not all test results are of the junit type.  You may be able 
to get all this information with the test.* classes

GetFailedTests is broken so you would likely want to getResult and take Avon 
depending on the type if object returned

-- 
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: Adventurous users wanted! Literate multi-branch project type

[teilo]

Hi Stephen,

Is the literate plugin going to be the only route into the multi-branch job?

Reason being for enterprisy software we need to enforce things in a 
build/release so I can't let my users run abitrary maven invocations that 
change the build (and make it unreproduceable).

e.g. they should not be able to change the settings by using mvn -s 
$workspace/some_setting_with_external_repo.xml -DskipTests=true

but at the same time its nice that you just branch and get a job (from say 
a job that's created from some kind of template, and that should allow the 
user to specify the properties exposed by that template only...)

(you haven't yet beaten my addiction to the maven job type...)

/James

On Friday, 20 September 2013 10:16:47 UTC+1, Stephen Connolly wrote:
>
> Ok!
>
> This is the first bit of noise about this. I'll be writing up a series of 
> blog posts around this, but as I just got everything OSS I thought that 
> some of the more adventurous amongst you may want to start playing with it 
> now.
>
> To play with this you need to do the following:
>
> 1. Checkout and build (mvn install) the branch-api-plugin
> 2. Checkout and build (mvn package) the literate-plugin
> 3a. Checkout and build (mvn package) the git plugin (either the master or 
> the refactoring branch... pick your poison)
> 3b. Checkout and build (mvn package) the subversion plugin (the 
> refactoring branch)
> 3c. Checkout and build (mvn package) the mercurial plugin
>
> In your Jenkins 1.509+ install the three (or more) plugins that you have 
> just built
>
> You should now be able to create literate multi-branch projects.
>
> To try it out.
>
> In your SCM system create a project. In the root of the project put the 
> following two files:
>
> $ touch .cloudbees.md
> cat - > README.md < Hello World project
> ==
>
> How to Build
> --
>
> echo 'Hello world'
>
> EOF
>
> Checkin these two files. Create a literate multi-branch project with your 
> project as a source. Trigger the indexing. You should see a sub-project for 
> the main branch of the project.
>
> *NOW* go and fork your main branch into another branch.
>
> Trigger indexing again... oh look that branch has a project too.
>
> Have fun.
>
> The 10 best bug reports will be getting at least a T-shirt from CloudBees, 
> but I am hoping to improve the swag that I can offer.
>
> -Stephen
>
> P.S. There will be an update centre that allows people to pull this 
> without building themselves... and there will be a blog post later today 
> detailing more of the fun you can do!
>
> P.P.S. The aim is to have enough people test this that it can be 
> considered GA ready for JUC in late Oct 2013
>
> P.P.P.S. Many thanks to my employers (CloudBees) for funding the 
> development of this fully open source (MIT license) feature for Jenkins... 
> the only "cost" is that the default marker file is called .cloudbees.md!
>  

-- 
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: extending classes and Jelly

[teilo]

For future referencee and archiving...

That's what org.kohsuke.stapler.StaplerProxy does that I hadn't implemented 
:-)

getTarget() returns the thing that should be the target of this request.

/James

On Friday, 20 September 2013 18:11:01 UTC+1, teilo wrote:
>
> Hi all,
>
> I am writing a TestResultAction (custom implementation of 
> hudson.task.test.*) and have been using the JUnit implementation as a bit 
> of a reference.
>
> I think The backend is pretty much all there, but I can't work out how the 
> JUnit implementation hooks up the UI.
>
> if I don't provide MyCustomTestResultAction/index.jelly then stapler 
> throws a wobbly when accessing joburl/testReport/
>
> Stapler processed this HTTP request as follows, but couldn't find the 
> resource to consume the request
>
> -> evaluate( 
> :hudson.model.Hudson,"/job/test/7/testReport")
>
> -> 
> evaluate(((StaplerProxy)).getTarget(),"/job/test/7/testReport")
>
> -> evaluate(.getJob("test"),"/7/testReport")
>
> -> evaluate( 
> :hudson.model.FreeStyleProject,"/7/testReport")
>
> -> 
> evaluate(.getDynamic("7",...),"/testReport")
>
> -> evaluate( :hudson.model.FreeStyleBuild,"/testReport")
>
> -> evaluate(.getDynamic("testReport",...),"")
>
> -> evaluate( 
> :myco.MyCustomTestResultAction,"")
>
> -> No matching rule was found on  for ""
>
>
> 
>  has the following URL mappings, in the order of preference:
>
>
>1. hudson.tasks.test.AbstractTestResultAction.doGraph(...) for 
> url=/graph/...
>   2. hudson.tasks.test.AbstractTestResultAction.doGraphMap(...) for 
> url=/graphMap/...
>   3. TOKEN.groovy for url=/TOKEN/...
>   4. VIEW.jelly for url=/VIEW
>   5. hudson.tasks.test.AbstractTestResultAction.owner for url=/owner/...
>   6. myco.MyTestResultAction.getResult() for url=/result/...
>   7. myco.MyCucumberTestResultAction.getResult() for url=/result/...
>   8. myco.MyCucumberTestResultAction.getFailCount() for url=/failCount/...
>   9. myco.MyCucumberTestResultAction.getSkipCount() for url=/skipCount/...
>   10. myco.MyCucumberTestResultAction.getTotalCount() for 
> url=/totalCount/...
>   11. hudson.tasks.test.AbstractTestResultAction.getDisplayName() for 
> url=/displayName/...
>   12. hudson.tasks.test.AbstractTestResultAction.getApi() for url=/api/...
>   13. hudson.tasks.test.AbstractTestResultAction.getUrlName() for 
> url=/urlName/...
>   14. hudson.tasks.test.AbstractTestResultAction.getIconFileName() for 
> url=/iconFileName/...
>   15. hudson.tasks.test.AbstractTestResultAction.getBuildHealth() for 
> url=/buildHealth/...
>   16. hudson.tasks.test.AbstractTestResultAction.getFailureDiffString() 
> for url=/failureDiffString/...
>   17. hudson.tasks.test.AbstractTestResultAction.getPreviousResult() for 
> url=/previousResult/...
>   18. hudson.tasks.test.AbstractTestResultAction.getFailedTests() for 
> url=/failedTests/...
>   19. java.lang.Object.getClass() for url=/class/...
>
> If I provide an the index.jelly that I can do all manner of normal things - 
> but as I am extending AbstractTestResultAction why isn't the 
> AbstractTestResultAction's jelly used.  I would have thought I would only 
> need to override the bits that I needed - and as far as I can tell the 
> hudson.task.junit.TestResultAction doesn't provide any jelly views so I am 
> struggling to work out how it works.
>
>
> Can anyone shed any light on this?
>
>
> Thanks
>
>
> James
>
>

-- 
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.

extending classes and Jelly

[teilo]

Hi all,

I am writing a TestResultAction (custom implementation of 
hudson.task.test.*) and have been using the JUnit implementation as a bit 
of a reference.

I think The backend is pretty much all there, but I can't work out how the 
JUnit implementation hooks up the UI.

if I don't provide MyCustomTestResultAction/index.jelly then stapler throws 
a wobbly when accessing joburl/testReport/

Stapler processed this HTTP request as follows, but couldn't find the 
resource to consume the request

-> evaluate( 
:hudson.model.Hudson,"/job/test/7/testReport")

-> 
evaluate(((StaplerProxy)).getTarget(),"/job/test/7/testReport")

-> evaluate(.getJob("test"),"/7/testReport")

-> evaluate( 
:hudson.model.FreeStyleProject,"/7/testReport")

-> 
evaluate(.getDynamic("7",...),"/testReport")

-> evaluate( :hudson.model.FreeStyleBuild,"/testReport")

-> evaluate(.getDynamic("testReport",...),"")

-> evaluate( 
:myco.MyCustomTestResultAction,"")

-> No matching rule was found on  for ""



 has the following URL mappings, in the order of preference:


   1. hudson.tasks.test.AbstractTestResultAction.doGraph(...) for url=/graph/...
  2. hudson.tasks.test.AbstractTestResultAction.doGraphMap(...) for 
url=/graphMap/...
  3. TOKEN.groovy for url=/TOKEN/...
  4. VIEW.jelly for url=/VIEW
  5. hudson.tasks.test.AbstractTestResultAction.owner for url=/owner/...
  6. myco.MyTestResultAction.getResult() for url=/result/...
  7. myco.MyCucumberTestResultAction.getResult() for url=/result/...
  8. myco.MyCucumberTestResultAction.getFailCount() for url=/failCount/...
  9. myco.MyCucumberTestResultAction.getSkipCount() for url=/skipCount/...
  10. myco.MyCucumberTestResultAction.getTotalCount() for 
url=/totalCount/...
  11. hudson.tasks.test.AbstractTestResultAction.getDisplayName() for 
url=/displayName/...
  12. hudson.tasks.test.AbstractTestResultAction.getApi() for url=/api/...
  13. hudson.tasks.test.AbstractTestResultAction.getUrlName() for 
url=/urlName/...
  14. hudson.tasks.test.AbstractTestResultAction.getIconFileName() for 
url=/iconFileName/...
  15. hudson.tasks.test.AbstractTestResultAction.getBuildHealth() for 
url=/buildHealth/...
  16. hudson.tasks.test.AbstractTestResultAction.getFailureDiffString() for 
url=/failureDiffString/...
  17. hudson.tasks.test.AbstractTestResultAction.getPreviousResult() for 
url=/previousResult/...
  18. hudson.tasks.test.AbstractTestResultAction.getFailedTests() for 
url=/failedTests/...
  19. java.lang.Object.getClass() for url=/class/...
   
If I provide an the index.jelly that I can do all manner of normal things - but 
as I am extending AbstractTestResultAction why isn't the 
AbstractTestResultAction's jelly used.  I would have thought I would only need 
to override the bits that I needed - and as far as I can tell the 
hudson.task.junit.TestResultAction doesn't provide any jelly views so I am 
struggling to work out how it works.


Can anyone shed any light on this?


Thanks


James

-- 
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: Jenkins as a deamon

[teilo]

If you use the --daemon option then I am pretty sure that Jenkins will keep 
the same PID when restarted via the UI as it can relaunch the JVM without 
starting a new process (due to the fun of Unix fork() and the magic coder 
that is Kohsuke).

At least that is my setup (with embedded winstone) on Linux and I install 
plugins and set to restart when no jobs are running and I can still control 
it with service jenkins stop/status

'java -jar jenkins.war --help' will show you all the options.

http://akuma.kohsuke.org/

/James

On Monday, 2 September 2013 09:16:29 UTC+1, Christophe Demarey wrote:
>
> Hi all, 
>
> I think I have a simple question for you but really important for me : How 
> to prevent Jenkins to change its PID after a Jenkins restart (ex: Jenkins 
> update or plugin update)? 
> I really need this behavior to have working daemon scripts because they 
> use the PID to know the status of the Jenkins process. If the Jenkins PID 
> changes, the script is lost. 
>
> For information, here is the command the deamon use to run Jenkins: 
> /usr/bin/daemon --name=myjenkins --inherit 
> --env=JENKINS_HOME=/home/myjenkins --output=/var/log/ci/myjenkins.log 
> --pidfile=/var/run/jenkins/myjenkins.pid -- /usr/bin/java -jar 
> /home/myjenkins/jenkins.war --webroot=/home/myjenkins/.jenkins/war 
> --httpPort=17001 --ajp13Port=-1 --httpsPort=-1 --prefix=/myjenkins 
>
> Thanks for any answer. 
>
> Berst regards, 
> Christophe.

-- 
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: fork request for plugin: quarantine

[teilo]

Wow - that looks really useful :-)

I wonder if it could use the generic hudson.task.test.* generic base 
classes rather than the hudson.task.junit ones so that it would work with 
other test data publishers...
If not looks like it would be pretty simple to wrap other test publishers 
in the same manner!

BTW - would be helpfully if you could put a LICENCE.txt in the root folder, 
or in the source files.  Otherwise some people may not be able to 
contribute fixes.

/James

On Thursday, 12 September 2013 03:21:47 UTC+1, Samuel Nobs wrote:
>
> hi all,
>
> i have come up with a plugin to quarantine flakey tests. i first intended 
> to merge it into the claim-plugin, but then diverged more and more both 
> conceptually and from an implementation point of view. therefore i think 
> it's more appropriate to have it as a separate plugin.
>
> see also: https://issues.jenkins-ci.org/browse/JENKINS-14089
>
> i have currently hosted it on:
> https://github.com/samsta/quarantine
>
>
> here's a quick description:
>
> imagine you have a flakey test that sometimes passes, sometimes fails. if 
> you go to the latest result of the test, that's what you see:
> [image: Inline image 1]
> let's quarantine it:
> [image: Inline image 2]
> after hitting quarantine:
> [image: Inline image 3]
> and on the test result page one level up:
>
> [image: Inline image 5]
>
> this won't make the job go green immediately, as jenkins does not allow 
> you to change the build status after the fact. but on the next run, the 
> following will happen (from the console output):
>
> Recording test results
> [Quarantine]: AnotherSuiteB.TestA failed but is quarantined
> [Quarantine]: 0 unquarantined failures remaining
> Finished: SUCCESS
>
> if now another test fails that has not been quarantined, this happens:
>
> Recording test results
> [Quarantine]: AnotherSuiteB.TestA failed but is quarantined
> [Quarantine]: 1 unquarantined failures remaining
> Build step 'Publish quarantinable JUnit test result report' changed build 
> result to UNSTABLE
> Finished: UNSTABLE
>
> there's also a top-level page listing all the tests that are in quarantine 
> so we don't forget about those quarantined tests:
>
> [image: Inline image 6]
>
>
> cheers,
> sam
> -- 
>  Samuel Nobs
> Senior Design Engineer
> Tait Communications
> DDI: +64 7 825 7538
> Email: samue...@taitradio.com 
>
> 
> www.taitradio.com
>
>  
>  
>
>
> -- 
> Samuel Nobs
> Senior Design Engineer
> Tait Communications
> DDI: +64 7 825 7538
> Email: samue...@taitradio.com 
>
> 
> www.taitradio.com
>
>  
> --
> This email, including any attachments, is only for the intended recipient. 
> It is subject to copyright, is confidential and may be the subject of legal 
> or other privilege, none of which is waived or lost by reason of this 
> transmission.
> If you are not an intended recipient, you may not use, disseminate, 
> distribute or reproduce such email, any attachments, or any part thereof. 
> If you have received a message in error, please notify the sender 
> immediately and erase all copies of the message and any attachments.
> Unfortunately, we cannot warrant that the email has not been altered or 
> corrupted during transmission nor can we guarantee that any email or any 
> attachments are free from computer viruses or other conditions which may 
> damage or interfere with recipient data, hardware or software. The 
> recipient relies upon its own procedures and assumes all risk of use and of 
> opening any attachments.
> --
>

-- 
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: Is there a way to 'upvote' a build result?

[teilo]

Have you thought about changing the logic.

 Make the xunit mark the build as unstable and then fail if there are more 
than N.

 That way you adhere to only changing the result on X failure and also only 
change the result from better to worse.

 There was a reason why this was implemented – I can’t recall it but if you 
search the history of the code that has the check the commit comment will 
probably tell you why.

 /James

On Tuesday, 10 September 2013 15:15:58 UTC+1, Mads Nielsen wrote:
>
> Hey everyone,
>
> I'm trying to create a plugin that should be able to override the result 
> of a given build (to be specific it's the JUnit plugin and xUnit projects 
> TestResultAction(s), but when looking at setResult(Result r) from the Run 
> class, it seems to include a check to see if the value you're trying to set 
> is worse than the current startus, meaning you can't really change a build 
> from FAILURE --> UNSTABLE for example. 
>
> Is there another way in which to 'intercept' or change this behaviour. The 
> reason for this is that it would allow me to create a very simple plugin 
> with xUnit as a dependency, but given that feature, i'd have to modify the 
> xUnit plugin to get my feature in place.
>
> Basically, it's because i want to only fail builds on repeat test-failures 
> (n-amount of failures in the last n-builds),
>
> Any help would be much appreciated!
>
> P.S would a method called setResultForce() be feasible in the future for 
> Jenkins?
>
> Best regards,
> Mads
>
> -- 
> *
> * 
> *Mads Nielsen
> Consultant
> Praqma A/S
> *
>
> *Tel: +45 50 98 18 09
> Mail: m...@praqma.net 
> web: www.praqma.net*
>  

-- 
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: Aw: Re: 1.509.3 RC1 posted

[teilo]

please ignore my last reply - no one had responded to my request to add a 
backport and had missed that it was actually done (oh for an stable-rc 
changelog!)

On Thursday, 29 August 2013 23:22:35 UTC+1, Dominik Bartholdi wrote:
>
> Yeah, specially as this one is such an easy fix...
> But if we are not going to fix anything more, what are we waiting for with 
> the release?
>
> Am 29.08.2013 um 10:11 schrieb "Christoph Kutzinski" 
> 
> >:
>
> I understand your pain. I've been waiting for a usable 1.509 LTS also for 
> some time.
> Luckily .3 seems now usable for me as we've recently switched completely 
> to maven 3.x
>   
> *Gesendet:* Donnerstag, 29. August 2013 um 05:06 Uhr
> *Von:* Domi >
> *An:* "jenkin...@googlegroups.com " <
> jenkin...@googlegroups.com >
> *Betreff:* Re: 1.509.3 RC1 posted
> Only with Maven 2.x...
> I understand, it's just because I'waiting for a usable version of this LTS 
> since its first release and every time there is another blocker for me. And 
> as we have to follow strict release cycles to get anything into production. 
> I'll have to wait another 3-4months months now :(
>
> Am 28.08.2013 um 23:53 schrieb Christoph Kutzinski 
> >:
>
> > With 'only seen with maven2' you mean it's only happening with Maven 2.x 
> (and okay with Maven 3.x) or do you mean the maven2 job type?
> >
> > Am 28.08.2013 19:41, schrieb domi:
> >> Seems not to be the case...
> >> I have only seen it with maven2 - but unfortunately we do still have 
> many of them.
> >> ...
> >>
> >> On 28.08.2013, at 19:37, Jesse Glick > 
> wrote:
> >>
> >>> On Wed, Aug 28, 2013 at 1:25 PM, domi > 
> wrote:
>  the logs are full with this:
>  https://issues.jenkins-ci.org/browse/JENKINS-18441
> >>>
> >>> My understanding was that this bug was a regression well after 1.509.
> >>> But perhaps not; may be specific to Maven version, in which case
> >>> lts-candidate would be appropriate.
> >>>
> >>> --
> >>> 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-de...@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-de...@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-de...@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-de...@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: Aw: Re: 1.509.3 RC1 posted

[teilo]

There are other Maven2 performance issues that are missing in .3RC

I say just ship it and start the backports on  1.509.4 immediately and try 
to get that ready for testing very quickly!

/James

On Thursday, 29 August 2013 23:22:35 UTC+1, Dominik Bartholdi wrote:
>
> Yeah, specially as this one is such an easy fix...
> But if we are not going to fix anything more, what are we waiting for with 
> the release?
>
> Am 29.08.2013 um 10:11 schrieb "Christoph Kutzinski" 
> 
> >:
>
> I understand your pain. I've been waiting for a usable 1.509 LTS also for 
> some time.
> Luckily .3 seems now usable for me as we've recently switched completely 
> to maven 3.x
>   
> *Gesendet:* Donnerstag, 29. August 2013 um 05:06 Uhr
> *Von:* Domi >
> *An:* "jenkin...@googlegroups.com " <
> jenkin...@googlegroups.com >
> *Betreff:* Re: 1.509.3 RC1 posted
> Only with Maven 2.x...
> I understand, it's just because I'waiting for a usable version of this LTS 
> since its first release and every time there is another blocker for me. And 
> as we have to follow strict release cycles to get anything into production. 
> I'll have to wait another 3-4months months now :(
>
> Am 28.08.2013 um 23:53 schrieb Christoph Kutzinski 
> >:
>
> > With 'only seen with maven2' you mean it's only happening with Maven 2.x 
> (and okay with Maven 3.x) or do you mean the maven2 job type?
> >
> > Am 28.08.2013 19:41, schrieb domi:
> >> Seems not to be the case...
> >> I have only seen it with maven2 - but unfortunately we do still have 
> many of them.
> >> ...
> >>
> >> On 28.08.2013, at 19:37, Jesse Glick > 
> wrote:
> >>
> >>> On Wed, Aug 28, 2013 at 1:25 PM, domi > 
> wrote:
>  the logs are full with this:
>  https://issues.jenkins-ci.org/browse/JENKINS-18441
> >>>
> >>> My understanding was that this bug was a regression well after 1.509.
> >>> But perhaps not; may be specific to Maven version, in which case
> >>> lts-candidate would be appropriate.
> >>>
> >>> --
> >>> 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-de...@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-de...@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-de...@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-de...@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.

JIRA upgrade?

[teilo]

Would it be possible to upgrade the his instance?

I find I want to comment on new issues when I am not at a computer more and 
more often, yet the version we have isn't mobile or tablet friendly.  The 
latest version is supposed to address this with a brand new mobile skin.

-- 
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.

Run.getExecutor

[teilo]

Hi,

Is there a valid reason why callers of 
Run.getExecutor()
 need 
to be aware of the type of run that they are interogating?

e.g. if the Run is a flyweight task this will always return null.

or to put it another way why doesn't getExectutor() check both real and 
oneOff exectutors - rather than forcing the caller to check both with an 
extra if (null) getOneOffExecutor()?

/James

-- 
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: BuildFlow Plugin licence - Afferro GPL / GPL?

[teilo]

On Wednesday, 21 August 2013 11:03:02 UTC+1, nicolas de loof wrote:
>
>
> BTW - the pom.xml still references LGPL v3
>>
>>
> fixed.
>
 
Many other files are also still under LGPL - 
Originally I thought it was as they had non cloudbees contributors and they 
had not consented to re-licence - but it seems arbitrary.
( 
FlowIcon.javais
 so simple and has only one committer)

build-flow-plugin>grep -r -l GNU pom.xml src/
src/main/groovy/com/cloudbees/plugins/flow/FlowDSL.groovy
src/main/java/com/cloudbees/plugins/flow/BuildFlow.java
src/main/java/com/cloudbees/plugins/flow/BuildFlowAction.java
src/main/java/com/cloudbees/plugins/flow/BuildFlowPlugin.java
src/main/java/com/cloudbees/plugins/flow/FlowIcon.java
src/main/java/com/cloudbees/plugins/flow/FlowRun.java
src/main/java/com/cloudbees/plugins/flow/JobNotFoundException.java
src/main/resources/com/cloudbees/plugins/flow/BuildFlow/configure-entries.jelly
src/main/resources/com/cloudbees/plugins/flow/BuildFlow/index.jelly
src/main/resources/com/cloudbees/plugins/flow/BuildFlow/newJobDetail.jelly
src/main/resources/com/cloudbees/plugins/flow/BuildFlow/newJobDetail.properties
src/main/resources/com/cloudbees/plugins/flow/Messages.properties
src/main/resources/index.jelly
src/test/groovy/com/cloudbees/plugins/flow/BindingTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/BuildTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/CombinationTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/DSLTestCase.groovy
src/test/groovy/com/cloudbees/plugins/flow/GuardTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/IgnoreTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/ParallelTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/RetryTest.groovy
src/test/groovy/com/cloudbees/plugins/flow/UpstreamTest.groovy



-- 
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: Found reliance on default encoding in ... 66 cases

[teilo]

In those cases would it not be better to explicitly pass the platform charset 
to make it obvious it is a conscious decision?

-- 
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: BuildFlow Plugin licence - Afferro GPL / GPL?

[teilo]

Hasn’t Kohskue already provided a solution that could be leveraged? 

 http://groovy-sandbox.kohsuke.org/  would need some work to also ask 
DSLExtensions what they need to run.

Short term I am working on limiting concurrent execution of jobs in a flow 
to prevent exhaustion (there is no point pulling myjob#2 from the queue 
when myjob#3 is in the queue as well - think parameterised jobs and 
build("myjob", upstream:build; other:fred) ). This is as a sepated plugin 
for the DSL - but I have some simple fixes for JENKINS-15966, typos and 
extend the DSL help (so that extensions can also display some help) that 
are for the flow plugin.  Hopefully I should have clearance for these 
sometime next week.

/James
On Wednesday, 21 August 2013 11:03:02 UTC+1, nicolas de loof wrote:
>
>
> 2013/8/21 teilo >
>
>> Excellent - I was hoping for GPLv2 but MIT should streamline being able 
>> to push patches back!
>>
>
> I've documented short term plan on 
> https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin in case you 
> have some clever solution to existing limitations ;)
>  
>
>>
>> BTW - the pom.xml still references LGPL v3
>>
>>   
>> 
>>
>>
>>
>> LGPL 3
>> http://www.gnu.org/licenses/lgpl.html
>>
>>
>> repo
>> 
>>
>>
>>   
>>
>>
> fixed.
>  
>
>>
>>
>>
>>
>>
>> On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote:
>>
>>> The plugin was initially created under AGPL, but I got approval to 
>>> relicense it under MIT.
>>> https://github.com/jenkinsci/**build-flow-plugin/commit/**
>>> 022b40b86383ef678184bf6fe6497b**e033254555<https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555>
>>>
>>>
>>> 2013/8/20 teilo 
>>>
>>>>  Hi Nicolas/Cloudbees/other buildflow contributors.
>>>>
>>>> Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 
>>>> (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3.
>>>>
>>>> Is this just an oversight when the plugin was re-licensed - or is this 
>>>> really a mix?
>>>>
>>>> (also any chance of changing it to something without the GPL v3 patent 
>>>> issues to make it more company friendly - even if it is dual licenced with 
>>>> the Jenkins enterprise plugins)  I don't ask for much do I ;-)
>>>>
>>>> /James
>>>>
>>>>
>>>>
>>>>
>>>>  -- 
>>>> 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-de...@**googlegroups.com.
>>>>
>>>> For more options, visit 
>>>> https://groups.google.com/**groups/opt_out<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-de...@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: BuildFlow Plugin licence - Afferro GPL / GPL?

[teilo]

Excellent - I was hoping for GPLv2 but MIT should streamline being able to 
push patches back!

BTW - the pom.xml still references LGPL v3

  

LGPL 3
http://www.gnu.org/licenses/lgpl.html
repo

  



On Wednesday, 21 August 2013 07:14:42 UTC+1, nicolas de loof wrote:
>
> The plugin was initially created under AGPL, but I got approval to 
> relicense it under MIT.
>
> https://github.com/jenkinsci/build-flow-plugin/commit/022b40b86383ef678184bf6fe6497be033254555
>
>
> 2013/8/20 teilo >
>
>> Hi Nicolas/Cloudbees/other buildflow contributors.
>>
>> Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 
>> (jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3.
>>
>> Is this just an oversight when the plugin was re-licensed - or is this 
>> really a mix?
>>
>> (also any chance of changing it to something without the GPL v3 patent 
>> issues to make it more company friendly - even if it is dual licenced with 
>> the Jenkins enterprise plugins)  I don't ask for much do I ;-)
>>
>> /James
>>
>>
>>
>>
>>  -- 
>> 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-de...@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: jelly help.

[teilo]

Got it the end. I had misspelt the name of the HTML file and the slash at the 
start was my other issue.

I can now even do  and it will use the jelly for of it exists, the HTML file or 
silently ignore it if none exist.

Happy days!

-- 
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.

BuildFlow Plugin licence - Afferro GPL / GPL?

[teilo]

Hi Nicolas/Cloudbees/other buildflow contributors.

Currently the licence of the BuildFlow plugin is a mix of Affero GPL v3 
(jelly files) and Lesser GPL v3 (most others), the pom.xml states LGPL v3.

Is this just an oversight when the plugin was re-licensed - or is this 
really a mix?

(also any chance of changing it to something without the GPL v3 patent 
issues to make it more company friendly - even if it is dual licenced with 
the Jenkins enterprise plugins)  I don't ask for much do I ;-)

/James




-- 
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: buildflow extensions

[teilo]

I'm working though legal to get the extension and fixes to buildflow 
approved - and I can't share until that happens.

However I think I have found the cause (and confusion).

I tried using 
   def concExt = extension.bogus-wibble

and my extension is called with "bogus" as the extension name not 
"bogus-wibble".

I can only presume that groovy is treating the extension.foo-bar-wibble as 
  extension.foo subtract bar subtract wibble.
and that the documentation on the BuildFlowDSLExtension to use the artifact 
id such as "external-resource-dispatcher" is wrong.

simply changing my extension name from build-flow-concurrent-extensions 
to buildflowconcurrentextensions makes the code and DSL work.

Not sure if this is intended or not - but I can happily test my plugin now!


On Friday, 16 August 2013 17:34:09 UTC+1, nicolas de loof wrote:
>
> Can you publish this on some github repo so I can check ?
> (or share in private => nicolas...@gmail.com  / 
> github:ndeloof)
>
>
> 2013/8/16 teilo >
>
>> Hi all,
>>
>> I'm attempting to write a buildflow extension.
>>
>> However as soon as I attempt to register the extension (not even use it) 
>> all existing flow functionality breaks.
>>
>> e.g.
>> the following DSL:
>>
>> def concExt = extension.build-flow-concurrent-extensions
>> build("job1", param: build.number)
>> build("job2", param: build.number)
>>
>>
>> produces the following error:
>>
>> ERROR: Failed to run DSL Script, java.lang.UnsupportedOperationException: 
>> No such extension available: build
>>
>>
>> As far as I can tell I am doing this the right way - in my 
>> BuildFlowDSLExtension.createExtension(String, FlowDelegate) I have a check 
>>  
>>
>> if ("build-flow-concurrent-extensions".equals(s)) {
>>   return new MyDSL(flowDelegate);
>> }
>> return null;
>>
>>
>> And for some reason this is called with "build" as the String.
>>
>> Any ideas where I am going wrong (I can't yet release the full code :-( )
>>
>> /James
>>
>> -- 
>> 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-de...@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.

buildflow extensions

[teilo]

Hi all,

I'm attempting to write a buildflow extension.

However as soon as I attempt to register the extension (not even use it) 
all existing flow functionality breaks.

e.g.
the following DSL:

def concExt = extension.build-flow-concurrent-extensions
build("job1", param: build.number)
build("job2", param: build.number)


produces the following error:

ERROR: Failed to run DSL Script, java.lang.UnsupportedOperationException: 
No such extension available: build


As far as I can tell I am doing this the right way - in my 
BuildFlowDSLExtension.createExtension(String, FlowDelegate) I have a check 
 

if ("build-flow-concurrent-extensions".equals(s)) {
  return new MyDSL(flowDelegate);
}
return null;


And for some reason this is called with "build" as the String.

Any ideas where I am going wrong (I can't yet release the full code :-( )

/James

-- 
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.

building core

[teilo]

Is buildhive for core working at the moment? Pull requests for the last day 
seem to have no comments on them and the ci server appears to have no executors

-- 
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.

How many jobs can jenkins support?

[teilo]

As you say an amount depends on the server resources, but also on how big your 
build history will be and how you have configured the jobs.

More then 1k jobs is used in the field, not sure anyone has got to >10k but 
from what I have heard it is getting close.  That's not too say that more jobs 
is not doable just I don't know of anyone who has that many. When you get to 
that many jobs its not just the server scaling but the ui and navigation etc 
which is not Jenkins specific

As for slaves I'd don't know as I support approx 1k jobs with 12 slaves. So 
scaling into the hundreds isn't even on  the radar for my setup!

-- 
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: Jenkins restart question

[teilo]

If the jobs are async jobs they survive restarts.

-- 
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: Missing maven-hpi-plugin-1.74 on BuildHive, central does not have it.

[teilo]

Go on then I'll bite...

If we had a useable alternative then we may not all be using it...

this includes (of the top of my head)

 *  knowing what is installed (by maven) so that it (can be optionally) 
automatically  added as an archive.
  * plugins that don’t fail the build when the foobar.xml they require 
doesn’t exist (as this build has no checkstyle as it is building an RPM)
  * Knowing where foobar.xml report is created… (not all checkstyle.xml are 
reports from the project that we want the plugin to scan!)

Managing 600+ jobs an having to keep a list of "artifacts to archive" in 
sync for all of these stuff (wildcards don’t work due to the nature of 
maven, the projects using it etc..) is not a viable option and would need a 
dedicated team of people to manage just the job configuration alone!

Provide us with a viable alternative and people will use it J

 Hasn't  Sacha signed off on you doing this work for Jenkins Enterprise yet!

Or actually I guess this is a Maven job type but one that only intercepts 
stuff and doesn’t mess with anything (changing the mojo config on the fly…)

 

/James



On Monday, 29 April 2013 09:36:30 UTC+1, Stephen Connolly wrote:
>
> Turns out this is actually a rather nasty bug in Jenkins' Maven project 
> type... which had been masked by some settings.xml magic that we were 
> applying but shouldn't have been applying
>
> [image: Inline images 1]
>
> And where is the problem?
>
> Well install:install is running and oh look Jenkins has mucked about 
> via its evil Maven job type
>
> Caused by: java.lang.IllegalStateException: Failed to build parent project 
> for org.jenkins-ci.plugins:jswidgets:hpi:1.10-SNAPSHOT
>   at 
> org.apache.maven.project.MavenProject.getParent(MavenProject.java:378)
>   at 
> hudson.maven.reporters.MavenFingerprinter.recordParents(MavenFingerprinter.java:141)
>   at 
> hudson.maven.reporters.MavenFingerprinter.postBuild(MavenFingerprinter.java:110)
>  
>
> So basically the Maven job type is trying to resolve the parents of the 
> files it fingerprints and because it doesn't know the repositories it blows 
> up and kills a perfectly fine build.
>
> Freestyle + Maven build step would never do this to you!
>
> Been saying that its evil for 6+ years now...
>
> ;-)
>
>
> On 26 April 2013 21:34, Jesse Glick >wrote:
>
>> On Fri, Apr 26, 2013 at 4:03 PM, Mirko Friedenhagen
>> > wrote:
>> > the job is trying to get maven-hpi-plugin-1.74 from central and fails 
>> because of this
>>
>> Yes a bunch of BuildHive jobs for Jenkins plugins got broken recently
>> due to a change in Maven mirror handling. We are working on
>> determining the real cause and how to fix it.
>>
>> --
>> 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-de...@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: candidate LTS backport commit

[teilo]

I may need more coffe but it looks as though this introduces an infinte 
loop leading to stack exhaustion?

the ctor calls the same c'tor...


On Tuesday, 16 April 2013 12:22:36 UTC+1, nicolas de loof wrote:
>
> Hi,
>
> I just hit a backward compatibility issue introduced in 1.509. (missing 
> backward compatible constructor)
> fixed as 
> https://github.com/jenkinsci/jenkins/commit/a0e4ec4bd7c7e245b4a975364c1c5b039c467cb4
>  
>
> I'd like we consider it for backport in 1.509.LTS
>
>

-- 
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: Notes from FOSDEM developer meet-up UI discussions

[teilo]

Grid control 
(example
)

Provide a grid control, with the master/detail pattern, the modal dialog 
for editing, and/or in-place editing.

This would reduce the amount of AJAX form validation request and hopefully 
help the performance. And perhaps more importantly, it'll save a lot of 
screen real estate in a long repetitive job configuration.
*Grid control with no copyleft license?*
The example links to extJS, which is only available under a copyleft 
license. We need to find a control that has a liberal license.


IANAL however - isn't extjs available under a non-copyleft so long as you 
are using an appropriate open source licence?
(or is this due to  commercial derrivatives like cloudbees)

If you would like to use the GPLv3 version of Ext JS with your non-GPLv3 
open source project, the following FLOSS (Free, Libre and Open Source) 
exceptions are available:

Open Source License Exception for 
Applications

Open Source License Exception for 
Development



On Tuesday, 12 March 2013 18:35:44 UTC, Kohsuke Kawaguchi wrote:
>
> Just like the last year, at FOSDEM Jenkins developers met and discussed 
> the UI improvements, with the goal of coming up with a prioritized list 
> that's small enough (as opposed to be comprehensive) that are actually 
> executable. 
>
> I've finally posted my notes at [1]. 
>
> If anyone else is willing to give it a shot at implementing some of 
> this, please put your name on it! 
>
>
> [1] 
>
> https://wiki.jenkins-ci.org/display/JENKINS/FOSDEM+UI+Enhancement+discussion+notes+2013
>  
> -- 
> 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/groups/opt_out.

Re: Groovy Interface(s) to Jenkins "security"

[teilo]

http://javadoc.jenkins-ci.org/jenkins/model/Jenkins.html#getSecurity() (and 
the other related methods) may help you in this regard.

/James

On Friday, 8 March 2013 17:08:34 UTC, Frank wrote:
>
> Posting on the user groups hasn't been helpful, I suspect folks here are 
> wiser on the Jenkins Internals.
>
> From Groovy Console, I would like to ask:
>
>
>1. Is security Enabled
>2. If so what kind?
>3. The expected answer is "Project Based" . . . in which case I want 
>to loop through the configured LDAP entries to get the user/group name(s) 
>and the permissions associated with each entry.
>
>
> Basically, I need to be able to "audit" the security settings . . . 
> changing is not required . . . just looking.
>
> I suspect this is all relatively easy, I just have no ideas what classes 
> to try to call into.
>
> Frank
>

-- 
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: question about how to disable shell "-ex" option in Hudson

[teilo]

This question is more appropriate for the users list - and I would suggest 
you use that for non development questions.

That said the solution is to start your script with the interpreter and 
options you want to use and it.

e.g.
#!/bin/tcsh



On Monday, 4 March 2013 15:06:06 UTC, inxt-c wrote:
>
> Hi Group,
> 
> The shell default use "-ex" option in Hudson Action, but I want to disable 
> the "-e" option. I can't configure it. :(
> In the Hudson commond lines, I add "source myshell.csh", but always shell 
> stop running in that commond.
> Note: in "mysell.csh", I use "if (...) then else endif", so it seems that 
> the "-e" option break my shell commond.
>  
> Thanks in advance.
> inxt
>
>
>
>
>
>
>
>

-- 
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.

AssertionError: Just copied ... but now I can't find it

[teilo]

Hi all,

Presumably someone put this Assertion error in to try and help to diagnose 
an rare/hard to find issue.

Well I can reliably hit it and its pretty easy. (although maybe not for the 
same reason it was put it).

I've put the info in https://issues.jenkins-ci.org/browse/JENKINS-16461 and 
thought I would ping the list in case this jobs someones memory who isn't 
subscribed tot the issues list.

/James

-- 
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: Jobs naming convention enforcer

[teilo]

The feature is implemented – you may want to look for “Restrict project 
naming” in your Jenkins (mange Jenkins – configure system).

Or is there something that you are missing in the current implementation?

On Thursday, 17 January 2013 13:25:48 UTC, lakshmi reddy wrote:
>
> Hi Daniel,
>
> I would like to implement the naming standards for our projects. Can you 
> please provide me access to the github repo. 
>
> Can you also help me in step-by-step process to implement those?
>
> Would really appreciate your kind help
>
> Thanks,
> B Lakshmireddy
>
> Le mercredi 29 février 2012 09:48:18 UTC, Daniel PETISME a écrit :
>>
>> I've created the following JIRA to gather the information
>> https://issues.jenkins-ci.org/browse/JENKINS-12928
>>
>> Cheers
>>
>> Daniel
>>
>>
>> Le jeudi 23 février 2012 14:16:17 UTC+1, Daniel PETISME a écrit :
>>>
>>> Hi guys,
>>>
>>> I want to know you have rules concerning the job's names? 
>>> I do and currently I don't have any tool to "force" the users to follow 
>>> the conventions.
>>> I've the maven-enforcer plugin in mind which check if you have specify 
>>> the versions of all your dependencies for instance.
>>>
>>> After a (very) quick research, I didn't see any Extension or equivalent 
>>> which allows me to specify any regexp-based naming convention.
>>> So, these modifications should be done in the core of Jenkins.
>>>
>>> How do you handle this use case?
>>>
>>> Thank you for your answers.
>>>
>>> Cheers
>>>
>>> Daniel
>>>
>>

Re: Scheduling m2release build pragmatically (e.g. from Build Flow plugin)

[teilo]

1. Is it possible trigger/schedule m2release build somehow else (not 
using ReleaseCause)? 

Not currently. 

2. Maybe some flag (like releaseEnvVar) could be used to indicate (when 
set by calling job) that release process was requested and all required 
parameters were set? 

I had started and parked some work to not require the ReleaseCause but the 
M2ReleaseBadgeAction was present - in which case you could schedule the 
build and pass that as an action - but it was not completed.

Note that I currently consider all of this internal plugin implementation 
and such it can (and has) changed from release to release.  Even the field 
names in the post have changed as no-one until now has mentioned automating 
releases (as it normally doesn't make much sense to put it at the end of a 
flow and would normally be a human descision to kick off a release process)

/James

On Friday, 4 January 2013 01:12:37 UTC, Marcin Zajączkowski wrote:
>
> Hi, 
>
> I'm looking for an ability to call/schedule m2release build in some 
> automatic way to be able to release a few modules with one click. 
>
> The only promising solution I've found was to call action via URL with 
> curl, but I don't like this as it would be problematic to call it from 
> another job and pass parameters. 
>
> I started from browsing source code for m2release plugin looking for a 
> way to do it programatically (e.g. from Build Flow Plugin), but as I 
> understand it is required to use ReleaseCause as a cause when call 
> project.scheduleBuild(). 
>
> My idea was to use CauseAction to be able to pass another cause from a 
> build flow: 
> actions.add(new CauseAction(new ReleaseCause()); 
> project.scheduleBuild2(project.getQuietPeriod(), flowCause, actions); 
>
> but analyzing AbstractProject.scheduleBuild2() it looks that another 
> CauseAction is created by this method itself and having two instance in 
> queueActions only the first (probably mine) would be used: 
> Actionable.java: 
> public  T getAction(Class type) { 
> for (Action a : getActions()) 
> if (type.isInstance(a)) 
> return type.cast(a); 
> return null; 
> } 
>
> which degenerates this call to: 
> project.scheduleBuild2(project.getQuietPeriod(), new ReleaseCause(), 
> actions); 
> which doesn't look good as flowCause isn't mentioned as a build cause 
> (and in addition a Build Flow plugin would have to depend on M2 Release 
> plugin). 
>
>
> Two questions: 
> 1. Is it possible trigger/schedule m2release build somehow else (not 
> using ReleaseCause)? 
> 2. Maybe some flag (like releaseEnvVar) could be used to indicate (when 
> set by calling job) that release process was requested and all required 
> parameters were set? 
>
>
> Marcin 
>
> -- 
> http://blog.solidsoft.info/ - Working code is not enough 
>

shell escaping

[teilo]

Is there a utility class anywhere that given an slave os will escape a 
command line?

I'm looking to fix JENKINS-14781 and could role my own solution - but I'm 
sure I would miss edge cases or not escape correctly so thought something 
may already exist somewhere.

I guess it needs to escape the following depending on platform

|  &  ;  <  >  (  )  $  `  \  "  '   *   ?   [   #   ˜   =   %  ^


/James

Re: CI for plugins

[teilo]

Hi Nicolas,

What accounts is this linked to?

I tried my github auth and grandcentral tells my my password is wrong 
(rather than my email is not recognised) - so I know I'm at least half 
registered...

 I 'm of course assuming that I haven't at some point used my personal 
email to register with CB, and I should be able to log in as there is a 
role "plugin-maintainers" :-)

/James

On Thursday, 18 October 2012 19:04:13 UTC+1, nicolas de loof wrote:
>
> Hi folks,
>
> I eventually completed setup 
> https://jenkins.ci.cloudbees.com/job/plugins/with a job for all plugins on 
> jenkinsci github. They all have been created 
> as maven jobs, so this won't make sense for ruby or gradle ones, just ping 
> me if you want to reconfigure with other build tools/rules. 
>
> github hooks are set to trigger a build on commit to master
>

Re: log messages from plugin doesn't reach system logger after restart of Jenkins

[teilo]

As a workaround
You can define the log level in a static file and configure java to
load that at startup.

Google logging.properties.

I have observed the same behaviour where a logger added in the yo is
lost on restart, I've never seen it kept and didn't think this was
even possible.

On Jul 4, 1:57 pm, Esben Rugbjerg  wrote:
> Hi,
>
> I have a problem where the logger messages from a plugin stops showing up
> in a the logger when Jenkins has been restarted.
>
> I am working on an SCM plugin. I have created a class where I instantiate a
> logger and use it in the methods:
>
> package dimtestplugin;
> ..
> import java.util.logging.Level;
> import java.util.logging.Logger;
> ...
> public class DimoScm extends SCM {
> .
> private static final Logger LOGGER =
> Logger.getLogger(DimoScm.class.getName());
> ...
> @Override
> public SCMRevisionState calcRevisionsFromBuild(AbstractBuild arg0,
> Launcher arg1, TaskListener arg2) throws IOException,
> InterruptedException {
>  DimRevisionState revisionState = new DimRevisionState();
> //Ask for the time stamp of the latest modification in the repos based on
> the path
> Date latestTimestamp = branch.getLastModificationDateByPath(path);
> ---> LOGGER.log(Level.FINE,"calcRevisionFromBuild - latestTimeStamp: " +
> latestTimestamp.toString());
>  revisionState.setTimeStampOfLastModification(latestTimestamp);
>  //return object containing the time stamp of the latest modification.
> return revisionState;
>
> }
> ...
> }
>
> In Jenkins I create a logger which is connected to the specific class
> 'dimtestplugin.DimoScm'. When I create the logger in Jenkins the generated
> log messages start appearing in the window. So far so good.
>
> Now, if I restart Jenkins the log messages stop appearing in the logger. If
> I then either create or delete a logger - it can be any of the loggers, it
> does not necessarily need to be related to my plugin, the messages start
> showing up again. I have created other loggers which for example logs
> messages from the Subversion plugin. These loggers doesn't stop working
> when I restart Jenkins.
>
> I really need this to work because I want to use the log for debugging, and
> I don't want to have to recreate the logger every time I have created a new
> version of my plugin and restarted Jenkins.
>
> Any help is much appreciated.
>
> Thank you.
> Esben

Re: Jenkins widely deletes downstream associations (Blocker issue)

[teilo]

Is that the correct issue? Your description doesn't seem to match the
issue described in jira.

On May 22, 4:04 pm, "Harry G." 
wrote:
> Dear all,
>
> could anyone please have a look at this 
> issue?https://issues.jenkins-ci.org/browse/JENKINS-13222
> It is really weird as when a user edits anything in any job, Jenkins
> deletes _all_ downstream job associations to all jobs this user has no
> access to inside _all_ jobs he even only has _read_ access and that have
> nothing to do with the job he edited!
> Sounds a bit confusing, but see a reproduceable example inside the issue.
> Thanks for looking!
>
>   Harry G.

Re: compiler errors hidden when building Maven project on Jenkins

[teilo]

> > I agree with Stephen that  the build should behave exactly the same on
> > a CI server as it does locally (otherwise when something goes wrong
> > you want to be able to reproduce it).
>
> > To be fair we are using checkstyle as an example but all Drulli's
> > plugin does is make sure if checkstyle is run that it produces an XML
> > output file (but still that possibly a change depending on how you
> > have configured checkstyle).
>
> > What I don't agree with is that its EVIL.
>
> > If a person A owns a gun shop and sells a gun to person B, and person
> > B then shoots person C - its person B that is EVIL not person
> > a )although person a may have been misguided) :-)
>
> > Anyway - I was thinking of seeing if I could wrap the
> > PlexusConfiguration and (dependeing on some setting) WARN in the build
> > logs that the build was changed (what mojo value was set) or WARN that
> > a mojo change was attempted but rejected.
>
> > So that would solve the two use cases - if you could then add a flag
> > to the Maven project (allow plugins to change the build behaviour)
> > that would toggle the behaviour between denying and warning.
>
> > WDYT?
>
> You can't make a silk purse out of a sow's ear...

So you are saying there are more fundamental issues with the maven job
type than the fact that the build can be different on the CI server vs
local machine?

> It ain't going to stop me writing the "Maven project type reloaded"
> plugin if that's what you are asking ;-)

Nope - I was going to open up eclipse and see what I could come up
with in a few hours of tinkering.

I thought if I could do the above it would help and prevent the "Maven
Job is evil".  I feel ultimately this is hurting jenkins because, if
you want CI and Maven (3+) and rule out the maven2 job type you may
well choose eclipse Hudson not Jenkins due to its reworked maven3
integration with freestyle jobs.
I'm not saying what I would come up with would be world class and I'm
sure someone with more Maven (and Jenkins) core knowledge could do
something fantastic - but they have either done it in Hudson - or
haven't got past the planning stage yet ;-P

(note not everyone has been able to move to Maven3 yet...)

But if nobody feels its worth (and hence won't get merged in) it I
wont put any effort in and will spend the time searching for wedding
venues instead :-)

Re: "Git On Windows with Jenkins" just doesn't work

[teilo]

a service will run on its own session context and will not have access
to things like mapped drives and must likely processes in other
sessions.

Use the ssh that comes with git and a public key with no password, and
secure that box and jobs running on it (or use a read only git user) .


On Feb 18, 12:24 am, Andrew Gray  wrote:
> Hi All,
>
> Git plugin frustrating...
>
> Environment: Windows 2003 SP2
> Jenkins 1.451 (running as a service under an administrative user, not a
> system account...i.e me)
>
> - Public key successfully uploaded to bitbucket
> - Public and private key copied to directories:
> 1. C:\documents and settings\\.ssh ; and
> 2. C:\Program Files\Git\.ssh
>
> - Trying to follow instructions 
> here:https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
>
> - Private key loaded into Pageant too.
>
> - When private key loaded into Pageant I CAN successfully run git clone
> g...@bitbucket.org:apgray/repository.git
>
> - Running ssh -T g...@bitbucket.org produces the following output:
> The authenticity of host 'bitbucket.org (207.223.240.181)' can't be
> established.
> RSA key fingerprint is 97:8c:1b:f2:6f:14:6b:5c:3b:ec:aa:46:46:74:7c:40.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'bitbucket.org,207.223.240.181' (RSA) to the
> list of known hosts.
> Permission denied (publickey).
>
> - known_hosts file is created which I copy to both the above directories so
> it is sitting with the public and private key.
>
> - GIT_SSH and Path environment variable are set as directed
>
> - Running plink bitbucket.org asks:
> login as:
>
> If I hit CTRL-C plink just exits and returns to the prompt
> If I enter apgray and hit Enter I get:
> FATAL ERROR: Disconnected: No supported authentication methods available
> (server sent: publickey)
>
> The above steps do not appear to have worked properly
>
> If I plow on in the vain hope that something worked and set up Jenkins to
> checkout from bitbucket
>
> Repository URL: g...@bitbucket.org:apgray/repository.git
> Name: leave blank
> Refspec: leave blank
> Branch Specifier: origin/master
>
> If I attempt a build this is what I get:
>
> Started by user Andrew Gray 
> Building on master in workspace D:\JenkinsHome\jobs\repository\workspace
> Checkout:workspace / D:\JenkinsHome\jobs\repository\workspace -
> hudson.remoting.LocalChannel@188665b
> Using strategy: Default
> Checkout:workspace / D:\JenkinsHome\jobs\repository\workspace -
> hudson.remoting.LocalChannel@188665b
> Cloning the remote Git repository
> Cloning repository origin
> ERROR: Error cloning remote repo 'origin' : Could not clone
> https://apg...@bitbucket.org/apgray/repository.githudson.plugins.git.GitException
> :
> Could not clone https://apg...@bitbucket.org/apgray/repository.git
>         at hudson.plugins.git.GitAPI.clone(GitAPI.java:245)
> 
>         at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1029)
> 
>         at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:970)
> 
>         at hudson.FilePath.act(FilePath.java:788)
> 
>         at hudson.FilePath.act(FilePath.java:770)
> 
>         at hudson.plugins.git.GitSCM.checkout(GitSCM.java:970)
> 
>         at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
> 
>         at 
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:576)
> 
>         at 
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465)
> 
>         at hudson.model.Run.run(Run.java:1409)
> 
>         at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 
>         at hudson.model.ResourceController.execute(ResourceController.java:88)
> 
>         at hudson.model.Executor.run(Executor.java:238)
> 
> Caused by: hudson.plugins.git.GitException
> :
> Error performing command: C:\Program Files\Git\bin\git.exe clone
> --progress -o ori

Re: compiler errors hidden when building Maven project on Jenkins

[teilo]

I agree with Stephen that  the build should behave exactly the same on
a CI server as it does locally (otherwise when something goes wrong
you want to be able to reproduce it).

To be fair we are using checkstyle as an example but all Drulli's
plugin does is make sure if checkstyle is run that it produces an XML
output file (but still that possibly a change depending on how you
have configured checkstyle).

What I don't agree with is that its EVIL.

If a person A owns a gun shop and sells a gun to person B, and person
B then shoots person C - its person B that is EVIL not person
a )although person a may have been misguided) :-)

Anyway - I was thinking of seeing if I could wrap the
PlexusConfiguration and (dependeing on some setting) WARN in the build
logs that the build was changed (what mojo value was set) or WARN that
a mojo change was attempted but rejected.

So that would solve the two use cases - if you could then add a flag
to the Maven project (allow plugins to change the build behaviour)
that would toggle the behaviour between denying and warning.

WDYT?


On Feb 16, 7:24 am, Stephen Connolly 
wrote:
> On Thursday, 16 February 2012, Jesse Farinacci  wrote:
> > Greetings,
>
> > On Wed, Feb 15, 2012 at 8:15 AM, Stephen Connolly
> >  wrote:
> >> IOW, the command shown on the console log will not behave the same if
> >> the user executes it themselves from the same directory as the same
> >> user.
>
> >> EVIL
>
> > I think there is some misunderstanding about what the point of the
> > Maven plugin is. It isn't simply to invoke Maven. It is to bind
> > Jenkins with Maven project in a reasonable way. Therefore, I think
> > your claim of EVIL is spurious.
>
> A reasonable way can be achieved that is not EVIL... I have been
> threatening to write an alternate maven project type since 2009... But
> other things keep getting in my way and sucking up my time... I think I
> have most of the shape of it in my head now, and it is probably more
> tractable than the coverage plugin problem...
>
> > If a Jenkins job requests checkstyle
> > reporting, then a Maven job type which ensures checkstyle is run is
> > the correct behavior.
>
> That is your view, but there is more than one way to skin a cat... What
> happens when I specifically don't want checkstyle reports from one sub
> module, but I want check style to run? SooL drop back to freestyle.
>
> > It will not be a complete match up to what
> > command lines were invoked for the build itself - it would be WRONG
> > for Jenkins not to have different behavior.
>
> Again, more than one way to skin a cat... It is wrong if running a Pom
> under a know command line and execution environment produces a different
> result... But then I would have to say that with my Apache Maven hat on.
>
>
>
> >> I have other issues with the Maven Project type. but "Modifying the
> >> effective pom" is the most evil one of all
>
> > I'm not sure if these two are roughly the same.
>
> Well I use the term "modifying the effective Pom" to cover all those class
> of changes where the maven project type modifies the effective build, the
> checkstyle changes, the test failure changes, etc
>
>
>
> > Again, your attack against Maven job type is highly suspicious to me.
>
> Where do you think I am coming from? I think it is well known that I love
> Jenkins as a CI engine and Maven as a build tool... So if you think I don't
> like the project type out of some dislike for Jenkins, I believe you are
> mistaken.
>
> I see KK as a friend, as well as a colleague and a supreme coder (doesn't
> stop the two of us from disagreeing... And all developers fight like cats
> ;-) ), so if you think I am attacking KK, again I believe you are mistaken
>
> > Most times, when I see someone having a problem with a Jenkins Maven
> > build it is (like you observed) a Maven problem.
>
> Not so much a maven problem, but a Pom problem, or a settings problem, or a
> "I faught the maven and the maven won" problem... All closely related to
> "it works on my machine"
>
> > Of the remaining
> > ones, I also ask them to try it as a Freestyle job type, but I go
> > further than you (I think)
>
> You think wrong, I ask that too
>
> > in that I request they pass the effective
> > command line flags which would have been invoked by all the
> > configuration options which they have enabled (e.g. Checkstyle) for
> > their Maven job type. The majority of these times are still broken!
>
> I have a different experiential history
>
> > That is, the Freestyle job type is not a magic solution, it is almost
> > always a misunderstanding by the user of what is actually going on
> > during the build.
>
> And understanding what is going on during the build is made a lot harder by
> the maven project type BECAUSE it hides the changes it makes... so people's
> understanding of how maven works becomes impaired, hence EVIL ;-) [but that
> could be my own personal biases since I wear a maven hat too]
>
>
>
> > I think the Jenkins Maven support

Re: Jenkins User Conference & T-Shirts

[teilo]

But you are missing  string of onions/Garlic around his neck to meet
all
the stereotypes :-)

On Feb 14, 8:30 am, nicolas de loof  wrote:
> +1 for butler drinking a glass of wine at a café
>
> I'd suggest to replace what looks like a hot-dog on the table with a
> baguette  or a
> croissant,
> and put an old citroën 2CV
> on his back, so that
> the image show all stereotypes for french guys :P
>
> 2012/2/14 Andrew Gray 
>
>
>
> > Chef +1
>
> > On Tuesday, February 14, 2012, Alyssa Tong  wrote:
> > > Hi All,
> > > I'm chair organizer for Jenkins User Conference. I work with KK at
> > CloudBees. We have 4 JUCs planned for this year: Paris, NY, SF, Antwerp.
> > > JUC attendees will be receiving Jenkins t-shirts this year. I would love
> > to get the community's feedback on the designs (attached).
> > > Pls let me know which ones you like, don't like and or your ideas to
> > alter the images.  I would love to have 4 different images to represent the
> > 4 JUC locations.
> > > We do not have to use any of the attached images so  if you have other
> > ideas or suggestions pls send it my way. So far my designer has been
> > stumped on Mr. Jenkins for Antwerp and SF.
> > > And if there are suggestions on what you'd like to see at the conf (i.e
> > more of workshop, hackathon, etc)..pls let me know. We want to make the
> > event
> > > successful and worthwhile for everyone.  Any other suggestions for
> > successful JUC is greatly appreciated.
> > > kind regards,
> > > alyssa