[JIRA] [maven] (JENKINS-21893) Maven Build gets slow after update to Jenkins ver. 1.532.2
Martin Nattrodt resolved JENKINS-21893 as Fixed Maven Build gets slow after update to Jenkins ver. 1.532.2 It seams that the new Version needs more Memory. After putting more Memory to the Slave and the Server the Build time was stable again. Change By: Martin Nattrodt (24/Feb/14 8:00 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl commented on JENKINS-21861 option to include attachment with console.txt from failed slaves What is the specific name of the plugin? I can't find one called "Matrix Projects" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21930) Jobs fail due to node went offline during the build
Marc Günther created JENKINS-21930 Jobs fail due to node went offline during the build Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Feb/14 8:47 AM Description: I keep getting failures on random jobs (see example below), when I take a slave offline. I thought the purpose of "take slave offline" (versus disconnecting a slave) is that running jobs can continue to run, but no new jobs are started, and I can then disconnect the slave when all jobs are finished (we have a small script which does exactly that, to take a slave out of the cluster). With the current behaviour, it is impossible to cleanly shutdown a slave. Expected: Taking a slave offline should NEVER have any impact on any of the jobs running on that slave. They should not even be aware of the fact. Looks like the node went offline during the build. Check the slave log for the details.FATAL: /var/lib/jenkins/logs/slaves/null/slave.log (No such file or directory) java.io.FileNotFoundException: /var/lib/jenkins/logs/slaves/null/slave.log (No such file or directory) at java.io.RandomAccessFile.open(Native Method) at java.io.RandomAccessFile.init(RandomAccessFile.java:212) at org.kohsuke.stapler.framework.io.LargeText$FileSession.init(LargeText.java:397) at org.kohsuke.stapler.framework.io.LargeText$2.open(LargeText.java:120) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:210) at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:159) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:605) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Project: Jenkins Priority: Major Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-21931) Uncaught Exception when using multiple checkout threads ( Checkout Thread Pool Size 1)
Matthias Rump created JENKINS-21931 Uncaught Exception when using multiple checkout threads ( Checkout Thread Pool Size 1) Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 24/Feb/14 9:21 AM Description: During the checkout process an uncaught Exception is thrown that fails the build. DEBUG IntegritySCM - Checkout on API thread: hudson.scm.APISession@fe9ee5 INFO IntegritySCM - java.util.concurrent.ExecutionException: java.lang.Exception: MKS124803: Internal error detected: Exception was: java.lang.RuntimeException: Release MKS Source registry for multiple updates: Attempt to release when not active! INFO IntegritySCM - at java.util.concurrent.FutureTask$Sync.innerGet(null:-1) INFO IntegritySCM - at java.util.concurrent.FutureTask.get(null:-1) INFO IntegritySCM - at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:361) INFO IntegritySCM - at hudson.scm.IntegrityCheckoutTask.invoke(IntegrityCheckoutTask.java:25) INFO IntegritySCM - at hudson.FilePath.act(FilePath.java:914) INFO IntegritySCM - at hudson.FilePath.act(FilePath.java:887) INFO IntegritySCM - at hudson.scm.IntegritySCM.checkout(IntegritySCM.java:789) INFO IntegritySCM - at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) INFO IntegritySCM - at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) INFO IntegritySCM - at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) INFO IntegritySCM - at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) INFO IntegritySCM - at hudson.model.Run.execute(Run.java:1670) INFO IntegritySCM - at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) INFO IntegritySCM - at hudson.model.ResourceController.execute(ResourceController.java:88) INFO IntegritySCM - at hudson.model.Executor.run(Executor.java:231) This happens only if the "Checkout Thread Pool Size" is 1. The occurrence of the exception is directly related to the "Checkout Thread Pool Size" : the bigger the pool, the more likely an exception is thrown. Environment: Jenkins 1.551 PTC-Integrity Plugin 1.23 Integrity Client and Server Version 10.4 Integrity Client as Integration Point Server Project: Jenkins Priority: Critical Reporter: Matthias Rump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19074) Why More than 1 builds are needed for the trend report?
Marc Günther commented on JENKINS-19074 Why More than 1 builds are needed for the trend report? This is in Core. It is simply the "(trend)" link, which appears in the upper right of the "Build History" section of every job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17616) Performance issue with Subversion plugin - trigger build on SVN commit takes too long
Jose Sa commented on JENKINS-17616 Performance issue with Subversion plugin - trigger build on SVN commit takes too long This seems to be working better with caching (tested with svn plugin 2.2), however due to credentials refactoring affecting svn:externals JENKINS-21785 there are still some issues that makes some cache misses. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodelabelparameter] (JENKINS-21932) Job hangs if one of multiple triggered builds was aborted
Sergey Irisov created JENKINS-21932 Job hangs if one of multiple triggered builds was aborted Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter, parameterized-trigger Created: 24/Feb/14 10:18 AM Description: I have two cases with job hanging: 1) Parent job triggers multiple different jobs and waits for their completion. I abort some triggered job while it stays in queue. After that parent job never finished, waiting for completion. 2) Parent job triggers multiple instances (via label factory) of one job on different slaves and waits for completion. I abort one of job while it executes on slave. Parent job hangs forever saying "Waiting for completion". I believe it worked correctly (in both cases parent job has failed) in some previous version. I've recently updated Jenkins from 1.48 to 1.532 As well as Parametrized Trigger Plugin from 2.16 to 2.22 And NodeLabel Parameter Plugin from 1.2.1 to 1.4 Project: Jenkins Priority: Major Reporter: Sergey Irisov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ownership] (JENKINS-21838) Allow to authenticate as a job's owner during the build
ikedam commented on JENKINS-21838 Allow to authenticate as a jobs owner during the build That is exactly what I considered at the last release. Finally I decided not to update the minor version as there was no meaningful changes for users. I treat the plugin version as an application version (for users), rather than a library version (for developers). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13035) Duplicate Views Tab Bar option
Ignacio Albors commented on JENKINS-13035 Duplicate Views Tab Bar option Sorry, I had missed this one. It doesn't have anything to do with the plugin but with core. Anyway, I've send a pull request that I think could fix the issue: https://github.com/jenkinsci/jenkins/pull/1141 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13035) Duplicate Views Tab Bar option
Ignacio Albors started work on JENKINS-13035 Duplicate Views Tab Bar option Change By: Ignacio Albors (24/Feb/14 10:58 AM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-16805) Keep this build forever build gets deleted by Discard old builds
evernat commented on JENKINS-16805 Keep this build forever build gets deleted by Discard old builds Is it reproduced with a recent Jenkins 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Dan Dumont edited a comment on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds Nicolas, Is there a way to link the pull request to the jira? Not sure how this project operates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Dan Dumont commented on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds Nicolas Morey, Is there a way to link the pull request to the jira? Not sure how this project operates. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Jesse Glick commented on JENKINS-21159 buildTimeTrend only shows last day of builds @domi better to file an issue blocking JENKINS-20892 to amend c5e2373 so that BuildTimelineWidget.builds are served lazily. Remember that the full list is shown (lazily) in the table beneath the widget. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Nicolas Morey commented on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds I tagged the issue in my commit but I don't know how JIRA likns the pull request I guess it only gets linked when my pull request will be integrated in master But FYI, it's here: https://github.com/jenkinsci/tikal-multijob-plugin/pull/49 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Dirk Kuypers commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue We are testing the attached version in our production environment since about 4 hours now. Works like a charm until now. We are consolidating two jenkins masters into one machine with about 15 Slaves now, 3000 jobs altogether and quite some continuously running jobs with concurrent builds that are heavily loading the about 100 cores. We even had severe problems with blocked threads when we rolled back to 1.8.0! Funny enough I was using the version 1.8.1 on "my" old master without problems before (even more jobs, same amount of nodes) and using the throttle concurrent builds plugin was "my" idea. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Christian Höltje created JENKINS-21933 PermGen leaks Issue Type: Bug Assignee: Unassigned Components: teamconcert Created: 24/Feb/14 3:27 PM Description: It appears that if you run with a JRE that uses PermGen (e.g. OpenJDK 1.6) that the Jenkins master will eventually run out of PermGen space. It seems like it is creating a gabillion Ant classes (approx. number)... It looks like O per build. You can recreate this by standing up a simple jenkins.war and adding a job that uses RTC SCM and then building it. Each build eats up more PermGen space. I suspect this is related to: https://bugs.eclipse.org/bugs/show_bug.cgi?id=130545 I am working around it by using IBM's 1.6 JRE, which doesn't have PermGen. However, it now eats a lot of Heap... I'm hoping that everything will be GC'd correctly. Either way, this should still be fixed. Project: Jenkins Labels: permgen Priority: Major Reporter: Christian Höltje This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Pascal Schöner commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building Same Problem with Jenkins 1.532.2, GIT Client Plugin 1.6.1, GIT Plugin 2.0.1, Multiple SCMs 0.3. We need a solution fast. 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/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais stopped work on JENKINS-21401 NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 Change By: Olivier Dagenais (24/Feb/14 3:40 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21401) NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013
Olivier Dagenais resolved JENKINS-21401 as Fixed NTLM authentication issue when using Git repository hosted on Team Foundation Server 2013 The fix should be in the next release of git-client-plugin Change By: Olivier Dagenais (24/Feb/14 3:41 PM) Status: Open Resolved Assignee: OlivierDagenais NicolasDeLoof Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
hagzag assigned JENKINS-21649 to itai Or High CPU Usage on master while slaves working (multijob) Itai/Alex could you please look into this, looks like a show stopper to me (if we ca re-produce). Tx Change By: hagzag (24/Feb/14 3:36 PM) Assignee: itaiOr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21883) [xUnit] skipped message not shown for QtTestLib
SCM/JIRA link daemon commented on JENKINS-21883 [xUnit] skipped message not shown for QtTestLib Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/QTestLibInputMetric.java src/main/resources/org/jenkinsci/plugins/xunit/types/qtestlib-to-junit-5.xsl src/test/java/org/jenkinsci/plugins/xunit/types/QTestlibTypeTest.java src/test/resources/org/jenkinsci/plugins/xunit/types/qtestlib/testcase2/result.xml http://jenkins-ci.org/commit/xunit-plugin/fad0e95e99be4193184f4662912bc05151904c34 Log: Fix JENKINS-21883 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21883) [xUnit] skipped message not shown for QtTestLib
Gregory Boissinot resolved JENKINS-21883 as Fixed [xUnit] skipped message not shown for QtTestLib Change By: Gregory Boissinot (24/Feb/14 4:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21278) java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102)
Gregory Boissinot resolved JENKINS-21278 as Fixed java.lang.NullPointerException at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:102) Mark as fixed for now. Please reopen it it there are new issues. Change By: Gregory Boissinot (24/Feb/14 4:18 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21234) [xUnit] [ERROR] - The plugin hasn't been performed correctly: hudson.util.IOException2: Failed to read xml file
Gregory Boissinot resolved JENKINS-21234 as Fixed [xUnit] [ERROR] - The plugin hasnt been performed correctly: hudson.util.IOException2: Failed to read xml file Show be fixed for now. The isssue is due to a regression in previous version where technically an object doesn't implement Serializable. Change By: Gregory Boissinot (24/Feb/14 4:24 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [multiple-scms] (JENKINS-14019) Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building
Mark Waite commented on JENKINS-14019 Multiple-SCM-Plugin does not see that nothing changed in Git-Repo and keeps building I think the only fast solution is to try switching to multiple SCM's version 0.2. I believe Nicolas De Loof found a bug in the multiple SCM plugin version 0.3 which caused him to switch the dependency in the git-client-plugin to the 0.2 version of that plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tasks-plugin] (JENKINS-21934) Be able to search for phrase last as 'catch-all' with no duplication
Ruth R created JENKINS-21934 Be able to search for phrase last as catch-all with no duplication Issue Type: Improvement Assignee: Ulli Hafner Components: tasks-plugin Created: 24/Feb/14 4:47 PM Description: My team uses priority level TODOs like this: high=TODO:1 medium=TODO:2, low=TODO:3. The scanner is good at catching these, but there are also unclassified level TODOs just as 'TODO:'. I put this in one of the searches as well, but it duplicates all the results (TODO: shows items that are also in TODO:1, TODO:2, and TODO:3). What I'd like to do is specify 'TODO:' to be searched last and catch everything that the other searches haven't already caught. Project: Jenkins Priority: Major Reporter: Ruth R This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Gregory Boissinot resolved JENKINS-18443 as Fixed SkipNoTestFiles flag ignored. Build still set to failed if test files missing Fixed for me. Check your version Change By: Gregory Boissinot (24/Feb/14 4:52 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-19637) Select filename for generated jUnit File
Gregory Boissinot closed JENKINS-19637 as Incomplete Select filename for generated jUnit File Closing the issue for now without new inputs. Please add comment and reopen it if you need more elements. Thanks Change By: Gregory Boissinot (24/Feb/14 4:56 PM) Status: Open Closed Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21935) add job-dsl-plugin support for repository-connector plugin
Matthias Balke created JENKINS-21935 add job-dsl-plugin support for repository-connector plugin Issue Type: New Feature Affects Versions: current Assignee: Matthias Balke Components: job-dsl-plugin Created: 24/Feb/14 4:57 PM Description: Currently the job-dsl-plugin does not include DSL support for the repository-connector plugin. I'm currently extending the job-dsl-plugin to support this. https://github.com/matthiasbalke/job-dsl-plugin I will send a pull request, as soon, as it is implemented and tested. Project: Jenkins Priority: Major Reporter: Matthias Balke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21247) [xunit] fails to parse junit test report with a single ignored testcase
Gregory Boissinot commented on JENKINS-21247 [xunit] fails to parse junit test report with a single ignored testcase How do you get this report (JUnit version?, etc). For an ignored test, you should get something like that testcase time="..." classname="..." name="..." skipped/ /testcase This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21247) [xunit] fails to parse junit test report with a single ignored testcase
Gregory Boissinot started work on JENKINS-21247 [xunit] fails to parse junit test report with a single ignored testcase Change By: Gregory Boissinot (24/Feb/14 5:10 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/groups/opt_out.
[JIRA] [git] (JENKINS-21936) Git Plugin 2.0.2 and later NullPointerException onNotifyCommit
Stefan Nuernberger created JENKINS-21936 Git Plugin 2.0.2 and later NullPointerException onNotifyCommit Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 24/Feb/14 5:59 PM Description: I am experiencing Internal Server Errors due to NullPointerException when triggering Git Plugin onNotifyCommit through the "Bitbucket Git Notify Commit" Hook Plugin. I am using Git Plugin 2.0.3 and the Error occurs on Line 271 of https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitStatus.java The offending Code was introduced into Jenkins Git Plugin in commit https://github.com/jenkinsci/git-plugin/commit/ec521564afcca7069403d48e51591f0251c0f98b I believe this is an error in the Git Plugin since the Hook was still working in 2.0.1 and the trigger.run() method omits a NullPointer check, while this is done for other uses of trigger in the same method. Project: Jenkins Labels: plugin jenkins exception git Priority: Major Reporter: Stefan Nuernberger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-19185) xUnit fails to correctly parse Boost.Test log
Gregory Boissinot closed JENKINS-19185 as Incomplete xUnit fails to correctly parse Boost.Test log Closing the issue for now. I don't have all the information. Please reopen it if you have new issues. Change By: Gregory Boissinot (24/Feb/14 6:10 PM) Status: InProgress Closed Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mail] (JENKINS-16106) Add Precedence: bulk header to notification emails
Brian Egge commented on JENKINS-16106 Add Precedence: bulk header to notification emails Additionally, one should have "Auto-Submitted: auto-generated" and "Return-Path: " http://tools.ietf.org/search/rfc3834 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-21714) More data from REST API
RobS commented on JENKINS-21714 More data from REST API Well I suppose you have a good point. However it would be more convenient for me when creating jobs not to have to do an additional step of keeping a build artifact around. But that's probably not worth the coding effort to keep data around for the REST api or whatever must happen. So thanks for pointing this out. You can close this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-15923) embunit support
SCM/JIRA link daemon commented on JENKINS-15923 embunit support Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/types/EmbUnitInputMetric.java src/main/java/org/jenkinsci/plugins/xunit/types/EmbUnitType.java src/main/resources/org/jenkinsci/plugins/xunit/types/embunit-to-junit.xsl http://jenkins-ci.org/commit/xunit-plugin/573192f685a76ab2cd5d30e46750f6e140f1c312 Log: Add support file for JENKINS-15923 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-name-setter] (JENKINS-13347) Build Name returns 'Unrecognized macro' errors for everything except ${BUILD_NUMBER}
Łukasz Jąder
assigned JENKINS-13347 to Łukasz Jąder
Build Name returns Unrecognized macro errors for everything except ${BUILD_NUMBER}
Change By:
Łukasz Jąder
(24/Feb/14 6:31 PM)
Assignee:
KohsukeKawaguchi
ŁukaszJąder
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Michael Kahn updated JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Michael Kahn (24/Feb/14 7:05 PM) Component/s: git-client This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20941) Stored git credentials not used when submodule is updated
Michael Kahn commented on JENKINS-20941 Stored git credentials not used when submodule is updated I also have this problem on a Fedora slave using SSH instead of HTTPS. It looks like this happens because the submoduleUpdate() function of git-client uses launchCommand() instead of launchCommandWithCredentials(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-failure-analyzer] (JENKINS-21937) build broken
Douglas Macedo created JENKINS-21937 build broken Issue Type: Task Assignee: Tomas Westling Components: build-failure-analyzer Created: 24/Feb/14 7:37 PM Description: "C:\MSBuildScripts\teste.msbuild" (default target) (1) - (StopPool target) - MSBUILD : warning MSB3073: The command "c:\utils\psexec ipserver %windir%\system32\inetsrv\appcmd stop apppool /apppool.name:QA_POOL" exited with code 6. C:\MSBuildScripts\teste.msbuild "C:\MSBuildScripts\teste.msbuild" (default target) (1) - (Copy target) - C:\MSBuildScripts\teste.msbuild(320,5): error MSB3191: Unable to create directory "\\ipserver\qa\teste\Produto\". Logon failure: unknown user name or bad password. C:\MSBuildScripts\teste.msbuild(320,5): error MSB3191: Project: Jenkins Priority: Major Reporter: Douglas Macedo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-16063) Add USER_ID variable to be available at the time of promotion if promoted manually
Jesse Glick updated JENKINS-16063 Add USER_ID variable to be available at the time of promotion if promoted manually Change By: Jesse Glick (24/Feb/14 7:51 PM) Assignee: GavriilKonovalenko ChristopherChong URL: https://github.com/jenkinsci/promoted-builds-plugin/pull/37 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-16063) Add USER_ID variable to be available at the time of promotion if promoted manually
Jesse Glick started work on JENKINS-16063 Add USER_ID variable to be available at the time of promotion if promoted manually Change By: Jesse Glick (24/Feb/14 7:51 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21730) Allow for selection of Bcc: for email recipients on global recipient list
SCM/JIRA link daemon commented on JENKINS-21730 Allow for selection of Bcc: for email recipients on global recipient list Code changed in jenkins User: Tyler Fitch Path: src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/plugins/RecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/CulpritsRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/DevelopersRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/ListRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/RequesterRecipientProvider.java src/main/webapp/help/globalConfig/defaultRecipients.html src/main/webapp/help/globalConfig/defaultRecipients_zh_TW.html src/main/webapp/help/projectConfig/globalRecipientList.html src/main/webapp/help/projectConfig/globalRecipientList_zh_TW.html src/main/webapp/help/projectConfig/mailType/recipientList.html src/main/webapp/help/projectConfig/mailType/recipientList_zh_TW.html src/test/java/hudson/plugins/emailext/recipients/EmailRecipientUtilsTest.java http://jenkins-ci.org/commit/email-ext-plugin/4aacabf9b9fa9be326ebc362519e2f5d1bbb43fb Log: JENKINS-21730 - Add bcc support to email-ext plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21730) Allow for selection of Bcc: for email recipients on global recipient list
SCM/JIRA link daemon commented on JENKINS-21730 Allow for selection of Bcc: for email recipients on global recipient list Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/plugins/RecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/CulpritsRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/DevelopersRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/ListRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/RequesterRecipientProvider.java src/main/webapp/help/globalConfig/defaultRecipients.html src/main/webapp/help/globalConfig/defaultRecipients_zh_TW.html src/main/webapp/help/projectConfig/globalRecipientList.html src/main/webapp/help/projectConfig/globalRecipientList_zh_TW.html src/main/webapp/help/projectConfig/mailType/recipientList.html src/main/webapp/help/projectConfig/mailType/recipientList_zh_TW.html src/test/java/hudson/plugins/emailext/recipients/EmailRecipientUtilsTest.java http://jenkins-ci.org/commit/email-ext-plugin/d97977c44e12c7e0e2ff9e92f6d63e2bf1a1d6ab Log: Merge pull request #88 from tfitch/JENKINS-21730-bcc-support-in-email-ext JENKINS-21730 - Add bcc support to email-ext plugin Compare: https://github.com/jenkinsci/email-ext-plugin/compare/624bb6e2ae01...d97977c44e12 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-15923) embunit support
Gregory Boissinot resolved JENKINS-15923 as Fixed embunit support Added in 1.84 Could you add some result samples for unit tests? Change By: Gregory Boissinot (24/Feb/14 8:12 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-21938) TF14044: Access Denied: User XXX needs the AdminWorkspaces global permission(s).
Vladimir Kralik created JENKINS-21938 TF14044: Access Denied: User XXX needs the AdminWorkspaces global permission(s). Issue Type: Bug Affects Versions: current Assignee: redsolo Components: tfs Created: 24/Feb/14 8:47 PM Description: I tryed checkout source code from TFS in described environment. It ends with this bug : workspace $ D:/utils/TEE-CLC-11.0.0/tf.cmd workspace \ -new jenkins-forms-vlk-MASTER;mylogin@MYDOMAIN \ -noprompt -server:http://s11-ba:8080/ An error occurred: TF14044: Access Denied: \ User MYDOMAIN\mylogin needs the AdminWorkspaces\ global permission(s). I did an investigation and realised, that the used commad is wrong. The correct commad should be : workspace $ D:/utils/TEE-CLC-11.0.0/tf.cmd workspace \ -new jenkins-forms-vlk-MASTER \ -noprompt -server:http://s11-ba:8080/ Also I tryed to find solution in source code. And I realised, that this was added in https://github.com/jenkinsci/tfs-plugin/commit/0c8af5367fca40734d7b456078ef68b3c1f96f76 But I don't understan why, because that request was marked "Won't fix" https://java.net/projects/hudson/lists/issues/archive/2010-09/message/992 Please revert this changeset. Environment: Jenkins v 1.551 + TFS Plugin 3.0.1 server : Microsoft TFS 2008 client : TEE-CLC-11.0.0 ( Team Explorer Everywhere ) Project: Jenkins Priority: Blocker Reporter: Vladimir Kralik This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-21939) Perforce Clean Workspace Full Wipe should not add -f option to sync.
Manvendra Singh created JENKINS-21939 Perforce Clean Workspace Full Wipe should not add -f option to sync. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: perforce Created: 24/Feb/14 8:53 PM Description: We are trying to run builds from Perforce read-only replica server which requires "-p" option since its a read-only. At the same time we want to clean the workspace before each build with "Full Wipe" option. Perforce sync fails when using "Clean Workspace Before Each Build Full Wipe" and "-p" option. Apparently "Full Wipe" is adding "-f" to the sync which makes it incompatible with "-p" which then fails the sync. The full wipe should not assume that user wants to force sync the workspace. Due Date: 25/Feb/14 12:00 AM Environment: Jenkins Version - 1.508 Perforce Plugin Version - 1.3.26 Platform - RHEL 6.3 x86_64 Fix Versions: current Project: Jenkins Priority: Major Reporter: Manvendra Singh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-21940) Maven tasks are unaffected by Run the build in a RVM-managed environment
Erik Swanson created JENKINS-21940 Maven tasks are unaffected by Run the build in a RVM-managed environment Issue Type: Bug Assignee: Unassigned Components: maven2, rvm Created: 24/Feb/14 9:01 PM Description: The RVM plugin adds to PATH, which are correctly available to shell script Jenkins tasks. Maven2 Jenkins tasks ignore the PATH additions, causing maven-antrun-plugin exec tasks to fail to find binaries/scripts that were installed in the RVM environment by prior Jenkins tasks. Environment: CentOS 6 build slave running as unprivileged user. Project: Jenkins Priority: Major Reporter: Erik Swanson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais started work on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Change By: Olivier Dagenais (24/Feb/14 10:25 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/groups/opt_out.
[JIRA] [tfs] (JENKINS-20426) FATAL: The IdentityManagementService is not available from the server
Olivier Dagenais commented on JENKINS-20426 FATAL: The IdentityManagementService is not available from the server Pull request #22 was submitted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-21924) Run groovy script for matrix parent builds
ikedam commented on JENKINS-21924 Run groovy script for matrix parent builds https://github.com/jenkinsci/groovy-postbuild-plugin/pull/10 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21914) Intermittent Git(hub) polling errors on Windows
Mark Waite commented on JENKINS-21914 Intermittent Git(hub) polling errors on Windows Since you're on a Windows machine, I suspect that a process is holding that file open, and while the file remains open the Windows file system refuses to delete the file. You could check: Is there a git.exe process still running on the machine? If there is and you kill that process, does it resolve the issue? Is an open file reported by the File Leak Detector plugin ( https://wiki.jenkins-ci.org/display/JENKINS/File+Leak+Detector+Plugin )? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21639) Jobs named . can be created, but not built, configured, accessed, ...
dogfood commented on JENKINS-21639 Jobs named . can be created, but not built, configured, accessed, ... Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21639 Prevent creation of job named '.'. (Revision 780b38bc755028f4c4d72378896407a182bd5b30) JENKINS-21639 Noting merge of #1117. (Revision 931d2960e9eb6765c0b0c2db7b64c042339b1eb9) Result = SUCCESS daniel-beck : 780b38bc755028f4c4d72378896407a182bd5b30 Files : core/src/main/java/jenkins/model/Jenkins.java Jesse Glick : 931d2960e9eb6765c0b0c2db7b64c042339b1eb9 Files : 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/groups/opt_out.
[JIRA] [core] (JENKINS-19832) missing help items on Configure Global Security page
dogfood commented on JENKINS-19832 missing help items on Configure Global Security page Integrated in jenkins_main_trunk #3192 FIXED JENKINS-19832 Added a descriptor for GlobalSecurityConfiguration. This enables helps on Configure Global Security page. (Revision 4dd7f71ec2cd5841d5e0685d7df45466c145bc5e) Result = SUCCESS Vojtech Juranek : 4dd7f71ec2cd5841d5e0685d7df45466c145bc5e Files : core/src/main/resources/hudson/security/GlobalSecurityConfiguration/index.groovy core/src/main/java/hudson/security/GlobalSecurityConfiguration.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20730) Wrong log message for out-of-order build record repair
dogfood commented on JENKINS-20730 Wrong log message for out-of-order build record repair Integrated in jenkins_main_trunk #3192 FIXED JENKINS-20730 Use correct folder in log message (Revision 5ba9bf4417a9de253d8af5471adfcc9baa4d1d3d) Result = SUCCESS daniel-beck : 5ba9bf4417a9de253d8af5471adfcc9baa4d1d3d Files : core/src/main/java/jenkins/diagnostics/ooom/BuildPtr.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-19898) hudson.tasks.test isn't generic enough for extension
dogfood commented on JENKINS-19898 hudson.tasks.test isnt generic enough for extension Integrated in jenkins_main_trunk #3192 FIXED JENKINS-19898 test base classes should not be linked to the junit implementation. (Revision 0e122dfcacebbf791223ca416ad845e12a4ca38e) Result = SUCCESS James Nord : 0e122dfcacebbf791223ca416ad845e12a4ca38e Files : core/src/main/java/hudson/tasks/junit/CaseResult.java core/src/main/java/hudson/tasks/test/TestObject.java core/src/main/java/hudson/tasks/test/AggregatedTestResultAction.java core/src/main/java/hudson/tasks/test/AbstractTestResultAction.java core/src/main/java/hudson/tasks/junit/ClassResult.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21777) Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly)
dogfood commented on JENKINS-21777 Allow actions of LabelAtomProperties to contribute to label index page (summary.jelly) Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21777 Actions contributing to Labels' index page (Revision 08a96df6b694314f008186c1748a2c02b5388d8f) Result = SUCCESS Vojtech Juranek : 08a96df6b694314f008186c1748a2c02b5388d8f Files : core/src/main/resources/hudson/model/Label/index.jelly 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/groups/opt_out.
[JIRA] [junit] (JENKINS-21261) CaseResult/index.jelly can be rendered with text/plain content type
dogfood commented on JENKINS-21261 CaseResult/index.jelly can be rendered with text/plain content type Integrated in jenkins_main_trunk #3192 JENKINS-21261 while I originally misdiagnosed the problem, the test is still marginally useful. (Revision c88698c0afc35d7427b16349f4d411d184f3ae3f) JENKINS-21261 (Revision 411c3cfecb8094da86fd0397dc8c29c723f53da3) Result = SUCCESS kohsuke : c88698c0afc35d7427b16349f4d411d184f3ae3f Files : test/src/test/java/hudson/tasks/junit/CaseResultTest.java kohsuke : 411c3cfecb8094da86fd0397dc8c29c723f53da3 Files : core/src/main/java/hudson/tasks/junit/TestResultAction.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-21772) Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME
dogfood commented on JENKINS-21772 Use of CLI login command resets Jenkins after restart when using default JENKINS_HOME Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21772 Only cache CLI credentials in ~/.hudson if it exists. (Revision 237dda40e08f4db759e965738b1b9b3755525161) Result = SUCCESS Vojtech Juranek : 237dda40e08f4db759e965738b1b9b3755525161 Files : core/src/main/java/hudson/cli/ClientAuthenticationCache.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
dogfood commented on JENKINS-20534 Pegged CPU by writeSymlink calls Integrated in jenkins_main_trunk #3192 JENKINS-20534 Avoid usage of temporary file to write symlink. (Revision c0742b8bff9fe407e568da7ed860f30d9ea8aedc) FIXED JENKINS-20534 Noting merge of #1057. (Revision 5c83c64e7af95bc5f216d841e4257c79403931d8) Result = SUCCESS Vincent Latombe : c0742b8bff9fe407e568da7ed860f30d9ea8aedc Files : core/src/main/java/jenkins/model/PeepholePermalink.java Jesse Glick : 5c83c64e7af95bc5f216d841e4257c79403931d8 Files : 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
dogfood commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Integrated in jenkins_main_trunk #3192 JENKINS-21373 Noting. (Revision f9810b5131e3024930df233a02a356e3cb5b5f84) Result = SUCCESS Jesse Glick : f9810b5131e3024930df233a02a356e3cb5b5f84 Files : 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/groups/opt_out.
[JIRA] [core] (JENKINS-21612) f:combobox is narrow
dogfood commented on JENKINS-21612 f:combobox is narrow Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21612 fixed wrong CSS class for f:combobox. (Revision cfbf4ca45ec97c05b47b69d1d59d3f5ae1f50c82) Result = SUCCESS devld : cfbf4ca45ec97c05b47b69d1d59d3f5ae1f50c82 Files : core/src/main/resources/lib/form/combobox.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21673) Sort groups on user index page alphabetically
dogfood commented on JENKINS-21673 Sort groups on user index page alphabetically Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21673 Sort authorities on user index page. (Revision 380eba7cb7920117e32daa082146dcce05a7dd4e) JENKINS-21673 Noting merge of #1120. (Revision 6dc15000562e04f11c01d4cce5a428301da04406) Result = SUCCESS daniel-beck : 380eba7cb7920117e32daa082146dcce05a7dd4e Files : core/src/main/java/hudson/model/User.java Jesse Glick : 6dc15000562e04f11c01d4cce5a428301da04406 Files : 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/groups/opt_out.
[JIRA] [core] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
dogfood commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Integrated in jenkins_main_trunk #3192 FIXED JENKINS-16332 Ensure that User records are saved when the fullName is not recoverable from the id. (Revision fdda9ca65689423794a8378c1f28faca7dffddf0) Result = SUCCESS Jesse Glick : fdda9ca65689423794a8378c1f28faca7dffddf0 Files : test/src/test/java/hudson/model/UserTest.java changelog.html core/src/main/java/hudson/model/User.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21780) DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories
dogfood commented on JENKINS-21780 DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21780 DirectoryBrowserSupport.FileComparator should cache isDirectory calls. (Revision d577c0850d10348c92d763309b163223be26f68b) Result = SUCCESS Jesse Glick : d577c0850d10348c92d763309b163223be26f68b 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/groups/opt_out.
[JIRA] [core] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
dogfood commented on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded Integrated in jenkins_main_trunk #3192 FIXED JENKINS-12124 Occasionally errors loading plugin classes since it is expected that findClass (and findLoadedClass) are called under synchronization. (Revision 898f1f76a37e1c69cf38df718a5d3899544ebb44) Result = SUCCESS Jesse Glick : 898f1f76a37e1c69cf38df718a5d3899544ebb44 Files : core/src/main/java/hudson/PluginManager.java core/src/main/java/jenkins/ClassLoaderReflectionToolkit.java changelog.html core/src/main/java/hudson/ClassicPluginStrategy.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20965) SSH CLI -v (console output) option causes high master CPU utilization
dogfood commented on JENKINS-20965 SSH CLI -v (console output) option causes high master CPU utilization Integrated in jenkins_main_trunk #3192 FIXED JENKINS-20965 Run.writeWholeLogTo causes high CPU usage. (Revision 82e94e5e738c988c36181d8c0ff6b9ffed846bcc) JENKINS-20965 Noting merge of #1137. (Revision 0d77f1795cf97a5e7dbd43f066ab5f97753b464b) Result = SUCCESS schristou88 : 82e94e5e738c988c36181d8c0ff6b9ffed846bcc Files : core/src/main/java/hudson/model/Run.java Jesse Glick : 0d77f1795cf97a5e7dbd43f066ab5f97753b464b Files : 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/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
dogfood commented on JENKINS-21023 WorkspaceCleanupThread does not handle folders Integrated in jenkins_main_trunk #3192 FIXED JENKINS-21023 Rewrote WorkspaceCleanupThread to determine where workspaces for known items should be, rather than looking for directories that look like they might be workspaces. (Revision cd526e99e63ae362f2d1ce1a04c3c68a38032a5c) Result = SUCCESS Jesse Glick : cd526e99e63ae362f2d1ce1a04c3c68a38032a5c Files : changelog.html test/src/test/java/hudson/model/WorkspaceCleanupThreadTest.java core/src/main/java/hudson/model/WorkspaceCleanupThread.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
dogfood commented on JENKINS-17606 Copy Artifacts fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied Integrated in jenkins_main_trunk #3192 FIXED JENKINS-17606 Reuse existing fingerprint action if present. (Revision be7a97ee32b57dcb27b8fd6c908ebbe451220902) Result = SUCCESS Stefan Wolf : be7a97ee32b57dcb27b8fd6c908ebbe451220902 Files : test/src/test/java/hudson/tasks/FingerprinterTest.java changelog.html core/src/main/java/hudson/tasks/Fingerprinter.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21474) Jenkins crash on startup after upgrade from 1.546 to 1.548
dogfood commented on JENKINS-21474 Jenkins crash on startup after upgrade from 1.546 to 1.548 Integrated in jenkins_main_trunk #3192 JENKINS-21474 Fix NPE in View.getComputers() (Revision e31f8dc2d361990194cb559395c55866092b35cb) Result = SUCCESS ogondza : e31f8dc2d361990194cb559395c55866092b35cb Files : test/src/test/java/hudson/model/ViewTest.java core/src/main/java/hudson/model/View.java core/src/main/java/hudson/model/AbstractProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21001) Git plugin should use git init + git fetch instead of git clone
Mark Waite resolved JENKINS-21001 as Fixed Git plugin should use git init + git fetch instead of git clone Marking the issue resolved after 10 days without a response from the submitter. Change By: Mark Waite (25/Feb/14 12:08 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/groups/opt_out.
[JIRA] [git] (JENKINS-21001) Git plugin should use git init + git fetch instead of git clone
Mark Waite closed JENKINS-21001 as Fixed Git plugin should use git init + git fetch instead of git clone Change By: Mark Waite (25/Feb/14 12:08 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19591) Pathological branch rename causes git fetch to fail
Mark Waite resolved JENKINS-19591 as Wont Fix Pathological branch rename causes git fetch to fail I wrote a test which confirms that the pathological branch rename causes a failure in the git-client-plugin checkout process when using command line git, and confirmed that the "git remote prune origin" command (and its matching setting in the API) resolve the issue. I don't think we should change the behavior to always prune because that will likely discover users who depend on it not pruning. Those users who encounter the problem may choose to enable pruning of orphan remote branches, or they can wipe the workspace as suggested in this bug report. Change By: Mark Waite (25/Feb/14 12:15 AM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-19591) Pathological branch rename causes git fetch to fail
Mark Waite closed JENKINS-19591 as Wont Fix Pathological branch rename causes git fetch to fail Change By: Mark Waite (25/Feb/14 12:15 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Mark Waite closed JENKINS-7411 as Fixed Slave environment variables are not used during Git Polling Change By: Mark Waite (25/Feb/14 12:30 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-7411) Slave environment variables are not used during Git Polling
Mark Waite resolved JENKINS-7411 as Fixed Slave environment variables are not used during Git Polling Closing the issue since the commit which fixed it was submitted over 6 months ago. Change By: Mark Waite (25/Feb/14 12:30 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20969) When branch build parameter is '*', '**' or empty, a stale revision is built
Ryan Beesley commented on JENKINS-20969 When branch build parameter is *, ** or empty, a stale revision is built I'm seeing a similar problem, but using a specific branch name, such as master builds another branch. I wonder if this is related. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-8593) asking hudson to build a git project whose repository is empty permanently disables builds until manual rmdir of workspace
Mark Waite resolved JENKINS-8593 as Fixed asking hudson to build a git project whose repository is empty permanently disables builds until manual rmdir of workspace I've confirmed that this is no longer an issue with git-client-plugin 1.6.2 and git-plugin 2.0.1 and later. I verified it with both the command line implementation and the JGit implementation. Steps I took: Create an empty bare repository on my git server (git protocol) Define a job which clones that bare repository Run that job and confirm the job fails (no revision to checkout) Push a change to that bare repository from a clone made elsewhere Run the job again and confirm that the job succeeds Change By: Mark Waite (25/Feb/14 12:49 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/groups/opt_out.
[JIRA] [git] (JENKINS-8593) asking hudson to build a git project whose repository is empty permanently disables builds until manual rmdir of workspace
Mark Waite closed JENKINS-8593 as Fixed asking hudson to build a git project whose repository is empty permanently disables builds until manual rmdir of workspace Change By: Mark Waite (25/Feb/14 12:49 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21929) Configurations of latest build parameters won't save
SCM/JIRA link daemon resolved JENKINS-21929 as Fixed Configurations of latest build parameters wont save Change By: SCM/JIRA link daemon (25/Feb/14 12:51 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/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21929) Configurations of latest build parameters won't save
SCM/JIRA link daemon commented on JENKINS-21929 Configurations of latest build parameters wont save Code changed in jenkins User: Fred G Path: src/main/java/jenkins/plugins/extracolumns/BuildParametersColumn.java src/main/resources/jenkins/plugins/extracolumns/BuildParametersColumn/config.jelly http://jenkins-ci.org/commit/extra-columns-plugin/a88cfac475a35c6f20585f5d2cecb6f8dc6aa15f Log: FIXED JENKINS-21929 Configurations of latest build parameters won't save This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20969) When branch build parameter is '*', '**' or empty, a stale revision is built
Mark Waite commented on JENKINS-20969 When branch build parameter is *, ** or empty, a stale revision is built Ryan, you'll need to provide more information, since I think your case is probably quite different from the problem originally reported in this bug. The case I was able to duplicate only happens if a wildcard is included in the parameterized branch name. That is also what the original submitter reported. Your description seems to indicate that you've found a case where the wrong branch is built, even if the parameter contains no wildcard. Can you provide more details (or even better, a separate bug report with detailed steps to show how to duplicate it)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-api] (JENKINS-21288) Build with Poll SCM trigger proceeds even though no SCM change
Charles Jones updated JENKINS-21288 Build with Poll SCM trigger proceeds even though no SCM change I've added subversion to the ticket components. Is there anything else I can do to get it properly looked at? Change By: Charles Jones (25/Feb/14 1:02 AM) Component/s: subversion This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20657) GIT throws an exception after setting repo URL
Mark Waite resolved JENKINS-20657 as Fixed GIT throws an exception after setting repo URL I don't see this exception and have not seen this type of exception for a few releases of the plugins. The most recent version I tested was git-client-plugin 1.6.2 and git-plugin 2.0.2 Change By: Mark Waite (25/Feb/14 1:07 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20657) GIT throws an exception after setting repo URL
Mark Waite closed JENKINS-20657 as Fixed GIT throws an exception after setting repo URL Change By: Mark Waite (25/Feb/14 1:07 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite resolved JENKINS-20196 as Fixed Failed to connect to URL (status = 404) Closing the bug report after 7 days without a response. I have verified that a bitbucket repository URL with the user name and password embedded work correctly. Change By: Mark Waite (25/Feb/14 1:09 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite closed JENKINS-20196 as Fixed Failed to connect to URL (status = 404) Change By: Mark Waite (25/Feb/14 1:10 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20969) When branch build parameter is '*', '**' or empty, a stale revision is built
Ryan Beesley commented on JENKINS-20969 When branch build parameter is *, ** or empty, a stale revision is built I was reading through the list of bugs to try and find something that looked like my issue this was close. Right now all I have are the logs and traces. Some jobs are doing what we expect, but this job in particular is refusing to build master. If that would be enough to submit a report, I can go ahead and do so, but I haven't completely eliminated user error and so I wasn't quite ready to declare that I've found a bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
Fred G commented on JENKINS-21740 Columns with value of a variable from script Sorry, but this sounds overly complicated. How is this different from a normal build parameter wrapped in a file? Without knowing more about the "Why?" it's really hard to find a good approach. You still did not provide a reasonable use case for the requested column. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20969) When branch build parameter is '*', '**' or empty, a stale revision is built
Mark Waite commented on JENKINS-20969 When branch build parameter is *, ** or empty, a stale revision is built If you're willing to continue the investigation to decide conclusively if it is a user error or a software bug, you'll save time that others would spend asking the same question, and you'll very likely increase the chances of the bug being fixed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-api] (JENKINS-21288) Build with Poll SCM trigger proceeds even though no SCM change
Mark Waite commented on JENKINS-21288 Build with Poll SCM trigger proceeds even though no SCM change Since Jenkins is an open source project, investigation happens when one of the volunteers on the project finds it interesting enough to investigate. Alternately, investigation can happen when someone purchases commercial support from one of the commercial support vendors (like CloudBees). Investigation can also happen when someone decides to learn enough of the code to perform that investigation themselves. If you can provide more details about the conditions which cause it to fail, sometimes that can encourage more interest from the developers on the project. If you can show that the problem is more widespread than just your installation, sometimes that can encourage more interest from the developers on the project. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21943) Parameterised Subversion revision should apply to subdirectories as well as the working copy root
trejkaz created JENKINS-21943 Parameterised Subversion revision should apply to subdirectories as well as the working copy root Issue Type: Improvement Assignee: Unassigned Components: subversion Created: 25/Feb/14 4:47 AM Description: We were trying to configure Jenkins to trigger one build from another, carrying the same Subversion revision over into the new build. I couldn't get this to work using the Parameterized Trigger plugin so I eventually filed a ticket about that (JENKINS-21586) because it wasn't doing what it said it would, but they said that this is a limitation in the Subversion plugin. Essentially, the Parameterized Trigger plugin is triggering a build and telling the Subversion plugin to use a specific revision for the URL when it checks it out. What I expect to happen is for both checkouts to use the revision which was passed in. What actually happens is that the root directory uses the revision which was passed in and the subdirectory is checked out from HEAD. Project: Jenkins Priority: Major Reporter: trejkaz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21944) Documentation contains broken link
cowwoc created JENKINS-21944 Documentation contains broken link Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 25/Feb/14 5:13 AM Description: https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin# contains a broken link to http://computercamp.cdwilson.us/jenkins-git-clone-via-ssh-on-windows-7-x64 I believe this link can be replaced by http://computercamp-cdwilson-us.tumblr.com/post/48589650930/jenkins-git-clone-via-ssh-on-windows-7-x64 Project: Jenkins Priority: Minor Reporter: cowwoc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Alexander Artemov commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing It works for me as well. Thank you for the fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) I just updated to "GIT plugin" 2.0.3 and "GIT client plugin" 1.6.3. Getting the following output: Cloning repository https://username:passw...@bitbucket.org/scodi/tools.git Fetching upstream changes from https://usern...@bitbucket.org/scodi/tools.git ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git fetch --tags --progress https://usern...@bitbucket.org/scodi/tools.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr: fatal: Authentication failed for 'https://usern...@bitbucket.org/scodi/tools.git/' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1173) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1043) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:74) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:207) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:358) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:847) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:880) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:118) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extra-columns] (JENKINS-21740) Columns with value of a variable from script
dor cohen commented on JENKINS-21740 Columns with value of a variable from script Hi Fred, By "a normal build parameter wrapped in a file", do you mean to the field "File Parameter" that appear when clicking "Add parameter" in the configuration page of a build? If so, then this option isn't good because that I provide the data (the file with it's contents) from outside of the script. The feature that I ask here tries to do the exact opposite - provide a piece of data that is created/calculated by the script, which is to be displayed in a column under a "view" page. The "Why?" is that currently nothing allows the script to create data and display it under one of the columns in one of the "Views" in Jenkins. Use case: 1. Run job "Foo" that is in view "Bar" 2. The script extracts a version number from a hardware (e.g. Arduino board or something similar) 3. The version number is written to a file in the workspace 4. At the end of the job, the number is displayed in one of the columns under the view named "Bar" (Each time that the job "Foo" is executed, the number will be taken from the last build) I hope that I answered properly, if not please ask and I'll try to elaborate! Thank you. Regards, Dor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials We are still not able to build releases with "artifactory release staging" since a week now, because of missing credntials artifactory tag commit. Any ideas, any workarounds ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
