date:20141201















































Jesse Glick
 commented on  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory















The error message does not suggest a problem with $PATH, but some other problem with nohup, perhaps related to the controlling terminal. Running from the native installer as opposed to using java -jar jenkins.war in a shell is certainly a plausible distinction here.



























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







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

[JIRA] [core] (JENKINS-17265) Builds disappearing from history
















































Jesse Glick
 resolved  JENKINS-17265 as Incomplete


Builds disappearing from history
















eguess74 if you are using the Gerrit Trigger plugin, you are probably seeing JENKINS-23152.





Change By:


Jesse Glick
(02/Dec/14 1:05 AM)




Status:


Reopened
Resolved





Resolution:


Incomplete



























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/d/optout.

[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately















































Jesse Glick
 commented on  JENKINS-24519


Flyweight tasks only use one-off executor when they can be scheduled immediately















What is the code you are referring to? Line numbers in blob URLs using a branch name rather than a hash are meaningless if the file is significantly changed. Do you mean

https://github.com/jenkinsci/jenkins/blob/7156e4470f05a9c41015be78d827dd1be0c02fca/core/src/main/java/hudson/model/Queue.java#L1097

?



























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) Shell step fails on Mac: nohup: can't detach from console: No such file or directory















































Daniel Beck
 commented on  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory















No, see the Jenkins home directory path. I ran java -jar jenkins.war with a pristine Jenkins home directory. I'm just pointing out that either there's something exceptionally wrong with your setup (hence my suggestion to look into PATH), and/or there's some other condition to reproduce this that is unknown so far. "It doesn't work on OS X" as this issue seems to imply is simply not the case.



























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/d/optout.

[JIRA] [core] (JENKINS-17265) Builds disappearing from history

2014-12-01 Thread egues...@java.net (JIRA)















































eguess74
 reopened  JENKINS-17265


Builds disappearing from history
















Change By:


eguess74
(02/Dec/14 12:20 AM)




Resolution:


Duplicate





Status:


Resolved
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







-- 
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/d/optout.

[JIRA] [core] (JENKINS-17265) Builds disappearing from history

2014-12-01 Thread egues...@java.net (JIRA)















































eguess74
 commented on  JENKINS-17265


Builds disappearing from history















I'm seeing it happening right now on Jenkins 1.578
I had a build that i triggered using gerrit trigger (query and trigger gerrit patches)
It appeared in the GUI, I saw it running in the the build queue, it sent an email about build being fixed, registered the result with gerrit, but no matter how i'm trying to access it the link to the build number leads to 404. Build is present on the file system as well.



























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/d/optout.

[JIRA] [ghprb-plugin] (JENKINS-25856) Tries to build PRs when the containing project is disabled

2014-12-01 Thread pas...@pwiddershoven.nl (JIRA)















































Pascal Widdershoven
 created  JENKINS-25856


Tries to build PRs when the containing project is disabled















Issue Type:


Bug



Assignee:


Honza Brázdil



Components:


ghprb-plugin



Created:


01/Dec/14 10:59 PM



Description:


I noticed that currently this plugin will try to build PRs even when the containing project is disabled. Ultimately there's no build triggered, but some other logic is executed (for example the build status in Github is set to pending).

I've submitted a PR that fixes this by not even trying to trigger a build when the project is disabled. Please review. 




Project:


Jenkins



Priority:


Minor



Reporter:


Pascal Widdershoven

























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) Shell step fails on Mac: nohup: can't detach from console: No such file or directory

2014-12-01 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory















Do you use default macos installer?



























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/d/optout.

[JIRA] [core] (JENKINS-25855) Mac agents fail reconnect when jenkins service restarted
















































Daniel Beck
 resolved  JENKINS-25855 as Duplicate


Mac agents fail reconnect when jenkins service restarted
















Change By:


Daniel Beck
(01/Dec/14 10: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







-- 
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/d/optout.

[JIRA] [github-oauth-plugin] (JENKINS-24069) Improve performance by caching and reducing number of github api calls

2014-12-01 Thread m...@mitsein.net (JIRA)















































Mark Keisler
 commented on  JENKINS-24069


Improve performance by caching and reducing number of github api calls















The associated pull request has been merged.  Has this fix been released yet?



























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/d/optout.

[JIRA] [core] (JENKINS-25855) Mac agents fail reconnect when jenkins service restarted















































Daniel Beck
 updated  JENKINS-25855


Mac agents fail reconnect when jenkins service restarted
















Workaround: Use the command line call to launch the slave, not the JNLP button in the browser.





Change By:


Daniel Beck
(01/Dec/14 9:57 PM)




Priority:


Major
Minor



























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/d/optout.

[JIRA] [core] (JENKINS-25855) Mac agents fail reconnect when jenkins service restarted

2014-12-01 Thread james.thei...@ge.com (JIRA)















































James Theisen
 created  JENKINS-25855


Mac agents fail reconnect when jenkins service restarted















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


01/Dec/14 9:41 PM



Description:


If the windows machine that jenkins is running on is restarted, or if the jenkins service is restarted, when it comes back up all my mac agents show as offline.  If you look at the mac agents there is a java error showing up on them and you have to press the ok button and then relaunch the JNLP.  

The error details on the mac are:
CouldNotLoadArgumentException[ Could not load file/URL specified: /var/tmp/javawsZAt0sJ]
	at com.sun.javaws.Main.launchApp(Unknown Source)
	at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
	at com.sun.javaws.Main.access$000(Unknown Source)
	at com.sun.javaws.Main$1.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:744)




Environment:


Jenkins 1.588 running on Windows 2008 R2




Project:


Jenkins



Priority:


Major



Reporter:


James Theisen

























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/d/optout.

[JIRA] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)

2014-12-01 Thread alfer...@hotmail.com (JIRA)













































  
Al Ferguson
 edited a comment on  JENKINS-25831


Branch not found (our case 12373)
















**POLLING LOG*
Started on Dec 1, 2014 3:28:02 PM
Using strategy: Default
[poll] Last Built Revision: Revision 939a053e91a5a0b1057733393e66473896f30f6b (refs/remotes/origin/dev)
 > git ls-remote -h g...@bitbucket.org:alogient/gcr-backend.git dev # timeout=10
[poll] Latest remote head revision is: 29371be20a7c9207271632e102bf4afef95e2340
Done. Took 0.43 sec
Changes found
*

I don't think this situation is the result of a polling problem.

The problem is that SquashCommitStrategy cannot find the remote branch ("The branch name (refs/remotes/origin/dev) contained in the git build data object, did not match a remote branch name").  

The code for this class has not been changed since the last release, so I have my doubts that it will be fixed for the release you plan this week.



























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/d/optout.

[JIRA] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)

2014-12-01 Thread alfer...@hotmail.com (JIRA)















































Al Ferguson
 commented on  JENKINS-25831


Branch not found (our case 12373)
















**POLLING LOG*
Started on Dec 1, 2014 3:28:02 PM
Using strategy: Default
[poll] Last Built Revision: Revision 939a053e91a5a0b1057733393e66473896f30f6b (refs/remotes/origin/dev2)
 > git ls-remote -h g...@bitbucket.org:alogient/gcr-backend.git dev2 # timeout=10
[poll] Latest remote head revision is: 29371be20a7c9207271632e102bf4afef95e2340
Done. Took 0.43 sec
Changes found
*

I don't think this situation is the result of a polling problem.

The problem is that SquashCommitStrategy cannot find the remote branch ("The branch name (refs/remotes/origin/dev) contained in the git build data object, did not match a remote branch name").  

The code for this class has not been changed since the last release, so I have my doubts that it will be fixed for the release you plan this week.



























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/d/optout.

