[JIRA] (JENKINS-16622) NPE while creating new job as copy of existing maven job

2013-02-09 Thread rino.kad...@qiy.nl (JIRA)














































Rino
 commented on  JENKINS-16622


NPE while creating new job as copy of existing maven job















Same here



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-15882) rebuild plugin should not store non-stored password parameter

2013-01-31 Thread rino.kad...@qiy.nl (JIRA)















































Rino
 assigned  JENKINS-15882 to Rino



rebuild plugin should not store non-stored password parameter
















Change By:


Rino
(31/Jan/13 10:03 AM)




Assignee:


ragesh_nair
Rino



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2013-01-31 Thread rino.kad...@qiy.nl (JIRA)















































Rino
 resolved  JENKINS-9211 as Fixed


Rebuild Plugin does not work for Subversion List Parameter
















Change By:


Rino
(31/Jan/13 10:18 AM)




Status:


Open
Resolved





Assignee:


ragesh_nair





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)














































Rino
 updated  JENKINS-16473


Build Pipeline View stops working after upgrading to Jenkins 1.499
















Change By:


Rino
(29/Jan/13 9:17 AM)




Priority:


Major
Critical



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)














































Rino
 updated  JENKINS-16473


Build Pipeline View stops working after upgrading to Jenkins 1.499
















Change By:


Rino
(29/Jan/13 9:17 AM)




Environment:


OS:FreeBSD7.2Jenkins:1.499
,1.500



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)














































Rino
 commented on  JENKINS-16473


Build Pipeline View stops working after upgrading to Jenkins 1.499















Log shows the following warning:

Jan 28, 2013 11:30:16 AM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: from.getBuildPipelineForm() in /jenkins/view/Pipeline_Core/. Reason: java.lang.IllegalArgumentException: Map must not be null
java.lang.IllegalArgumentException: Map must not be null
at org.apache.commons.collections.map.AbstractMapDecorator.init(AbstractMapDecorator.java:63)
at org.apache.commons.collections.map.UnmodifiableMap.init(UnmodifiableMap.java:73)
at org.apache.commons.collections.map.UnmodifiableMap.decorate(UnmodifiableMap.java:62)
at org.jenkinsci.lib.envinject.EnvInjectAction.getEnvMap(EnvInjectAction.java:41)
at org.jenkinsci.plugins.envinject.EnvInjectBuildVariableContributor.buildVariablesFor(EnvInjectBuildVariableContributor.java:30)
at hudson.model.AbstractBuild.getBuildVariables(AbstractBuild.java:1049)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:90)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.getBuildPipelineForm(BuildPipelineView.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at 

[JIRA] (JENKINS-16473) Build Pipeline View stops working after upgrading to Jenkins 1.499

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)












































 
Rino
 edited a comment on  JENKINS-16473


Build Pipeline View stops working after upgrading to Jenkins 1.499
















In our case the pipeline view was empty.
Log shows the following warning:

Jan 28, 2013 11:30:16 AM hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: from.getBuildPipelineForm() in /jenkins/view/Pipeline_Core/. Reason: java.lang.IllegalArgumentException: Map must not be null
java.lang.IllegalArgumentException: Map must not be null
at org.apache.commons.collections.map.AbstractMapDecorator.init(AbstractMapDecorator.java:63)
at org.apache.commons.collections.map.UnmodifiableMap.init(UnmodifiableMap.java:73)
at org.apache.commons.collections.map.UnmodifiableMap.decorate(UnmodifiableMap.java:62)
at org.jenkinsci.lib.envinject.EnvInjectAction.getEnvMap(EnvInjectAction.java:41)
at org.jenkinsci.plugins.envinject.EnvInjectBuildVariableContributor.buildVariablesFor(EnvInjectBuildVariableContributor.java:30)
at hudson.model.AbstractBuild.getBuildVariables(AbstractBuild.java:1049)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:90)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.ProjectForm.init(ProjectForm.java:84)
at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.getBuildPipelineForm(BuildPipelineView.java:356)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258)
at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104)
at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81)
at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at 

[JIRA] (JENKINS-14905) Make Rebuild button available for builds before plugin installation time

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)















































Rino
 resolved  JENKINS-14905 as Fixed


Make Rebuild button available for builds before plugin installation time
















Change By:


Rino
(29/Jan/13 10:10 AM)




Status:


Open
Resolved





Assignee:


ragesh_nair





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-14387) Cause of rebuilt job should be Cause.UserIdCause

