from:"b...@java.net $JIRA$"















































bap
 updated  JENKINS-15841


tried to access method hudson.model.AbstractBuild.setBuiltOnStr(Ljava/lang/String;)V
















Change By:


bap
(10/Feb/13 11:22 PM)




Assignee:


bap





Component/s:


maven





Component/s:


any-buildstep



























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-16743) Please show warning if typed-in file is not found or found in different case
















































bap
 assigned  JENKINS-16743 to bap



Please show warning if typed-in file is not found or found in different case
















Change By:


bap
(10/Feb/13 11:28 PM)




Assignee:


AlexEarl
bap



























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-16743) Please show warning if typed-in file is not found or found in different case















































bap
 commented on  JENKINS-16743


Please show warning if typed-in file is not found or found in different case















IMO this would be a very poor addition to the plugin.

There is only one special case where the user would benefit - at all other times, it would just be meaningless.

The only time that the files would match is - 1) if the jobs build on the master jenkins server and 2) the job has already been build at least once, and the workspace is still present.

Jobs are usually configured before they are executed.
If a user uses slaves, then this would always report an error.
The Source files pattern can use tokens to locate files eg $BUILD_NUMBER these would never resolve successfully at validation time.

Checking for the existence of files in a workspace when configuring a job is just a very bad idea.



























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-16743) Please show warning if typed-in file is not found or found in different case
















































bap
 resolved  JENKINS-16743 as Wont Fix


Please show warning if typed-in file is not found or found in different case
















Change By:


bap
(10/Feb/13 11:39 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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-16742) Let user pick source file and target folder
















































bap
 resolved  JENKINS-16742 as Wont Fix


Let user pick source file and target folder
















See JENKINS-16743 for most of the reasons.

In addition, the remote folder is created if it does not exist - this is to enable build variables in the folder name, such as $BUILD_NUMBER, $JOB_NAME or even using the build date to create the remote folder name.





Change By:


bap
(10/Feb/13 11:43 PM)




Status:


Open
Resolved





Assignee:


AlexEarl
bap





Resolution:


WontFix



























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-16739) Can't strip **/
















































bap
 resolved  JENKINS-16739 as Not A Defect


Cant strip **/
















Remove prefix will remove a String from the start of all source files that have been selected - it does not support expressions or patterns





Change By:


bap
(10/Feb/13 11:50 PM)




Status:


Open
Resolved





Assignee:


AlexEarl
bap





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







-- 
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-4819) Enable/disable build step by one click

2013-01-11 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-4819


Enable/disable build step by one click















https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin

Use the condition "Always" to enable and "Never" to disable.



























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-16149) Ability to match multiple Policies

2012-12-17 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-16149


Ability to match multiple Policies















Have you tried adding the build step twice by using the https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin ?

I have not tried it, but it should "just work".



























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-14475) Conditional build steps should be available as post-build actions

2012-12-17 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-14475


Conditional build steps should be available as post-build actions















cjo fixed issue 12418 by adding run conditions to the parameterized trigger. This means that you should be able to add the parameterized trigger step directly (without Flexible Publish) and selecting the run condition within the Parameterized Trigger step



























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-15954) [RTC Plugin] NullPointerException

2012-11-28 Thread b...@java.net (JIRA)















































bokc
 created  JENKINS-15954


[RTC Plugin] NullPointerException















Issue Type:


Bug



Affects Versions:


current



Assignee:


Deluan Quintão



Components:


rtc



Created:


28/Nov/12 3:17 PM



Description:


$ scm accept -u  -P  -d D:\Jenkins\jobs\RTC-Artemis-Main-HSQL\workspace -s "Main Artemis Dev" --flow-components -o -v -c 8244 8246

Espace de travail inchangé.

FATAL: null
java.lang.NullPointerException
	at com.deluan.jenkins.plugins.rtc.changelog.JazzChangeSet.copyItemsFrom(JazzChangeSet.java:150)
	at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:112)
	at com.deluan.jenkins.plugins.rtc.JazzSCM.checkout(JazzSCM.java:104)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1324)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
	at hudson.model.Run.execute(Run.java:1518)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)




Environment:


RTC V4.0.0.1




Project:


Jenkins



Labels:


plugin
scm
rtc




Priority:


Blocker



Reporter:


bokc

























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-15689) send files or execute commands over ssh option not showing in promotion actions menu

2012-11-01 Thread b...@java.net (JIRA)
















































bap
 resolved  JENKINS-15689 as Not A Defect


send files or execute commands over ssh option not showing in promotion actions menu
















It is listed as "Send build artifacts over SSH"

See https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+...#PublishOver...-Promotions for more details about publish over plugins and promotions





Change By:


bap
(01/Nov/12 11:29 AM)




Status:


Open
Resolved





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-15694) Wiki displaying old pages (not updating cache after edits)

2012-11-01 Thread b...@java.net (JIRA)















































bap
 created  JENKINS-15694


Wiki displaying old pages (not updating cache after edits)















Issue Type:


Bug



Assignee:


Unassigned


Components:


infrastructure



Created:


01/Nov/12 11:59 AM



Description:


Wiki is serving old versions of pages.

Page:
https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+...

Page info displayed (cached):
Added by Bap bap2000, last edited by Bap bap2000 on Sep 10, 2012  (view change)

Current (after clicking on view changes):
Current by Bap bap2000 on Oct 22, 2012 14:14. 




Project:


Jenkins



Priority:


Major



Reporter:


bap

























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-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin

2012-10-31 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-13230


Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin















@chanti I have no idea what you mean by "natural" environment variables

Your output example looks like it is entirely to do with recursive resolution (JENKINS-14340) and I can't see the connection with this issue which is to do with the EnvInject plugin.



























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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist

2012-10-26 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they dont exist















From above: "Install the flexible publish plugin and use the file exists or the files match run condition"

Put the files that you want to archive in the run condition (File exists or Files match), it will then only run "Archive the artifacts" if those files are found.

https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin



























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-15590) Publisher should have an option to always run even if the build failed
















































bap
 closed  JENKINS-15590 as Wont Fix


Publisher should have an option to always run even if the build failed
















Change By:


bap
(22/Oct/12 2:26 PM)




Status:


Resolved
Closed



























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-15590) Publisher should have an option to always run even if the build failed
















































bap
 resolved  JENKINS-15590 as Wont Fix


Publisher should have an option to always run even if the build failed
















Use "Send files or execute commands over SSH after the build runs"

https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+SSH+Plugin#PublishOverSSHPlugin-wrappers





Change By:


bap
(22/Oct/12 2:25 PM)




Status:


Open
Resolved





Resolution:


WontFix



























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-14693) Conditional BuildStep Fails Build with NullPointerException
















