[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks

2014-12-01 Thread tim.w...@salesforce.com (JIRA)















































Tim Wood
 commented on  JENKINS-10944


MatrixProject can run on a heavyweight executor, leading to deadlocks















It's not clear a fix to the other would fix this.  Can we make this a "see also," describing another use case, rather than "duplicate?"  Discussion on this general issue goes back years.



























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/d/optout.

[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks















































Daniel Beck
 commented on  JENKINS-10944


MatrixProject can run on a heavyweight executor, leading to deadlocks















Jesse Glick Isn't this just a duplicate of JENKINS-24519? The other has more watchers and a better network of related/duplicate issues, so I'd rather resolve this.

(Also, ZD-21888.)



























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) Shell step fails on Mac: nohup: can't detach from console: No such file or directory















































Daniel Beck
 commented on  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory
















Started by user anonymous
Running: Allocate node : Start
Running on master in /Users/danielbeck/Workflow-Home/jobs/wf/workspace
Running: Allocate node : Body : Start
Running: Shell Script
[workspace] Running shell script
+ echo hello world
hello world
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
Finished: SUCCESS


Make sure your PATH contains /usr/bin.



























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/d/optout.

[JIRA] [core] (JENKINS-25704) Scheduled triggering stops working until restart

2014-12-01 Thread abune...@gmail.com (JIRA)















































David Resnick
 commented on  JENKINS-25704


Scheduled triggering stops working until restart















I'll be able to check tomorrow. I did check some logs on the master today (e.g. cron) and saw that there were no jumps of the date/time. Timestamps in jenkins.log are also predictable, after the triggers stop too.



























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/d/optout.

[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks















































Jesse Glick
 updated  JENKINS-10944


MatrixProject can run on a heavyweight executor, leading to deadlocks
















Change By:


Jesse Glick
(01/Dec/14 7:14 PM)




Labels:


deadlock flyweight
matrix
 queue shutdown



























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/d/optout.

[JIRA] [core] (JENKINS-10944) MatrixProject can run on a heavyweight executor, leading to deadlocks















































Jesse Glick
 updated  JENKINS-10944


MatrixProject can run on a heavyweight executor, leading to deadlocks
















Change By:


Jesse Glick
(01/Dec/14 7:09 PM)




Summary:


Jobs "deadlocking"
MatrixProject can run
 on
 remote slave
 a heavyweight executor, leading to deadlocks





Labels:


matrix





Component/s:


core





Component/s:


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







-- 
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/d/optout.

[JIRA] [run-condition-plugin] (JENKINS-25853) Check other job's current build status

2014-12-01 Thread mailtoa...@gmail.com (JIRA)















































Arlo Louis O'Keeffe
 updated  JENKINS-25853


Check other job's current build status
















Change By:


Arlo Louis O'Keeffe
(01/Dec/14 6:54 PM)




Issue Type:


Bug
New Feature



























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/d/optout.

[JIRA] [core] (JENKINS-25854) Regression Bug from Enhancement (3177)

2014-12-01 Thread martybjo...@gmail.com (JIRA)















































Marty Jones
 created  JENKINS-25854


Regression Bug from Enhancement (3177)















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


01/Dec/14 7:00 PM



Description:


I was going to create an enhancement request for highlighting rows in big tables and noticed that there was a closed enhancement already filed and closed as fixed (https://issues.jenkins-ci.org/browse/JENKINS-3177).  Looks like the change got removed somehow since the rows are no longer highlighted on mouse over in big tables.




Project:


Jenkins



Priority:


Minor



Reporter:


Marty Jones

























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/d/optout.

[JIRA] [run-condition-plugin] (JENKINS-25853) Check other job's current build status

2014-12-01 Thread mailtoa...@gmail.com (JIRA)















































Arlo Louis O'Keeffe
 created  JENKINS-25853


Check other job's current build status















Issue Type:


Bug



Assignee:


bap



Components:


run-condition-plugin



Created:


01/Dec/14 6:52 PM



Description:


It would be great to have a condition for the current status of a configured job.

The use case for this would be something like the following:

Imagine a develop and release build. Release is triggered manually. We want release to only run if develop was successful. That way we fail early without having to run the entire build again. Something similar could be imagined for deploy and release. Where we want to tell Jenkins to deploy but only if release was successful.




Project:


Jenkins



Priority:


Minor



Reporter:


Arlo Louis O'Keeffe

























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/d/optout.

[JIRA] [windows-slaves-plugin] (JENKINS-25845) Node startup log should contain a timestamp















































Daniel Beck
 updated  JENKINS-25845


Node startup log should contain a timestamp
















SSH Slaves log date/time for most relevant messages, so this seems specific to the slave launcher.





Change By:


Daniel Beck
(01/Dec/14 6:40 PM)




Component/s:


windows-slaves-plugin





Component/s:


core



























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/d/optout.

[JIRA] [core] (JENKINS-25704) Scheduled triggering stops working until restart















































Daniel Beck
 commented on  JENKINS-25704


Scheduled triggering stops working until restart















Are you running an NTP client?



























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/d/optout.

[JIRA] [core] (JENKINS-25836) Cannot add steps that are available through drop down menus















































Daniel Beck
 commented on  JENKINS-25836


Cannot add steps that are available through drop down menus















Note that if you're asking for help, rather than reporting an issue, the jenkinsci-users list or #jenkins on Freenode would be better due to a larger audience. For tips how to ask, see http://www.catb.org/esr/faqs/smart-questions.html or https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+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







-- 
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/d/optout.

[JIRA] [git-plugin] (JENKINS-25846) Parameterized job for branches with git hook doesn't work.

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)















































Antoine Morisseau
 updated  JENKINS-25846


Parameterized job for branches with git hook doesn't work.
















Change By:


Antoine Morisseau
(01/Dec/14 5:56 PM)




Environment:


Windows server 2008,Jenkins 1.590git-plugin 2.3
.1





Description:


Hello,We have an issue quite annoying in Jenkins and the git-plugin in our case.We have some projects that have severals branches that we are working on it.We would like to be able to manually start a build on a selected branche (So we have to create a parameterized build and thanks to Stash and a plugin https://wiki.jenkins-ci.org/display/JENKINS/StashBranchParameter we can retrieve the list of existing branche easily )So in order to do that we use a env variable ${BRANCHES} in order to pass in into the Branches to build section. (i specify */${BRANCHES})So manually it work wonders !But now we want to be able to trigger a build from the same Job from a git push thanks to the hook available.We are using Stash and the Stash notifier plugin to the web hooks.But it doesn't work if we specified */${BRANCHES} in the Branches to build section.If we specify \*/\* the trigger work. But the manual mode doesn't work anymore.even by putting the ${BRANCHES} default value at * it still doesn't work.The only workaround avaible for now is to create two job. One for the manual and one for the git hook...I think my issue is related to this issue since i use the Stash plugin to trigger the notification : ( https://issues.jenkins-ci.org/browse/JENKINS-25708 )
I saw the resolved issue ( https://issues.jenkins-ci.org/browse/JENKINS-14276 )so i did the update in hope to fix my issue.The variable is now resolved but the issue come from a non reset variable.it's like the workspace of the job is not properly reset.
Kind regards,



























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/d/optout.

[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)















































Antoine Morisseau
 commented on  JENKINS-14276


Git SCM-polling doesn't work when using a parametrized branch-name















Wonderful ! It's still not working !
Well... it almost work...
The parameter variable is resolved. But it doesn't retrieve the proper default value.
It retrieve the previous value if it was define by an user.

user case : 

Let's say i have a choice parameter : 

branche v1
branche v2
master

the parameter variable is git_branche_v
the default value is **

in the branch specifier is set at */${GIT_BRANCHE_V}

If a dev do a git push in branche v1
the scm polling use /*.

then if a user manually call the build and select branche v1
the scm polling use */branche v1.

And then if a dev do a git push in branche v2
the scm polling use */branche v1.

It seems that the variable is not reset properly. or maybe the workspace is not reset.

any workaround ?



























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/d/optout.

[JIRA] [build-flow-plugin] (JENKINS-16135) Build Flow dependency graph doesn't render on job status page
















































Craig Rodrigues
 resolved  JENKINS-16135 as Fixed


Build Flow dependency graph doesn't render on job status page
















Fixed in build-flow-plugin 0.17:

https://github.com/jenkinsci/build-flow-plugin/commit/19db461eb8fa37241d184e83d2664e9f3de8c05e






Change By:


Craig Rodrigues
(01/Dec/14 5:51 PM)




Status:


Open
Resolved





Assignee:


Nicolas De Loof
Damien Nozay





Resolution:


Fixed



























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







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

[JIRA] [build-flow-plugin] (JENKINS-24875) Build-flow version 0.14 and 0.15 does not show any build-graph (buildgraph-view 1.1.1)
















































Craig Rodrigues
 resolved  JENKINS-24875 as Fixed


Build-flow version 0.14 and 0.15 does not show any build-graph (buildgraph-view 1.1.1)
















Fixed in build-flow-plugin 0.17:

https://github.com/jenkinsci/build-flow-plugin/commit/19db461eb8fa37241d184e83d2664e9f3de8c05e






Change By:


Craig Rodrigues
(01/Dec/14 5:48 PM)




Status:


Open
Resolved





Assignee:


Nicolas De Loof
Damien Nozay





Resolution:


Fixed



























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







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

[JIRA] [build-flow-plugin] (JENKINS-20762) Build-Flow graph don't show when using "buildgraph-view" plug-in
















































Craig Rodrigues
 resolved  JENKINS-20762 as Fixed


Build-Flow graph don't show when using "buildgraph-view" plug-in
















Fixed in 0.17 of build-flow-plugin https://github.com/jenkinsci/build-flow-plugin/commit/19db461eb8fa37241d184e83d2664e9f3de8c05e





Change By:


Craig Rodrigues
(01/Dec/14 5:45 PM)




Status:


Open
Resolved





Assignee:


berthelot nicolas
Damien Nozay





Resolution:


Fixed



























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







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

[JIRA] [buildgraph-view-plugin] (JENKINS-19470) Build Graph not displaying
















































Craig Rodrigues
 resolved  JENKINS-19470 as Fixed


Build Graph not displaying
















Fixed in build-flow-plugin 0.17:

https://github.com/jenkinsci/build-flow-plugin/commit/19db461eb8fa37241d184e83d2664e9f3de8c05e





Change By:


Craig Rodrigues
(01/Dec/14 5:44 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [copyartifact-plugin] (JENKINS-25852) Lost options on Permalink form

2014-12-01 Thread plp...@gmail.com (JIRA)















































Pedro Lopez
 created  JENKINS-25852


Lost options on Permalink form















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


Copyartifact-Permalink.docx



Components:


copyartifact-plugin



Created:


01/Dec/14 5:41 PM



Description:


On version 1.32.1 of the plugin, the form select option has disappeared.There is no more choice available and the completion doesn't work properly.




Environment:


copyartifact-plugin 1.32.1, jenkins version 1.580.1




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Pedro Lopez

























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/d/optout.

[JIRA] [maven-plugin] (JENKINS-25406) MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED















































Jesse Glick
 commented on  JENKINS-25406


MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED















Note that functional tests will run with assertions enabled, so it seems likely that this bug is only triggered under some condition that is not covered by the existing tests.



























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/d/optout.

[JIRA] [maven-plugin] (JENKINS-25406) Some post step build result in IllegalStateException















































Jesse Glick
 updated  JENKINS-25406


Some post step build result in IllegalStateException
















Seems like a bug in the Maven plugin. Not sure why it was trying to set the result of a completed build. If it really needs to do so for some special reason, it should use the protected Result result field by special permission of the MavenBuild.





Change By:


Jesse Glick
(01/Dec/14 4:39 PM)




Assignee:


Sonar Team





Component/s:


violations-plugin





Component/s:


sonar



























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/d/optout.

[JIRA] [maven-plugin] (JENKINS-25406) MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED















































Jesse Glick
 updated  JENKINS-25406


MavenBuild$ProxyImpl.setResult illegally called after build is COMPLETED
















Change By:


Jesse Glick
(01/Dec/14 4:40 PM)




Summary:


Some post step
MavenBuild$ProxyImpl.setResult illegally called after
 build
 result in IllegalStateException
 is COMPLETED



























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/d/optout.

[JIRA] [youtrack-plugin] (JENKINS-24333) No action for executing command from build step

2014-12-01 Thread erikzie...@hotmail.com (JIRA)















































Erik Zielke
 commented on  JENKINS-24333


No action for executing command from build step















Sorry for not getting back sooner. I think I found an fixed the problem with the names. I have deployed to the live plugin center. Futhermore I have added the ability to customize the "related build" message.

No, the variable is only available within that specific build 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







-- 
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/d/optout.

[JIRA] [workflow-plugin] (JENKINS-25851) Richer return value for build step















































Jesse Glick
 created  JENKINS-25851


Richer return value for build step















Issue Type:


New Feature



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


01/Dec/14 3:56 PM



Description:


Currently the build step will either return Result.SUCCESS, or fail. It should rather return some POJO with whitelisted methods to get the result, get a number/URL, set a description, and so on.

The obvious fix is to just return the Run. The problem is how to allow setDescription. This checks UPDATE, so as a rule it should be allowed only when running with a defined authentication. But flows usually do not run with any authentication, in which case this would fail—even though we should arguably always allow it on a build we triggered ourselves. On the other hand, it is desirable going forward to ask for authentication on projects, in which case you would need some permission on the downstream project to trigger its build anyway.

Compatibility: the current return value is useless and so no one would be relying on it, but some scripts may be relying on a non-stable downstream build failing the flow, so it should be an option to allow the flow to proceed even if the downstream build is not stable (in which case the new return value takes effect).




Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























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/d/optout.

[JIRA] [trac-plugin] (JENKINS-25850) not working for matrix builds

2014-12-01 Thread markus.et...@cryptovision.com (JIRA)















































Markus
 created  JENKINS-25850


not working for matrix builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


trac-plugin



Created:


01/Dec/14 3:54 PM



Description:


The pluggin is not effective for the changes pages of individual matrix builds, only for the parent build I see the additional formatting and links.




Environment:


Jenkins 1.554.2, trac-plugin 1.13




Project:


Jenkins



Priority:


Major



Reporter:


Markus

























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/d/optout.

[JIRA] [plot-plugin] (JENKINS-25849) remove unneccessary stack traces in jenkins log

2014-12-01 Thread markus.et...@cryptovision.com (JIRA)















































Markus
 created  JENKINS-25849


remove unneccessary stack traces in jenkins log















Issue Type:


Improvement



Assignee:


nidaley



Components:


plot-plugin



Created:


01/Dec/14 3:48 PM



Description:


Parsing should accept unset (empty string) number of builds instead of logging a "severe" problem each time all data is plotted.


int numBuilds;
try {
	numBuilds = Integer.parseInt(getURLNumBuilds());
} catch (NumberFormatException nfe) {
	LOGGER.log(Level.SEVERE, "Exception converting to integer", nfe);
	numBuilds = Integer.MAX_VALUE;
}





Environment:


Jenkins 1.554.2, plot-plugin 1.8




Project:


Jenkins



Priority:


Major



Reporter:


Markus

























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/d/optout.

[JIRA] [maven-plugin] (JENKINS-9693) maven.build.timestamp.format is not obeyed in maven builds

2014-12-01 Thread anthonyagre...@gmail.com (JIRA)















































Anthony Agresta
 commented on  JENKINS-9693


maven.build.timestamp.format is not obeyed in maven builds















After updating to the latest version of Jenkins, this issue appears to be fixed.



























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







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

[JIRA] [powershell-plugin] (JENKINS-15890) [PATCH] Powershell improvements

2014-12-01 Thread mr.usm...@gmail.com (JIRA)













































  
Muhammad Saad Shahid Usmani
 edited a comment on  JENKINS-15890


[PATCH] Powershell improvements
















Can you please guide me how to apply this patch? I am using Jenkins ver. 1.591 on windows as Windows native package.

I am new to jenkins if you can guide me.

I don't see these 2 files under my Jenkins home directory. 

Where I can find the following file in Jenkins build directory?

src/main/java/hudson/plugins/powershell/PowerShell.java



























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) Shell step fails on Mac: nohup: can't detach from console: No such file or directory















































Jesse Glick
 commented on  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory















A fix of JENKINS-25503 would supersede this, but there may be a simpler short-term fix, if this can be reproduced by other Mac users. (Can it?)

Fortunately it seems my logic in DurableTaskStep to do a hard kill on the second abort is working here, and allows the flow to at least be cleanly killed.



























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/d/optout.

[JIRA] [powershell-plugin] (JENKINS-15890) [PATCH] Powershell improvements

2014-12-01 Thread mr.usm...@gmail.com (JIRA)















































Muhammad Saad Shahid Usmani
 commented on  JENKINS-15890


[PATCH] Powershell improvements















Can you please guide me how to apply this patch? I am using Jenkins ver. 1.591 on windows as Windows native package.

I am new to jenkins if you can guide me.

I don't see these 2 files under my Jenkins home directory. 



























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) Shell step fails on Mac: nohup: can't detach from console: No such file or directory















































Jesse Glick
 updated  JENKINS-25848


Shell step fails on Mac: nohup: can't detach from console: No such file or directory
















Change By:


Jesse Glick
(01/Dec/14 3:39 PM)




Summary:


infinite shell execution
Shell step fails
 on
 mac os
 Mac: nohup: can't detach from console: No such file or directory





Priority:


Major
Critical





Labels:


mac workflow





Assignee:


Jesse Glick
Kohsuke Kawaguchi





Component/s:


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







-- 
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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25848) infinite shell execution on mac os

2014-12-01 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 created  JENKINS-25848


infinite shell execution on mac os















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


durable-task-plugin, workflow-plugin



Created:


01/Dec/14 3:33 PM



Description:


Simple hello world from workflow-plugin

node {
 sh 'echo hello world'
}

fails

Running: Allocate node : Start
Running on master in /Users/Shared/Jenkins/Home/jobs/workflow/workspace
Running: Allocate node : Body : Start
Running: Shell Script
[workspace] Running shell script
nohup: can't detach from console: No such file or directory
Aborted by asdf
Aborted by asdf
Running: Allocate node : Body : End
Running: Allocate node : End
Running: End of Workflow
Finished: ABORTED





Project:


Jenkins



Priority:


Major



Reporter:


Kanstantsin Shautsou

























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25503) Use setsid instead of nohup















































Jesse Glick
 updated  JENKINS-25503


Use setsid instead of nohup
















Change By:


Jesse Glick
(01/Dec/14 3:31 PM)




Labels:


workflow



























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/d/optout.

[JIRA] [xshell-plugin] (JENKINS-25847) Using non-space-separated (concatenated) DOS-style environment variables with X-shell do not get subsitituted to UNIX properly

2014-12-01 Thread rick.patter...@ca.ibm.com (JIRA)















































Rick Patterson
 created  JENKINS-25847


Using non-space-separated (concatenated) DOS-style environment variables with X-shell do not get subsitituted to UNIX properly















Issue Type:


Bug



Assignee:


Unassigned


Components:


xshell-plugin



Created:


01/Dec/14 3:31 PM



Description:


With X-shell, you should be able to use either DOS-style environment variables (i.e. %VARIABLE%),  or Unix style variables ($VARIABLE, or with braces: ${VARIABLE}, and both styles should work on either platform.   If two Unix variables are to be used concatenated together (i.e. not space separated) then braces must be used, as in:"  ${VARIABLE_1}_${VARIABLE2}.  The equivalent of this in DOS is %VARIABLE_1%_%VARIABLE_2%.  

The issue is:  When two non-space separated variables are specified in an X-shell commandline using the DOS-style variable specification (%XXX%, they should be converted to Unix format by the use of braces, but they are not, and so they do not get substituted properly on UNIX.

Test case:

1) the following Unix-style non-space separated variables work properly with X-shell on both Windows or Unix:

Command as given to X-shell:
echo doing Unix-style variables separate $Generation $Component $Stream and together with braces ${Generation}_${Component}_${Stream}.log

Results - all variables whether space separated or not get substituted:

doing Unix-style variables separate generation_x component_x stream_x and together with braces generation_x_component_x_stream_x.log

2) the following DOS-style non-space separated variables do NOT work properly with X-shell on Unix (work only on DOS)

Command:   
echo doing DOS-style variables separate %Generation% %Component% %Stream% and together %Generation%%Component%%Stream%.log

Results - all variables do not get substituted on UNIX (DOS okay):

doing DOS-style variables separate generation_x component_x stream_x and together $Generation_$Component_stream_x.log






Environment:


Windows/Unix




Project:


Jenkins



Priority:


Major



Reporter:


Rick Patterson

























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/d/optout.

[JIRA] [durable-task-plugin] (JENKINS-25503) Use setsid instead of nohup















































Jesse Glick
 commented on  JENKINS-25503


Use setsid instead of nohup















If this saves durable tasks running on master or via CommandLauncher from e.g. Ctrl-C then great. My main concern is availability across POSIXish platforms. Does Mac OS X have it? /usr/bin?



























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/d/optout.

[JIRA] [powershell-plugin] (JENKINS-21142) [PATCH] Powershell mark build as unstable instead of failed

2014-12-01 Thread mr.usm...@gmail.com (JIRA)















































Muhammad Saad Shahid Usmani
 commented on  JENKINS-21142


[PATCH] Powershell mark build as unstable instead of failed















Can you please guide me how to apply this patch? I am using Jenkins ver. 1.591 on windows as Windows native package.

I am new to jenkins if you can guide me.



























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/d/optout.

[JIRA] [script-security-plugin] (JENKINS-25833) Allow access to static members
















































Jesse Glick
 resolved  JENKINS-25833 as Won't Fix


Allow access to static members
















Static fields, like instance fields, must be whitelisted before use. These cases would make sense to be covered by JENKINS-25804.





Change By:


Jesse Glick
(01/Dec/14 3:23 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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/d/optout.

[JIRA] [core] (JENKINS-9142) Session replication chokes on BoundObjectTable$Table, breaking UI

2014-12-01 Thread martin.blankenst...@googlemail.com (JIRA)















































Jesse Glick
 commented on  JENKINS-9142


Session replication chokes on BoundObjectTable$Table, breaking UI















hridyesh pant I suspect your problem is an unrelated bug, perhaps in the Publish Over SSH 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







-- 
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/d/optout.

[JIRA] [core] (JENKINS-25836) Cannot add steps that are available through drop down menus

2014-12-01 Thread hp...@expedia.com (JIRA)















































hridyesh pant
 commented on  JENKINS-25836


Cannot add steps that are available through drop down menus















Thanks Danieal.
we found this issue is only occurring when trying to access Jenkins via HTTP protocol.
if we use HTTPS ,everything working fine.
Any suggestion.



























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/d/optout.

[JIRA] [git-plugin] (JENKINS-25846) Parameterized job for branches with git hook doesn't work.

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)















































Antoine Morisseau
 updated  JENKINS-25846


Parameterized job for branches with git hook doesn't work.
















Change By:


Antoine Morisseau
(01/Dec/14 2:51 PM)




Description:


Hello,We have an issue quite annoying in Jenkins and the git-plugin in our case.We have some projects that have severals branches that we are working on it.We would like to be able to manually start a build on a selected branche (So we have to create a parameterized build and thanks to Stash and a plugin https://wiki.jenkins-ci.org/display/JENKINS/StashBranchParameter we can retrieve the list of existing branche easily )So in order to do that we use a env variable ${BRANCHES} in order to pass in into the Branches to build section. (i specify */${BRANCHES})So manually it work wonders !But now we want to be able to trigger a build from the same Job from a git push thanks to the hook available.We are using Stash and the Stash notifier plugin to the web hooks.But it doesn't work if we specified */${BRANCHES} in the Branches to build section.If we specify
 "
 \
*/
\
*
"
 the trigger work. But the manual mode doesn't work anymore.even by putting the ${BRANCHES} default value at * it still doesn't work.The only workaround avaible for now is to create two job. One for the manual and one for the git hook...I think my issue is related to this issue since i use the Stash plugin to trigger the notification : ( https://issues.jenkins-ci.org/browse/JENKINS-25708 )Kind regards,



























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/d/optout.

[JIRA] [git-plugin] (JENKINS-25846) Parameterized job for branches with git hook doesn't work.

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)















































Antoine Morisseau
 updated  JENKINS-25846


Parameterized job for branches with git hook doesn't work.
















Change By:


Antoine Morisseau
(01/Dec/14 2:47 PM)




Description:


Hello,We have an issue quite annoying in Jenkins and the git-plugin in our case.We have some projects that have severals branches that we are working on it.We would like to be able to manually start a build on a selected branche (So we have to create a parameterized build and thanks to Stash and a plugin https://wiki.jenkins-ci.org/display/JENKINS/StashBranchParameter we can retrieve the list of existing branche easily )So in order to do that we use a env variable ${BRANCHES} in order to pass in into the Branches to build section. (i specify */${BRANCHES})So manually it work wonders !But now we want to be able to trigger a build from the same Job from a git push thanks to the hook available.We are using Stash and the Stash notifier plugin to the web hooks.But it doesn't work if we specified
 /
*
/
${BRANCHES} in the Branches to build section.If we specify
 "
 */*
"
 the trigger work. But the manual mode doesn't work anymore.even by putting the ${BRANCHES} default value at * it still doesn't work.The only workaround avaible for now is to create two job. One for the manual and one for the git hook...I think my issue is related to this issue since i use the Stash plugin to trigger the notification : ( https://issues.jenkins-ci.org/browse/JENKINS-25708 )Kind regards,



























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/d/optout.

[JIRA] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves

2014-12-01 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 commented on  JENKINS-21861


option to include attachment with console.txt from failed slaves















Hi Alex Earl,

Sorry for the late reply, haven't got any build failures since 

When I configure the Job as suggested, we get a separate e-mail for every configuration in the matrix.

What I'd like to see is a single e-mail for the multi-configuration Job including the console logs for all configurations in the matrix.

For example:

	MyMultiJob
	
		CONFIG_VAR=a
		CONFIG_VAR=b
		CONFIG_VAR=c
	
	



Now, when a and c configurations in MyMultiJob fail, I get an e-mail for:

	MyMultiJob >> a
	MyMultiJob >> c



I want a single e-mail:

	MyMultiJob (including console log for MyMultiJob, MyMultiJob >> a, and MyMultiJob >> c)





























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/d/optout.

[JIRA] [git-plugin] (JENKINS-25846) Parameterized job for branches with git hook doesn't work.

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)

Antoine Morisseau
created JENKINS-25846

Parameterized job for branches with git hook doesn't work.

Issue Type:

Bug

Assignee:

Nicolas De Loof

Components:

git-plugin

Created:

01/Dec/14 2:45 PM

Description:

Hello,

We have an issue quite annoying in Jenkins and the git-plugin in our case.

We have some projects that have severals branches that we are working on it.
We would like to be able to manually start a build on a selected branche (So we have to create a parameterized build and thanks to Stash and a plugin https://wiki.jenkins-ci.org/display/JENKINS/StashBranchParameter we can retrieve the list of existing branche easily )

So in order to do that we use a env variable ${BRANCHES} in order to pass in into the Branches to build section. (i specify */${BRANCHES})

So manually it work wonders !

But now we want to be able to trigger a build from the same Job from a git push thanks to the hook available.
We are using Stash and the Stash notifier plugin to the web hooks.
But it doesn't work if we specified /*${BRANCHES} in the Branches to build section.
If we specify / the trigger work. But the manual mode doesn't work anymore.

even by putting the ${BRANCHES} default value at * it still doesn't work.

The only workaround avaible for now is to create two job. One for the manual and one for the git hook...

I think my issue is related to this issue since i use the Stash plugin to trigger the notification : ( https://issues.jenkins-ci.org/browse/JENKINS-25708 )

Kind regards,

Environment:

Windows server 2008,

Jenkins 1.590

git-plugin 2.3

Project:

Jenkins

Labels:

jenkins
stash
parameter
hook

Priority:

Minor

Reporter:

Antoine Morisseau

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/d/optout.

[JIRA] [matrix-reloaded-plugin] (JENKINS-19970) ( Praqma case 10162 ) Matrix-reloaded does not adhere to build permissions in the same way that normal manual build triggering does.

2014-12-01 Thread markus.et...@cryptovision.com (JIRA)















































Markus
 commented on  JENKINS-19970


( Praqma case 10162 ) Matrix-reloaded does not adhere to build permissions in the same way that normal manual build triggering does. 















I got the same problem with Jenkins 1.554.2. and matrix-reloaded 1.1.3.



























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/d/optout.

[JIRA] [core] (JENKINS-25845) Node startup log should contain a timestamp

2014-12-01 Thread da...@orionrobots.co.uk (JIRA)















































Danny Staple
 created  JENKINS-25845


Node startup log should contain a timestamp















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


01/Dec/14 2:14 PM



Description:


When starting a windows slave with difficulties, debugging would be easier if there were timestamps on the log output from "manage jenkins">node>log. Otherwise it is hard to tell that anything new has happened when pressing "launch slave agent" when slave agent troubles (like the DCOM issue) are encountered.




Environment:


Jenkins 1.580.1 LTS on Fedora, Windows Slave




Project:


Jenkins



Priority:


Minor



Reporter:


Danny Staple

























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/d/optout.

[JIRA] [git-client-plugin] (JENKINS-21139) Git client fails to handle slashes in branch refs

2014-12-01 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-21139


Git client fails to handle slashes in branch refs















Alex Rovner could you submit a new bug report for the inconsistency between the behavior and the help text?

This bug is closed, and it was related to a behavioral inconsistency, not an inconsistency in the help text.



























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/d/optout.

[JIRA] [git-plugin] (JENKINS-25708) Add configuration to ignore "branches" or "sha1" when a build is triggered by the notifyCommit HTTP request

2014-12-01 Thread morisseau.anto...@gmail.com (JIRA)















































Antoine Morisseau
 commented on  JENKINS-25708


Add configuration to ignore "branches" or "sha1" when a build is triggered by the notifyCommit HTTP request















I could not more agree about that improvement !
I spent almost three full days in order to try to make this things works.



























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/d/optout.

[JIRA] [git-client-plugin] (JENKINS-21139) Git client fails to handle slashes in branch refs

2014-12-01 Thread alexrov...@gmail.com (JIRA)















































Alex Rovner
 commented on  JENKINS-21139


Git client fails to handle slashes in branch refs















In the new version, tooltip message is not consistent with the actual behavior:

"Name of the repository, such as origin, that contains the branch you specify below. If left blank, it'll default to the name of the first repository configured above."



























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/d/optout.

[JIRA] [gitlab-plugin] (JENKINS-25844) Can't fetch branch from remote builds

2014-12-01 Thread kas...@easyspeedy.com (JIRA)















































Kasper Fock
 created  JENKINS-25844


Can't fetch branch from remote builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


gitlab-plugin



Created:


01/Dec/14 1:49 PM



Description:


When jobs are run on a slave not the ParametersAction parameter is null and thereby the plugin will not check if the build matches the branch requested. 

To fix this use the git plugin data to test which branch this build covers




Environment:


ubuntu with slave nodes to build on




Project:


Jenkins



Labels:


git-plugin
gitlab
jenkins




Priority:


Minor



Reporter:


Kasper Fock

























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/d/optout.

[JIRA] [scriptler-plugin] (JENKINS-18862) Add an ability to specify external GIT repository for scripts

2014-12-01 Thread michael.bros...@fmr.com (JIRA)















































Mike Brosnan
 commented on  JENKINS-18862


Add an ability to specify external GIT repository for scripts















If this plugin allowed access to use a different external repo, I believe that enterprise users of Jenkins would still contribute some scripts to github and scriptler, but the main body of scripts would be from an internal repo.

If scriptler is not updated to allow an internal catalog, then teams will just fork the code to build their own internal versions of the 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







-- 
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/d/optout.

[JIRA] [sicci_for_xcode] (JENKINS-25843) add documentation

2014-12-01 Thread d...@fortysix.ch (JIRA)















































Dominik Bartholdi
 created  JENKINS-25843


add documentation















Issue Type:


Improvement



Assignee:


Benedikt Biallowons



Components:


sicci_for_xcode



Created:


01/Dec/14 12:47 PM



Description:


Please add some documentation on confluence: https://wiki.jenkins-ci.org/display/JENKINS/SICCI+for+Xcode+Plugin




Project:


Jenkins



Priority:


Major



Reporter:


Dominik Bartholdi

























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/d/optout.

[JIRA] [active-directory-plugin] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication















































Martin Blankenstein
 commented on  JENKINS-24958


UsernameNotFoundException when ActiveDirectory used for API and token authentication















Maybe really an error in Jenkins??,

I also get this exception.
We use Jenkins 1.580.1 and an active directory plugin.
When we use the api/xml with an apitoken I get this exception every 2nd request. I don't know why, but my work around is to do each request twice.
Maybe this helps...



























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/d/optout.

[JIRA] [active-directory-plugin] (JENKINS-24958) UsernameNotFoundException when ActiveDirectory used for API and token authentication

2014-12-01 Thread martin.blankenst...@googlemail.com (JIRA)













































  
Martin Blankenstein
 edited a comment on  JENKINS-24958


UsernameNotFoundException when ActiveDirectory used for API and token authentication
















Maybe really a bug in Jenkins??,

I also get this exception.
We use Jenkins 1.580.1 and an active directory plugin.
When we use the api/xml with an apitoken I get this exception every 2nd request. I don't know why, but my work around is to do each request twice.
Maybe this helps...



























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/d/optout.

[JIRA] [core] (JENKINS-25822) No more connections to slaves - no log - troncated command















































Oleg Nenashev
 updated  JENKINS-25822


No more connections to slaves - no log - troncated command
















Most probably, the core is unrelated. Assigned the issue to ssh-slaves





Change By:


Oleg Nenashev
(01/Dec/14 11:55 AM)




Assignee:


Kohsuke Kawaguchi





Component/s:


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







-- 
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/d/optout.

[JIRA] [core] (JENKINS-25822) No more connections to slaves - no log - troncated command

2014-12-01 Thread pizani...@limule.com (JIRA)

clement igonet
commented on JENKINS-25822

No more connections to slaves - no log - troncated command

Here is a copy/past of the plugins page:

Ant Plugin
This plugin adds Apache Ant support to Jenkins.
1.2

Build Monitor View
Provides a highly visible view of the status of selected Jenkins jobs. It easily accommodates different computer screen sizes and is ideal as an Extreme Feedback Device to be displayed on a screen on your office wall.
1.6+build.132

Build Pipeline Plugin
This plugin renders upstream and downstream connected jobs that typically form a build pipeline. In addition, it offers the ability to define manual triggers for jobs that require intervention prior to execution, e.g. an approval process outside of Jenkins.
1.4.4

build timeout plugin
This plugin allows builds to be automatically terminated after the specified amount of time has elapsed.
1.14

Configuration Slicing plugin
Perform mass configuration of select project properties, including email, timer, discard old builds, and Maven configuration.
1.40

Credentials Plugin
This plugin allows you to store credentials in Jenkins.
1.18

Custom Job Icon plugin
This plugin allows users to set a custom icon for the jobs.
0.2

CVS Plugin
Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient.
2.11

Dashboard View
Customizable dashboard that can present various views of job information.
2.9.4

Dependency Analyzer Plugin
This plugin search for the depency:analyze results into the maven build output and summarize it.
0.7

Dependency Graph Viewer Plugin
This plugin shows a dependency graph of the projects. It uses dot (from graphviz) for drawing.
0.11

Dependency Queue Plugin
This plugin will make sure the order of dependencies is honored in the build queue.
1.1

Downstream build view
This plug-in allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully.
1.9

Email Ext Recipients Column Plugin
This plugin is a sample to explain how to write a Jenkins plugin.
1.0

Email Extension Plugin
This plugin is a replacement for Jenkins's email publisher
2.39

Environment Injector Plugin

This plugin makes it possible to set an environment for the builds.
1.90

EzWall Plugin
This plugin simply add a button to display a fullscreen buildwall on each view.
0.2

Git Client Plugin
Shared library plugin for other Git related Jenkins plugins.
1.11.1

Git Plugin
This plugin integrates GIT with Jenkins.
2.2.5

Javadoc Plugin
This plugin adds Javadoc support to Jenkins.
1.1

Job Configuration History Plugin
Job history plugin for Jenkins.
2.10

Job Direct Mail Plugin
Plugin for sending emails direcrtly from job or build view.
1.5

Join plugin
This plugin allows a job to be run after all the immediate downstream jobs have completed.
1.15

jQuery plugin
This allows other plugins to use jQuery in UI.
1.7.2-1

jQuery UI plugin
This plugin allows you to use jQuery UI on view descriptions.
1.0.2

JUnit Plugin
Allows JUnit-format test results to be published.
1.0

LDAP Plugin
Security realm based on LDAP authentication.
1.6

Mail Watcher Plugin
This plugin notifies configured email recipients on various events.
1.8

Mailer
This plugin allows you to configure email notifications. This is a break-out of the original core based email component.
1.10

MapDB API Plugin
This plugin provides a shared dependency on the MapDB library so that other plugins can co-operate when using this library.
1.0.6.0

Matrix Authorization Strategy Plugin
Offers matrix-based security authorization strategies (global and per-project).
1.1

Matrix Project Plugin
Multi-configuration (matrix) project type.
1.3

Maven Dependency Update Trigger
This plugin will check if any SNAPSHOT dependencies (or optionally plugins SNAPSHOT) have been updated during your project's dependencies resolution and trigger a build. You have to configure a cron _expression_.
1.4

Maven Info Plugin
Adds columns configurable in views to show info about Maven jobs.
0.2.0

Maven Project Plugin
Jenkins plugin for building Maven 2/3 jobs via a special project type.
2.5

Metrics Plugin
This plugin exposes the Metrics API to Jenkins plugins.
3.0.9

Monitoring external jobs
Adds the ability to monitor the result of externally executed jobs.
1.2

NeoLoad Pl

[JIRA] [core] (JENKINS-25822) No more connections to slaves - no log - troncated command

2014-12-01 Thread pizani...@limule.com (JIRA)















































clement igonet
 commented on  JENKINS-25822


No more connections to slaves - no log - troncated command















SSH plugin: 2.4
SSH Credential plugin: 1.10
Credential plugin: 1.18
I have updated all of them.



























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/d/optout.

[JIRA] [core] (JENKINS-25822) No more connections to slaves - no log - troncated command

2014-12-01 Thread pizani...@limule.com (JIRA)















































clement igonet
 commented on  JENKINS-25822


No more connections to slaves - no log - troncated command















Here is my current config:
System Properties
Name  ↓	Value   
awt.toolkit	sun.awt.X11.XToolkit
executable-war	/usr/share/jenkins/jenkins.war
file.encoding	UTF-8
file.encoding.pkg	sun.io
file.separator	/
hudson.diyChunking	true
java.awt.graphicsenv	sun.awt.X11GraphicsEnvironment
java.awt.headless	true
java.awt.printerjob	sun.print.PSPrinterJob
java.class.path	/usr/share/jenkins/jenkins.war
java.class.version	51.0
java.endorsed.dirs	/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsed
java.ext.dirs	/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext
java.home	/usr/lib/jvm/java-7-openjdk-amd64/jre
java.io.tmpdir	/tmp
java.library.path	/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
java.runtime.name	OpenJDK Runtime Environment
java.runtime.version	1.7.0_65-b32
java.specification.name	Java Platform API Specification
java.specification.vendor	Oracle Corporation
java.specification.version	1.7
java.vendor	Oracle Corporation
java.vendor.url	http://java.oracle.com/
java.vendor.url.bug	http://bugreport.sun.com/bugreport/
java.version	1.7.0_65
java.vm.info	mixed mode
java.vm.name	OpenJDK 64-Bit Server VM
java.vm.specification.name	Java Virtual Machine Specification
java.vm.specification.vendor	Oracle Corporation
java.vm.specification.version	1.7
java.vm.vendor	Oracle Corporation
java.vm.version	24.65-b04
jna.platform.library.path	/usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib
line.separator	
mail.smtp.sendpartial	true
mail.smtps.sendpartial	true
os.arch	amd64
os.name	Linux
os.version	3.14-1-amd64
path.separator	:
sun.arch.data.model	64
sun.boot.class.path	/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/classes
sun.boot.library.path	/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64
sun.cpu.endian	little
sun.cpu.isalist	
sun.font.fontmanager	sun.awt.X11FontManager
sun.io.unicode.encoding	UnicodeLittle
sun.java.command	/usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 --prefix=/jenkins
sun.java.launcher	SUN_STANDARD
sun.jnu.encoding	UTF-8
sun.management.compiler	HotSpot 64-Bit Tiered Compilers
sun.os.patch.level	unknown
svnkit.http.methods	Digest,Basic,NTLM,Negotiate
svnkit.ssh2.persistent	false
user.country	US
user.dir	/
user.home	/var/lib/jenkins
user.language	en
user.name	jenkins
user.timezone	Europe/Paris
Environment Variables
Name  ↓	Value   
_	/usr/bin/daemon
GEM_PATH	file:/var/lib/jenkins/plugins/ruby-runtime/WEB-INF/lib/stapler-jruby-1.209.jar!/gem
HOME	/var/lib/jenkins
JENKINS_HOME	/var/lib/jenkins
LANG	en_US.UTF-8
LANGUAGE	en_US:en
LOGNAME	jenkins
MAIL	/var/mail/jenkins
NEXUS_HOME	/usr/local/nexus
NEXUS_PLATFORM	linux-x86-64
PATH	/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/usr/local/nexus/bin
PWD	/mnt/share/ssd01/jenkins
SHELL	/bin/bash
SHLVL	1
TERM	xterm
USER	jenkins
Plugins
Name  ↓	Version   	Enabled   	Pinned   
analysis-core	1.65	true	false
ant	1.2	true	false
antisamy-markup-formatter	1.1	true	false
build-monitor-plugin	1.6+build.132	true	false
build-pipeline-plugin	1.4.4	true	false
build-timeout	1.14	true	false
configurationslicing	1.40	true	false
credentials	1.18	true	false
custom-job-icon	0.2	true	false
cvs	2.11	true	false
dashboard-view	2.9.4	true	false
dependency-queue-plugin	1.1	true	false
dependencyanalyzer	0.7	true	false
depgraph-view	0.11	true	false
downstream-buildview	1.9	true	false
email-ext	2.39	true	false
email-ext-recipients-column	1.0	true	false
envinject	1.90	true	false
external-monitor-job	1.2	true	false
ezwall	0.2	true	false
git	2.2.5	true	false
git-client	1.11.1	true	false
javadoc	1.1	true	true
job-direct-mail	1.5	true	false
jobConfigHistory	2.10	true	false
join	1.15	true	false
jquery	1.7.2-1	true	false
jquery-ui	1.0.2	true	false
junit	1.0	true	false
ldap	1.6	true	false
mail-watcher-plugin	1.8	true	false
mailer	1.10	true	false
mapdb-api	1.0.6.0	true	false
matrix-auth	1.1	true	false
matrix-project	1.3	true

[JIRA] [core] (JENKINS-25842) User Permissions Wiped After Jenkins Restart

2014-12-01 Thread cjp...@gmail.com (JIRA)















































Chris Parr
 commented on  JENKINS-25842


User Permissions Wiped After Jenkins Restart















I have also updated to the latest version and the issue remains



























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/d/optout.

[JIRA] [core] (JENKINS-25842) User Permissions Wiped After Jenkins Restart

2014-12-01 Thread cjp...@gmail.com (JIRA)















































Chris Parr
 updated  JENKINS-25842


User Permissions Wiped After Jenkins Restart
















Change By:


Chris Parr
(01/Dec/14 11:45 AM)




Description:


See here also: http://stackoverflow.com/questions/27131560/jenkins-user-permissions-wiped-on-restartEssentially I can set up security and it works, but after a restart all permissions are wiped:1. Downloaded Redhat rpm from Jenkings main site (jenkins-1.590-1.1.noarch.rpm) and installed directly onto server2. Jobs can be set up and work fine3. Enabled jenkins own DB authentication with matrix permissions4. Add myself a user ID and assign full permissions, allowing anonymous 'overall read' (NOTE I have done this with and without setting this anonymous permission and the result is the same)5. Save6. Restart jenkins7. Create an account to link the ID added in #48. All seems fine, permissions are in place and I can do everything I want to9. can log out and back in without problem10. Restart jenkins11. Log back into the account12. All permissions are gone and I can't access the system.13. If I try to hit a secure page directly I get the message "t143ahe is missing the Overall/Administer permission"14. This will happen with all users if I have added more than one.
The same happens with project based matrix authentication.
To get get back into Jenkins I have to disable security by deleting config.xml and deleting user folders from the users directory.
Rightly or wrongly I've marked this as a Blocker as I can't set up CI in my company without this security in place (can't have Joe Bloggs kicking off a production build).





Priority:


Minor
Blocker



























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/d/optout.

[JIRA] [core] (JENKINS-25842) User Permissions Wiped After Jenkins Restart

2014-12-01 Thread cjp...@gmail.com (JIRA)

Chris Parr
created JENKINS-25842

User Permissions Wiped After Jenkins Restart

Issue Type:

Bug

Assignee:

Unassigned

Components:

core, security

Created:

01/Dec/14 11:42 AM

Description:

See here also: http://stackoverflow.com/questions/27131560/jenkins-user-permissions-wiped-on-restart

Essentially I can set up security and it works, but after a restart all permissions are wiped:

1. Downloaded Redhat rpm from Jenkings main site (jenkins-1.590-1.1.noarch.rpm) and installed directly onto server

2. Jobs can be set up and work fine

3. Enabled jenkins own DB authentication with matrix permissions

4. Add myself a user ID and assign full permissions, allowing anonymous 'overall read' (NOTE I have done this with and without setting this anonymous permission and the result is the same)

5. Save

6. Restart jenkins

7. Create an account to link the ID added in #4

8. All seems fine, permissions are in place and I can do everything I want to

9. can log out and back in without problem

10. Restart jenkins

11. Log back into the account

12. All permissions are gone and I can't access the system.

13. If I try to hit a secure page directly I get the message "t143ahe is missing the Overall/Administer permission"

14. This will happen with all users if I have added more than one.

To get get back into Jenkins I have to disable security by deleting config.xml and deleting user folders from the users directory.

Environment:

System Properties

Name / Value

com.sun.akuma.Daemon daemonized

executable-war /usr/lib/jenkins/jenkins.war

file.encoding UTF-8

file.encoding.pkg sun.io

file.separator /

guice.disable.misplaced.annotation.check true

http.proxyHost icsarray.ics.express.tnt

http.proxyPort 8080

hudson.diyChunking true

java.awt.graphicsenv sun.awt.X11GraphicsEnvironment

java.awt.headless true

java.awt.printerjob sun.print.PSPrinterJob

java.class.path /usr/lib/jenkins/jenkins.war

java.class.version 50.0

java.endorsed.dirs /communique2/java/jdk1.6.0_71/jre/lib/endorsed

java.ext.dirs /communique2/java/jdk1.6.0_71/jre/lib/ext:/usr/java/packages/lib/ext

java.home /communique2/java/jdk1.6.0_71/jre

java.io.tmpdir /tmp

java.library.path /communique2/java/jdk1.6.0_71/jre/lib/amd64/server:/communique2/java/jdk1.6.0_71/jre/lib/amd64:/communique2/java/jdk1.6.0_71/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

java.runtime.name Java(TM) SE Runtime Environment

java.runtime.version 1.6.0_71-b12

java.specification.name Java Platform API Specification

java.specification.vendor Sun Microsystems Inc.

java.specification.version 1.6

java.vendor Sun Microsystems Inc.

java.vendor.url http://java.sun.com/

java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi

java.version 1.6.0_71

java.vm.info mixed mode

java.vm.name Java HotSpot(TM) 64-Bit Server VM

java.vm.specification.name Java Virtual Machine Specification

java.vm.specification.vendor Sun Microsystems Inc.

java.vm.specification.version 1.0

java.vm.vendor Sun Microsystems Inc.

java.vm.version 20.71-b01

JENKINS_HOME /var/lib/jenkins

jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib

jnidispatch.path /tmp/jna--1712433994/jna4896909062887311416.tmp

line.separator

mail.smtp.sendpartial true

mail.smtps.sendpartial true

os.arch amd64

os.name Linux

os.version 2.6.18-238.5.1.el5

path.separator :

securerandom.source file:/dev/./urandom

sun.arch.data.model 64

sun.boot.class.path /communique2/java/jdk1.6.0_71/jre/lib/resources.jar:/communique2/java/jdk1.6.0_71/jre/lib/rt.jar:/communique2/java/jdk1.6.0_71/jre/lib/sunrsasign.jar:/communique2/java/jdk1.6.0_71/jre/lib/jsse.jar:/communique2/java/jdk1.6.0_71/jre/lib/jce.jar:/communique2/java/jdk1.6.0_71/jre/lib/charsets.jar:/communique2/java/jdk1.6.0_71/jre/lib/modules/jdk.boot.jar:/communique2/java/jdk1.6.0_71/jre/classes

sun.boot.library.path /communique2/java/jdk1.6.0_71/jre/lib/amd64

sun.cpu.endian little

sun.cpu.isalist

sun.io.unicode.encoding UnicodeLittle

sun.java.command /usr/l

[JIRA] [msbuild-plugin] (JENKINS-25841) MSBuild exe in white space path messes up properties on command line

2014-12-01 Thread ulf.jon...@elekta.com (JIRA)















































Ulf Jonson
 created  JENKINS-25841


MSBuild exe in white space path messes up properties on command line















Issue Type:


Bug



Assignee:


kdsweeney



Components:


msbuild-plugin



Created:


01/Dec/14 11:26 AM



Description:


This works for a MSBuild located in the .NET folder (4.0) (i.e. no spaces in path) but when using MSBuild 12.0.


Command Line Argument (in Jenkins config):
/p:SolutionFileName=Framework.sln;.\VS2010_projects\Framework2010.sln
or
/p:SolutionFileName="Framework.sln;.\VS2010_projects\Framework2010.sln"
(this works at command line when not using cmd /c msbuild.exe ...)

Log in console:
Path To MSBuild.exe: C:\Program Files (x86)\MSBuild\12.0\bin\amd64\msbuild.exe
Executing the command cmd.exe /C "C:\Program Files (x86)\MSBuild\12.0\bin\amd64\msbuild.exe" /m /p:SolutionFileName=Framework.sln;.\VS2010_projects\Framework2010.sln ci.msbuild.xml

Error:
MSBUILD : error MSB1006: Property is not valid.
Switch: .\VS2010_projects\Framework2010.sln


Command Line Argument:
/p:SolutionFileName='"Framework.sln;.\VS2010_projects\Framework2010.sln"'

Log in console:
Path To MSBuild.exe: C:\Program Files (x86)\MSBuild\12.0\bin\amd64\msbuild.exe
Executing the command cmd.exe /C "C:\Program Files (x86)\MSBuild\12.0\bin\amd64\msbuild.exe" /m /p:SolutionFileName="Framework.sln;.\VS2010_projects\Framework2010.sln" ci.msbuild.xml

Error:
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.


If "cmd /c" is executed on a command line you need to put an extra quote in front and at end to get i to execute. I cannot come up with a workaround to execute this on Jenkins, and it is valid msbuild syntax. Anyone?

Example that works on command line.
cmd.exe /C ""C:\Program Files (x86)\MSBuild\12.0\bin\amd64\msbuild.exe" /m /p:
SolutionFileName="Framework.sln;.\VS2010_projects\Framework2010.sln" ci.msbuild.xml"





Environment:


Jenkins 1.591

MSBuild Plugin 1.23




Project:


Jenkins



Priority:


Major



Reporter:


Ulf Jonson

























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/d/optout.

[JIRA] [openid-plugin] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in

2014-12-01 Thread varuag.chha...@gmail.com (JIRA)















































Gaurav Chhabra
 commented on  JENKINS-23431


Google is phasing out OpenID endpoint. Need to move on to G+ sign-in















We are using Jenkins Google Apps SSO (with OpenID) and since last few days, we started getting the following message while logging in into Jenkins: "Important notice: OpenID2 for Google accounts is going away on April 20, 2015". Switching to any other Access Control in Jenkins would really be a pain.

A fix from Jenkins to accommodate the changes made by Google will really be appreciated.



























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/d/optout.

[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names if ClientNameFormat substitution fails















































Oleg Nenashev
 commented on  JENKINS-25559


Missing hash in client names if ClientNameFormat substitution fails















The issue has been fixed in PR #60 and PR #61
https://github.com/jenkinsci/perforce-plugin/pull/61
https://github.com/jenkinsci/perforce-plugin/pull/60

Automatic SCM Linking does not 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







-- 
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/d/optout.

[JIRA] [perforce-plugin] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration















































Oleg Nenashev
 commented on  JENKINS-23599


Perforce plugin should replace variables from matrix configuration















Please do not re-open cases without an analysis. 
JENKINS-25599 overs your case.
Hopefully, the new plugin version will be released on this week.

P.S: If you experience any issue, please feel free to contribute. There's no 24/7 maintainers of this 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







-- 
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/d/optout.

[JIRA] [perforce-plugin] (JENKINS-25559) Missing hash in client names if ClientNameFormat substitution fails















































Oleg Nenashev
 updated  JENKINS-25559


Missing hash in client names if ClientNameFormat substitution fails
















Change By:


Oleg Nenashev
(01/Dec/14 10:44 AM)




Summary:


Missing hash in client names
 with EXECUTOR_NUMBER leads to workspace collisions
 if ClientNameFormat substitution fails



























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/d/optout.

[JIRA] [matrix-project-plugin] (JENKINS-2670) Error 404 for multi-configuration projects when values contains a slash '/'
















































Oleg Nenashev
 resolved  JENKINS-2670 as Fixed


Error 404 for multi-configuration projects when values contains a slash '/'
















Please check existing issues before reopening unrelated ones





Change By:


Oleg Nenashev
(01/Dec/14 10:40 AM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [matrix-project-plugin] (JENKINS-2670) Error 404 for multi-configuration projects when values contains a slash '/'

2014-12-01 Thread krizleeb...@java.net (JIRA)















































krizleebear
 updated  JENKINS-2670


Error 404 for multi-configuration projects when values contains a slash '/'
















Change By:


krizleebear
(01/Dec/14 10:40 AM)




Description:


For multi-configuration projects where the values for a axis contains a slash


'/' a Error 404 occures when a link is clicked which refers to the build status


for that specifc build. The build exists and can be found in the jobs-directory


with log files and success status etc. Thus the build is successfull but cannot


be viewed via the web-interface.


=== Example ===


Build-axis name: foo


Build-axis values (foo): foo.txt dir1/foo.txt dir2/foo.txt


In this case links refering to axis foo with value foo.txt will work. The other


two will give "Error 404". The link gets the form:


http://server:port/view/viewname/jobname/foo=foo.txt


http://server:port/view/viewname/jobname/foo=dir1/foo.txt


http://server:port/view/viewname/jobname/foo=dir2/foo.txt


===
 Updated
 Environment
 (after reopening issue)
 ===


Hudson: 1.
255
580.1
Java:
 Sun Java
 java version "
 1.6.
0_02
0_27"OpenJDK Runtime Environment (IcedTea6 1.12.5) (6b27
-
b05
1.12.5-0ubuntu0.12.04.1)
Browser: Firefox
 3
 33
.
03
1



























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/d/optout.

[JIRA] [perforce-plugin] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

2014-12-01 Thread krizleeb...@java.net (JIRA)















































krizleebear
 commented on  JENKINS-23599


Perforce plugin should replace variables from matrix configuration















Thanks a lot! The new version of Perforce plugin released in November includes this issue and it works like a charm! 

Unfortunately there's a subsequent problem with encoding slash characters in Jenkins core (or matrix plugin?) that should have been fixed a few years ago. I reopened this issue: https://issues.jenkins-ci.org/browse/JENKINS-2670
Is there anything else I can do to help this problem getting fixed?



























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







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

[JIRA] [maven-dependency-update-trigger-plugin] (JENKINS-23502) Maven Dependency Update Trigger crashes due to missing class (AETHER)

2014-12-01 Thread adrien.lecharpent...@gmail.com (JIRA)















































Adrien Lecharpentier
 commented on  JENKINS-23502


Maven Dependency Update Trigger crashes due to missing class (AETHER)















Hello,

no release has been done since the PR. It will be fixed with the next release.

This exception is due to the modification of packages naming inside maven aether artifacts from org.sonatype.aether to org.eclipse.aether.



























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/d/optout.

[JIRA] [maven-plugin] (JENKINS-12873) use custom workspace option not exist for maven project

2014-12-01 Thread mtu...@java.net (JIRA)













































  
mturra
 edited a comment on  JENKINS-12873


use custom workspace option not exist for maven project
















This option change location in the GUI depending on project type!

Freestyle
Available at: "Advanced Project Options"-->"Advanced"
Maven2/3
Available at: "Build"-->"Advanced"
Ivy
Available at: "Ivy Module Configuration"-->"Advanced"
Matrix
Available at: "Advanced Project Options"-->"Advanced"



























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/d/optout.

[JIRA] [core] (JENKINS-25836) Cannot add steps that are available through drop down menus