[JIRA] [git-client-plugin] (JENKINS-25389) Allow push of tags created during the build
Mario Mancino created JENKINS-25389 Allow push of tags created during the build Issue Type: New Feature Assignee: Nicolas De Loof Components: git-client-plugin, git-plugin Created: 31/Oct/14 6:11 AM Description: Currently the GIT Plugin only allows to create pre-defined tags, but not to push all tags created during a build. Project: Jenkins Priority: Minor Reporter: Mario Mancino This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master
Steve Maring
commented on JENKINS-18088
Build flow execute on slave but write file on master
Yeah ... but issue for me too. Drop this into the Flow DSL:
import java.net.InetAddress;
println("host: " + InetAddress.getLocalHost().getHostName());
You will see that it always executes on the master. Even if you pull a groovy file out of github and read it out of the workspace on the slave, it will STILL only execute on the master.
It would be nice to have the option of execution on the slave
This message is automatically generated by JIRA.
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] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Daniel Beck commented on JENKINS-25330 Folders should offer to use a hash for workspace path (like matrix does) Ali Raza: >From a technical POV, yes. The package names for logging and the option name would change, that's it. Note that there is no functional or other advantage for you other than this feature being included without installing another plugin; for example the addition to the folder config form uses the same API as e.g. the similar Credentials-related options. In fact, functionally it'd be better left separate, as it'd allow users on older Jenkins + Folders versions to use it as well once I reduce the version requirements. Whether the addition would be accepted by the Folders maintainers is another question. Since this proposal was filed by CloudBees employees I'm hopeful, but whether the specific implementation is acceptable, I don't know. If changes are requested by them, you'd have to evaluate which you prefer. Do you have any other comments/requests regarding this plugin? Is the functionality as expected? Are the parts in which I differed from the acceptance criteria acceptable? (What's still missing is the inline help for the two options, that's still on the todo 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] [build-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master
Daniel Beck
commented on JENKINS-18088
Build flow execute on slave but write file on master
This is not a bug, simply how the plugin (and in fat all job types) works. Use FilePath to write to files in the workspace, e.g.:
build.workspace.child("foo").write("bar", "UTF-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] [build-flow-plugin] (JENKINS-18088) Build flow execute on slave but write file on master
Daniel Beck
edited a comment on JENKINS-18088
Build flow execute on slave but write file on master
This is not a bug, simply how the plugin (and in fact all job types) works. Use FilePath to write to files in the workspace, e.g.:
build.workspace.child("foo").write("bar", "UTF-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] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Ali Raza commented on JENKINS-25330 Folders should offer to use a hash for workspace path (like matrix does) Hi Daniel, I didn't get much of a chance to test today. Will this weekend. A few questions 1. I have folder subfolder 1 - subfolder 2 etc. Should this option be checked in all the folders for the desired effect? 2. Can you add some screenshot of what the results look like before and after this setting. Thanks This message is automatically generated by JIRA. 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] [configurationslicing-plugin] (JENKINS-25378) java.lang.IllegalStateException: Form too large ... 200000
Eric Düll commented on JENKINS-25378 java.lang.IllegalStateException: Form too large ... 20 Sorry, but I don't get yours or mwebbers point. The first page of the Google job results led me to here, opening an issue for the configuration slicing plugin as requested. In https://issues.jenkins-ci.org/browse/JENKINS-20327 you said that this issue is not a core problem but a problem of the job configuration slicing plugin. The next suggestion of mwebber was: (16/Okt/14 3:26 PM) @marco, you should open a separate issue for the job config slicing plugin (this issue is for the core problem). Also, if you read the comments above, you will find a workaround. And just to remeber: I do not have millions of jobs. I just have 100. Why does the configuration slicing plugin lists all the modules of a job at all? The unnecessary listing of modules causes this problem. From my point of view this issue is not fixed at all, I just have a workaroud and it would be great if you could reopen it or at least create a follow up 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] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Michael Niestegge commented on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, too . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Michael Niestegge edited a comment on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, too . As a workaround I installed Compact Columns and order the view by the last state. This message is automatically generated by JIRA. 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge updated JENKINS-7844 A Filter to sort jobs by last run time. Change By: Michael Niestegge (31/Oct/14 8:35 AM) Attachment: view.png Attachment: settings.png This message is automatically generated by JIRA. 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-7844) A Filter to sort jobs by last run time.
Michael Niestegge edited a comment on JENKINS-7844 A Filter to sort jobs by last run time. I am missing this feature, too . As a workaround I installed Compact Columns and order the view by the last state. This message is automatically generated by JIRA. 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-25390) New design breaks build history layout
Thorsten Meinl created JENKINS-25390 New design breaks build history layout Issue Type: Bug Assignee: Unassigned Attachments: broken_layout.png, ok.png Components: core Created: 31/Oct/14 8:48 AM Description: With the new design the build history panel on the left of each job is broken. It's rendered too small so that build date and build size are wrapped which looks darn-ugly. Funnily, if I make the browser window smaller it suddenly looks correct (see attached screenshots). Apart from that the new design seems to needs considerably more space, probably because the font size is larger (or because of the changed font). This is a drawback in my opinion. Environment: Jenkins 1.580.1 (LTS), Linux, Firefox 24.8 Project: Jenkins Priority: Minor Reporter: Thorsten Meinl This message is automatically generated by JIRA. 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] [cucumber-testresult-plugin] (JENKINS-21835) Cucumber Test Result Plugin does not correctly parse Scenario Outline results
teilo resolved JENKINS-21835 as Fixed Cucumber Test Result Plugin does not correctly parse Scenario Outline results workaround enabled. Enabling this may cause tests that have failed to not cause the build to be marked as unstable - but there is no information about the result so there is nothing else that can be done. The cause of the issue has fixes upstream - so it is a matter of getting those fixes into all the relevant tools to get a real fix. Change By: teilo (31/Oct/14 8:48 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.
[JIRA] [core] (JENKINS-25390) New design breaks build history layout
Thorsten Meinl updated JENKINS-25390 New design breaks build history layout Another issue: the duration column in the tests view is also too small, see screenshot. It may be due to the german translation but still this was not problem before. Change By: Thorsten Meinl (31/Oct/14 8:52 AM) Attachment: duration_column_too_small.png This message is automatically generated by JIRA. 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-25390) New design breaks build history layout
Thorsten Meinl updated JENKINS-25390 New design breaks build history layout Another issue: the duration column in the tests view is also too small, see screenshot. It may be due to the german translation but still this was not problem before. Change By: Thorsten Meinl (31/Oct/14 8:52 AM) Attachment: duration_column_too_small.png This message is automatically generated by JIRA. 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-25390) New design breaks build history layout
Daniel Beck updated JENKINS-25390 New design breaks build history layout Disk Usage plugin's size badge is much larger than any badges shipped with core, so that's not surprising. Change By: Daniel Beck (31/Oct/14 9:21 AM) Labels: user-experience This message is automatically generated by JIRA. 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] [cloudbees-folder-plugin] (JENKINS-25391) Cannot delete project
Morne Joubert created JENKINS-25391 Cannot delete project Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 31/Oct/14 9:37 AM Description: When trying to delete any project that is inside the cloudbees-folder i get the following. I am sure we did not get this on 1.565.2 but am now getting this is 1.565.3 javax.servlet.ServletException: java.lang.NumberFormatException: null at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:783) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:733) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:863) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:636) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:198) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at
[JIRA] [p4-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error Do you have any idea what might have changed to cause the issue? e.g. Does the workspace 'uc_vj_ci' still exist? Has its ownership changed? Are you using triggers, a broker, or changed any server permissions? The Perforce server logs may hold a clue, can you see any connections from jenkins.p4-plugin/1.0.xx/xxx To try and get past the issue try creating a new Credential, a new Jenkins job and Perforce Workspace. This message is automatically generated by JIRA. 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-pipeline-plugin] (JENKINS-25391) Cannot delete project
Daniel Beck updated JENKINS-25391 Cannot delete project From the error (and experience) it appears to be related to build pipeline. Change By: Daniel Beck (31/Oct/14 10:18 AM) Assignee: JesseGlick Component/s: build-pipeline-plugin Component/s: cloudbees-folder-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7844) A Filter to sort jobs by last run time.
Michael Niestegge updated JENKINS-7844 A Filter to sort jobs by last run time. Change By: Michael Niestegge (31/Oct/14 10:29 AM) Attachment: view.png This message is automatically generated by JIRA. 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] [cloudbees-folder-plugin] (JENKINS-25330) Folders should offer to use a hash for workspace path (like matrix does)
Daniel Beck commented on JENKINS-25330 Folders should offer to use a hash for workspace path (like matrix does) 1. I have folder subfolder 1 - subfolder 2 etc. Should this option be checked in all the folders for the desired effect? It is enabled for a job when any folder in it's hierarchy has this enabled. So if FoldA/FoldB has the property set, it will be effective for FoldA/FoldB/job1 and FoldA/FoldB/FoldC/job2, but not for FoldA/job3 or job4. For the 'advanced' option to place the workspace inside the folder's workspace, it uses the configuration of the innermost/most deeply nested folder that has 'Use short workspace enabled'. Example: FoldA - no short workspace selected FoldA/FoldB - short workspace selected FoldA/FoldB/FoldC - short workspace selected, and opting in to place it inside folder's workspace FoldA/FoldB/FoldC/FoldD - no short workspace selected FoldA/FoldB/FoldC/FoldD/FoldE - short workspace selected Then the following behavior will occur: FoldA/job1 - Workspace is JENKINS_HOME/workspace/FoldA/job1 (no element in the hierarchy has the option enabled) FoldA/FoldB/job2 - Workspace is JENKINS_HOME/workspace/01234abcd (enabled through parent folder, but not placed inside the parent folder's workspace) FoldA/FoldB/FoldC/job3 - Workspace is JENKINS_HOME/workspace/FoldA/FoldB/FoldC/abcd01234 (enabled through parent folder, and placed inside parent folder's workspace) FoldA/FoldB/FoldC/FoldD/job4 - Workspace is JENKINS_HOME/workspace/FoldA/FoldB/FoldC/4321dcba (enabled through grandparent folder, and placed inside grandparent folder's workspace) FoldA/FoldB/FoldC/FoldD/FoldE/job5 - Workspace is JENKINS_HOME/workspace/9876cafe (enabled through parent folder, and no placed inside parent folder's workspace) 2. Can you add some screenshot of what the results look like before and after this setting. I'm not sure what you want to see. Windows Explorer? The build log mentions where the workspace is (for freestyle jobs at least, didn't try for Build Flow, and it looks like Building on master in workspace /var/lib/jenkins/workspace/c032452b(enabled) orBuilding on master in workspace /var/lib/jenkins/workspace/FoldA/FoldB/c032452b(enabled and configured to place the short workspace inside the folder's workspace); rather than the default of:Building on master in workspace /var/lib/jenkins/workspace/FoldA/FoldB/job2 Results are similar on Windows, just e.g. C:\Jenkins rather than /var/lib/jenkins. This message is automatically generated by JIRA. 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
Omar Ahmad created JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 31/Oct/14 10:37 AM Description: This issue can be reproduced via carrying out the following steps: 1. Create a new Jenkins maven project 2. As a pre step, add an "execute system groovy scrip" 3. Type a simple command which throws an exception 4. Add a maven clean in the main build 5. Add a post build invoke maven target step and add a clean (tick the selection which states to only run post builds if success) 6. Save and execute the job. Observer how the groovy exception stack trace is shown at the very end and the post build step was attempted to run regardless of the groovy script failure. Project: Jenkins Priority: Major Reporter: Omar Ahmad This message is automatically generated by JIRA. 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-plugin] (JENKINS-25300) Several of my p4 projects do not list *any* changes between builds
SCM/JIRA link daemon commented on JENKINS-25300 Several of my p4 projects do not list *any* changes between builds Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/CheckoutChanges.java src/main/java/org/jenkinsci/plugins/p4/CheckoutTask.java src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java src/main/java/org/jenkinsci/plugins/p4/workspace/ManualWorkspaceImpl.java http://jenkins-ci.org/commit/p4-plugin/341b8812274091ca12117facd16cbc3994f94fbe Log: Improvements to SCM Polling Moved change list calculation into a new class CheckoutChanges. Should enable normal build to build every thing and poll to follow polling behaviour: limit based on pin and per-change if set. JENKINS-25300 This message is automatically generated by JIRA. 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] [deployment-notification-plugin] (JENKINS-23569) Missing index.jelly resource for org.jenkinsci.plugins.deployment.promoted_builds.DeploymentPromotionCondition
SCM/JIRA link daemon commented on JENKINS-23569 Missing index.jelly resource for org.jenkinsci.plugins.deployment.promoted_builds.DeploymentPromotionCondition Code changed in jenkins User: fbelzunc Path: src/main/resources/org/jenkinsci/plugins/deployment/DeploymentPromotionCondition/index.jelly http://jenkins-ci.org/commit/deployment-notification-plugin/1d208239f2487daead5674541b6a953286a72dba Log: FIX JENKINS-23569 This message is automatically generated by JIRA. 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] [deployment-notification-plugin] (JENKINS-23569) Missing index.jelly resource for org.jenkinsci.plugins.deployment.promoted_builds.DeploymentPromotionCondition
SCM/JIRA link daemon commented on JENKINS-23569 Missing index.jelly resource for org.jenkinsci.plugins.deployment.promoted_builds.DeploymentPromotionCondition Code changed in jenkins User: Nicolas De loof Path: src/main/resources/org/jenkinsci/plugins/deployment/DeploymentPromotionCondition/index.jelly http://jenkins-ci.org/commit/deployment-notification-plugin/ad614a2d5d6dffd540d13bce1df84d3f220fa371 Log: Merge pull request #1 from fbelzunc/patch-1 FIX JENKINS-23569 Compare: https://github.com/jenkinsci/deployment-notification-plugin/compare/9e8f6f667bb8...ad614a2d5d6d This message is automatically generated by JIRA. 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-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains a whitespace
Derk-Jan Hartman commented on JENKINS-24686 scm-sync-configuration fails if job name contains a whitespace me three ! This message is automatically generated by JIRA. 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-7844) A Filter to sort jobs by last run time.
Daniel Beck resolved JENKINS-7844 as Fixed A Filter to sort jobs by last run time. Compact Columns solves this issue. Change By: Daniel Beck (31/Oct/14 12:21 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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] [configurationslicing-plugin] (JENKINS-25378) java.lang.IllegalStateException: Form too large ... 200000
Daniel Beck commented on JENKINS-25378 java.lang.IllegalStateException: Form too large ... 20 In https://issues.jenkins-ci.org/browse/JENKINS-20327 you said that this issue is not a core problem but a problem of the job configuration slicing plugin. To clarify, I meant that Marco's comment did not refer to the issue the other report was about (moving the goal posts after a change was committed isn't useful); not necessarily that it's a bug in JCS. Why does the configuration slicing plugin lists all the modules of a job at all? This should have been fixed in 1.37.1, released over a year ago. Looks like JENKINS-18455 was reopened because of this, and it's tracked there. The problem is that the plugin sends huge forms by design (that's how the UI works) if there are many projects, and current Winstone-Jetty doesn't like that. If that is what this report is about, then please reopen (and clarify that in the issue description). A redesigned form may help here. But since the plugin has no control over embedded Winstone-Jetty, it cannot increase the limit on its own. (And FWIW, that is already being discussed in https://github.com/jenkinsci/winstone/pull/20 so maybe this is soon obsolete anyway) To just get rid of the problem (one instance's DoS protection breaks another instance's config forms), you can set the System property as described in the other issue reports. This message is automatically generated by JIRA. 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] [groovy-plugin] (JENKINS-25392) Post Build Steps still running regardless of Pre Step Groovy Script failure
vjuranek commented on JENKINS-25392 Post Build Steps still running regardless of Pre Step Groovy Script failure Hi, groovy plugin itself doesn't provide any pre-build actions. I guess that you use M2 Extra Steps Plugin (Jenkins core 1.433) or Jenkins core functionality. Please move this bug to appropriate component (m2-extra-steps-plugin or maven-plugin) according to the version you use. Thanks. This message is automatically generated by JIRA. 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] [configurationslicing-plugin] (JENKINS-18455) all modules of all maven projects are listed separately
Eric Düll commented on JENKINS-18455 all modules of all maven projects are listed separately The plugin lists all modules for the following tasks SCM Timer Trigger Slicer JDK per project Block Build when Downstream Building Slicer (bool) Block Build when Upstream Building Slicer (bool) Discard Old Builds Slicer - Days to keep artifacts Discard Old Builds Slicer - Days to keep builds Discard Old Builds Slicer - Max # of builds to keep Discard Old Builds Slicer - Max # of builds to keep with artifacts E-mail Notification Editable Email Notification Job Disabled Build Slicer (bool) Job Disabled Build Slicer (String) Tied Label Slicer Timer Trigger Slicer It does not add modules for the following tasks Ant version per project Custom Workspace Slicer Execute shell slicer Execute Windows batch command slicer Maven Goals and Options (Maven project) Maven top-level targets Maven Version MAVEN_OPTS per Maven project Parameters Quiet Period Slicer This message is automatically generated by JIRA. 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] [accurev-plugin] (JENKINS-24710) Invalid Accurev change log entries ([accusync])
Skylar Sutton commented on JENKINS-24710 Invalid Accurev change log entries ([accusync]) Did a little additional investigation today: Does not occur in Accurev plugin v0.6.27 Does occur in Accurev plugin v0.6.30 All bogus entries are transactions with an action="" and no file modifications. This message is automatically generated by JIRA. 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] [configurationslicing-plugin] (JENKINS-18455) all modules of all maven projects are listed separately
Daniel Beck commented on JENKINS-18455 all modules of all maven projects are listed separately Fairly obvious left overs from https://github.com/jenkinsci/configurationslicing-plugin/commit/cfcd3d0f6aec34035e773d656d1991aa45a8061c The fix in https://github.com/jenkinsci/configurationslicing-plugin/commit/eefdd378edd33db54ec7e2abcddbc63ca7428fec only took care of Maven Version. This message is automatically generated by JIRA. 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-25393) UI: Build History box looks bad with medium to long build labels
Paul Mendelson
created JENKINS-25393
UI: Build History box looks bad with medium to long build labels
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
31/Oct/14 2:13 PM
Description:
The build history box allocates about 50% of its width to the build label and about 50% to the build time. This often means that the build label wraps after the status icon.
The simplest solution would be to define the style:
#buildHistory .build-name {
/* max-width: 120px; */
white-space: nowrap;
}
Along with that it would be good to either make the build time use a smaller font size or use a format for the date that takes less space or use a different date format based on how long ago the build was.
Project:
Jenkins
Priority:
Minor
Reporter:
Paul Mendelson
This message is automatically generated by JIRA.
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-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error I created a new Jenkins Job, new Credential and a new Perforce Workspace. The Job does nothing other than the default Perforce action(sync). Same as before, the job ran fine on first run and then failed on second. This message is automatically generated by JIRA. 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-failure-analyzer-plugin] (JENKINS-25394) Sort failure causes on management page
Michael Keppler created JENKINS-25394 Sort failure causes on management page Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 31/Oct/14 2:18 PM Description: Looking at a rather large page for managing build failure causes, I always have to scan the complete page, when editing some existing cause, as they seem to be in random order. Any chance for sorting the page by cause name, alphabetical? Or even use a sortable table (with the name being sorted by default), if other people want to sort by category and other columns. Project: Jenkins Priority: Minor Reporter: Michael Keppler This message is automatically generated by JIRA. 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-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Philip Cheong commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I downgraded to the LTS Jenkins ver. 1.580.1 today and just hit the same problem. This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error Yes I am using Build Now to build. Java version is java version "1.7.0_65" OpenJDK Runtime Environment (rhel-2.5.1.2.el6_5-x86_64 u65-b17) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) #uname -a Linux 38d1e80d522e 2.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37:12 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Jenkins is run as a war file. Something to note is that all of this is being run in a docker environment. It was working before but suddenly started showing this strangeness. Is there anything else in environment that you can think of ? env variables etc This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error This is strange? I presume you are using the Build Now button for both builds? What Java and version are you using? I don't use CentOS, but perhaps it ships with an old Java version? Are you running Jenkins as a Jar or with something like Tomcat. What permission does the user running the job have in Perforce? It will need a minimum of 'open' to support the reconcile 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/d/optout.
[JIRA] [core] (JENKINS-25393) UI: Build History box looks bad with medium to long build labels
Daniel Beck commented on JENKINS-25393 UI: Build History box looks bad with medium to long build labels May even be a duplicate of JENKINS-25381. This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error Do you have 'P4_CLIENT', 'change' or 'label' set in the environment? I have just made a new release, which cleaned up some of the client/workspace code. However, most of the changes were related to Polling, so I doubt it will fix your issue. The 1.0.17 might not be on the update centre (typically takes a few hours for Jenkins to push it out). You can download it here: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/p4/ This message is automatically generated by JIRA. 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge created JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Issue Type: Bug Assignee: Unassigned Attachments: AuthExcpetion.png Components: repository-connector-plugin Created: 31/Oct/14 3:14 PM Description: I installed an update on our jenkins installation and also updated several plugins. After the update several jobs were not able to retrieve the latest release version from my maven repository. Investigating the console output showed me the mentioned exception when trying to download the maven-metadata.xml. For further details please see I downgraded the Repository Connector Plugin to 0.8.2 an everything works again. So the bug seems to be part of the 1.0.1 release of the plugin. Environment: Jenkins 1.585 Repository Connector Plugin 1.0.1 Project: Jenkins Labels: jenkins exception plugin Priority: Minor Reporter: Michael Niestegge This message is automatically generated by JIRA. 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] [google-oauth-plugin] (JENKINS-24160) Can this plugin support Google OAuth 2.0?
kylecordes commented on JENKINS-24160 Can this plugin support Google OAuth 2.0? It looks like such an issue already exists: JENKINS-23431 ...And I put some hopefully relevant comments there. So this one can probably be closed as a duplicate. I don't know if it's something I can do as a mere end-user of this particular issue tracker instance This message is automatically generated by JIRA. 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-plugin] (JENKINS-25241) svn+ssh checkout fails on remote nodes
Paulo Moreira commented on JENKINS-25241 svn+ssh checkout fails on remote nodes Hello, Same problem with: Jenkins ver. 1.587 SSH Slaves plugin 1.8 Subversion Plugin 2.4.4 This message is automatically generated by JIRA. 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] [repository-connector-plugin] (JENKINS-25395) org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml
Michael Niestegge updated JENKINS-25395 org.apache.maven.wagon.authorization.AuthorizationException when requesting maven-metadata.xml Change By: Michael Niestegge (31/Oct/14 3:28 PM) Priority: Minor Major This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error I have updated my setup to use the 1.0.17 version but the problem remains. There are no P4PORT/P4CONFIG/P4 anything in env. This message is automatically generated by JIRA. 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] [rebuild-plugin] (JENKINS-19910) Support rebuilding projects using maven metadata plugin
Mads Mohr Christensen resolved JENKINS-19910 as Fixed Support rebuilding projects using maven metadata plugin Included in version 1.21 Change By: Mads Mohr Christensen (31/Oct/14 3:59 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] [p4-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error Please can you check the new Build Job config.xml file for the line: scm class="org.jenkinsci.plugins.p4.PerforceScm" plugin="p4@1.0.17" and the credentials.xml for: org.jenkinsci.plugins.p4.credentials.P4PasswordImpl plugin="p4@1.0.17" Do you get the error if you use the Build Review button and set: Label: now Status: submitted (leave the others empty) This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error Hmm. All the lines show p4@1.0.16 however in Jenkins list of Installed plugins it shows 1.0.17 for Perforce plugin. I tried the Build review settings and this is what I get ERROR: Unable to setup workspace: java.lang.NullPointerException ERROR: Unable to setup workspace: java.lang.NullPointerException Finished: FAILURE This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error The ERROR is strange, did you remove any context? The console log should look something like: Started by user Building in workspace /var/lib/jenkins/jobs/Test001/workspace Connected to server: x.perforce.com:1666 Connected to client: jenkins-node-project-platform SCM Task: cleanup workspace: jenkins-node-project-platform 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 -ed SCM Task: syncing files at client/label: now ... sync /var/lib/jenkins/jobs/Test001/workspace/...@now ... force update false ... bypass have false listing changes: //jenkins-node-project-platform/...@950227,now Finished: SUCCESS Do you not even see the 'Started by user' text? Please can you send me the client spec, e.g. p4 client -o uc_vj_ci ... Is this a normal client or one designed for a BuildReplica or EdgeServer? ... Is the Host field 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/d/optout.
[JIRA] [p4-plugin] (JENKINS-25364) Unable to update workspace error
Paul Allen commented on JENKINS-25364 Unable to update workspace error Please can you also try this against your server and not via the proxy. It just eliminates one more item. This message is automatically generated by JIRA. 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-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error Actually the full log is Started by user Naveen Gogineni Building in workspace /var/jenkins_home/jobs/VJ_BUILD_2/workspace ERROR: Unable to setup workspace: java.lang.NullPointerException ERROR: Unable to setup workspace: java.lang.NullPointerException Finished: FAILURE Client spec is Client: uc_vj_ci_2 Update: 2014/10/31 07:15:06 Access: 2014/10/31 10:42:00 Owner: p4build_vj_ci Root: /var/jenkins_home/jobs/VJ_BUILD_2/workspace Options:noallwrite clobber nocompress unlocked nomodtime normdir SubmitOptions: submitunchanged LineEnd:local View: //VJ/Technical/Software/... //uc_vj_ci_2/Technical/Software/... This message is automatically generated by JIRA. 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-25390) New design breaks build history layout
Daniel Beck resolved JENKINS-25390 as Duplicate New design breaks build history layout Duplicates JENKINS-25393 (while that is newer, it also has the link to JENKINS-25381) Change By: Daniel Beck (31/Oct/14 5:53 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-24160) Can this plugin support Google OAuth 2.0?
Daniel Beck commented on JENKINS-24160 Can this plugin support Google OAuth 2.0? So this one can probably be closed as a duplicate. I don't know if it's something I can do as a mere end-user of this particular issue tracker instance Not worth the 5 clicks it takes, but go for 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] [google-oauth-plugin] (JENKINS-24160) Can this plugin support Google OAuth 2.0?
kylecordes closed JENKINS-24160 as Not A Defect Can this plugin support Google OAuth 2.0? duplicate of JENKINS-23431 Change By: kylecordes (31/Oct/14 6:22 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/d/optout.
[JIRA] [p4-plugin] (JENKINS-25364) Unable to update workspace error
Naveen Gogineni commented on JENKINS-25364 Unable to update workspace error I tried to sync to server directly from command line and noticed that it completed without error but didn't sync all files. So I used the "-f" option to force sync and that synced everything. So in the Jenkins job I changed the Populate Options from "Auto clean and sync" to "Forced clean and sync". That seems to go well with the sync and my build progresses. I am going to test more and report. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-25396) Build flow job and build pages break when last build is aborted
Luc Cary created JENKINS-25396 Build flow job and build pages break when last build is aborted Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow-plugin Created: 31/Oct/14 8:06 PM Description: When a build flow job is running, and the most recent build is canceled, the job page and that build page breaks. Attempting to get job page raises a 500-error and returns the following warning in the jenkins log: Oct 28, 2014 4:14:39 AM winstone.Logger logInternal WARNING: Untrapped Error in Servlet javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.532.2.jar!/hudson/model/AbstractProject/main.jelly:76:66: st:include org.apache.commons.jelly.JellyTagException: java.util.concurrent.CancellationException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at
[JIRA] [build-flow-plugin] (JENKINS-25396) Build flow job and build pages break when last build is aborted
Luc Cary commented on JENKINS-25396 Build flow job and build pages break when last build is aborted More details for reproducing the failure: have the flow run builds in parallel, trigger flow using gerrit-trigger, abort the flow by either clicking 'X' from the job's build history window, or from the 'X' next to the status bar in build and console log pages, or by uploading a new patchset to gerrit. This message is automatically generated by JIRA. 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-failure-analyzer-plugin] (JENKINS-25396) Build flow job and build pages break when last build is aborted
Daniel Beck updated JENKINS-25396 Build flow job and build pages break when last build is aborted Change By: Daniel Beck (31/Oct/14 9:01 PM) Component/s: build-failure-analyzer-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [changelog-history-plugin] (JENKINS-25397) SCM history lost when job fails
Nathan Malinoski created JENKINS-25397 SCM history lost when job fails Issue Type: Bug Assignee: Unassigned Components: changelog-history-plugin Created: 31/Oct/14 9:19 PM Description: This issue cropped up for me while I was debugging jobs affected by JENKINS-21785 (some jobs were never reconfigured with the additional credentials). I noticed that the changelog history (Recent Changes) for both the failed and the following successful jobs would be blank. What would happen: 1. An external for a project in the Subversion repo would get updated 2. A job that checks out that aforementioned project would be started (Note this job is not configured with the additional credentials like it's supposed to) 3. The main project as well as the external would be checked out from the repo successfully 4. The Subversion plugin would throw a revision check error on the external (as expected), causing the build to fail 5. The job is run again, resulting in a successful build The first build in this scenario had new stuff to deploy compared to the previous, successful build. If the build had been successful, these changes and their revision numbers would be noted in the Recent Changes section for the job, but they weren't. This behavior kind of makes sense to me since they weren't deployed*; however, on the subsequent build that was successful, again, no changes were logged--and this time they were deployed! I would have expected the changes to be logged in at least one of these jobs. It would equally make sense to log changes introduced in a given build even if it fails, but then only when the a compilation failure is caused by borked code, so you could see which changes contributed to the failure; however, in this case, the job failed due to a credentials issue--before any build steps were run. Environment: Jenkins 1.587; Credentials Plugin 1.18, Subversion Plugin 2.4.4 RHEL 6.6 Project: Jenkins Priority: Minor Reporter: Nathan Malinoski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo
commented on JENKINS-20387
git submodule update timeout value should be configurable per job
I'm disappointed to report that I can still reproduce this issue. I have Jenkins 1.585, git plugin 2.2.7, and git client plugin 1.11.0. The last comment here says it's fixed in git plugin 2.3, but that was three months ago. Is 2.3 on the way?
In any case, I have been using the same test project as mentioned earlier, configured with a 240 minute timeout on submodules. The output is below. You can see the timeouts in the output, but it seems like they are commented out.
{{
Building in workspace C:\Jenkins\jobs\git-test\workspace
Cloning the remote Git repository
Cloning repository g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe init C:\Jenkins\jobs\git-test\workspace # timeout=10
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe --version # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/:refs/remotes/origin/ # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.fetch +refs/heads/:refs/remotes/origin/ # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config remote.origin.url g...@github.com:stimulant/IMR4.git # timeout=10
Fetching upstream changes from g...@github.com:stimulant/IMR4.git
C:\Program Files (x86)\Git\cmd\git.exe fetch --tags --progress g...@github.com:stimulant/IMR4.git +refs/heads/:refs/remotes/origin/ # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/dev^{commit}" # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe rev-parse "refs/remotes/origin/origin/dev^{commit}" # timeout=10
Checking out Revision 696e4dea88730d445406e6a7dd5101b00be2d751 (refs/remotes/origin/dev)
C:\Program Files (x86)\Git\cmd\git.exe config core.sparsecheckout # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe checkout -f 696e4dea88730d445406e6a7dd5101b00be2d751 # timeout=240
C:\Program Files (x86)\Git\cmd\git.exe rev-list 696e4dea88730d445406e6a7dd5101b00be2d751 # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe remote # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule init # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule sync # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe config --get remote.origin.url # timeout=10
C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive
ERROR: Timeout after 10 minutes
FATAL: Command "C:\Program Files (x86)\Git\cmd\git.exe submodule update --init --recursive" returned status code -1:
}}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job No, git plugin 2.3 has not released. The 2.3 beta 4 release is available in the experimental update center. Since you're using Jenkins 1.585, you can use the experimental update center and install 2.3 beta 4. The 2.3 beta 4 release should be very nearly the same quality and stability as the pre-release 2.2.8 version of the plugin. They've been kept in close synchronization. The git plugin 2.3 is not likely to release from beta very soon, because it depends on Jenkins version 1.568 or newer. The git plugin is used by so many installations that we generally don't require a Jenkins version that is newer than about 1 year old. That allows users of "stable" Jenkins servers to continue installing newer versions of plugin without requiring that they upgrade their Jenkins version. Currently, that means the git plugin supports Jenkins 1.509 and newer. Soon we may switch to require at least Jenkins 1.532, but it will likely be 6+ months before the plugin is ready to support Jenkins 1.580 (the first long term support version after 1.568). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo commented on JENKINS-20387 git submodule update timeout value should be configurable per job Thanks for your reply. I am now on git plugin 2.3-beta-4. I see the same result. In the output above, note the "# timeout=NN" at the end of each command. I'm still seeing that with the new plugin. I'm guessing that comments out the timeout argument. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Daniel Beck commented on JENKINS-20387 git submodule update timeout value should be configurable per job Josh Santangelo: Timeout as being shown is only informational, as it's not a command argument, but how Jenkins waits for the process to quit. https://github.com/jenkinsci/git-client-plugin/blob/53fd10a7601906cb80c5fbf56d8639de747d29d8/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1427 https://github.com/jenkinsci/git-client-plugin/blob/53fd10a7601906cb80c5fbf56d8639de747d29d8/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1431 This message is automatically generated by JIRA. 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-25397) SCM history lost when job fails
Nathan Malinoski updated JENKINS-25397 SCM history lost when job fails Change By: Nathan Malinoski (01/Nov/14 12:20 AM) Component/s: core Component/s: changelog-history-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25397) SCM history lost when job fails
Nathan Malinoski commented on JENKINS-25397 SCM history lost when job fails @Daniel Beck: Side effect of not reading the instructions closely enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job I am not sure why you're not seeing it in the log file. I used git plugin 2.2.7 with git client plugin 1.11.0, opened the "Advanced submodules" and set the timeout in minutes for submodule operations to 39. That gave the following output on initial build: First time build. Skipping changelog. git remote # timeout=10 git submodule init # timeout=10 git submodule sync # timeout=10 git config --get remote.origin.url # timeout=10 git submodule update # timeout=39 When I ran that same build a second time, it reported: Checking out Revision 021ab742e3593a863a39584f2309be22cf7a9307 (refs/remotes/origin/tests/getSubmodules) git config core.sparsecheckout # timeout=10 git checkout -f 021ab742e3593a863a39584f2309be22cf7a9307 git rev-list 021ab742e3593a863a39584f2309be22cf7a9307 # timeout=10 git remote # timeout=10 git submodule init # timeout=10 git submodule sync # timeout=10 git config --get remote.origin.url # timeout=10 git submodule update # timeout=39 Did you set the timeout value in the "Advanced submodules" section of the job configuration, or somewhere 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/d/optout.
[JIRA] [performance-plugin] (JENKINS-23158) unsorted URIs in the Performance Report
Hitesh Patel resolved JENKINS-23158 as Fixed unsorted URIs in the Performance Report https://github.com/jenkinsci/performance-plugin/pull/35 Change By: Hitesh Patel (01/Nov/14 2:47 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.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Josh Santangelo commented on JENKINS-20387 git submodule update timeout value should be configurable per job I had the extended timeout in the "advanced clone behaviours" and "advanced checkout behaviours" sections. I did not have it in "advanced submodules behaviours". When I configured it there, it seemed to work correctly. All three of these claim to honor "org.jenkinsci.plugins.gitclient.Git.timeout" in their help text. If I set that globally, will it be permanently sorted for all jobs? Thanks again for your help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-20387) git submodule update timeout value should be configurable per job
Mark Waite commented on JENKINS-20387 git submodule update timeout value should be configurable per job If you set that property, as far as I know, it will be honored for all jobs which execute on that node and do not set a timeout value. Jobs on other nodes (slaves, for example) will not honor that setting unless you set the property in the slave java virtual machine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-25387) JGit in git client should support reference repositories
Mark Waite updated JENKINS-25387 JGit in git client should support reference repositories Change By: Mark Waite (01/Nov/14 3:22 AM) Summary: JGit implentationofGitClientPlugin ingitclient should also support referencerepositories This message is automatically generated by JIRA. 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.