bap
 closed  JENKINS-14693 as Cannot Reproduce


Conditional BuildStep Fails Build with NullPointerException
















Change By:


bap
(22/Oct/12 2:27 PM)




Status:


Resolved
Closed



























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-13831) Need a way to copy empty directories with Publish Over SSH Plugin
















































bap
 closed  JENKINS-13831 as Fixed


Need a way to copy empty directories with Publish Over SSH Plugin
















Change By:


bap
(22/Oct/12 2:29 PM)




Status:


Resolved
Closed



























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-13126) Create empty directories on remote server
















































bap
 closed  JENKINS-13126 as Fixed


Create empty directories on remote server
















Change By:


bap
(22/Oct/12 2:29 PM)




Status:


Resolved
Closed



























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-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin















































bap
 commented on  JENKINS-13230


Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin















IMO this is a fundamental design problem

Without EnvInject, the build environment can be accessed directly.

If someone installs EnvInject then it "hijacks" the environment variables and moves them to its own action - they are no longer available directly from the build object.

This requires every plugin to code for the existence of an optional plugin if it wants to be able to access the environment variables that the EnvInject plugin has moved.

@gbois is there some method in core that can be called to access the variables that EnvInject would contribute to so that this dependency can be broken?



























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-4214) Disable Execute Shell

2012-10-17 Thread b...@java.net (JIRA)















































bap
 commented on  JENKINS-4214


Disable Execute Shell















Use the Conditional BuildStep plugin with Run condition Always.
Switch to Never to temporarily disable, then back to Always to enable it again.



























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-15445) DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor

2012-10-10 Thread b...@java.net (JIRA)

bap
reopened JENKINS-15445

DefaultBuilderDescriptorLister should not check buildstep class for @DataBoundConstructor

The history is not in this plugin because the code was copied from the Flexible Publish plugin.

The original check is both necessary - and not aggressive enough. The descriptors should be filtered for those with newInstance methods too. Some plugins appear to have both DBC and newInstance!

The reason they need to be filtered is that the Flexible publish creates instances using a data bound constructor. Any instances of build step that are contained within will fail to be configured corectly if it uses configuration from the form and also uses newInstance.

100% of buildsteps I tested which used newInstance failed to be correctly configured when the form was submitted.*

The descriptor listers are used to enable publishers as build steps and build steps as publishers (using the Any Build Step plugin). For this reason, build steps returned need to be configurable using both configuration mechanisms.

If you believe that the newInstance will be correctly configured when contained within a DBC configured container, please add a unit test to the Any Build Step plugin showing successful configuration submission of a newInstance configured buildstep (builder) inside the Flexible Publish publisher.

Maybe I've missed something, and you can help me undestand, but like I said, I did not find a single build step that configured correctly when using newInstance.

Change By:

bap
(10/Oct/12 9:34 AM)

Resolution:

Fixed

Status:

Resolved
Reopened

Assignee:

domi
NicolasDeLoof

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-13920) Provide an option whether or not fail the build on artifact archiving not finding any artifacts















































bap
 commented on  JENKINS-13920


Provide an option whether or not fail the build on artifact archiving not finding any artifacts















Install the flexible publish plugin and use the file exists or the files match run condition



























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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist















































bap
 commented on  JENKINS-10502


Add an option to make archiving the artifacts non-fatal if they dont exist















Install the flexible publish plugin and use the file exists or the files match run condition



























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-13920) Provide an option whether or not fail the build on artifact archiving not finding any artifacts
















































bap
 closed  JENKINS-13920 as Fixed


Provide an option whether or not fail the build on artifact archiving not finding any artifacts
















duplicate





Change By:


bap
(17/Sep/12 2:16 PM)




Status:


Open
Closed





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

[JIRA] (JENKINS-13920) Provide an option whether or not fail the build on artifact archiving not finding any artifacts















































bap
 reopened  JENKINS-13920


Provide an option whether or not fail the build on artifact archiving not finding any artifacts
















Change By:


bap
(17/Sep/12 2:17 PM)




Resolution:


Fixed





Status:


Closed
Reopened



























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-13920) Provide an option whether or not fail the build on artifact archiving not finding any artifacts
















































bap
 closed  JENKINS-13920 as Duplicate


Provide an option whether or not fail the build on artifact archiving not finding any artifacts
















Change By:


bap
(17/Sep/12 2:18 PM)




Status:


Reopened
Closed





Resolution:


Duplicate



























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-15203) rsync (over ssh)
















































bap
 closed  JENKINS-15203 as Wont Fix


rsync (over ssh)
















An rsync plugin would be excellent - but that has nothing to do with this plugin.





Change By:


bap
(17/Sep/12 5:31 PM)




Status:


Open
Closed





Resolution:


WontFix



























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-14721) 500 error switching to Pegdown
















































bap
 closed  JENKINS-14721 as Fixed


500 error switching to Pegdown
















Change By:


bap
(13/Sep/12 10:03 AM)




Status:


Resolved
Closed



























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-14283) Publish Over FTP - as Build Step
















































bap
 closed  JENKINS-14283 as Fixed


Publish Over FTP - as Build Step
















Change By:


bap
(13/Sep/12 10:04 AM)




Status:


Resolved
Closed



























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-14068) Mark build unstable does not work
















































bap
 closed  JENKINS-14068 as Not A Defect


Mark build unstable does not work
















Change By:


bap
(13/Sep/12 10:05 AM)




Status:


Resolved
Closed



























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-13693) Add DefaultExcludes boolean option to transfer set
















































bap
 closed  JENKINS-13693 as Fixed


Add DefaultExcludes boolean option to transfer set
















Change By:


bap
(13/Sep/12 10:06 AM)




Status:


Resolved
Closed



























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-13795) NPE with Flexible Publisher job
















































bap
 closed  JENKINS-13795 as Fixed


NPE with Flexible Publisher job
















Change By:


bap
(13/Sep/12 10:05 AM)




Status:


Resolved
Closed



























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-14514) Repeatable jelly tag appears to be broken in 1.474+















































bap
 updated  JENKINS-14514


Repeatable jelly tag appears to be broken in 1.474+
















Change By:


bap
(23/Jul/12 11:13 AM)




Summary:


PublishOverSSH(
Repeatablejellytagappearstobebrokenin
1.
7)cannotworkatJenkinsver.1.
474
+





Assignee:


Slide-O-Mix





Component/s:


core





Component/s:


gui





Component/s:


publish-over-cifs





Component/s:


publish-over-ftp





Component/s:


publish-over-ssh





Component/s:


adaptiveplugin



























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-14514) Repeatable jelly tag appears to be broken in 1.474+
















































bap
 assigned  JENKINS-14514 to Kohsuke Kawaguchi



