[JIRA] [teamconcert] (JENKINS-20994) Make Just accept and fetch from a build workspace more full featured
Scott Cowan updated JENKINS-20994 Make Just accept and fetch from a build workspace more full featured Change By: Scott Cowan (13/Dec/13 2:05 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18421) Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition
Scott Cowan commented on JENKINS-18421 Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition Hi Praveen, The Team Concert Plugin for Jenkins does not currently support starting post-build options in RTC. That is what this enhancement is intended to address. Would you mind detailing your build at https://jazz.net/forum and asking your questions there? You'll have a wider audience of Jazz developers to respond. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18691) Team Concert plugin is adding components to a workspace
Scott Cowan resolved JENKINS-18691 as Not A Defect Team Concert plugin is adding components to a workspace Change By: Scott Cowan (11/Jul/13 1:21 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-18419) Snapshot name is missing build number
Scott Cowan resolved JENKINS-18419 as Fixed Snapshot name is missing build number Change By: Scott Cowan (09/Jul/13 5:55 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] [release] (JENKINS-18548) Release build runs different than manual build
Scott Cowan updated JENKINS-18548 Release build runs different than manual build Change By: Scott Cowan (09/Jul/13 5:59 PM) Component/s: release Component/s: teamconcert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18548) Release build runs different than manual build
Scott Cowan created JENKINS-18548 Release build runs different than manual build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: teamconcert Created: 28/Jun/13 4:37 PM Description: I just tried to release teamconcert 1.0.6, and the release ran fine on my client machine, but the build failed, https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/31 Then I manually requested a build with no changes and it succeeded, https://buildhive.cloudbees.com/job/jenkinsci/job/teamconcert-plugin/32 I did a diff of the logs and found some additional logged entries in the successful build that seem related to the error reported in the failed build. They are at the bottom. This all seems related to the special requirements of our plugin that lead us to using a file repo, https://github.com/jenkinsci/teamconcert-plugin/tree/master/com.ibm.team.build.hjplugin/repo See history of our plugin requirements for reference here, https://groups.google.com/forum/?fromgroups#!searchin/jenkinsci-dev/cowan/jenkinsci-dev/aFN3wcTt2Sw/hB8nDczGU14J CONSOLE LOG: DEBUG Using connector WagonRepositoryConnector with priority 0 for http://repo.cloudbees.com/content/repositories/central DEBUG Using connector WagonRepositoryConnector with priority 0 for file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo Downloading: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml DEBUG Using connector WagonRepositoryConnector with priority 0 for http://repo.jenkins-ci.org/public/ Downloading: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml Downloading: file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo/org/kohsuke/stapler/stapler/maven-metadata.xml DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties 457/457 B 457/457 B 4/6 KB 457/457 B 6/6 KB Downloaded: http://repo.cloudbees.com/content/repositories/central/org/kohsuke/stapler/stapler/maven-metadata.xml (457 B at 4.7 KB/sec) DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties Downloaded: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/stapler/maven-metadata.xml (6 KB at 38.4 KB/sec) DEBUG Writing resolution tracking file /home/jenkins/.m2/repository/org/kohsuke/stapler/stapler/resolver-status.properties DEBUG Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in hjplugin-rtc-repo (file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo) DEBUG Could not find metadata org.kohsuke.stapler:stapler/maven-metadata.xml in local (/home/jenkins/.m2/repository) DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session. DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session. DEBUG Failure to find org.kohsuke.stapler:stapler/maven-metadata.xml in file:///scratch/jenkins/workspace/jenkinsci/teamconcert-plugin/com.ibm.team.build.hjplugin/repo was cached in the local repository, resolution will not be reattempted until the update interval of hjplugin-rtc-repo has elapsed or updates are forced DEBUG Skipped remote update check for org.kohsuke.stapler:stapler/maven-metadata.xml, already updated during this session. DEBUG Using connector WagonRepositoryConnector with priority 0 for http://download.java.net/maven/2/ Downloading: http://download.java.net/maven/2/org/kohsuke/stapler/stapler/maven-metadata.xml 4/5 KB 5/5 KB 5/5 KB Fix Versions: current Project: Jenkins Labels:
[JIRA] [teamconcert] (JENKINS-18284) Team Concert plugin doesn't load components as root folders
Scott Cowan updated JENKINS-18284 Team Concert plugin doesnt load components as root folders Change By: Scott Cowan (20/Jun/13 7:42 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18419) Snapshot name is missing build number
Scott Cowan commented on JENKINS-18419 Snapshot name is missing build number Hi Florian, I agree it would be too long to wait for each CLM release. We'll consider a Team Concert Plugin release with each CLM Sprint. Scott This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
