pull request for Debian package

2013-08-23 Thread Peter Eisentraut 
As per instructions in the wiki, I would like to draw attention to my pull 
request that's been open for a long time:

https://github.com/jenkinsci/jenkins/pull/591

It's a small tweak on the Debian packaging.

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

releasing plugin to jenkins-ci.org

2013-08-23 Thread Joachim Rodrigues 
I have created ssh keys with this tutorial : 
https://help.github.com/articles/generating-ssh-keys

And followed this tutotial 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

I'm in the case that i have different login/password  for my GitHub and 
jenkins-ci.org accounts i added in the settings.xml file 


> 
>   maven.jenkins-ci.org 
>jenkins-ci.org account name  
>jenkins-ci.org account pass 
> 
> 
>   


and stared an ssh agent ans imported the generated key 

eval `ssh-agent`
> ssh-add  /Users/joachimrodrigues/.ssh/id_rsa


but when trying to release i always get this error : 

ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.2.2:prepare (default-cli) 
> on project graphiteIntegrator: Unable to tag SCM
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] Permission denied (publickey).
> [ERROR] fatal: The remote end hung up unexpectedly
> [ERROR] -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
> -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, 
> please read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException



somebody has already met this error ?

Thanks

-- 
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: Not able to bind json data to object when the variables are dynamic in jenkins plugin

2013-08-23 Thread swastb 
no issues at all ..im glad that someone replied.. :)

On Friday, 23 August 2013 19:18:26 UTC+5:30, Ikedam wrote:
>
> Sorry for annoying you.
>
> There seems something wrong with Google Groups, posts from iPhone get 
> delayed (suspended?), and mails are delivered twice in this topic.
> I wish this post won't be delivered twice...
>
>

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

disable checkpointing at a global level

2013-08-23 Thread Surya Gaddipati 

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

comparing build to a previous build doesnt make any sense in scenarios 
where people are working on their branches and pushing code. It doesnt make 
sense to compare branch A to branch B to  see how test coverage change.

There are tons of plugins which block on checkpoint, it would be nice to 
get rid of this horrid checkpointing behavior through a global option or 
something. 


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

Disable checkpoint globally

2013-08-23 Thread Surya Gaddipati 
We use git with lots of branches and the whole idea of waiting for previous 
builds to calculate diffs doesnt make much sense( makes no sense to compare 
branch x to some unrelated branch y). 
Is there a way to disable this checkpoint business?

Checkpoints have been bane of our jenkin's existence, we have builds 
running for hours/days because they are blocked on checkpoints.

https://issues.jenkins-ci.org/browse/JENKINS-9913?focusedCommentId=184112


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

2013-08-23 Thread 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?

2013-08-23 Thread nicolas de loof 
fixed.
I'm not used with Intellij license header tooling, expected it to
automagically update everything


2013/8/23 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.
>

-- 
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: AggregatedTestResult inconsistencies/problems

2013-08-23 Thread Stefan Wolf 
The pull request is now https://github.com/jenkinsci/jenkins/pull/916.

Am Freitag, 23. August 2013 15:41:15 UTC+2 schrieb Stefan Wolf:
>
> Hi,
>
> after trying to use the feature "Aggregate Downstream Test Results", i.e. 
> the AggregatedTestResultPublisher, I ran into some problems. The main 
> problem is fixed by my pull request 
> https://github.com/jenkinsci/jenkins/pull/915, namely that clicking the 
> "Latest Test Result" link on the Project page does not return a 404 
> anymore. I tried to document the current behaviour of the feature with a 
> "Unit" test: 
> https://github.com/wolfs/jenkins/blob/aggregate-test-result/test/src/test/java/hudson/tasks/test/AggregatedTestResultPublisherTest.java
> .
> When merging this pull request the behaviour is:
> 1. Only aggregated test results:
> - On the project page there is a link with name "Latest Test Result" which 
> goes to the aggregated test result page on the corresponding build
> 2. Only test results:
> - On the project page there is a link with name "Latest Test Result" which 
> goes to the test result page of the corresponding build
> 3. Aggregated test results and test results
> - On the project page there is a link with name "Latest Test Result" which 
> goes to the test result page of the corresponding build
>
> Moreover, there is not test result trend for the aggregated test result 
> action.
> My proposal how to make this consistent would be:
> - If the link on the project page goes to the aggregated test result page 
> then it should be named "Latest Aggregated Test Result"
> - If there are test results and aggregated test results then there should 
> be two links, one name "Latest Test Result" and one named "Latest 
> Aggregated Test Result"
> - There should be a Trend for the aggregated test results on the project 
> page
>
> If there are no objections, then I would go forward implementing this.
>
> For the implementation I would like to get some suggestions:
> - Would it make sense if the TestResult from the 
> AggregatedTestResultPublisher would extend AggregatedTestResult?
> - In the current implementation there is a method 
> 'getAggregatedTestResultAction' on the AbstractBuild class which never 
> yields the TestResult of the AggregatedTestResultPublisher. The 
> AggregatedTestResultAction yielded from this method has the urlName 
> 'testResult'. The TestResultAction of the AggregatedTestResultPublisher is 
> not an AggregatedTestResultAction and has the urlName 
> 'aggregatedTestResult'. Therefore, the old implementation on main.jelly on 
> AbstractProject did not really make sense to me:
>   
> 
>   
> 
>   ${%Latest Test Result}
>   
> 
>   
> 
>
>  value="${it.lastCompletedBuild.aggregatedTestResultAction}"/>
> 
>   
>  class="model-link inside">${%Latest Aggregated Test Result}
> 
>   
> 
> Should the UI use getAction with the corresponding classes?
> - This main.jelly should not be used from any of the classes using the 
> AggregatedTestResultAction (MavenModuleSet, MatrixProject). Is this 
> correct? So can I just change the jelly file without breaking anything?
> - What do I have to do in order to add the Trend Report for the aggregated 
> test result to the project page?
>
> Thank you for reading to the end,
> Stefan
>

-- 
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: Not able to bind json data to object when the variables are dynamic in jenkins plugin

2013-08-23 Thread Ikedam 
Sorry for annoying you.

There seems something wrong with Google Groups, posts from iPhone get 
delayed (suspended?), and mails are delivered twice in this topic.
I wish this post won't be delivered twice...

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

AggregatedTestResult inconsistencies/problems

2013-08-23 Thread Stefan Wolf 
Hi,

after trying to use the feature "Aggregate Downstream Test Results", i.e. 
the AggregatedTestResultPublisher, I ran into some problems. The main 
problem is fixed by my pull 
request https://github.com/jenkinsci/jenkins/pull/915, namely that clicking 
the "Latest Test Result" link on the Project page does not return a 404 
anymore. I tried to document the current behaviour of the feature with a 
"Unit" 
test: 
https://github.com/wolfs/jenkins/blob/aggregate-test-result/test/src/test/java/hudson/tasks/test/AggregatedTestResultPublisherTest.java.
When merging this pull request the behaviour is:
1. Only aggregated test results:
- On the project page there is a link with name "Latest Test Result" which 
goes to the aggregated test result page on the corresponding build
2. Only test results:
- On the project page there is a link with name "Latest Test Result" which 
goes to the test result page of the corresponding build
3. Aggregated test results and test results
- On the project page there is a link with name "Latest Test Result" which 
goes to the test result page of the corresponding build

Moreover, there is not test result trend for the aggregated test result 
action.
My proposal how to make this consistent would be:
- If the link on the project page goes to the aggregated test result page 
then it should be named "Latest Aggregated Test Result"
- If there are test results and aggregated test results then there should 
be two links, one name "Latest Test Result" and one named "Latest 
Aggregated Test Result"
- There should be a Trend for the aggregated test results on the project 
page

If there are no objections, then I would go forward implementing this.

For the implementation I would like to get some suggestions:
- Would it make sense if the TestResult from the 
AggregatedTestResultPublisher would extend AggregatedTestResult?
- In the current implementation there is a method 
'getAggregatedTestResultAction' on the AbstractBuild class which never 
yields the TestResult of the AggregatedTestResultPublisher. The 
AggregatedTestResultAction yielded from this method has the urlName 
'testResult'. The TestResultAction of the AggregatedTestResultPublisher is 
not an AggregatedTestResultAction and has the urlName 
'aggregatedTestResult'. Therefore, the old implementation on main.jelly on 
AbstractProject did not really make sense to me:
  

  

  ${%Latest Test Result}
  

  




  
${%Latest Aggregated Test Result}

  

Should the UI use getAction with the corresponding classes?
- This main.jelly should not be used from any of the classes using the 
AggregatedTestResultAction (MavenModuleSet, MatrixProject). Is this 
correct? So can I just change the jelly file without breaking anything?
- What do I have to do in order to add the Trend Report for the aggregated 
test result to the project page?

Thank you for reading to the end,
Stefan

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

2013-08-23 Thread 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: Plugin Installation trend not updated on the Jenkins wiki

2013-08-23 Thread James Nord (jnord) 
You are finally writing your Maven+ plugin :-P


(I'm probably going to have to drop into stealth mode as well to get the 
*exciting new stuff* done enough to push out a new set of OSS plugins for 
Jenkins... Deadlines! )



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