Repeatable jelly tag appears to be broken in 1.474+
















Change By:


bap
(23/Jul/12 11:17 AM)




Assignee:


Slide-O-Mix
KohsukeKawaguchi



























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-14514) Repeatable jelly tag appears to be broken in 1.474+















































bap
 commented on  JENKINS-14514


Repeatable jelly tag appears to be broken in 1.474+















The repeatable blocks fail to display when using jenkins 1.474 onwards (possibly due to the modular js and the use of adjunct)

https://github.com/jenkinsci/publish-over-ftp-plugin/blob/2bba237f3deaac9eb543f6312d038a711f7f2862/src/main/resources/jenkins/plugins/publish_over_ftp/BapFtpPublisherPlugin/config.jelly behaves correctly on 1.388 - 1.473



























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-14536) Jenkins logo in JIRA is served using http resulting in a security warning for every page load















































bap
 created  JENKINS-14536


Jenkins logo in JIRA is served using http resulting in a security warning for every page load















Issue Type:


Bug



Assignee:


Unassigned


Components:


infrastructure



Created:


23/Jul/12 6:09 PM



Description:


When using the jenkins jira instance (using https) every page load results in a warning from the web browser as the logo is served over HTTP




Environment:


Any modern web browser




Project:


Jenkins



Priority:


Major



Reporter:


bap

























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-14340) Remote directory of a Transfer Set should resolve env variable more than once















































bap
 commented on  JENKINS-14340


Remote directory of a Transfer Set should resolve env variable more than once















This is non trivial due to the way variables are currently resolved in the publish over plugins.

I will look into it at some point, and see if the token macro plugin can be used to resolve variables without affecting the current behaviour.



























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-14514) Repeatable jelly tag appears to be broken in 1.474+















































bap
 commented on  JENKINS-14514


Repeatable jelly tag appears to be broken in 1.474+















Another candidate is the change to prevent ajax calls when the page is not visible.

I cannot find anything else in the changes from 1.473 to 1.474 that may have introduced this issue



























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-14294) Action List is empty when adding Post-Build Action

2012-07-03 Thread b...@java.net (JIRA)
















































bap
 resolved  JENKINS-14294 as Duplicate


Action List is empty when adding Post-Build Action
















Change By:


bap
(03/Jul/12 9:02 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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-14068) Mark build unstable does not work

2012-06-11 Thread b...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-14068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163734#comment-163734
 ] 

bap commented on JENKINS-14068:
---

Yes, that is correct.

Oops, sorry - Fail the build is a builder. You can use it by installing the 
https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin and enabling 
Any build step for the Flexible publisher in the main Jenkins configuration.

 Mark build unstable does not work
 -

 Key: JENKINS-14068
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14068
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Affects Versions: current
Reporter: Martin d'Anjou
Assignee: bap
 Attachments: flexible_publish_bug.png, 
 flexible_publish_does_not_have_set_the_build_state.png


 To reproduce:
 Run? File exists
 File: file.html
 Base directory: Workspace
 On evaluation failure: Mark the build unstable
 Action: Publish HTML reports
 HTML Directory to archive: empty
 Index page: file.html
 Report Title: HTML Report
 Keep passed HTML report: unchecked
 Sample console output:
 {noformat}
 Started by user anonymous
 Building in workspace /home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] enabling prebuild for step [Publish HTML reports]
 [workspace] $ /bin/bash /tmp/hudson8053411243245269594.sh
 /mnt/homes/home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] preventing perform for step [Publish HTML reports]
 Finished: SUCCESS
 {noformat}
 It finished with SUCCESS, it should be UNSTABLE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14068) Mark build unstable does not work

2012-06-11 Thread b...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-14068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163810#comment-163810
 ] 

bap commented on JENKINS-14068:
---

You dont need a shell - use the Not condition with the File exists 
condition and the action is Set build status.

 Mark build unstable does not work
 -

 Key: JENKINS-14068
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14068
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Affects Versions: current
Reporter: Martin d'Anjou
Assignee: bap
 Attachments: flexible_publish_bug.png, 
 flexible_publish_does_not_have_set_the_build_state.png


 To reproduce:
 Run? File exists
 File: file.html
 Base directory: Workspace
 On evaluation failure: Mark the build unstable
 Action: Publish HTML reports
 HTML Directory to archive: empty
 Index page: file.html
 Report Title: HTML Report
 Keep passed HTML report: unchecked
 Sample console output:
 {noformat}
 Started by user anonymous
 Building in workspace /home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] enabling prebuild for step [Publish HTML reports]
 [workspace] $ /bin/bash /tmp/hudson8053411243245269594.sh
 /mnt/homes/home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] preventing perform for step [Publish HTML reports]
 Finished: SUCCESS
 {noformat}
 It finished with SUCCESS, it should be UNSTABLE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-14068) Mark build unstable does not work

2012-06-10 Thread b...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-14068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-14068.
---

Resolution: Not A Defect

The File exists condition was successfully evaluated (to false)
The result of evaluating a Run condition is binary. The On evaluation failure 
allows you to choose what happens if the condition failed to discover whether 
the file exists or not.

If you want to mark the build unstable when the file does not exist you can add 
another conditional action, and select Set the build status from the Fail the 
Build Plugin https://wiki.jenkins-ci.org/display/JENKINS/Fail+The+Build+Plugin

 Mark build unstable does not work
 -

 Key: JENKINS-14068
 URL: https://issues.jenkins-ci.org/browse/JENKINS-14068
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Affects Versions: current
Reporter: Martin d'Anjou
Assignee: bap
 Attachments: flexible_publish_bug.png


 To reproduce:
 Run? File exists
 File: file.html
 Base directory: Workspace
 On evaluation failure: Mark the build unstable
 Action: Publish HTML reports
 HTML Directory to archive: empty
 Index page: file.html
 Report Title: HTML Report
 Keep passed HTML report: unchecked
 Sample console output:
 {noformat}
 Started by user anonymous
 Building in workspace /home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] enabling prebuild for step [Publish HTML reports]
 [workspace] $ /bin/bash /tmp/hudson8053411243245269594.sh
 /mnt/homes/home/deepchip/.jenkins/jobs/deepchip-test/workspace
 Run condition [File exists] preventing perform for step [Publish HTML reports]
 Finished: SUCCESS
 {noformat}
 It finished with SUCCESS, it should be UNSTABLE.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12890) Current path of Exec command is not related for Remote directory

2012-06-10 Thread b...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-12890.
-


 Current path of Exec command is not related for Remote directory
 

 Key: JENKINS-12890
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12890
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Affects Versions: current
Reporter: Artem V. Navrotskiy
Assignee: bap

 Scripts, added by Exec command started in remote user home path.
 You can not specify a script that runs in the directory where the files were 
 uploaded without explicitly specifying the full path in the script.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13731) When using ssh-exec with yum install timeout occurs