2013-01-29 Thread rino.kad...@qiy.nl (JIRA)















































Rino
 resolved  JENKINS-14387 as Fixed


Cause of rebuilt job should be Cause.UserIdCause
















Change By:


Rino
(29/Jan/13 10:11 AM)




Status:


Open
Resolved





Assignee:


ragesh_nair





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-13644) Rebuild plugin can't rebuild when using parameters specified by copyartifact

2013-01-07 Thread rino.kad...@qiy.nl (JIRA)















































Rino
 assigned  JENKINS-13644 to Rino



Rebuild plugin cant rebuild when using parameters specified by copyartifact
















Change By:


Rino
(07/Jan/13 10:26 AM)




Assignee:


ragesh_nair
Rino



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13358) Timeout not working

2012-12-18 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 commented on  JENKINS-13358


Timeout not working















We had to do the following to remove jobs from the queue:

download the jenkins command line interface from your buildserver: http://yourbuildserver/jenkins/cli

java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ login --username yourusername --password yourpassword

java -jar jenkins-cli.jar -s http://yourbuildserver/jenkins/ delete-builds Name_Of_Job Build_Number_You_Want_To_Delete



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-16006) Re Deploy the previous artifact into weblogic servers

2012-12-13 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 commented on  JENKINS-16006


Re Deploy the previous artifact into weblogic servers















If you want to rebuild from source you could use the /path/to/source@revision to indicate the revision you would like to checkout and build. Or, in case you created a tag you could checkout the tag. If you want to deploy the result of the build you should create a separate (parameterized) project to deploy the artifacts. This separate build could pull the artifacts from a repository (e.g. Nexus) or use https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin to copy from another jenkins project.

You could use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin to create a nice view of your build chain. If you select "Always allow manual trigger on pipeline steps" you will see a green rebuild icon on all builds. This will allow you to continue building at any point in the pipeline.

Assuming that your artifacts are still in the repository and you created a separate project to deploy your artifacts, you could simply use the rebuild plugin to pull the artifacts from your repository and deploy those to your weblogic server.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-16006) Re Deploy the previous artifact into weblogic servers

2012-12-13 Thread rino.kad...@qiy.nl (JIRA)















































Rino Kadijk
 resolved  JENKINS-16006 as Not A Defect


Re Deploy the previous artifact into weblogic servers
















This is a question





Change By:


Rino Kadijk
(13/Dec/12 12:57 PM)




Status:


Open
Resolved





Assignee:


ragesh_nair





Resolution:


NotADefect



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2012-09-23 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 updated  JENKINS-9211


Rebuild Plugin does not work for Subversion List Parameter
















Improved patch to be more in line with the existing param copying.





Change By:


Rino Kadijk
(23/Sep/12 1:09 PM)




Attachment:


JENKINS-9211_20120923.patch



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2012-09-23 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 updated  JENKINS-9211


Rebuild Plugin does not work for Subversion List Parameter
















Change By:


Rino Kadijk
(23/Sep/12 1:12 PM)




Attachment:


rebuild.hpi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-14748) Rebuild plugin throws JellyTagException after upgrade to 477

2012-09-23 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 updated  JENKINS-14748


Rebuild plugin throws JellyTagException after upgrade to 477
















I attached a snapshot build with a ListSubversionTagsParameterValue.jelly included. Could you please test if this resolves the issue?





Change By:


Rino Kadijk
(23/Sep/12 1:36 PM)




Attachment:


rebuild.hpi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2012-09-05 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 updated  JENKINS-9211


Rebuild Plugin does not work for Subversion List Parameter
















patch attached





Change By:


Rino Kadijk
(05/Sep/12 8:16 AM)




Attachment:


JENKINS-9211-_Rebuild_Plugin_does_not_work_for_Subversion_List_Parameter.patch



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2012-09-04 Thread rino.kad...@qiy.nl (JIRA)












































 
Rino Kadijk
 edited a comment on  JENKINS-9211


Rebuild Plugin does not work for Subversion List Parameter
















Patched rebuilder plugin (see attachment) to pick up the Tag and Repository URL.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-9211) Rebuild Plugin does not work for Subversion List Parameter

2012-09-04 Thread rino.kad...@qiy.nl (JIRA)














































Rino Kadijk
 updated  JENKINS-9211


Rebuild Plugin does not work for Subversion List Parameter
















Patched rebuilder plugin to pick up the Tag and Repository URL.





Change By:


Rino Kadijk
(04/Sep/12 1:25 PM)




Attachment:


rebuild.hpi



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira