[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Upgraded Jenkins GIT client plugin to 1.6.0. Started getting the following output: Building in workspace D:\Jenkins\jobs\Project\workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git using GIT_SSH to set credentials -- Killed it after 6 minutes. Then the following output: FATAL: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git hudson.plugins.git.GitException: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.plugins.git.GitException: Error performing git command at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1108) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 10 more Caused by: java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1095) ... 16 more Last build before upgrade had the following output related to Git: Building in workspace D:\Jenkins\jobs\Project\workspace@2 Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git Checking out Revision bbb4481de2d3f8eb16d5dbf9f5a992c24eb4f1ed (master) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård reopened JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Change By: Hallvard Nygård (20/Dec/13 8:10 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård edited a comment on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Upgraded Jenkins GIT client plugin to 1.6.0. Running Jenkins as Windows service on Windows Server 2012 Started getting the following output: Building in workspace D:\Jenkins\jobs\Project\workspace Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git using GIT_SSH to set credentials -- Killed it after 6 minutes. Then the following output: FATAL: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git hudson.plugins.git.GitException: Failed to fetch from ssh://jenkins@gerrit:29418/Project.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:612) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:836) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1412) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1679) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: hudson.plugins.git.GitException: Error performing git command at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1108) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:985) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:69) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:218) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.fetch(CliGitAPIImpl.java:224) at hudson.plugins.git.GitAPI.fetch(GitAPI.java:229) at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:610) ... 10 more Caused by: java.lang.InterruptedException at java.lang.ProcessImpl.waitFor(Unknown Source) at hudson.Proc$LocalProc.join(Proc.java:319) at hudson.Proc.joinWithTimeout(Proc.java:168) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1095) ... 16 more Last build before upgrade had the following output related to Git: Building in workspace D:\Jenkins\jobs\Project\workspace@2 Fetching changes from the remote Git repository Fetching upstream changes from ssh://jenkins@gerrit:29418/Project.git Checking out Revision bbb4481de2d3f8eb16d5dbf9f5a992c24eb4f1ed (master) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials
Hallvard Nygård commented on JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials Downgraded "Git Client Plugin" to 1.4.5 and it worked fine again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations I've already commented to some degree at https://github.com/jenkinsci/jenkins/commit/04d85eb476bdc57eb7ac3c2bb34e91be5b55c487#commitcomment-4893865 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations Extending on that: I agree that failed builds form (in most but not all cases) an exceptional case I do not agree that using failed builds is 'completely meaningless' - as Oliver pointed already out the next build may be likely to fail again, so the time until it will complete is of some value these are only estimates for the build duration and at no place - AFAIK - is specified that this only applies only to successful (and unstable) builds and not to failed builds. It's just the time until the current build will finish So in conclusion: I would be fine to apply a lesser weight to failed builds, so that in case there are failed and successful the successful builds will get more weight in the estimate. I don't think that leaving out failing builds completely is a good idea. There may be jobs which are failing all the time and not giving any estimate at all for them when I could do better is not feasible IMHO This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi updated JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations Change By: kutzi (20/Dec/13 8:38 AM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Magnus Sandberg commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Yes this is actually already fixed for the 2.3 where the init is done with Initializer (after.JOB_LOADED)(I though that was already in 2.2 but is is not) https://github.com/emsa23/priority-sorter-plugin/commit/a2447a7e371869cb4ada8ed76a7114b3eb165ee8 @Oleg do you think that fix will do it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś created JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly Issue Type: Bug Assignee: bklarson Attachments: configuration.png Components: prioritysorter Created: 20/Dec/13 8:55 AM Description: Probably plugin incorrectly assigns priorities to jobs. I have a job in two views: Sonar and All (plugin configuration is in the screenshot). According to the description "priorities are assigned top down by first match" - the job should receive priority 4 (or 3 if user run build), and unfortunately always receives 3 (or 2 if user run build). Environment: Jenkins Priority Sorter Plugin 2.2 jenkins-1.544-1.1.noarch java-1.7.0-openjdk-1.7.0.45-2.4.3.4.el6_5.x86_64 Linux kera 2.6.32-431.1.2.0.1.el6.x86_64 #1 SMP Fri Dec 13 13:06:13 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Major Reporter: Adam Gabryś This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [confluence-publisher] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Markus Helm
created JENKINS-21104
Confluence Publisher Plugin ignores Jenkins proxy settings
Issue Type:
Bug
Assignee:
Joe Hansche
Attachments:
error.msg
Components:
confluence-publisher
Created:
20/Dec/13 8:58 AM
Description:
It seems as if the jenkins proxy settings (Plugin Manager > Advanced) get ignored by the confluence publisher plugin.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.net.ConnectException: Connection timed out
...
Environment:
jenkins 1.544
confluence-publisher 1.8
Project:
Jenkins
Labels:
jenkins
plugin
confluence
publisher
Priority:
Blocker
Reporter:
Markus Helm
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Adam Gabryś updated JENKINS-21103 "Priorities are assigned top down by first match" does not work correctly Change By: Adam Gabryś (20/Dec/13 9:06 AM) Description: Probably plugin incorrectly assigns priorities to jobs. I have a job in two views: Sonar and All (plugin configuration is in the screenshot). According to the description "priorities are assigned top down by first match" - the job should receive priority 4 (or 3 if user run build) , and but unfortunately always receives 3 (or 2 if user run build). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Oleg Nenashev commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init Most probably, it will help with the issue. BTW, any test cases will be appreciated Is it guaranteed that initializer's method call will be finished before starting of scheduling? If no, it makes sense to somehow synchronize methods. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
Daniel Beck commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations these are only estimates for the build duration and at no place - AFAIK - is specified that this only applies only to successful (and unstable) builds and not to failed builds. It's just the time until the current build will finish The only place I could find was Executor#isLikelyStuck() which seems to have the implied requirement that the estimated time uses successful builds (or rather builds with somewhat homogeneous durations), otherwise this feature wouldn't make a lot of sense. Jenkins telling me my build is "likely stuck" because I fixed it so it doesn't fail anymore isn't helpful. Are there situations the new estimates are actually more helpful to users? I understand that the estimates are in some ways 'more accurate' as they don't exclude so many builds – but I don't see when they'd be 'more helpful' than the previous ones. Maybe it's because we copy jobs whenever we're creating release branches, but I'm used to seeing the indeterminate progress indicator and it doesn't bother me. Estimates that are deliberately far off any actual build durations OTOH I have no need for. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Magnus Sandberg commented on JENKINS-21034 Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init I've added some test cases in the 2.3 pull - testing the queue behaviour is not that easy though. Regarding the order I'm not sure - one option could be to use before=COMPLETED rather than after=JOB_LOADED but I'm not sure. I have restarted Jenkins with items in the queue like a gazillion times and I have never seen this so it is a bit tricky for me to to verify this. I reckon that it cannot be wore than it is so I'm considering releasing 2.3 with the current 2.3 pull (https://github.com/jenkinsci/priority-sorter-plugin/pull/10) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
Anders Hammar stopped work on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Change By: Anders Hammar (20/Dec/13 9:43 AM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
Anders Hammar commented on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed I'm fixing this by indicating in the badge if a release build failed (red 'x'). The tooltip will also state this by saying "Failed release...". To align the badge icons I'm replacing the old one for dryruns as well, with a yellow/orange '!' to indicate that it was a dryrun. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-21091) Config flip-flopping
James Howe commented on JENKINS-21091 Config flip-flopping It doesn't seem related to startup or reloading. It may correspond to running the job, but I don't have evidence for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xfpanel] (JENKINS-16094) Better Job filtering capabilities - make use of JobViewsFilterPlugin
Marcel Schutte commented on JENKINS-16094 Better Job filtering capabilities - make use of JobViewsFilterPlugin I just created pull request [1], implementing Oleg's suggestion. [1] https://github.com/jenkinsci/xfpanel-plugin/pull/12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-21105) Multiple testflight upload actions
Nicolae Ghimbovschi created JENKINS-21105 Multiple testflight upload actions Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: testflight Created: 20/Dec/13 10:35 AM Description: Hi, If Jenkins allows, it would be useful to have the possibility to add more than one "Upload to Testflight" action to "Post-build Actions". In my case I have a project which has more than one app scheme. I've configured a Jenkins job which creates all IPAs. Because I can have just one Testflight upload job. I have to create separate Jenkins jobs, which in the end is harder to manage. Fix Versions: current Project: Jenkins Labels: multiple post-build Priority: Minor Reporter: Nicolae Ghimbovschi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-21105) Multiple testflight upload actions
Nicolae Ghimbovschi updated JENKINS-21105 Multiple testflight upload actions Change By: Nicolae Ghimbovschi (20/Dec/13 10:36 AM) Description: Hi, If Jenkins allows, it would be useful to have the possibility to add more than one "Upload to Testflight" action to "Post-build Actions".In my case I have a project which has more than one app scheme.I've configured a Jenkins job which creates all IPAs.Because I can have just one Testflight upload job . , I have to create separate Jenkins jobs, which in the end is harder to manage. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-21091) Config flip-flopping
James Howe commented on JENKINS-21091 Config flip-flopping To clarify , it changes between "" and being omitted entirely. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mail] (JENKINS-21039) NullPointerException in Jenkins Mail Sender
Fritz Elfert commented on JENKINS-21039 NullPointerException in Jenkins Mail Sender Actually, this appears to be two issues (the NPE only being the result of the recipients tag vanishing in the job configuration). See my observations on the jenkins-users list: https://groups.google.com/forum/#!topic/jenkinsci-users/ywqNSVOdw2I This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Peter Phillips commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Fix for incorrect syntax in the store command and also to write the password to the temporary credentials file: https://github.com/jenkinsci/git-client-plugin/pull/45 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16189) "jobs//modules/" is never clear which leads to full disk usage
evernat commented on JENKINS-16189 "jobs//modules/" is never clear which leads to full disk usage Is this still a problem? It seems to me that old builds and or old artifacts are automatically cleared, depending on the configuration of the job, and that a Maven job can disable its automatic artifacts archiving. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21020) Builds disappear from the job after its renaming
Nickolay Rumyantsev updated JENKINS-21020 Builds disappear from the job after its renaming Change By: Nickolay Rumyantsev (20/Dec/13 12:13 PM) Priority: Major Minor Description: When a job is renamed, all its builds disappear from the build history (but remain it the filse file system). Jenkins restart or reload fixes this completely.To reproduce: - Choose a job with builds. - Rename it. - Run System.gc() several times in the Script Console. - Now job shows no builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14713) Cancel permission is granted for users having build permission
Nickolay Rumyantsev commented on JENKINS-14713 Cancel permission is granted for users having build permission Is there any progress with this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: "FATAL: No remotes found!"
Thomas Weese commented on JENKINS-21057 Cannot checkout git repository with submodules: "FATAL: No remotes found!" In my case were the submodules not added to the .git/config file in my project. I did this manually now with "git submodule update --init". Now is the all working again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations > which seems to have the implied requirement that the estimated time uses successful builds (or rather builds with somewhat homogeneous durations), otherwise this feature wouldn't make a lot of sense. I don't see this. Of course it also would make sense, if the 'usual' outcome of a build is a failure. > Are there situations the new estimates are actually more helpful to users? One situation I sometimes see myself is, when I try to set up a new job which is failing several times until I 1st manage to get it successful. In that case an estimation how long the build will take is of some use. Also build often tend to fail for several times in a row until they are fixed. In that case it's IMO also useful to know who long the build will take. > Estimates that are deliberately far off any actual build durations OTOH I have no need for. They are not deliberately far off. Quite in contrary they try to produce the best estimate given the available data, As said, if you want to provide an algorithm which would create more accurate estimations - what is inherently difficult as the usage patterns vary so much - I'll would be fine to include it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi commented on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations BTW: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Run.java#L2228 "Returns the estimated duration for this run if it is currently running." No word whether this only applies to successful builds! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: "FATAL: No remotes found!"
Thomas Weese edited a comment on JENKINS-21057 Cannot checkout git repository with submodules: "FATAL: No remotes found!" Updated The main reason is that the remote configuration is not added to .git/config, after adding this manually the submodule update and build process works. I'm using the Git Client 1.61 Plugin with Git 1.8.3.4 of my Mac OS X. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21106) hudson.slaves.WorkspaceList setting not working
Massimo Rossello
created JENKINS-21106
hudson.slaves.WorkspaceList setting not working
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
20/Dec/13 12:52 PM
Description:
Our compiler's linker is complaining for the @ in the workspace path that comes with multiple concurrent jobs, so I wish to change the character using -Dhudson.slaves.WorkspaceList=+.
Changed /etc/default/jenkins and restarted the service.
Through ps I can see the property has been used:
/usr/bin/java -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 -Dhudson.slaves.WorkspaceList=+
Tried also with underscore, and surrounding the character with apostrophes ('), but it seems not working. Both on master and on slaves, the parallel workspaces are created using '@'.
Environment:
Jenkins 1.534 on Ubuntu 12.04.1
Project:
Jenkins
Priority:
Major
Reporter:
Massimo Rossello
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
kutzi edited a comment on JENKINS-21099 Don't give useless build time estimates by considering failed builds' durations > which seems to have the implied requirement that the estimated time uses successful builds (or rather builds with somewhat homogeneous durations), otherwise this feature wouldn't make a lot of sense. I don't see this. Of course it also would make sense, if the 'usual' outcome of a build is a failure. > Are there situations the new estimates are actually more helpful to users? One situation I sometimes see myself is, when I try to set up a new job which is failing several times until I 1st manage to get it successful. In that case an estimation how long the build will take is of some use. Also builds often tend to fail for several times in a row until they are fixed. In that case it's IMO also useful to know how long the build will take. > Estimates that are deliberately far off any actual build durations OTOH I have no need for. They are not deliberately far off. Quite in contrary, they try to produce the best estimate given the available data. As said, if you want to provide an algorithm which would create more accurate estimations - what is inherently difficult as the usage patterns vary so much - I would be fine to include it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Angelo Schneider created JENKINS-21107 can't commit / or check out from local git repository (local filesystem) Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Attachments: scm-synch-2013-12-20 14_36_43 Configure System [Jenkins].png Components: scm-sync-configuration Created: 20/Dec/13 1:38 PM Description: I use file based git Repository on local host (/J2EE/home/jenkins/git-repository) $HOME of user jenkins is /J2EE/home/jenkins and $JENKINS_HOME is /J2EE/home/jenkins/.jenkins As long as /J2EE/home/jenkins/git-repository was empty, the scm-sync-configuration plug in bailed out because it could not "check out" from there. Now I tried to help myself by doing "git init " inside /J2EE/home/jenkins/git-repository Now however the plug in can not commit to that location. See: [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git add – jobs [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git status [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git add – jobs/just-for-fun-ABC [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git status [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git add – jobs/just-for-fun-ABC/config.xml [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git status [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git status [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git commit --verbose -F /tmp/maven-scm-1363919153.commit -a [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git symbolic-ref HEAD [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration [INFO] Executing: /bin/sh -c cd /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration && git push file:///J2EE/home/jenkins/git-repository master:master [INFO] Working directory: /J2EE/home/jenkins/.jenkins/scm-sync-configuration/checkoutConfiguration 20.12.2013 14:13:23 hudson.plugins.scm_sync_configuration.SCMManipulator checkinFiles SCHWERWIEGEND: [checkinFiles] Problem during SCM commit : remote: error: refusing to update checked out branch: refs/heads/masterESC[K remote: error: By default, updating the current branch in a non-bare repositoryESC[K remote: error: is denied, because it will make the index and work tree inconsistentESC[K remote: error: with what you pushed, and will require 'git reset --hard' to matchESC[K remote: error: the work tree to HEAD.ESC[K remote: error: ESC[K remote: error: You can set 'receive.denyCurrentBranch' configuration variable toESC[K remote: error: 'ignore' or 'warn' in the remote repository to allow pushing intoESC[K remote: error: its current branch; however, this is not recommended unless youESC[K remote: error: arr
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/fa5b79e059e7dee6cd6633a4a6ebf7098be8b4a0 Log: JENKINS-21016 fix git credentials so that password is included in file and correct syntax of store command This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20983) Improve help text for "Preselect append Jenkins username" option
Anders Hammar assigned JENKINS-20983 to Anders Hammar Improve help text for "Preselect append Jenkins username" option Change By: Anders Hammar (20/Dec/13 1:47 PM) Assignee: teilo Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21060) Improve help text of "Number of successful release builds to keep"
Anders Hammar assigned JENKINS-21060 to Anders Hammar Improve help text of "Number of successful release builds to keep" Change By: Anders Hammar (20/Dec/13 1:47 PM) Assignee: teilo Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/a301ee341de5b6ec98cc01173acff7f2c1812e7d Log: JENKINS-21016 do not actually need to replace path with forward slashes, so revert. More importantly need the credentials on a single line so that the git command can read successfully Compare: https://github.com/jenkinsci/git-client-plugin/compare/bb904844edd0...a301ee341de5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [prioritysorter] (JENKINS-21103) "Priorities are assigned top down by first match" does not work correctly
Magnus Sandberg assigned JENKINS-21103 to Magnus Sandberg "Priorities are assigned top down by first match" does not work correctly Change By: Magnus Sandberg (20/Dec/13 2:02 PM) Assignee: bklarson Magnus Sandberg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-21066) Config Rotator jobs builds needlessly (our case 10378)
Mads Nielsen resolved JENKINS-21066 as Fixed Config Rotator jobs builds needlessly (our case 10378) Change By: Mads Nielsen (20/Dec/13 2:11 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-21069) Improve the performance of config rotator (our case 10377)
Mads Nielsen resolved JENKINS-21069 as Fixed Improve the performance of config rotator (our case 10377) Change By: Mads Nielsen (20/Dec/13 2:11 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-21068) Clarify error messages when invalid component is specified (our case 10417)
Mads Nielsen resolved JENKINS-21068 as Fixed Clarify error messages when invalid component is specified (our case 10417) Change By: Mads Nielsen (20/Dec/13 2:12 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Thomas VIN reopened JENKINS-17508 The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503. Hello, We're running Jenkins 1.533 and we still notice the same behavior reported by Sergei Ivanov. Even though we have old builds properly deleted, the clean is not propagated to the underlying modules for which we keep having a bunch of orphans. Best regards. Change By: Thomas VIN (20/Dec/13 2:17 PM) Resolution: Fixed 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/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-20747) CCUCM 1.5.0 on RHEL 5.6 fails to list baselines (our case 10335)
Mads Nielsen resolved JENKINS-20747 as Fixed CCUCM 1.5.0 on RHEL 5.6 fails to list baselines (our case 10335) Change By: Mads Nielsen (20/Dec/13 2:24 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Frédéric Camblor commented on JENKINS-21107 can't commit / or check out from local git repository (local filesystem) Instead of `git init` please try `git init --bare` when initializing your repository This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-18983) $JENKINS_HOME/monitoring/ grows continually
evernat commented on JENKINS-18983 $JENKINS_HOME/monitoring/ grows continually @jglick Is it still a problem or can we close this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-19657) Baseline naming templates needs an overhaul, case 10061
Mads Nielsen resolved JENKINS-19657 as Fixed Baseline naming templates needs an overhaul, case 10061 Change By: Mads Nielsen (20/Dec/13 2:24 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21108) Creating a VM with jcloud plugin fails due to empty userData
Giulio Eulisse created JENKINS-21108 Creating a VM with jcloud plugin fails due to empty userData Issue Type: Bug Assignee: Unassigned Components: jclouds-jenkins Created: 20/Dec/13 2:41 PM Description: Creating a VM via jcloud plugin, using the nova-ec2 interface, fails with: Caused by: java.lang.IllegalArgumentException: userData cannot be empty atcom.google.common.base.Preconditions.checkArgument(Preconditions.java:92) at org.jclouds.ec2.options.RunInstancesOptions.withUserData(RunInstancesOptions.java:89) at org.jclouds.ec2.compute.strategy.CreateKeyPairAndSecurityGroupsAsNeededAndReturnRunOptions.execute(CreateKeyPairAndSecurityGroupsAsNeededAndReturnRunOptions.java:95) at org.jclouds.ec2.compute.strategy.EC2CreateNodesInGroupThenAddToSet.createKeyPairAndSecurityGroupsAsNeededThenRunInstances(EC2CreateNodesInGroupThenAddToSet.java:216) at org.jclouds.ec2.compute.strategy.EC2CreateNodesInGroupThenAddToSet.runInstancesAndWarnOnInvisible(EC2CreateNodesInGroupThenAddToSet.java:154) at org.jclouds.ec2.compute.strategy.EC2CreateNodesInGroupThenAddToSet.execute(EC2CreateNodesInGroupThenAddToSet.java:135) at org.jclouds.compute.internal.BaseComputeService.createNodesInGroup(BaseComputeService.java:212) at org.jclouds.ec2.compute.EC2ComputeService.createNodesInGroup(EC2ComputeService.java:147) at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.get(JCloudsSlaveTemplate.java:316) at jenkins.plugins.jclouds.compute.JCloudsSlaveTemplate.provisionSlave(JCloudsSlaveTemplate.java:182) at jenkins.plugins.jclouds.compute.JCloudsCloud.doProvision(JCloudsCloud.java:283) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) any idea? Project: Jenkins Priority: Blocker Reporter: Giulio Eulisse This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Nicolas De loof Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/79c0e19d01da2a07c015ff9d46a7425569bc4ff0 Log: Merge pull request #47 from pphillips-techphob/master JENKINS-21016 Remove credential section as helper is a property within the credential section. Compare: https://github.com/jenkinsci/git-client-plugin/compare/3a9eddbf310d...79c0e19d01da This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/151bd0373ff93fe246cbb48a0c82c7cbe8e48509 Log: JENKINS-21016 ensure that credential section is removed otherwise end up with multiple [credential] sections, or worse, multiple credential.helper rows This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/e21e44ccd1446ae24fac492c71ec4aae004110bb Log: JENKINS-21016 fix git credentials so that password is included in file and correct syntax of store command This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/b63b7d8fe11c2c7e1acd87405ddfdf3ae96e05d0 Log: JENKINS-21016 do not actually need to replace path with forward slashes, so revert. More importantly need the credentials on a single line so that the git command can read successfully This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
SCM/JIRA link daemon commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) Code changed in jenkins User: Peter Phillips Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/43c83d78d2a678a2d671339d5c01961b5d49104a Log: JENKINS-21016 the section is called credential rather than credential helper. Remove the whole section as using unset to remove credential.helper caused a new credential section to appear on the next set This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat commented on JENKINS-20935 Provide separate monitoring pages for each slave node The source of the plugin is still in subversion: https://svn.jenkins-ci.org/trunk/hudson/plugins/monitoring (and the github mirror does not update itself anymore) It may be migrated to github at some point, but I have not yet decided when to do it. (I have some difficulty to change from subversion which works well for me, to git which does not yet have stable tools: the github client is very slow and the jenkins(/eclipse) git clients are probably not yet stable enough. I would suggest to submit a diff file as patch in this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21034) Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Magnus Sandberg
updated JENKINS-21034
Jenkins Startup Deadlock - QueueSorter.installDefaultQueueSorter and Queue.init
Change By:
Magnus Sandberg
(20/Dec/13 2:49 PM)
Environment:
Jenkins 1.544
/ Jenkins Priority Sorter Plugin 2.2
Description:
{code}Found one Java-level deadlock:="Handling GET /jenkins/view/Portal/ : RequestHandlerThread[#12]": waiting to lock monitor 0x1a449d08 (object 0x000419d757e8, a hudson.ExtensionList$Lock), which is held by "QueueSorter.installDefaultQueueSorter""QueueSorter.installDefaultQueueSorter": waiting to lock monitor 0x1ae56c48 (object 0x00041895e0f0, a hudson.model.Queue), which is held by "Queue.init""Queue.init": waiting to lock monitor 0x1a449d08 (object 0x000419d757e8, a hudson.ExtensionList$Lock), which is held by "QueueSorter.installDefaultQueueSorter"{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-18983) $JENKINS_HOME/monitoring/ grows continually
Jesse Glick commented on JENKINS-18983 $JENKINS_HOME/monitoring/ grows continually Not sure, was reporting this on behalf of a user who had a ridiculously large monitoring directory that was causing problems. If you believe some recent change has fixed this, then close it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat commented on JENKINS-20935 Provide separate monitoring pages for each slave node When there are many slaves, it really makes sense to be able to call the monitoring "System actions" for one slave individually, instead of for all slaves. It would be great to be able to do for one slave the following actions: Execute the garbage collector Generate a heap dump View memory histogram MBeans View OS processes Currently this is done by RemoteCallHelper and NodesController in https://svn.jenkins-ci.org/trunk/hudson/plugins/monitoring/src/main/java/net/bull/javamelody/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-20953) Suggestion: "Last Build Time" column
Fred G updated JENKINS-20953 Suggestion: "Last Build Time" column Change By: Fred G (20/Dec/13 2:57 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-18983) $JENKINS_HOME/monitoring/ grows continually
evernat resolved JENKINS-18983 as Fixed $JENKINS_HOME/monitoring/ grows continually Thanks. Yes, old records are already cleaned and recent changes has reduced the disk used, so resolving as fixed. Reopen if needed. Change By: evernat (20/Dec/13 3:06 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-18983) $JENKINS_HOME/monitoring/ grows continually
evernat edited a comment on JENKINS-18983 $JENKINS_HOME/monitoring/ grows continually Thanks. Yes, old records are already cleaned and recent changes have reduced the disk used, so resolving as fixed. Reopen if needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-19887) Allow time zone to be set on a per user basis
Christian Höltje commented on JENKINS-19887 Allow time zone to be set on a per user basis This is a near duplicate of JENKINS-1962 "Detect timezone from browser". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-1962) Detect timezone from browser
Christian Höltje commented on JENKINS-1962 Detect timezone from browser The core problem is that each user can have a different timezone. This means that you are annoying the heck out of some people. Some things to mitigate this include: 1) Using more relative times. These are always useful, though they become stale if the page isn't refreshed or reloaded. 2) Adding timezones to times. (e.g. JENKINS-13092) Re: detecting from the browser – I like this, but instead of putting it in a cookie, put it in the user's profile if it isn't set there. Some authentication strategies (e.g. OpenID, LDAP, etc.) can have TZ information that can be used – in those cases, it shouldn't be set based on browser's timezone. Ciao! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20983) Improve help text for "Preselect append Jenkins username" option
SCM/JIRA link daemon resolved JENKINS-20983 as Fixed Improve help text for "Preselect append Jenkins username" option Change By: SCM/JIRA link daemon (20/Dec/13 3:41 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/groups/opt_out.
[JIRA] [m2release] (JENKINS-20983) Improve help text for "Preselect append Jenkins username" option
SCM/JIRA link daemon commented on JENKINS-20983 Improve help text for "Preselect append Jenkins username" option Code changed in jenkins User: Anders Hammar Path: src/main/webapp/help-projectConfig-selectAppendHudsonUsername.html http://jenkins-ci.org/commit/m2release-plugin/48719654879814ae6dc99209bcc63f99f5fd5e33 Log: [FIXED JENKINS-20983] Improve help text for "Preselect append Jenkins username" option Signed-off-by: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21060) Improve help text of "Number of successful release builds to keep"
SCM/JIRA link daemon commented on JENKINS-21060 Improve help text of "Number of successful release builds to keep" Code changed in jenkins User: Anders Hammar Path: src/main/webapp/help-projectConfig-numberOfReleaseBuildsToKeep.html http://jenkins-ci.org/commit/m2release-plugin/9fee394c9b4da38aa83872467dc7699f2538728d Log: [FIXED JENKINS-21060] Improve help text of "Number of successful release builds to keep" Signed-off-by: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21060) Improve help text of "Number of successful release builds to keep"
SCM/JIRA link daemon resolved JENKINS-21060 as Fixed Improve help text of "Number of successful release builds to keep" Change By: SCM/JIRA link daemon (20/Dec/13 3:40 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/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
Jim Gallagher commented on JENKINS-19888 NPE when running plugin Having done a lot of investigation on this, no simple solution presents itself, as the issue is basically caused by a malformed JSON file (not invalid JSON, just missing elements) - results are also missing for certain steps. I'm going to close the issue, despite the lack of resolution, but will re-open should it be reported as a problem for anyone else. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
Jim Gallagher resolved JENKINS-19888 as Won't Fix NPE when running plugin Change By: Jim Gallagher (20/Dec/13 3:40 PM) Status: In Progress 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/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat commented on JENKINS-20935 Provide separate monitoring pages for each slave node To implement this feature, I think that some href links should be added somewhere, with a part parameter like today (/monitoring/nodes?part=x) and with a new node parameter to identify which slave needs to be called in RemoteCallHelper. That is, some "node" parameter can be added in the methods or in the constructor of RemoteCallHelper. Is it possible to add the href links in the current Jenkins "/computer" list? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-21060) Improve help text of "Number of successful release builds to keep"
SCM/JIRA link daemon commented on JENKINS-21060 Improve help text of "Number of successful release builds to keep" Code changed in jenkins User: jtnord Path: src/main/webapp/help-projectConfig-numberOfReleaseBuildsToKeep.html http://jenkins-ci.org/commit/m2release-plugin/9f8cd64fda3b7b2baf2f8ebc2b30daa669bcbaa9 Log: Merge pull request #18 from andham/JENKINS-21060 [FIXED JENKINS-21060] Improve help text of "Number of successful release... Compare: https://github.com/jenkinsci/m2release-plugin/compare/e70a17d791e6...9f8cd64fda3b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [m2release] (JENKINS-20983) Improve help text for "Preselect append Jenkins username" option
SCM/JIRA link daemon commented on JENKINS-20983 Improve help text for "Preselect append Jenkins username" option Code changed in jenkins User: jtnord Path: src/main/webapp/help-projectConfig-selectAppendHudsonUsername.html http://jenkins-ci.org/commit/m2release-plugin/e1e1016da59251a648aa2376d1e56bad2770c005 Log: Merge pull request #19 from andham/JENKINS-20983 [FIXED JENKINS-20983] Improve help text for "Preselect append Jenkins us... Compare: https://github.com/jenkinsci/m2release-plugin/compare/9f8cd64fda3b...e1e1016da592 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
Oleg Nenashev
commented on JENKINS-20935
Provide separate monitoring pages for each slave node
> Is it possible to add the href links in the current Jenkins "/computer" list?
Yes, It can be done via NodeMonitor extension. It makes sense to keep in mind something like "monitoring thresholds" during implementation of the extension (just to stop node if something goes wrong).
Regarding other topics, my vision is almost similar.
BTW, I'd prefer to have links like ${JENKINS_URL}/computer/${NODE_NAME}/monitoring. Such URLs can be easily implemented via Computer Actions.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-20953) Suggestion: "Last Build Time" column
Daniel Beck commented on JENKINS-20953 Suggestion: "Last Build Time" column Duplicating Compact Columns 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/groups/opt_out.
[JIRA] [maven] (JENKINS-19978) Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory
Christian Höltje commented on JENKINS-19978 Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory @jglick – I have no idea what you mean "defunct 1.509.x"; according to the front page 1.509.4 is the current Long Term Support version. Is the front page wrong or is Long Term Support not supported? Detailed work around instructions: 1. Go to the plugins directory in your Jenkins installation. 2. rm -rf maven-plugin maven-plugin.jpi 3. curl -L -o maven-plugin.jpi http://updates.jenkins-ci.org/download/plugins/maven-plugin/1.509.3/maven-plugin.hpi 4. touch maven-plugin.jpi.pinned This will prevent Jenkins from auto-updating the maven-plugin on restart and sets the version to 1.509.3 which doesn't have this show-stopper bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [image-gallery] (JENKINS-21109) Provide an option to show the image gallery on its own page
Steve Mokris created JENKINS-21109 Provide an option to show the image gallery on its own page Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: image-gallery Created: 20/Dec/13 4:07 PM Description: I love that the Image Gallery plugin allows me to easily see an overview of images generated by my build process. But my build process generates dozens of large images, and now the Build Status page takes a long time to load. Could the Image Gallery plugin provide an option to move the gallery to its own page (listed among the other build details links in the left navigation bar), to make the Build Status page smaller? Project: Jenkins Priority: Major Reporter: Steve Mokris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
vjuranek commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in Hi, are you able to reproduce on fresh instance? I downloaded 1.544, setup "Unix user/group database" and "Project-based Matrix Authorization Strategy" authentication and authorization and non-admin user with overall read access is able to log in without any problem (i.e. I'm still not able to reproduce) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
vjuranek commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in I looked the track trace little bit more carefully, it seems the root cause can in greenballs plugin. However, cannot reproduce even it latest green balls plugin. Which version of green balls plugin are you on? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21110) Git Publisher failes because remote.origin.url is not set
Nathan Nutter created JENKINS-21110 Git Publisher failes because remote.origin.url is not set Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 20/Dec/13 4:25 PM Description: I saw a comment that may be the basis of the problem: git-plugin 2.0 don't use remote..url anymore The error is very similar to JENKINS-20258 but this is occurring in the Git Publisher Post-build Actions: 07:23:10 Started by an SCM change 07:23:10 Building on master in workspace XXX 07:23:10 Fetching changes from the remote Git repository 07:23:10 Fetching upstream changes from ssh://XXX.git 07:23:20 Checking out Revision XXX (origin/perl-tests) 07:23:23 Cleaning workspace 07:23:23 Resetting working tree 07:23:24 Triggering XXX 07:59:13 XXX completed with result SUCCESS 07:59:13 Pushing HEAD to branch XXX at repo origin 07:59:14 ERROR: Failed to push branch XXX to origin 07:59:14 hudson.plugins.git.GitException: Command "git config --get remote.origin.url" returned status code 1: 07:59:14 stdout: 07:59:14 stderr: 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1099) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1076) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:917) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:927) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:656) 07:59:14 at hudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) 07:59:14 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.push(CliGitAPIImpl.java:1129) 07:59:14 at hudson.plugins.git.GitAPI.push(GitAPI.java:65) 07:59:14 at hudson.plugins.git.GitPublisher.perform(GitPublisher.java:303) 07:59:14 at hudson.plugins.git.GitPublisher$1.endBuild(GitPublisher.java:138) 07:59:14 at hudson.matrix.MatrixBuild$MatrixBuildExecution.post2(MatrixBuild.java:403) 07:59:14 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) 07:59:14 at hudson.model.Run.execute(Run.java:1703) 07:59:14 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) 07:59:14 at hudson.model.ResourceController.execute(ResourceController.java:88) 07:59:14 at hudson.model.Executor.run(Executor.java:231) 07:59:14 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) 07:59:14 Notifying upstream projects of job completion 07:59:14 Finished: SUCCESS Environment: Jenkins ver. 1.544 Jenkins GIT plugin ver. 2.0 Jenkins GIT client plugin ver. 1.6.0 Project: Jenkins Priority: Major Reporter: Nathan Nutter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-19978) Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory
Jesse Glick commented on JENKINS-19978 Cannot run maven x.x builds after LTS 1.509.4 upgrade because of InvalidClassException PlexusModuleContributorFactory @docwhat the front page is wrong. The current LTS is 1.532.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/groups/opt_out.
[JIRA] [ci-game] (JENKINS-1608) [game] Administration of game participants
Christian Höltje reopened JENKINS-1608 [game] Administration of game participants I'm not able to edit the score because when I configure the user, the is marked readonly and disabled. If I edit the HTML via "Inspect Element" in chrome to remove readonly and disabled, then I can edit. So the HTML just needs to detect if someone is an admin or not. Change By: Christian Höltje (20/Dec/13 4:29 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21110) Git Publisher fails because remote.origin.url is not set
Nathan Nutter updated JENKINS-21110 Git Publisher fails because remote.origin.url is not set Change By: Nathan Nutter (20/Dec/13 4:30 PM) Summary: Git Publisher failes fails because remote.origin.url is not set This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20993) org.apache.commons.jelly.JellyTagException when Logging in
vjuranek commented on JENKINS-20993 org.apache.commons.jelly.JellyTagException when Logging in hm, sorry, it's very likely it's not related to green balls plugin in any way This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Angelo Schneider resolved JENKINS-21107 as Fixed can't commit / or check out from local git repository (local filesystem) @Frédéric Camblor you where right, my fault to know not enough about git. I close the issue. Change By: Angelo Schneider (20/Dec/13 5:31 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/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Angelo Schneider closed JENKINS-21107 as Fixed can't commit / or check out from local git repository (local filesystem) User error. Change By: Angelo Schneider (20/Dec/13 5:31 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-21107) can't commit / or check out from local git repository (local filesystem)
Frédéric Camblor commented on JENKINS-21107 can't commit / or check out from local git repository (local filesystem) You're welcome This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters edited a comment on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, you can try the following EAR path to see if it works for you. "../../modules/**/test.ear" or ""../modules/**/test.ear" Remote Deployment to WebSphere *New Requirements* First, you'll need to import the DummyClientTrustFile.jks from WebSphere into your "cacerts" trust store in the JDK that jenkins is running under. The path is typically jre/lib/security/cacerts Lastly, if you are deploying remotely to WebSphere, you may need to include the hostname and IP of the Solaris box in Windows "etc/hosts" file. Since Windows needs to resolve the DNS (This my not be needed, put add it if you're unsure) I've identified the fix on my end so the above workaround may work for you until I get the next release out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters commented on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, you can try the following EAR path to see if it works for you. "../../modules/*/test.ear" or ""../modules/*/test.ear" Remote Deployment to WebSphere *New Requirements* First, you'll need to import the DummyClientTrustFile.jks from WebSphere into your "cacerts" trust store in the JDK that jenkins is running under. The path is typically jre/lib/security/cacerts Lastly, if you are deploying remotely to WebSphere, you may need to include the hostname and IP of the Solaris box in Windows "etc/hosts" file. Since Windows needs to resolve the DNS (This my not be needed, put add it if you're unsure) I've identified the fix on my end so the above workaround may work for you until I get the next release out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters edited a comment on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, you can try the following EAR path to see if it works for you. "../../modules/**/test.ear" or "../modules/**/test.ear" (without quotes) Remote Deployment to WebSphere *New Requirements* First, you'll need to import the DummyClientTrustFile.jks from WebSphere into your "cacerts" trust store in the JDK that jenkins is running under. The path is typically jre/lib/security/cacerts Lastly, if you are deploying remotely to WebSphere, you may need to include the hostname and IP of the Solaris box in Windows "etc/hosts" file. Since Windows needs to resolve the DNS (This my not be needed, put add it if you're unsure) I've identified the fix on my end so the above workaround may work for you until I get the next release out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-20891) Websphere Deployer fails to deploy to remote server
Greg Peters edited a comment on JENKINS-20891 Websphere Deployer fails to deploy to remote server Reza, you can try the following EAR path to see if it works for you. "../../modules/**/test.ear" or "../modules/**/test.ear" (without quotes) Remote Deployment to WebSphere *New Requirements* First, you'll need to import the DummyClientTrustFile.jks from WebSphere into your "cacerts" trust store in the JDK that jenkins is running under. The path is typically jre/lib/security/cacerts Lastly, if you are deploying remotely to WebSphere, you may need to include the hostname and IP of the Solaris box in Windows "etc/hosts" file. Since Windows needs to resolve the DNS (This my not be needed, but add it if you're unsure) I've identified the fix on my end so the above workaround may work for you until I get the next release out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21070) "Set build displayname" does not work
Julian M.
commented on JENKINS-21070
"Set build displayname" does not work
Since you tried it successful, I tested a few settings. It seems like it's the pattern. It is not working if you are having an "+" in your pattern.
My pattern was like 1.6.0+${BUILD_NUMBER}.${SVN_REVISION} (according to Semantic Versioning http://semver.org/ ). No displayname is set if this pattern is choosen.
If I change it to 1.6.0_${BUILD_NUMBER}, it's working.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21070) "Set build displayname" does not work
Patrik Boström
commented on JENKINS-21070
"Set build displayname" does not work
I have now managed to recreate your problem, and it was the pattern that was the problem.
Unfortunately it is just possible to see the error in the Jenkins log file:
WARNING: Error creating version
org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'SVN_REVISION' in '1.6.0+${BUILD_NUMBER}.${SVN_REVISION}'
at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:198)
If you change the pattern to:
1.6.0+${BUILD_NUMBER}.${ENV,var="SVN_REVISION"}
it works.
I will add a error message the the console output of the build to it will be easier to see these types of errors.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-perf] (JENKINS-19888) NPE when running plugin
teilo commented on JENKINS-19888 NPE when running plugin What is broken in the json? We where seeing this on our tests yet neither the cucumber test result plugin (and the cucumber plugin) had any issues parsing the json files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-21111) No way to set path to bzr on remote slaves
Andrew Johnson created JENKINS-2 No way to set path to bzr on remote slaves Issue Type: Bug Assignee: Monty Taylor Components: bazaar Created: 20/Dec/13 8:19 PM Description: The Bazaar plugin uses an external executable to check out the branch for the job, but it doesn't provide a way to set the path to that executable on remote build slaves (my Windows slave can't find it even though I have a bzr.bat file ). The Git client plugin uses what appears to be a standard mechanism for slaves to configure their tool paths, can the Bazaar one be updated to use this too? Environment: Windows slave agent Project: Jenkins Priority: Major Reporter: Andrew Johnson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-21112) Add 2x Image(s) Or Use HTML To Better Support Retina Screens
Joe Fitzgerald created JENKINS-21112 Add 2x Image(s) Or Use HTML To Better Support Retina Screens Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: embeddable-build-status Created: 20/Dec/13 8:28 PM Description: Currently, the embeddable build status plugin uses images which look poor on Retina screens. This could be addressed by either: Supporting 2x Images Building the build status widget/icon using HTML instead of an image Project: Jenkins Priority: Major Reporter: Joe Fitzgerald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [monitoring] (JENKINS-20935) Provide separate monitoring pages for each slave node
evernat commented on JENKINS-20935 Provide separate monitoring pages for each slave node I am a bit short, can you help on the Jenkins and user interface side? I can do the NodesController / RemoteCallHelper side. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [embeddable-build-status] (JENKINS-21112) Add 2x Image(s) Or Use HTML To Better Support Retina Screens
Joe Fitzgerald updated JENKINS-21112 Add 2x Image(s) Or Use HTML To Better Support Retina Screens Change By: Joe Fitzgerald (20/Dec/13 8:29 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-20970) Unexpected close of a file stream
Raphael CHAUMIER resolved JENKINS-20970 as Fixed Unexpected close of a file stream Change By: Raphael CHAUMIER (20/Dec/13 9:18 PM) Status: In Progress 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/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-20970) Unexpected close of a file stream
Raphael CHAUMIER commented on JENKINS-20970 Unexpected close of a file stream I released 2.9.1 which should fixed this regression. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-20146) ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory
Raphael CHAUMIER commented on JENKINS-20146 ERROR: [WeblogicDeploymentPlugin] - Failed to get artifact from archive directory Hi Abhishek, I don't if you have upgraded your plugin version to 2.9.1 (2.9 was bugged). Do you have more infos in the jenkins log ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-13981) Adding configuration file validation for weblogic-deployer-plugin
Raphael CHAUMIER stopped work on JENKINS-13981 Adding configuration file validation for weblogic-deployer-plugin Change By: Raphael CHAUMIER (20/Dec/13 9:26 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18586) weblogic deployer plugin - unable to load configuration file
Raphael CHAUMIER updated JENKINS-18586 weblogic deployer plugin - unable to load configuration file Change By: Raphael CHAUMIER (20/Dec/13 9:27 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/groups/opt_out.