2012-06-10 Thread b...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-13731.
-


 When using ssh-exec with yum install timeout occurs
 ---

 Key: JENKINS-13731
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13731
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Sebastian Ruehl
Assignee: bap

 When using a ssh-exec with yum install a timeout occurs.
 It seems that is a problem with the progress bar that won't be displayed 
 during the build but after.
 At the end of the build you can see that for each output a line is produced.
 (3/5): package-a- (29%) 26% [=== ] 421 kB/s |  20 MB 02:14 ETA 
 (3/5): package-a- (29%) 26% [=== ] 402 kB/s |  20 MB 02:20 ETA 
 (3/5): package-a_f- (29%) 26% [=== ] 348 kB/s |  20 MB 02:42 ETA 
 SSH: Disconnecting configuration [rpm target] ...
 ERROR: Exception when publishing, exception message [Exec timed out or was 
 interrupted after 240.653 ms]
 It seems that these outputs are not recognized during a build which leads to 
 a timeout.
 Possible workaround: Turnup timeout
 Caveat: you don't know whenever the build is running or stuck...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13731) When using ssh-exec with yum install timeout occurs

2012-05-12 Thread b...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162702#comment-162702
 ] 

bap commented on JENKINS-13731:
---

The outputs are not monitored for inactivity, the command completes when the 
output and error streams are closed.

The timeout is an overall timeout ie. if the command does not complete in this 
time, then it is probably borked, so disconnect, mark as failure and allow 
jenkins to release the executor

From the above, it looks like you have configured a 4 minute timeout and the 
yum command did not complete within that window.
Try setting your timeout to 150% or 200% of the time you expect the command to 
complete in.
Looking at the above output I would suggest starting with at least 10 minutes, 
and see how it goes.

 When using ssh-exec with yum install timeout occurs
 ---

 Key: JENKINS-13731
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13731
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Sebastian Ruehl
Assignee: bap

 When using a ssh-exec with yum install a timeout occurs.
 It seems that is a problem with the progress bar that won't be displayed 
 during the build but after.
 At the end of the build you can see that for each output a line is produced.
 (3/5): package-a- (29%) 26% [=== ] 421 kB/s |  20 MB 02:14 ETA 
 (3/5): package-a- (29%) 26% [=== ] 402 kB/s |  20 MB 02:20 ETA 
 (3/5): package-a_f- (29%) 26% [=== ] 348 kB/s |  20 MB 02:42 ETA 
 SSH: Disconnecting configuration [rpm target] ...
 ERROR: Exception when publishing, exception message [Exec timed out or was 
 interrupted after 240.653 ms]
 It seems that these outputs are not recognized during a build which leads to 
 a timeout.
 Possible workaround: Turnup timeout
 Caveat: you don't know whenever the build is running or stuck...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13731) When using ssh-exec with yum install timeout occurs

2012-05-12 Thread b...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-13731.
---

Resolution: Not A Defect

 When using ssh-exec with yum install timeout occurs
 ---

 Key: JENKINS-13731
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13731
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Sebastian Ruehl
Assignee: bap

 When using a ssh-exec with yum install a timeout occurs.
 It seems that is a problem with the progress bar that won't be displayed 
 during the build but after.
 At the end of the build you can see that for each output a line is produced.
 (3/5): package-a- (29%) 26% [=== ] 421 kB/s |  20 MB 02:14 ETA 
 (3/5): package-a- (29%) 26% [=== ] 402 kB/s |  20 MB 02:20 ETA 
 (3/5): package-a_f- (29%) 26% [=== ] 348 kB/s |  20 MB 02:42 ETA 
 SSH: Disconnecting configuration [rpm target] ...
 ERROR: Exception when publishing, exception message [Exec timed out or was 
 interrupted after 240.653 ms]
 It seems that these outputs are not recognized during a build which leads to 
 a timeout.
 Possible workaround: Turnup timeout
 Caveat: you don't know whenever the build is running or stuck...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13714) Drag and drop handle missing from transfer sets

bap created JENKINS-13714:
-

 Summary: Drag and drop handle missing from transfer sets
 Key: JENKINS-13714
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13714
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: bap
Assignee: bap
Priority: Minor




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13693) Add DefaultExcludes boolean option to transfer set


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap reassigned JENKINS-13693:
-

Assignee: bap

 Add DefaultExcludes boolean option to transfer set
 --

 Key: JENKINS-13693
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13693
 Project: Jenkins
  Issue Type: Improvement
  Components: publish-over-ssh
Affects Versions: current
Reporter: Adrian Smith
Assignee: bap
Priority: Minor

 Publish-over-ssh follows the Ant patterns 
 (http://ant.apache.org/manual/dirtasks.html#patterns) but does not allow me 
 to set the defaultexcludes=no attribute.
 I want to send all my .git* files to the remote system.
 I know this can be bad practice, but I imagine it's a pretty common request.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13460) Environment variables not explanded for Remote Directory configuration


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-13460.
---

Resolution: Won't Fix

 Environment variables not explanded for Remote Directory configuration
 

 Key: JENKINS-13460
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Bertrand Latinville
Assignee: bap
Priority: Minor
  Labels: deployment, plugin

 I'm using publish over ssh to send file on a remote folder
 and Exec commands. 
 As the folder where I put the files may change in the future I defined a
 Jenkins environment variable: REMOTE_LOCATION.
 I'd like to use this variable in SSH publish over configuration and in the 
 Exec command of the job.
 I configured ssh publish over plugin with Remote Directory set to 
 ${REMOTE_LOCATION}
 I get this error : 
 ERROR: Exception when publishing, exception message [Failed to change to 
 remote directory [${REMOTE_LOCATION}]]
 Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
 I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the 
 Exec command.
 Variables should be expanded in the Remote Directory configuration field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13460) Environment variables not explanded for Remote Directory configuration


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-13460.
-


 Environment variables not explanded for Remote Directory configuration
 

 Key: JENKINS-13460
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Bertrand Latinville
Assignee: bap
Priority: Minor
  Labels: deployment, plugin

 I'm using publish over ssh to send file on a remote folder
 and Exec commands. 
 As the folder where I put the files may change in the future I defined a
 Jenkins environment variable: REMOTE_LOCATION.
 I'd like to use this variable in SSH publish over configuration and in the 
 Exec command of the job.
 I configured ssh publish over plugin with Remote Directory set to 
 ${REMOTE_LOCATION}
 I get this error : 
 ERROR: Exception when publishing, exception message [Failed to change to 
 remote directory [${REMOTE_LOCATION}]]
 Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
 I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the 
 Exec command.
 Variables should be expanded in the Remote Directory configuration field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12891) Use a temporary name for the uploading files


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-12891.
---

