[JIRA] [repository-connector] (JENKINS-17541) target directory does not expand token macro parameters
Dominik Bartholdi resolved JENKINS-17541 as Fixed target directory does not expand token macro parameters fixed with 0.9.0 Change By: Dominik Bartholdi (18/Jul/14 7:04 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-22544) Conditional BuildStep Plugin
Dominik Bartholdi updated JENKINS-22544 Conditional BuildStep Plugin conditional-buildstep does not implement any conditions, there are currently two separate plugins which provide conditions. So this feature request should go into one of these. Change By: Dominik Bartholdi (18/Jul/14 7:35 PM) Component/s: run-condition Component/s: run-condition-extras This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-22544) Conditional BuildStep Plugin
Dominik Bartholdi edited a comment on JENKINS-22544 Conditional BuildStep Plugin conditional-buildstep does not implement any conditions, there are currently two separate plugins which provide conditions. So this feature request should go into one of these: run-condition or run-condition-extras This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller updated JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Change By: Marco Miller (18/Jul/14 7:42 PM) Component/s: core Component/s: safe-restart Component/s: saferestart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23774) Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
Jesse Glick resolved JENKINS-23774 as Cannot Reproduce Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor. Change By: Jesse Glick (18/Jul/14 7:43 PM) Status: Reopened Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18435) Navigating back, then forward, from a job configuration causes loss of config data
Jesse Glick commented on JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data Lazy-loaded form fragments are added to the DOM by some _javascript_ hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller edited a comment on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. So I just updated the component (set it to core); please let me know if that is still wrong though =) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18435) Navigating back, then forward, from a job configuration causes loss of config data
Jesse Glick commented on JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) A plugin that does that is essentially sample code. Would one resolve this issue for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
Jesse Glick started work on JENKINS-20663 file name encoding broken in zip archives Change By: Jesse Glick (18/Jul/14 7:55 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) I guess it would; you mean "simple" above right Daniel? (rather than "sample") This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't belive Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8. How can this be for such a used versioning system (even though many use git also9. This should be a high priority issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8???. How can this be for such a used version system (even though many use git also). This should really be a high priority issue now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19828) Kill or rework auto refresh
Jesse Glick commented on JENKINS-19828 Kill or rework auto refresh Yeah I would really advocate the first option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8???. How can this be for such a used version system (even though many use git also). This should really be a high priority issue now. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8?.This should really be a high priority issue now. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-23687) when running build
Jesse Glick resolved JENKINS-23687 as Not A Defect when running build Use the Credentials dropdown to set your username and password, rather than packing them into the URL. Change By: Jesse Glick (18/Jul/14 8:13 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-23687) when running build
Jesse Glick updated JENKINS-23687 when running build Change By: Jesse Glick (18/Jul/14 8:12 PM) Component/s: maven2 Component/s: active-directory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8?.This should really be a high priority issue now, hope someone stands up to fix the issue. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present
M Chon
created JENKINS-23884
Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git, git-client, github
Created:
18/Jul/14 8:16 PM
Description:
git-client plugin: 1.9.1
github plugin: 1.8
git plugin: 2.2.2
We had a project which was set up to trigger on GHE changes to the "festivus-dev" branch. We noticed that changes being pushed to the "master" branch on GHE was triggering a the "festivus-dev" branch job.
It turns out that there was a second "jdoe/blah/festivus-dev" branch that was present and it appeared to cause the polling command to think there were always changes present.
When we removed the "jdoe/blah/festivus-dev" branch from the repo, polling returned to normal. Changes checked into the "master" branch no longer triggered builds in the "festivus-dev" project.
We also noticed that when the similarly named branch ("jdoe/blah/festivus-dev") was present in the repo, it did not matter what was entered in the branch section of the project. We had a typo in there, and the build was still being triggered.
Prior to removing the similarly-named branch, we saw this in the jenkins.log:
INFO: Poked Festivus_master_CI
Jul 18, 2014 12:04:04 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: Poked Festivus_festivus-dev_CI
Jul 18, 2014 12:04:04 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: SCM changes detected in Festivus_festivus-dev_CI. Triggering #1547
Jul 18, 2014 12:04:05 PM com.cloudbees.jenkins.GitHubPushTrigger$1 run
INFO: SCM changes detected in Festivus_master_CI. Triggering #317
Jul 18, 2014 12:04:13 PM hudson.model.Run execute
And we also saw this in the polling log:
Started on Jul 18, 2014 12:04:04 PM
Using strategy: Default
poll Last Built Revision: Revision 652d86ee1fb4715c28902b386d32d623c15c77e9 (origin/festivus-dev)
/usr/bin/git ls-remote -h g...@github.some.where.com:SITE/Festivus.git festivus-dev
Done. Took 0.43 sec
Changes found
And we also saw this on the command line:
git ls-remote -h g...@github.some.where.com:SITE/Festivus.git festivus-dev
849c9e7c5d497816427516146d5bd8f778897641refs/heads/jdoe/blah/festivus-dev
652d86ee1fb4715c28902b386d32d623c15c77e9refs/heads/festivus-dev
After we removed the jdoe/blah/festivus-dev branch,
INFO: Poked Festivus_master_CI
Jul 18, 2014 12:37:55 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: Poked Festivus_festivus-dev_CI
Jul 18, 2014 12:37:55 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: SCM changes detected in Festivus_master_CI. Triggering #322
Environment:
Ubuntu
Project:
Jenkins
Labels:
plugin
git
trigger
scm
polling
git-client
ghe
Priority:
Minor
Reporter:
M Chon
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
[JIRA] [core] (JENKINS-21977) java.io.IOException: Failed to clean up temp dirs because of secret.key
Jesse Glick commented on JENKINS-21977 java.io.IOException: Failed to clean up temp dirs because of secret.key This code should simply be disabled when Functions.getIsUnitTest(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) It's so simple it could well be available somewhere to teach people about writing plugins. Hence, it could be sample code. Behold: https://github.com/daniel-beck/unsafe-restart-plugin Just git clone, mvn -DskipTests verify (Maven 3.0.5+) and install the resulting target/unsafe-restart.hpi by uploading on Manage Jenkins » Manage Plugins » Advanced Note that I don't think making this particular URL accessible from a management link in core would be a good idea, as it's quite dangerous in the sense that it would kill builds in progress. Too accident prone for the default config IMO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
SCM/JIRA link daemon commented on JENKINS-20663 file name encoding broken in zip archives Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/DirectoryBrowserSupport.java http://jenkins-ci.org/commit/jenkins/84c76253862a2f36f813a7aa45b77d99c1616be4 Log: FIXED JENKINS-20663 For now, go back to using ZipOutputStream from Ant that supports setting the filename encoding (present in java.util.zip only in Java 7+). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
SCM/JIRA link daemon resolved JENKINS-20663 as Fixed file name encoding broken in zip archives Change By: SCM/JIRA link daemon (18/Jul/14 8:46 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8.This should really be a high priority issue now, hope someone stands up to be a hero and fix the issue. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Big thx Daniel! -will try it out asap; then we'll see how we update this very issue accordingly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. I have a screen grab if you want me to post 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/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Shannon Kerr: It's deliberate on small screens. The switch happens at around 985px width on desktop screens for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. I have a screen grab if you want me to post it. btw, switching to desktop mode did not make a difference in the appearance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I don't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way, even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I didn't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way, even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Daniel, if I have a trivial, small, cosmetic issue, would you like a ticket or shall I just post it here or email it to you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I didn't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way (with 1.572), even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. Now I know what to expect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas created JENKINS-23885 Time duration missing for inheritance projects Issue Type: Bug Assignee: Unassigned Components: lastfailureversioncolumn, lastsuccessdescriptioncolumn Created: 18/Jul/14 9:20 PM Description: The time duration for Last Success and Last Failure are replaced by "N/A" on all the projects created with the inheritance plugin. Environment: Windows 7 64-bit Project: Jenkins Priority: Trivial Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas updated JENKINS-23885 Time duration missing for inheritance projects Change By: Arun Thomas (18/Jul/14 9:24 PM) Description: ThetimedurationforLastSuccessandLastFailurearereplacedbyN/Aonalltheprojectscreatedwiththeinheritanceplugin inListViewmode . Component/s: project-inheritance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23886) Last successful build artifacts not showing in the main project page.
Arun Thomas created JENKINS-23886 Last successful build artifacts not showing in the main project page. Issue Type: Improvement Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:27 PM Description: For a simple project, after a build runs and artifacts are created, they show up in the main project window. For inheritance projects, they do not. Please add this feature. Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Shannon: Probably best to create an issue. Emailing me would be the worst option as I have nothing to do with these UI changes other than having reviewed some Re Nexus 7, would be interesting to know what the effective resolution is. Could well try to render web pages on ~800px wide or so if possible to have them remain legible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Re Nexus 7, would be interesting to know what the effective resolution is. Could well try to render web pages on ~800px wide or so if possible to have them remain legible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23887) View Full Build Flow does not correctly order build steps
Arun Thomas created JENKINS-23887 View Full Build Flow does not correctly order build steps Issue Type: Bug Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:36 PM Description: I have one child project inheriting from two ordered parent projects. The first parent project is responsible for setting up the environment, then the child project runs, and then the second parent project is responsible for moving the artifacts and archiving them. The flow is: 1. Preparation(Parent1) 2. Build(Child) 3. Clean-up/Archive(Parent2) When the build is executed, the steps run correctly in the expected order. The minor issue, however, is in the "View Full Build Flow" list, the projects seem to be out of order. 1. Preparation 2. Clean-up/Archive 3. Build This does not affect the build process which is good. Nonetheless, it is misleading. Environment: Windows 7 64 bit Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20663) file name encoding broken in zip archives
dogfood commented on JENKINS-20663 file name encoding broken in zip archives Integrated in jenkins_main_trunk #3531 FIXED JENKINS-20663 For now, go back to using ZipOutputStream from Ant that supports setting the filename encoding (present in java.util.zip only in Java 7+). (Revision 84c76253862a2f36f813a7aa45b77d99c1616be4) Result = SUCCESS Jesse Glick : 84c76253862a2f36f813a7aa45b77d99c1616be4 Files : core/src/main/java/hudson/model/DirectoryBrowserSupport.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Daniel Beck commented on JENKINS-23877 With 1.572, long consoles will not display full console while build is still running, only a portion Apparently caused by Timestamper plugin not handling the redesign in 1.572 well, according to the mailing lists. Try disabling that plugin in the job config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Daniel Beck updated JENKINS-23877 With 1.572, long consoles will not display full console while build is still running, only a portion Change By: Daniel Beck (18/Jul/14 9:58 PM) Assignee: PraqmaSupport Affects Version/s: current Component/s: core Component/s: logging Component/s: build-monitor Component/s: console-tail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Het Shannon. Thanks for having a look at this. If you have issues you want addressed then either create a PR with a fix, or create a JIRA. If you have feedback/comments then you can email me or post them to the Jenkins dev 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/d/optout.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Craig Phillips created JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Issue Type: New Feature Assignee: Gregory Boissinot Components: cppcheck Created: 18/Jul/14 10:18 PM Description: For example cppcheckResult/source.All?state=new,resolved Project: Jenkins Priority: Minor Reporter: Craig Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Daniel Beck commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Steven Christou: I merged your fix into a private build of 1.554.3 and verified this fixes the issue as described in my earlier comment from 09/May/14 11:42 PM. Unpatched 1.554.3 doesn't kill 'sleep' on the slave, patched does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Adam Crews commented on JENKINS-22820 Changes are not commited when using a recent git client I can also confirm that it seems to be something related to git 1.9. I do not have this issue with git 1.7 nor 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-5979) Subversion checkout log is very verbose
John Faith commented on JENKINS-5979 Subversion checkout log is very verbose It seems that the SubversionEventHandlerImpl in java/hudson/scm/SubversionEventHandlerImpl.java could take an option and do nothing if set. Is this method's only job to out.println() strings to look like commnad-line svn? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Too much changelog
dan tran commented on JENKINS-23881 Too much changelog looks to me it only happens for the first batch of log, subsequence checks are fine This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23889) Remove Eclipse generate files from source tree
dan tran created JENKINS-23889 Remove Eclipse generate files from source tree Issue Type: Task Assignee: Unassigned Components: p4 Created: 19/Jul/14 12:23 AM Description: this way eclipse will not complain when user try to use m2e to import the projects Those files are .project, .settings, etc Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23890) Error on next changes build
dan tran created JENKINS-23890 Error on next changes build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 19/Jul/14 2:58 AM Description: When there is a scm change in the next jenkins build ( no scheduler ATM) jenkins fails to build. I am able to produce it using workshop.perforce.coma an at my own company's depot. Subsequent manual invocation works ( provided that no new scm changes ) Here is console log Started by user anonymous Building in workspace C:\.jenkins\jobs\p4maven\workspace SCM Task: cleanup workspace: dan-laptop-p4maven-jenkins SCM Task: reverting all pending and shelved revisions. ... list = revert ... rm list | ABANDONED SCM Task: removing all non-versioned files. ... list = reconcile -n -a ... rm list SCM Task: restoring all missing and changed revisions. ... list = reconcile -n SCM Task: syncing files at change: 9725 ... sync C:\.jenkins\jobs\p4maven\workspace/...@9725 ... force update false ... bypass have false Parsing POMs ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:284) at hudson.maven.MavenModuleSetBuild$1.init(MavenModuleSetBuild.java:254) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:247) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:701) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) project=hudson.maven.MavenModuleSet@25e0a843p4maven project.getModules()=[hudson.maven.MavenModule@44169c4ap4maven/com.perforce.p4maven:p4mavenp4maven/com.perforce.p4maven:p4mavenrelativePath:, hudson.maven.MavenModule@76d0e830p4maven/com.perforce.p4maven:p4maven-devp4maven/com.perforce.p4maven:p4maven-devrelativePath:p4maven-dev, hudson.maven.MavenModule@57458e21p4maven/com.perforce.p4maven:p4maven-mojop4maven/com.perforce.p4maven:p4maven-mojorelativePath:p4maven-mojo, hudson.maven.MavenModule@13328cbdp4maven/com.perforce.p4maven:p4maven-providerp4maven/com.perforce.p4maven:p4maven-providerrelativePath:p4maven-provider] project.getRootModule()=hudson.maven.MavenModule@44169c4ap4maven/com.perforce.p4maven:p4mavenp4maven/com.perforce.p4maven:p4mavenrelativePath: FATAL: null java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:284) at hudson.maven.MavenModuleSetBuild$1.init(MavenModuleSetBuild.java:254) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:247) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:701) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Here is another log at build job = A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException:
[JIRA] [svnmerge] (JENKINS-6851) [svnmerge-plugin] Add support for merging from upstream before building.
Hugues Chabot resolved JENKINS-6851 as Fixed [svnmerge-plugin] Add support for merging from upstream before building. Change By: Hugues Chabot (19/Jul/14 4:18 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
