[JIRA] [scm-sync-configuration] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL
jan_ruzicka commented on JENKINS-22076 SCM Sync Configuration crashes after enter repository URL the SCM Sync Configuration Plugin was working up to the latest update. I wasn't paying close attention, but previous version of the SVN plugin may have been 2.0. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22076) SCM Sync Configuration crashes after enter repository URL
jan_ruzicka commented on JENKINS-22076 SCM Sync Configuration crashes after enter repository URL During restart Jenkins log shows: WARNING: null java.lang.RuntimeException: Error during ScmSyncConfiguration initialisation ! at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.init(ScmSyncConfigurationPlugin.java:154) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationItemListener.onLoaded(ScmSyncConfigurationItemListener.java:24) at jenkins.model.Jenkins.init(Jenkins.java:861) at hudson.model.Hudson.init(Hudson.java:81) at hudson.model.Hudson.init(Hudson.java:77) at hudson.WebAppMain$3.run(WebAppMain.java:221) Caused by: java.lang.NullPointerException at hudson.plugins.scm_sync_configuration.scms.ScmSyncSubversionSCM.extractScmCredentials(ScmSyncSubversionSCM.java:51) at hudson.plugins.scm_sync_configuration.scms.SCM.getConfiguredRepository(SCM.java:63) at hudson.plugins.scm_sync_configuration.SCMManipulator.scmConfigurationSettledUp(SCMManipulator.java:57) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.initializeRepository(ScmSyncConfigurationBusiness.java:69) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.init(ScmSyncConfigurationBusiness.java:64) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.init(ScmSyncConfigurationPlugin.java:152) ... 5 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [starteam] (JENKINS-21523) NPE during SCM polling of missing StarTeam repository
jan_ruzicka created JENKINS-21523 NPE during SCM polling of missing StarTeam repository Issue Type: Bug Affects Versions: current Assignee: jan_ruzicka Components: starteam Created: 27/Jan/14 6:34 PM Description: The SCM polling triggers NullPointerException (NPE) and fails to close socket to StarTeam server. This led to Jenkins exhausting allowed number of open file handles. Log entry: SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@196d898Learn about Maven 2 - again java.lang.NullPointerException at hudson.plugins.starteam.StarTeamConnection.close(StarTeamConnection.java:409) at hudson.plugins.starteam.StarTeamPollingActor.invoke(StarTeamPollingActor.java:92) at hudson.plugins.starteam.StarTeamPollingActor.invoke(StarTeamPollingActor.java:22) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.starteam.StarTeamSCM.pollChanges(StarTeamSCM.java:190) at hudson.scm.SCM.poll(SCM.java:375) at hudson.model.AbstractProject._poll(AbstractProject.java:1402) at hudson.model.AbstractProject.poll(AbstractProject.java:1335) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Environment: Jenkins ver. 1.509.2, StarTeam plugin 0.6.11 Project: Jenkins Priority: Major Reporter: jan_ruzicka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17228) Fail build when subversion workspace is locked
jan_ruzicka commented on JENKINS-17228 Fail build when subversion workspace is locked the Hudson commit moved around https://github.com/hudson3-plugins/subversion-plugin/commit/37ca9c134702878e6bb824dde108d63c6df043d8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17228) Fail build when subversion workspace is locked
jan_ruzicka commented on JENKINS-17228 Fail build when subversion workspace is locked current location of the fixed section in jenkinsci/subversion-plugin is src/main/java/hudson/scm/subversion/UpdateUpdater.java lines 181 and 182 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17228) Fail build when subversion workspace is locked
jan_ruzicka commented on JENKINS-17228 Fail build when subversion workspace is locked Will the failing build unlock the workspace? or will all the fallowing builds fail? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-8738) The changelog.xml can contain characters which cause problems for XML parsing
jan_ruzicka resolved JENKINS-8738 as Fixed The changelog.xml can contain characters which cause problems for XML parsing fixed in commit e507578f9f32bd113d500484a440e86ae84dd8c1 Change By: jan_ruzicka (01/Mar/13 5:10 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] (JENKINS-8738) The changelog.xml can contain characters which cause problems for XML parsing
jan_ruzicka closed JENKINS-8738 as Fixed The changelog.xml can contain characters which cause problems for XML parsing Fixed in 0.6.7 Change By: jan_ruzicka (01/Mar/13 5:14 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] (JENKINS-2879) Enhance starteam plugin
jan_ruzicka commented on JENKINS-2879 Enhance starteam plugin It is not being worked on at the moment. But there may be even better solution. If the Starteam Plugin behaves correctly, it can be used with Multiple SCMs Plugin1. Can you help with testing? 1 https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+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] (JENKINS-13699) Jenkins plugin does not identify itself as a ClientApplication
jan_ruzicka resolved JENKINS-13699 as Fixed Jenkins plugin does not identify itself as a ClientApplication change released in starteam-0.6.8 Change By: jan_ruzicka (27/Feb/13 4:39 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] (JENKINS-13699) Jenkins plugin does not identify itself as a ClientApplication
jan_ruzicka closed JENKINS-13699 as Fixed Jenkins plugin does not identify itself as a ClientApplication checked in starteam-0.6.8 Change By: jan_ruzicka (27/Feb/13 4:41 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] (JENKINS-14368) Create or Update Label in StarTeam displays passwords as clear text in Console Output
jan_ruzicka resolved JENKINS-14368 as Cannot Reproduce Create or Update Label in StarTeam displays passwords as clear text in Console Output Change By: jan_ruzicka (27/Feb/13 4:44 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14368) Create or Update Label in StarTeam displays passwords as clear text in Console Output
jan_ruzicka closed JENKINS-14368 as Cannot Reproduce Create or Update Label in StarTeam displays passwords as clear text in Console Output Change By: jan_ruzicka (27/Feb/13 4:45 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] (JENKINS-2879) Enhance starteam plugin
jan_ruzicka commented on JENKINS-2879 Enhance starteam plugin the multiple SCM seems to have issue with same types of repositories. (Git, TFS) JENKINS-9287. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13770) StarTeam Plugin SCM Polling failing on Slave machines
jan_ruzicka assigned JENKINS-13770 to Hugo Ares StarTeam Plugin SCM Polling failing on Slave machines Does this re-assign work? Change By: jan_ruzicka (13/Dec/12 9:46 PM) Assignee: jan_ruzicka HugoAres This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13054) Starteam plugin error when executing checkout by label.
jan_ruzicka assigned JENKINS-13054 to Hugo Ares Starteam plugin error when executing checkout by label. Re-assignig attempt Change By: jan_ruzicka (13/Dec/12 9:47 PM) Assignee: jan_ruzicka HugoAres This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
jan_ruzicka commented on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I run into same issue. Option under the second Advanced button are all checked. First time after changing configuration, the trend was showing historical data. The trend information disappeared after a new build finished. The cpp check plugin shows tabular information with a few cpp check findings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15707) Cppcheck Trend graph is blank even though the plugin processes stats correctly
jan_ruzicka edited a comment on JENKINS-15707 Cppcheck Trend graph is blank even though the plugin processes stats correctly I run into same issue. Option under the second Advanced button are all checked. First time after changing configuration, the trend was showing historical data. The trend information disappeared after a new build finished. The cpp check plugin shows tabular information with a few cpp check findings. It actually looks fine now ... I don't know what happened. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14538) Separate configure tools page
jan_ruzicka commented on JENKINS-14538 Separate configure tools page This is interesting idea. Can there be a link from the main configuration page to the one with separated plugin settings? It would be nice for easier transition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14368) Create or Update Label in StarTeam displays passwords as clear text in Console Output
jan_ruzicka commented on JENKINS-14368 Create or Update Label in StarTeam displays passwords as clear text in Console Output The log entry doesn't look familiar. What is the project setup? Is maven used for compilation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11939) Provide a way to add custom xdoc files to describe the checkstyle rules
jan_ruzicka commented on JENKINS-11939 Provide a way to add custom xdoc files to describe the checkstyle rules Would use of PHP Code Sniffer producing checkstyle reports be a case for using the xdoc files? Currently each entry shows "No description available. Please upgrade to latest checkstyle version.". Would the xdoc address 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
[JIRA] (JENKINS-14003) Starteam plugin takes a very long time for code check out
[
https://issues.jenkins-ci.org/browse/JENKINS-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163560#comment-163560
]
jan_ruzicka commented on JENKINS-14003:
---
Thanks for getting back to me.
Sorry for not wording my questions properly.
Are some projects slowed down more then others?
I meant Do you have different styles of projects? and Does it make
difference?
Looking for indications as: Projects with just a few files are better then with
many. Big files slow down more then small files.
Clean project checkout takes 10 minutes? That is quite unusual by itself. What
kind of project are we talking about? Are there thousands of files and Gigs of
data?
By What setup is used? I meant StartTeam setup.
Example: Dedicated server for ST and dedicated server for ST Database.
Jenkins is on separate computer from ST server.
ST server network round-trips are min/avg/max/stddev = 0.522/0.718/1.097/0.137
ms
(ping from ST client machine to the ST server)
By What version of server and client are in play? I meant StartTeam server
version and StartTeam client version. Is it ST 2008, 2009, ...?
Output of stcmd would be helpful. First few lines are showing the executable
version information.
The command line parameters with filtering for NCO specifies only new and
changed files to be checked out
{{stcmd co -p project path -is -F NCO -rp C:\Jenkins\Workspace\MyProject
*}}
If you remove the contents of the local directory and try to check out the
project, how long does it take?
Starteam plugin takes a very long time for code check out
-
Key: JENKINS-14003
URL: https://issues.jenkins-ci.org/browse/JENKINS-14003
Project: Jenkins
Issue Type: Improvement
Components: starteam
Reporter: K Ningthouj
Assignee: jan_ruzicka
We are using Starteam plugin with Jenkins for our project. When we perform
check-outs, it takes a very long time unlike when we run the starteam command
line using stcmd which is pretty fast. Is there any possibility in the
current plug-in that provides a way that we can pass a parameter just like
the starteam command line to speed up the checkout process?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14003) Starteam plugin takes a very long time for code check out
[ https://issues.jenkins-ci.org/browse/JENKINS-14003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163482#comment-163482 ] jan_ruzicka commented on JENKINS-14003: --- Thank you for filing a bug report. Can you help me understand details more clearly? Can the problem be reproduced easily? Does it show on all projects every time or are some projects slowed down more then others? Does the checkout take same time as checking out clean project using command line? Is the slowdown observed on a master or a slave? Does it make a difference? What setup is used? What version of server and client are in play? What configuration? Are cache agents used? (mentioned in [JENKINS-13398] ) What parameters are passed to StarTeam command to speed up checkout? Starteam plugin takes a very long time for code check out - Key: JENKINS-14003 URL: https://issues.jenkins-ci.org/browse/JENKINS-14003 Project: Jenkins Issue Type: Improvement Components: starteam Reporter: K Ningthouj Assignee: jan_ruzicka We are using Starteam plugin with Jenkins for our project. When we perform check-outs, it takes a very long time unlike when we run the starteam command line using stcmd which is pretty fast. Is there any possibility in the current plug-in that provides a way that we can pass a parameter just like the starteam command line to speed up the checkout process? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13398) support for starteam cache agents
[ https://issues.jenkins-ci.org/browse/JENKINS-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162562#comment-162562 ] jan_ruzicka commented on JENKINS-13398: --- node vs. master was meant as jenkins node vs jenkins master. The jenkins master stores configuration and some details. Nodes do the work and don't have to be on same computer. Nodes can be on a different lan, they can be a different OS ... . support for starteam cache agents - Key: JENKINS-13398 URL: https://issues.jenkins-ci.org/browse/JENKINS-13398 Project: Jenkins Issue Type: Improvement Components: starteam Affects Versions: current Reporter: mistafunk Assignee: jan_ruzicka Priority: Minor it would be nice to have support for starteam cache agents, this would accelerate checkouts quite a bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13398) support for starteam cache agents
[ https://issues.jenkins-ci.org/browse/JENKINS-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162563#comment-162563 ] jan_ruzicka commented on JENKINS-13398: --- Is it possible to have setup without cache and still work with the changes[1]? Can there be unit test cases for both setup with cache and without? Main issue is a backward compatibility ... (There were some requests for support of StarTeam 6.0) [1] https://github.com/mistafunk/starteam-plugin/commit/58249bf78db0fc25e36ea8141b2571072bc19f0e support for starteam cache agents - Key: JENKINS-13398 URL: https://issues.jenkins-ci.org/browse/JENKINS-13398 Project: Jenkins Issue Type: Improvement Components: starteam Affects Versions: current Reporter: mistafunk Assignee: jan_ruzicka Priority: Minor it would be nice to have support for starteam cache agents, this would accelerate checkouts quite a bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13699) Jenkins plugin does not identify itself as a ClientApplication
[ https://issues.jenkins-ci.org/browse/JENKINS-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162507#comment-162507 ] jan_ruzicka commented on JENKINS-13699: --- Changes were in commit d1e3cf743b382f49f0984aadce2a2cee9fd60321 and commit 8489692fcfb05f5e0a0da9b150078fe1680cd390. Jenkins plugin does not identify itself as a ClientApplication -- Key: JENKINS-13699 URL: https://issues.jenkins-ci.org/browse/JENKINS-13699 Project: Jenkins Issue Type: New Feature Components: starteam Reporter: pauldawg Assignee: jan_ruzicka Priority: Minor This fix has already been submitted and pulled into mainline. I am submitting the issue as a formality, but would like this pulled into a new release of the plugin as soon as possible. Without this feature, it blocks StarTeam administrators from taking advantage of the AppControl feature in 2009 to block unauthorized clients and utilities. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13398) support for starteam cache agents
[ https://issues.jenkins-ci.org/browse/JENKINS-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161437#comment-161437 ] jan_ruzicka commented on JENKINS-13398: --- patches are welcome ... I don't have a cache agent to test on ... support for starteam cache agents - Key: JENKINS-13398 URL: https://issues.jenkins-ci.org/browse/JENKINS-13398 Project: Jenkins Issue Type: Improvement Components: starteam Affects Versions: current Reporter: mistafunk Assignee: jan_ruzicka Priority: Minor it would be nice to have support for starteam cache agents, this would accelerate checkouts quite a bit. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10465) Get Support Subscription points to hudson-ci
[ https://issues.jenkins-ci.org/browse/JENKINS-10465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159038#comment-159038 ] jan_ruzicka commented on JENKINS-10465: --- The plugin in question is named Hudson Support Subscription Notification Plugin artifactId: scis-ad groupId: org.jvnet.hudson.plugins Get Support Subscription points to hudson-ci -- Key: JENKINS-10465 URL: https://issues.jenkins-ci.org/browse/JENKINS-10465 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Reporter: Vlad Dumitrescu Priority: Minor In Manage Jenkins I have an item that is outdeted Get Support Subscription Commercial support subscription available from Sun Microsystems. The link goes to hudson-ci.org/support where it is also mentioned that Oracle will soon provide support... (I have another installation where this item is not present, is this from a plugin?) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