Resolution: Won't Fix

 Use a temporary name for the uploading files
 

 Key: JENKINS-12891
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12891
 Project: Jenkins
  Issue Type: Improvement
  Components: publish-over-ssh
Affects Versions: current
Reporter: Artem V. Navrotskiy
Assignee: bap

 Now when downloading large files for a long time at the destination may not 
 be a complete file. This can lead to various problems.
 To avoid this problem you need to load it under a temporary name and then 
 rename the.
 For example:
 {code}
 sftp put bigfile.bin bigfile.bin~tmp123
 sftp rename bigfile.bin~tmp123 bigfile.bin
 {code}
 Now you need to do:
   - Script to rename a file in the working directory;
   - Upload renamed files by ssh;
   - Using Exec command to change cuurent directory to upload directory 
 (JENKINS-12890) and rename files back.
 This workaround looks like ugly :(

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13714) Drag and drop handle missing from transfer sets


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-13714.
-


 Drag and drop handle missing from transfer sets
 ---

 Key: JENKINS-13714
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13714
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: bap
Assignee: bap
Priority: Minor



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13315) Build Keeper plugin: support keeping all unstable, failing runs


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-13315.
-


 Build Keeper plugin: support keeping all unstable, failing runs
 ---

 Key: JENKINS-13315
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13315
 Project: Jenkins
  Issue Type: Improvement
  Components: build-keeper-plugin
Affects Versions: current
Reporter: Steve Roth
Assignee: bap
Priority: Minor

 First off, thanks for this very helpful plugin.   
 I use this plugin to monitor for systemic stability issues and keep the 
 relevant build artifacts when issues are found.  Then when I have time, I 
 review these artifacts and identify the most common issues.
 One feature which would really help this use-case, which I think may be a 
 minor change, would be to add
 'keep all unstable and failing builds'.
 There may also be use-cases for:
 'keep all unstable builds'.
 'keep all failing builds'.
 But for our particular case, we'd ideally want to be able to use 'keep all 
 unstable and failing builds'.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13460) Environment variables not explanded for Remote Directory configuration

2012-04-19 Thread b...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161768#comment-161768
 ] 

bap commented on JENKINS-13460:
---

If you use a vaiable in the global config, I can then set that variable to 
anything I want in the job configuration.
This exactly what you are trying to avoid!

 Environment variables not explanded for Remote Directory configuration
 

 Key: JENKINS-13460
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13460
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Bertrand Latinville
Assignee: bap
Priority: Minor
  Labels: deployment, plugin

 I'm using publish over ssh to send file on a remote folder
 and Exec commands. 
 As the folder where I put the files may change in the future I defined a
 Jenkins environment variable: REMOTE_LOCATION.
 I'd like to use this variable in SSH publish over configuration and in the 
 Exec command of the job.
 I configured ssh publish over plugin with Remote Directory set to 
 ${REMOTE_LOCATION}
 I get this error : 
 ERROR: Exception when publishing, exception message [Failed to change to 
 remote directory [${REMOTE_LOCATION}]]
 Build step 'Send build artifacts over SSH' changed build result to UNSTABLE
 I checked that the variable is set properly by echo ${REMOTE_LOCATION} in the 
 Exec command.
 Variables should be expanded in the Remote Directory configuration field.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13111) Plugin activation cause a NullPointerException


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-13111.
-


 Plugin activation cause a NullPointerException
 --

 Key: JENKINS-13111
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13111
 Project: Jenkins
  Issue Type: Bug
  Components: pegdown-formatter-plugin
Affects Versions: current
 Environment: Debian x64
Reporter: Sébastien Heurtematte
Assignee: bap
 Attachments: stacktrace-monitoring.log, 
 stacktrace-without-monitoring.log


 NullPointerException in the jenkins 1.455
 I have different stacktrace depends on monitoring plugin or not 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12890) Current path of Exec command is not related for Remote directory


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161651#comment-161651
 ] 

bap commented on JENKINS-12890:
---

correct.

The remote directory can be used as a convenient default location for files, 
or, if Exec is disabled, can be used to ensure that files can only be uploaded 
under this path.

There is no way to provide a universal mechanism to change directory.
The shell of the user that you log in with could be anything - including a 
home grown script

 Current path of Exec command is not related for Remote directory
 

 Key: JENKINS-12890
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12890
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Affects Versions: current
Reporter: Artem V. Navrotskiy
Assignee: bap

 Scripts, added by Exec command started in remote user home path.
 You can not specify a script that runs in the directory where the files were 
 uploaded without explicitly specifying the full path in the script.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12891) Use a temporary name for the uploading files

[
https://issues.jenkins-ci.org/browse/JENKINS-12891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161652#comment-161652
]

bap commented on JENKINS-12891:
---

This approach is only useful if you are only uploading a single large file.

If you are updating a directory, then you will want the entire directory update
to be atomic, otherwise some users/application may see some files from the
previous version and some from the current one.

This will probably require OS specific commands/flags (eg 'ln') or stoping
services whilst the copy is in progress.

Should the files be copied to a temporary location (where) to minimise service
downtime, or should the service/ access be stopped so that the files can be
uploaded in place because the disk space is limited.

I'm not sure there is a sensible default behaviour to support this - it is up
to you where you upload your files and scripts, and what you do before and
after they have been transferred.

Use a temporary name for the uploading files

Key: JENKINS-12891
URL: https://issues.jenkins-ci.org/browse/JENKINS-12891
Project: Jenkins
Issue Type: Improvement
Components: publish-over-ssh
Affects Versions: current
Reporter: Artem V. Navrotskiy
Assignee: bap

Now when downloading large files for a long time at the destination may not
be a complete file. This can lead to various problems.
To avoid this problem you need to load it under a temporary name and then
rename the.
For example:
{code}
sftp put bigfile.bin bigfile.bin~tmp123
sftp rename bigfile.bin~tmp123 bigfile.bin
{code}
Now you need to do:
- Script to rename a file in the working directory;
- Upload renamed files by ssh;
- Using Exec command to change cuurent directory to upload directory
(JENKINS-12890) and rename files back.
This workaround looks like ugly :(

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13143) Can't connect on host using a port greater than 999


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-13143.
---

