[JIRA] [teamconcert] (JENKINS-18421) Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition
Nick Edgar commented on JENKINS-18421 Teamconcert plugin to trigger Post-Build Events configured in RTC Build Definition Regarding post-build deliver, the plugin does not currently support that, just the initial SCM phase. In the interim, it's possible to add a step to the build to invoke JBE as a one-off to run a particular phase of the build, e.g.: jbe -repository REPO_ADDR -userId USER_ID -passwordFile PASSWORD_FILE -engineId ENGINE_ID -buildResultUUID $buildResultUUID -participants com.ibm.team.build.autoDeliver -noComplete -verbose Where $buildResultUUID is the property within Jenkins containing the build result UUID. Can also use -pass PASSWORD if you're not using a password file, but there's a risk then that the password would appear in the build log. 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-18293) Team Concert plugin cannot cope with symbolic links
Nick Edgar commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links Danny had responded by email (before Heather's responses above): >> This is a tricky one, since the ability to create a symbolic link can also be limited by the OS (Win 7 supports it, by requires updated user & application security settings. Win XP requires a patch). However the system and userids I’m using are set-up to allow the creation of symbolic links. Therefore it stands to reason it’s either the application security settings, or the ‘inability’ of the application. >> Regarding the ability of the application: If you’re utilizing the (l)scm load command, it usually does create the symbolic links when we start it from the command line in a CMD file ourselves. If run the same CMD file in a Jenkins Job, it usually doesn’t. We haven’t been able to figure out why… >> Regarding the security settings to allow creation of symlinks: Can you indicate what the (user/application security) settings should be, to allow the plugin to create symbolic links on Win7? >> You have a good suggestion, but it’s only a workaround. We’re currently looking into it. Hopefully the article Heather linked to above helps with the question of settings. 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-18292) Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path
Nick Edgar commented on JENKINS-18292 Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path I had made a similar suggestion by email: This is a defect which we'll investigate (it's supposed to use the full path if given, and only append to Jenkins workspace path if relative). For now, please specify a relative path in the build definition, or use "." if you want to use the Jenkins workspace directory directly. Danny responded with: >> We’ve already switched to a relative path setting in the 'Load Directory'-setting of the 'Jazz Source Control'-tab in the Build Definition. Good suggestion to use the “.” here, 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] [teamconcert] (JENKINS-18284) Team Concert plugin doesn't load components as root folders
Nick Edgar commented on JENKINS-18284 Team Concert plugin doesn't load components as root folders I had made the same suggestion to Danny. He responded by email with: >> We’ve already switched to using the Build Definition setting. However it would have been nice if this limitation would have been mentioned somewhere. Or the description of the plugin would describe that for now you support “simple workspace-only config” when using the ‘Just accept and fetch from a build workspace’-setting. >> Expected solution: When you’re utilizing the scm commands, add the ‘-i’ option, as a choice in the Jenkins Job configuration, just as in the Jazz Build Definition: . We could perhaps add something to that effect in the ? help for the simple workspace option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