Resolution: Cannot Reproduce

 Can't connect on host using a port greater than 999
 ---

 Key: JENKINS-13143
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13143
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-ssh
Reporter: Frédéric Camblor
Assignee: bap
Priority: Critical

 I configured publish-over-ssh plugin (v1.6) on my current jenkins, with port 
 2232, and it fails to connect.
 Using port 22 (on another host) works fine though.
 When I use verbose mode on the plugin, I have :
 SSH: Connecting from host [jenkins-slave-ubuntu3]
 SSH: Connecting with configuration [XXX nightly] ...
 SSH: Creating session: username [xxx], hostname [X.X.X.X], port [2,232]
 SSH: Connecting session ...
 ERROR: Exception when publishing, exception message [Failed to connect 
 session for config [XXX nightly]. Message [java.net.ConnectException: 
 Connection refused]]
 I think the 2,232 is the cause of the problem :-)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin

[
https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161669#comment-161669
]

bap commented on JENKINS-13230:
---

@gbois
I was just explaining to Suresh why the variables were not restored - the
publish over plugins would need to be EnvInject aware and have code written
to specifically access the stored variables.
Thanks for the code - but it is the publish over plugins that don't know how to
read and restore the variables not me ;-)

Not able to use Jenkins Environment Variables and variables injected through
Env Inject plugin when executing commands over ssh in Publish over SSH plugin
--

Key: JENKINS-13230
URL: https://issues.jenkins-ci.org/browse/JENKINS-13230
Project: Jenkins
Issue Type: Bug
Components: publish-over-ssh
Affects Versions: current
Environment: RHEL 5.5
Reporter: suresh kukalakuntla
Assignee: bap

I am trying to use Jenkins environment variables and variables injected
through Env Inject plugin in Execute section of 'Send build artifacts over
SSH'. It does not recognize them. It does recognize the build parameters and
replaces them with the values. When I look at the 'Injected environment
variables' I see all the variables I want to use. Not sure if I have to do
anything different to be able to use those variables.
In Job configuration I checked 'Prepare an environment for the run' and 'Keep
Jenkins Environment Variables', 'Keep Jenkins Build Variables'.
I have an 'Evaluated Groovy script' that sets 'MODULE_HOME' based on build
time parameter MODULE_NAME.
Please let me know how to proceed.

[JIRA] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap reassigned JENKINS-12433:
-

Assignee: bap  (was: Slide-O-Mix)

 Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to 
 load help file: Not Found
 

 Key: JENKINS-12433
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12433
 Project: Jenkins
  Issue Type: Bug
  Components: publish-over-cifs
Affects Versions: current
 Environment: Jenkins ver. 1.424.2
 Tomcat Version:  7.0.23
 JVM Version:  1.7.0_02-b13
 OS:  Windows Server 2008 R2
Reporter: Dan Oster
Assignee: bap
Priority: Minor
 Attachments: project_config__cifs_publishers.png, 
 system_config__cifs_shares.png, system_config__global_properties.png


 Clicking any of the help ? icons displays ERROR: Failed to load help file: 
 Not Found.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin

2012-03-26 Thread b...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160793#comment-160793
 ] 

bap commented on JENKINS-13230:
---

The following is the output (on a windows master, Jenkins 1.456) from a job 
that injects variables from Prepare an environment for the run, Build 
Environment and from an Inject environment variables build step.
All of the variables are set using the Properties Content textarea.
The variables are all replaced when the Exec command is run after the 
variable has been injected.
When the command is run before the variable has been injected, the variable is 
not replaced, and can be seen in the command with the dollar sign in front.
This all looks exactly as expected. I can test in a linux environment in a week 
or so, but I have no reason to expect a different result.
Can you please test using the Properties Content textarea and check that the 
variables are replaced?

Started by user anonymous
[EnvInject] - Preparing an environment for the build.
[EnvInject] - Keep Jenkins system variables.
[EnvInject] - Keep Jenkins build variables.
[EnvInject] - Injecting as environment variables the properties content 
injectedFromPrepare=Injected from Prepare

[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'PROMPT' variable.
Building in workspace C:\Users\bap\jenkins\1.456\JENKINS_HOME\jobs\test inject 
ssh\workspace
SSH: Connecting from host [essien]
SSH: Connecting with configuration [localhost] ...
SSH: EXEC: STDOUT/STDERR from command [echo Before build Injected from Prepare 
 echo Before build $injectedFromBuildEnv  echo Before build 
$injectedFromBuilder] ...
Before build Injected from Prepare 
Before build $injectedFromBuildEnv 
Before build $injectedFromBuilder
SSH: EXEC: completed after 200 ms
SSH: Disconnecting configuration [localhost] ...
SSH: Transferred 0 file(s)
[EnvInject] - Executing scripts and injecting environment variables after the 
SCM step.
[EnvInject] - Injecting as environment variables the properties content 
injectedFromBuildEnv=Injected from Build Environment

[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'PROMPT' variable.
SSH: Connecting from host [essien]
SSH: Connecting with configuration [localhost] ...
SSH: EXEC: STDOUT/STDERR from command [echo A build step before inject build 
step Injected from Prepare  echo A build step before inject build step 
Injected from Build Environment  echo A build step before inject build step 
$injectedFromBuilder] ...
A build step before inject build step Injected from Prepare 
A build step before inject build step Injected from Build Environment 
A build step before inject build step $injectedFromBuilder
SSH: EXEC: completed after 401 ms
SSH: Disconnecting configuration [localhost] ...
SSH: Transferred 0 file(s)
[EnvInject] - Injecting environment variables from a build step.
[EnvInject] - Injecting as environment variables the properties content 
injectedFromBuilder=Injected from Builder

[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'PROMPT' variable.
SSH: Connecting from host [essien]
SSH: Connecting with configuration [localhost] ...
SSH: EXEC: STDOUT/STDERR from command [echo A build step after inject build 
step Injected from Prepare  echo A build step after inject build step 
Injected from Build Environment  echo A build step after inject build step 
Injected from Builder] ...
A build step after inject build step Injected from Prepare 
A build step after inject build step Injected from Build Environment 
A build step after inject build step Injected from Builder
SSH: EXEC: completed after 201 ms
SSH: Disconnecting configuration [localhost] ...
SSH: Transferred 0 file(s)
SSH: Connecting from host [essien]
SSH: Connecting with configuration [localhost] ...
SSH: EXEC: STDOUT/STDERR from command [echo After build Injected from Prepare 
 echo After build Injected from Build Environment  echo After build 
Injected from Builder] ...
After build Injected from Prepare 
After build Injected from Build Environment 
After build Injected from Builder
SSH: EXEC: completed after 200 ms
SSH: Disconnecting configuration [localhost] ...
SSH: Transferred 0 file(s)
SSH: Connecting from host [essien]
SSH: Connecting with configuration [localhost] ...
SSH: EXEC: STDOUT/STDERR from command [echo Publisher Injected from Prepare  
echo Publisher Injected from Build Environment  echo Publisher Injected from 
Builder] ...
Publisher Injected from Prepare 
Publisher Injected from Build Environment 
Publisher Injected from Builder
SSH: EXEC: completed after 400 ms
SSH: Disconnecting configuration [localhost] ...
SSH: Transferred 0 file(s)
Finished: SUCCESS

 Not able to use Jenkins Environment Variables and variables injected through 
 Env Inject plugin when executing commands over ssh in Publish over SSH plugin

[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin

2012-03-26 Thread b...@java.net (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160797#comment-160797
]

bap commented on JENKINS-13230:
---

Ah! It's in a promotion.
Try prefixing the variable names with promotion_, eg. $promotion_MODULE_NAME

Not able to use Jenkins Environment Variables and variables injected through
Env Inject plugin when executing commands over ssh in Publish over SSH plugin
--

[JIRA] (JENKINS-13230) Not able to use Jenkins Environment Variables and variables injected through Env Inject plugin when executing commands over ssh in Publish over SSH plugin

2012-03-26 Thread b...@java.net (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160804#comment-160804
]

bap commented on JENKINS-13230:
---

The injected variables are not replaced when the promotion executes.
You need to either execute the script again during the promotion, or store the
variables in a file, archive it, and then inject again during the promotion.
When the variables are injected during the promotion, they will need the
promotion_ prefix.

Not able to use Jenkins Environment Variables and variables injected through
Env Inject plugin when executing commands over ssh in Publish over SSH plugin
--

[JIRA] (JENKINS-12925) Build is failed when using Jenkins on windows


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap updated JENKINS-12925:
--

   Assignee: (was: bap)
   Priority: Trivial  (was: Critical)
Component/s: core
 (was: any-buildstep)

This is nothing to do with the Any Build Step Plugin.
It looks like your make is failing.
I suggest you send an email to the [Jenkins user discussion list] [1] to ask 
for help there.

[1]: https://wiki.jenkins-ci.org/display/JENKINS/Mailing+Lists

 Build is failed when using Jenkins on windows
 -

 Key: JENKINS-12925
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12925
 Project: Jenkins
  Issue Type: Bug
  Components: core
Affects Versions: current
 Environment: Windows XP, 
Reporter: cholan dhamodaran
Priority: Trivial
  Labels: jenkins
 Fix For: current

 Attachments: build_log.log


 Im doing coverity build in windows from batch scripts.
 When I doing coverity build manually means throw command prompt, its working 
 fine.
 But when doing same coverity build, in jenkins, Im getting build error.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12930) Unable to load resource hudson/model/Messages.properties


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap updated JENKINS-12930:
--

Component/s: maven
 (was: any-buildstep)

 Unable to load resource hudson/model/Messages.properties
 

 Key: JENKINS-12930
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12930
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Affects Versions: current
 Environment: Unix Master
 Windows XP Slave
Reporter: N Pink
Assignee: bap
 Attachments: exception.txt


 We are running Jenkins Version 1.447.
 At the end of my maven build on my windows slave, im getting an exception 
 stacktrace and the build is being failed despite all steps in my maven build 
 completing successfully.
 It doesnt seem to matter what what contents of the pom is, I get the 
 exception from running any maven builds on the windows slave machine.
 The slave is setup to run as a windows service. There is nothing in the slave 
 logs to indicate what is causing the problem.
 Full stack trace in attached file.
 java.lang.reflect.InvocationTargetException
   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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
   at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
   at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
   at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
   at hudson.remoting.Request$2.run(Request.java:287)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: java.lang.Error: Unable to load resource 
 hudson/model/Messages.properties
   at 
 hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:202)
   at java.lang.ClassLoader.getResource(ClassLoader.java:1003)
   at java.lang.Class.getResource(Class.java:2074)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:83)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
   at 
 org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139)
   at hudson.model.Messages.Node_Mode_NORMAL(Messages.java:1685)
   at hudson.model.Node$Mode.clinit(Node.java:432)
   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 java.lang.Class.getEnumConstantsShared(Class.java:2942)
   at java.lang.Class.getEnumConstants(Class.java:2920)
   at jenkins.model.Jenkins.clinit(Jenkins.java:3662)
   at hudson.model.Computer.clinit(Computer.java:1170)
   at hudson.FilePath.act(FilePath.java:784)
   at hudson.FilePath.act(FilePath.java:766)
   at hudson.FilePath.digest(FilePath.java:1380)
   at 
 hudson.maven.reporters.MavenFingerprinter.record(MavenFingerprinter.java:238)
   at 
 hudson.maven.reporters.MavenFingerprinter.postExecute(MavenFingerprinter.java:100)
   at 
 hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
   at 
 hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
   at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
   at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
   at

[JIRA] (JENKINS-12930) Unable to load resource hudson/model/Messages.properties


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap reassigned JENKINS-12930:
-

Assignee: (was: bap)

 Unable to load resource hudson/model/Messages.properties
 

 Key: JENKINS-12930
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12930
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Affects Versions: current
 Environment: Unix Master
 Windows XP Slave
Reporter: N Pink
 Attachments: exception.txt


 We are running Jenkins Version 1.447.
 At the end of my maven build on my windows slave, im getting an exception 
 stacktrace and the build is being failed despite all steps in my maven build 
 completing successfully.
 It doesnt seem to matter what what contents of the pom is, I get the 
 exception from running any maven builds on the windows slave machine.
 The slave is setup to run as a windows service. There is nothing in the slave 
 logs to indicate what is causing the problem.
 Full stack trace in attached file.
 java.lang.reflect.InvocationTargetException
   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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
   at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
   at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
   at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
   at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
   at hudson.remoting.UserRequest.perform(UserRequest.java:118)
   at hudson.remoting.UserRequest.perform(UserRequest.java:48)
   at hudson.remoting.Request$2.run(Request.java:287)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:619)
 Caused by: java.lang.Error: Unable to load resource 
 hudson/model/Messages.properties
   at 
 hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:202)
   at java.lang.ClassLoader.getResource(ClassLoader.java:1003)
   at java.lang.Class.getResource(Class.java:2074)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:83)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
   at 
 org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102)
   at 
 org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139)
   at hudson.model.Messages.Node_Mode_NORMAL(Messages.java:1685)
   at hudson.model.Node$Mode.clinit(Node.java:432)
   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 java.lang.Class.getEnumConstantsShared(Class.java:2942)
   at java.lang.Class.getEnumConstants(Class.java:2920)
   at jenkins.model.Jenkins.clinit(Jenkins.java:3662)
   at hudson.model.Computer.clinit(Computer.java:1170)
   at hudson.FilePath.act(FilePath.java:784)
   at hudson.FilePath.act(FilePath.java:766)
   at hudson.FilePath.digest(FilePath.java:1380)
   at 
 hudson.maven.reporters.MavenFingerprinter.record(MavenFingerprinter.java:238)
   at 
 hudson.maven.reporters.MavenFingerprinter.postExecute(MavenFingerprinter.java:100)
   at 
 hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
   at 
 hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
   at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
   at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
   at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
   at

[JIRA] (JENKINS-13112) Adding any post-build step as a build step causes exception


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160679#comment-160679
 ] 

bap commented on JENKINS-13112:
---

Is this using Conditional steps (multiple) or Conditional step (single)?
Does it work with Conditional step (single)?
Which build step (post build action) are you attempting to add - name of plugin 
and version?
Which version of Jenkins, Conditional Build Step and Any Build Step plugins are 
you using?

 Adding any post-build step as a build step causes exception
 ---

 Key: JENKINS-13112
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13112
 Project: Jenkins
  Issue Type: Bug
  Components: any-buildstep
 Environment: Windows Server 2008
Reporter: Anthony Hartwig
Assignee: bap
 Attachments: stacktrace.txt


 When attempting to add a post build step as a build step, then click save, an 
 exception is thrown.  Stack trace attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12871) Save buttons hides search result in install plugin page

2012-02-23 Thread b...@java.net (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap resolved JENKINS-12871.
---

Resolution: Duplicate

JENKINS-12641

 Save buttons hides search result in install plugin page
 ---

 Key: JENKINS-12871
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12871
 Project: Jenkins
  Issue Type: Improvement
  Components: core
 Environment: Firefox 10.0.2, Windows 7, Jenkins 1.451
Reporter: Alex Lehmann
Priority: Minor

 When searching with ctrl-f in the plugin list on the manage pluings install 
 page, the save button always hides the search result, if it is displayed at 
 the bottom of the page.
 E.g. start at the top of the page and search for git, the highlighted text is 
 not visible, however if you scroll down 3 or 4 lines, the highlight becomes 
 visible. I assume that the highlight text scrolls the page to the bottom line 
 of the screen so that the hidden section covers the line.
 Maybe it would be possible to realign the page so that the highlighted 
 section is visible above the save button.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap closed JENKINS-12692.
-


 Plugin destroys configuration of Publishers
 ---

 Key: JENKINS-12692
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Reporter: Ulli Hafner
Assignee: bap
Priority: Blocker

 After installing the flexible-publish plugin, the Publishers of some jobs get 
 corrupted on save. 
 E.g. I have a WarningsPublisher in my job with the following serialization:
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 After installing the flexible-publish plug-in, I get the following result 
 when saving the configuration. Seems that there is an interaction between 
 these plug-ins.  
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   thresholdLimitlow/thresholdLimit
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 The following tag is removed: 
 {code}
  thresholdLimitlow/thresholdLimit
 {code}
 I have no idea what is causing that problem. Maybe the reason is something 
 deep in core or in my analysis plug-ins. I need to attach a debugger to our 
 server...
 Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is 
 it intercepting the publishers somehow?
 Interestingly, the problem has been reported with another simpilar plug-ins 
 too: the template project. 
 Here some related issues: JENKINS-8185, JENKINS-12182.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12692) Plugin destroys configuration of Publishers


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap reopened JENKINS-12692:
---


 Plugin destroys configuration of Publishers
 ---

 Key: JENKINS-12692
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Reporter: Ulli Hafner
Assignee: bap
Priority: Blocker

 After installing the flexible-publish plugin, the Publishers of some jobs get 
 corrupted on save. 
 E.g. I have a WarningsPublisher in my job with the following serialization:
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 After installing the flexible-publish plug-in, I get the following result 
 when saving the configuration. Seems that there is an interaction between 
 these plug-ins.  
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   thresholdLimitlow/thresholdLimit
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 The following tag is removed: 
 {code}
  thresholdLimitlow/thresholdLimit
 {code}
 I have no idea what is causing that problem. Maybe the reason is something 
 deep in core or in my analysis plug-ins. I need to attach a debugger to our 
 server...
 Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is 
 it intercepting the publishers somehow?
 Interestingly, the problem has been reported with another simpilar plug-ins 
 too: the template project. 
 Here some related issues: JENKINS-8185, JENKINS-12182.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12692) Radio buttons in the warnings plugin are deselected when the Flexible Publish plugin is installed


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

bap updated JENKINS-12692:
--

Summary: Radio buttons in the warnings plugin are deselected when the 
Flexible Publish plugin is installed  (was: Plugin destroys configuration of 
Publishers)

 Radio buttons in the warnings plugin are deselected when the Flexible Publish 
 plugin is installed
 -

 Key: JENKINS-12692
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
 Project: Jenkins
  Issue Type: Bug
  Components: flexible-publish
Reporter: Ulli Hafner
Assignee: bap
Priority: Blocker

 After installing the flexible-publish plugin, the Publishers of some jobs get 
 corrupted on save. 
 E.g. I have a WarningsPublisher in my job with the following serialization:
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 After installing the flexible-publish plug-in, I get the following result 
 when saving the configuration. Seems that there is an interaction between 
 these plug-ins.  
 {code}
 publishers
 hudson.plugins.warnings.WarningsPublisher
   healthy/healthy
   unHealthy/unHealthy
   thresholdLimitlow/thresholdLimit
   pluginName[WARNINGS] /pluginName
   defaultEncoding/defaultEncoding
   canRunOnFailedfalse/canRunOnFailed
   useDeltaValuesfalse/useDeltaValues
   thresholds
 unstableTotalAll/unstableTotalAll
 unstableTotalHigh/unstableTotalHigh
 unstableTotalNormal/unstableTotalNormal
 unstableTotalLow/unstableTotalLow
 failedTotalAll/failedTotalAll
 failedTotalHigh/failedTotalHigh
 failedTotalNormal/failedTotalNormal
 failedTotalLow/failedTotalLow
   /thresholds
   shouldDetectModulesfalse/shouldDetectModules
   dontComputeNewtrue/dontComputeNew
   parserConfigurations/
   consoleLogParsers
 stringJava Compiler/string
   /consoleLogParsers
 /hudson.plugins.warnings.WarningsPublisher
 {code}
 The following tag is removed: 
 {code}
  thresholdLimitlow/thresholdLimit
 {code}
 I have no idea what is causing that problem. Maybe the reason is something 
 deep in core or in my analysis plug-ins. I need to attach a debugger to our 
 server...
 Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is 
 it intercepting the publishers somehow?
 Interestingly, the problem has been reported with another simpilar plug-ins 
 too: the template project. 
 Here some related issues: JENKINS-8185, JENKINS-12182.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12692) Radio buttons in the warnings plugin are deselected when the Flexible Publish plugin is installed