[JIRA] [teamconcert-plugin] (JENKINS-26560) Too long description of BuildResutUUID that team Concert Plugin creates makes editing difficult
Heather Fraser-Dube commented on JENKINS-26560 Too long description of BuildResutUUID that team Concert Plugin creates makes editing difficult We are running Jenkins 1.596. I have builds defined with a long description for a build parameter and it wraps nicely. Seems like Jenkins has fixed their issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-plugin] (JENKINS-25762) Build Engine going inactive due to no credentials
Heather Fraser-Dube commented on JENKINS-25762 Build Engine going inactive due to no credentials On the build engine's overview tab, try turning off "Monitor the last contact time". 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James, I think the thread dump (of all the threads) would help (for next time). By previous build, I mean the Jenkins build for the same job that just ran previous to it. For example it looks like TRUNKP was the job that was run with the personal build workspace. If that was build #73 then how did the TRUNKP build #72 end? Legitimate failure (test failure as opposed to not a failure during the load step, not cancelled). Just trying to exclude the idea of a previous build impacting the next one. 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source I have raised : 336647: Personal builds can encounter deadlock when fetching source for this in jazz.net 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] [teamconcert-plugin] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James Can you look at the RTC Build result for this build that was started in RTC. When you open the build result there are tabs of different pieces of info. Is there an Activities tab? Does the Activities tab have any entries. Specifically I am interested in one that says "Fetching files" and whether it was complete or not. Can you tell if the source code was all loaded or not? Was the stack trace showing it was stuck in the same place again? Were there other threads (or the other executor) running and were any of them running RTC or Plugin code? Did the build prior to this one finish normally or was it cancelled? 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] [teamconcert] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi James, Sorry for the delay. Things have been a bit busy here and unfortunately I am away next week. I've looked over our code in this area but don't see anything obvious. The problem is at a lower level than us, but I don't quite understand what would trigger it. So a bunch of questions... Does this only happen for 1 user's personal build or is it randomly affecting all personal builds? If it affects just 1 (or a given set of) user, can you check their workspace and see if its visible to the user that the Jenkins job is configured to use. Also see if there are missing or extra components from what is normally in the build workspace. If there are extra components, are they visible to the user that the Jenkins job is configured to use. I don't think this is the problem, but I want to rule it out too. The sandbox is where the RTC repository workspace is to be loaded. Its defined on the Source Control tab of the build definition as the Load directory. If you set the path to ".", it will end up being in the Jenkins job's workspace. I am interested in knowing if you use any special features wrt loading (i.e. in the build definition, do you have delete directory before loading checked? Is Create folders for components checked?) When it happens, can you look at the job's log. I am interested in all the messages that are related to the check out (or possibly corrupted metadata). It will also help to understand how far it got during the load. I think that they would follow the "RTC Checkout : Source control setup" message. Does the build result have an activity for Fetching Files... If so, was it completed? Does trying to cancel the build help when this happens? 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] [teamconcert] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
Heather Fraser-Dube commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source What version of the build toolkit are you using? Do you allow the same Jenkins job to run with more than one instance? By default I think Jenkins allows only 1 instance of a job to run at a time. Do you know if the checkout of the job was successful or if an error occurred. The stack trace shows that it is trying to release the lock on the sandbox. Do the personal builds use the same sandbox? If so, then it is not a good idea to run them in parallel (one will overwrite the sandbox with different contents in the middle of the build potentially. Are the jobs running on the Jenkins master or on slaves when this occurs? 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] [plugin] (JENKINS-24738) Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable
Heather Fraser-Dube resolved JENKINS-24738 as Not A Defect Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable Jenkins doesn't do the substitution of variables. The plugin itself won't do either because I don't think we will have the variables as configured for the slave in order to do the substitution. You can configure the slave to point to a toolkit that is in a different directory than on the master by following the Master-Slave configuration instructions Change By: Heather Fraser-Dube (18/Sep/14 1:20 PM) Status: Open Resolved Resolution: Not A Defect 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] [plugin] (JENKINS-24738) Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable
Heather Fraser-Dube assigned JENKINS-24738 to Heather Fraser-Dube Dynamically use Build Toolkit on Slave Machine when path to it is provided as an Environment Variable Change By: Heather Fraser-Dube (18/Sep/14 1:11 PM) Assignee: Deluan Quintão Heather Fraser-Dube 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] [teamconcert] (JENKINS-24459) Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577
Heather Fraser-Dube resolved JENKINS-24459 as Not A Defect Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577 I am resolving this as invalid because its not a plugin problem. The referenced work item is being updated with the ongoing investigation. Change By: Heather Fraser-Dube (27/Aug/14 4:31 PM) Status: Open Resolved Assignee: Heather Fraser-Dube Resolution: Not A Defect 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] [teamconcert] (JENKINS-24459) Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577
Heather Fraser-Dube commented on JENKINS-24459 Jenkins RTC Plugin 1.1.8 doesn't work with Jenkins Version higher then 1.577 This isn't actually a problem with the Team Concert plugin. The problem reported is with RTC starting a Jenkins job (which may or may not be configured to use the RTC SCM (i.e. using the Team Concert plugin)). It is being tracked in a workitem against RTC's integration RTC Hudson/Jenkins server-side integration doesn't work with Jenkins Version higher then 1.575 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Lorelei can you describe how you would be using this. Would it be for users running their own personal build or would it be triggered another way? 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] [teamconcert] (JENKINS-19675) RTC Build Toolkit can't be installed automatically
Heather Fraser-Dube assigned JENKINS-19675 to Scott Cowan RTC Build Toolkit can't be installed automatically Change By: Heather Fraser-Dube (16/Jun/14 12:33 PM) Assignee: Heather Fraser-Dube Scott Cowan 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] [teamconcert] (JENKINS-19675) RTC Build Toolkit can't be installed automatically
Heather Fraser-Dube commented on JENKINS-19675 RTC Build Toolkit can't be installed automatically This is also being tracked in 303666: Investigate supporting "Install automatically" option for RTC Build toolkit in Team Concert Plugin for Jenkins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-21038) Improve security in team-concert plugin
Heather Fraser-Dube resolved JENKINS-21038 as Fixed Improve security in team-concert plugin In release 1.1.2 the team concert plugin now makes use of the credentials plugin. The userid and password are maintained by the credentials plugin instead. There is some manual migration required. You will need to create credentials for RTC and update the jobs to reference the credentials instead of the user/password/password file entered in the scm configuration. Change By: Heather Fraser-Dube (12/Jun/14 12:22 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/d/optout.
[JIRA] [teamconcert] (JENKINS-21537) Option to use Global User and Password when RTC url is overidden
Heather Fraser-Dube resolved JENKINS-21537 as Fixed Option to use Global User and Password when RTC url is overidden In release 1.1.2 of the plugin, the credentials plugin is now used to maintain the credentials used by the job. This means credentials can be stored in 1 place and referenced by many jobs. Change By: Heather Fraser-Dube (12/Jun/14 12:18 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/d/optout.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube resolved JENKINS-21933 as Cannot Reproduce PermGen leaks The client's script was causing issues. Change By: Heather Fraser-Dube (12/Jun/14 12:17 AM) Status: Open Resolved Resolution: Cannot Reproduce 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube resolved JENKINS-22110 as Cannot Reproduce Jenkins RTC SCM Jobs error out after Master Restart We haven't encountered this issue. Side discussion resulted in changes for the toolkit to be installed automatically instead of all slaves trying to access the same toolkit in a shared location. If the problem still exists, please re-open. Change By: Heather Fraser-Dube (12/Jun/14 12:15 AM) Status: Open Resolved Assignee: Heather Fraser-Dube Resolution: Cannot Reproduce 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart Hi Bernie We (and another user of the plugin) have tried it out and it does work. The auto-install can't be from the jazz.net page, but it can be from your own internal location. The wiki page for the plugin has been recently updated to describe a setup. https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-Master%2FSlaveConfiguration (scenario works for all the versions of the plugin since the auto-install is a Jenkins feature). 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart So does this mean you are using the Oracle jvm and not IBMs? I would like to rule out JENKINS-23176 We do update the class loader. This is because the Build toolkit classes needed to perform RTC related tasks like loading are not part of the Jenkins class path. The class loader we create is a URLClassLoader with the System class loader as the parent. The urls of the jars that form the toolkit have been added to it. The code that is running under that class loader does not have any dependencies on Jenkins classes so there is no need to retrieve them from the master (i.e. using the RemoteClassLoader from Jenkins). Have you thought about installing the toolkit on each slave? We have been experimenting with the auto install of Jenkins tools and believe it can work with a zip copy of the build toolkit. 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] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Christian, I don't understand why you would have 8 Jenkins instances. What other plugins do you have installed? Do you have other things (monitoring?) going on during that timeframe? 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] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Jim you also need to enable garbage collection on classes loaded. See the comment from Abhishek above. If you are using more than 1 toolkit you may also need to increase the permgen area size. 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart We are constructing a URL class loader with the plugin jar that contains BuildClient and all the toolkit jars. I am not sure how the class path can be involved with that. The BuildClient is in the same jar as RTCFacade that is trying to instantiate it. How are you starting the slave? I want to confirm you aren't adding all the toolkit jars to its class path. Only thing I can think of is if all the slaves are referencing the same set of jars that there could be contention there. Maybe they are being prevented from reading the jars to resolve classes? 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] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Christian, I examined the 2nd dump you sent. It does look like class loader issues. It looks like there are 8 toolkit class loaders being referenced. I dug further and see 8 copies of the class that manages the class loader. We expect 1, this is a class that is never instantiated, so I have the feeling that something with multiple different class loaders resulted in us being referenced. I am also seeing 8 of the jenkins.model.Jenkins class. How are you starting Jenkins, are you running it within winstone? tomcat? WAS? something else? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22013) With Team concert plugin saving the configuration always gives error.
Heather Fraser-Dube resolved JENKINS-22013 as Cannot Reproduce With Team concert plugin saving the configuration always gives error. Insufficient information to further investigate. Team Concert plugin is not within the stack trace. Change By: Heather Fraser-Dube (27/Mar/14 12:23 PM) Status: Open Resolved Resolution: Cannot Reproduce 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Note to self: Another request for ability to substitute the build defn/workspace name 309370: Jazz RTC plugin for Jenkins does not accept parameters 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. If substitution can be done on the build definition/workspace name, what would be the expectation wrt polling? Or are these builds triggered by other builds? 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube edited a comment on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart I am not entirely sure what is going wrong on the slave. I think it should be able to find the jars for the toolkit (I assume it did before). I also don't think I ever saw this problem when I was testing with the slaves. Only thing I can suggest is to turn on debugging for the slave and see if anything strange is happening wrt class loading. On the Slave while we log messages at level FINER, the logs never come back. We have support for a debug flag which will result in the debug output going into a build's console log Environment variable "com.ibm.team.build.debug" with the value "true" will activate the debug logging To configure on a single Slave Jenkins > Manage Jenkins > Manage nodes Hover over the link of the node to configure. Choose Configure from the popup context menu In the Node properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. Alternately to configure on the Master and all Slaves Jenkins > Manage Jenkins > Configure System In the Global Properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. The debug flag currently only logs information relating to the class loader setup. 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] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart I am not entirely sure what is going wrong on the slave. I think it should be able to find the jars for the toolkit (I assume it did before). I also don't think I ever saw this problem when I was testing with the slaves. Only thing I can suggest is to turn on debugging for the slave and see if anything strange is happening wrt class loading. On the Slave while we log messages at level FINER, the logs never come back. We have support for a debug flag which will result in the debug output going into a build's console log Environment variable "com.ibm.team.build.debug" with the value "true" will activate the debug logging To configure on a single Slave Jenkins > Manage Jenkins > Manage nodes Hover over the link of the node to configure. Choose Configure from the popup context menu In the Node properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. Alternately to configure on the Master and all Slaves Jenkins > Manage Jenkins > Configure System In the Global Properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. The debug flag currently only logs information relating to the class loader setup. 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] [teamconcert] (JENKINS-22013) With Team concert plugin saving the configuration always gives error.
Heather Fraser-Dube commented on JENKINS-22013 With Team concert plugin saving the configuration always gives error. Are you saving a job configuration? or the Jenkins configuration page? Does this only happen when you have chosen TeamConcert as the plugin? Which release of the plugin are you using? Which release of Jenkins are you using? I am not seeing anything in the stack trace that is from the Team Concert 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube commented on JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Another option would be use the Hudson/Jenkins integration provided by RTC. There you could set up a build definition that references your Jenkins build. When requesting a build of the rtc build definition you can pick the workspace you want built. 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] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
Heather Fraser-Dube assigned JENKINS-21964 to Unassigned Build definition and workspace name should accept parameters and/or environment variables. Change By: Heather Fraser-Dube (28/Feb/14 10:58 AM) Assignee: Deluan Quintão 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
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Thanks Abhishek for the workaround. We do special class loading in order to access the toolkit(s). But the class loader should be cached and re-used. 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
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks I have raised 305293: PermGen leaks with HJPlugin to continue tracking this. 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
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Are you using a build definition or a build workspace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Thought about this more. We shouldn't be using Antrunner afik. Is this happening with a single job with a single toolkit and a single build user defined? If the answer is No... How many toolkits do you have defined? How many any other jobs on your Jenkins instance? Do they use different toolkits? Different build users ids? Is polling enabled? If so at what frequency and for how many jobs? What version of the toolkit are you using? Which version of Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Is it a single build you are building over and over when it runs out of permgen space? Does the build run any ant tasks? 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-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Heather Fraser-Dube commented on JENKINS-21857 com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF Pushed the missing files. When developing within Eclipse we also install the -rtc jars into the hjplugin repo. 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-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Heather Fraser-Dube resolved JENKINS-21857 as Fixed com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF Change By: Heather Fraser-Dube (20/Feb/14 4:31 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] [teamconcert] (JENKINS-21857) com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF
Heather Fraser-Dube assigned JENKINS-21857 to Heather Fraser-Dube com.ibm.team.build.hjplugin-rtc is missing the MANIFEST.MF Change By: Heather Fraser-Dube (18/Feb/14 7:40 PM) Assignee: Heather Fraser-Dube 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-21694) Building from workspace: Add checkbox to return workspace to a pristine state
Heather Fraser-Dube edited a comment on JENKINS-21694 Building from workspace: Add checkbox to return workspace to a pristine state So right now the load is not going to do what you want because it leaves the ignored files on disk. So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load I also made the work item for the build definition source control participant to support it too Support a "Pristine" load when configuring the source control of a build definition which would make the functionality available for use consistently in the plugin. I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well. wrt to being able to have API to programmatically create/update/destroy build definitions, you will be interested in 272836: CCM Design SDK API. You might want to chime in there and identify the forum posts/workitems you have the describe your needs. 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-21694) Building from workspace: Add checkbox to return workspace to a pristine state
Heather Fraser-Dube edited a comment on JENKINS-21694 Building from workspace: Add checkbox to return workspace to a pristine state So right now the load is not going to do what you want because it leaves the ignored files on disk. So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load I also made the work item for the build definition source control participant to support it too Support a "Pristine" load when configuring the source control of a build definition which would make the functionality available for use consistently in the plugin. I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well. wrt to being able to have API to programmatically create/update/destroy build definitions, you will be interested in 272836: CCM Design SDK API. You might want to chime in there and identify the forum posts/workitems you have that describe your needs. 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-21694) Building from workspace: Add checkbox to return workspace to a pristine state
Heather Fraser-Dube commented on JENKINS-21694 Building from workspace: Add checkbox to return workspace to a pristine state So right now the load is not going to do what you want because it leaves the ignored files on disk. So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load I also made the work item for the build definition source control participant to support it too Support a "Pristine" load when configuring the source control of a build definition which would make the functionality available for use consistently in the plugin. I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well. wrt to being able to have API to programmatically create/update/destroy build definitions, you will be interested in [272836: [CCM] Design SDK API|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/272836]. You might want to chime in there and identify the forum posts/workitems you have the describe your needs. 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-21694) Building from workspace: Add checkbox to return workspace to a pristine state
Heather Fraser-Dube commented on JENKINS-21694 Building from workspace: Add checkbox to return workspace to a pristine state So Build definition's delete before loading is what you are doing now if I understand your forum question. Basically deleting the entire sandbox directory and then loading. I got from your forum post that this is too heavy. Sounds to me like you want the sandbox to hold exclusively just the contents of the workspace being built (i.e. some other build step can't populate the sandbox directory with other contents like scripts, tools, etc.). As well when the load takes place, it replaces the contents on disk with whats in the repository. If there are files/folders/links that are ignored & not in the repository, they should be deleted from disk (often build artifacts like bin directory, .class files etc. are marked as ignored and not in the repo, so they should be deleted to ensure a full build). Currently our load operation will leave those ignored items on disk. Just want to be sure I understand your definition of "pristine". 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-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. The build toolkit is used on the Master when determining if there are changes that should trigger a build. It is also used on the master to obtain some info prior to starting the build on the slave. A build toolkit of version 4.0.2 can NOT be used against a 4.0.1 server. Is it still an issue... Depends on how you look at it. It is a problem in 4.0.1 RTC, its not a problem with the Jenkins plugin. For RTC, if you report it, they will suggest that you update to the next version where it is fixed. If you are unable to update, then you can raise an APAR and see if you can get a patch. 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] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube assigned JENKINS-21477 to Unassigned Enable multiple Jazz servers per project Change By: Heather Fraser-Dube (29/Jan/14 8:24 PM) Assignee: Deluan Quintão 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-21537) Option to use Global User and Password when RTC url is overidden
Heather Fraser-Dube commented on JENKINS-21537 Option to use Global User and Password when RTC url is overidden Sounds reasonable. I've raised 300177: Option to use Global User and Password when RTC url is overridden in RTC to track this. 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-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube resolved JENKINS-21483 as Fixed java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. This is a problem with the Build toolkit provided by the RTC product. The defect has been fixed in a later release of RTC. Change By: Heather Fraser-Dube (29/Jan/14 3:10 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] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. I found defects for this in jazz.net 213302: Error in the log every time I start the client (Sun 1.7 VM) and 234968: SCM Daemon prints stacktrace always which was marked as a duplicate of the previous one. It has been fixed in the 4.0.2 release of RTC (CLM). So I am going to resolve this. If you are running with a more recent version of the toolkit, please re-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] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube commented on JENKINS-21477 Enable multiple Jazz servers per project Thanks for the details. I've raised an enhancement request for this so that it is tracked in both places. 300164: Enable multiple Jazz servers per 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] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. Thanks, I haven't seen this before. Can you provide a full stack trace. What release of the RTC Build toolkit are you using? On which platform? Have you made any changes to the toolkit since originally installed (upgraded/applied patch/etc.)? Is this occurring on the master or a slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube commented on JENKINS-21477 Enable multiple Jazz servers per project I don't have any easy answers for you. It does sound like you need a job that builds the code from Server A and then a job that builds the code from Server B on top of it. It does introduce a dependency in jobs, but it simply reflects the dependency already there. If you wanted everything built only in 1 job, then you would need to do scripting to accept & load the code from Server A (using CLI), but this would not give you much in terms of traceability in the build to know what changed in the build from Server A. It would also be harder to reproduce a build unless you also start creating snapshots on Server A too. Which would mean you pretty much replicate in the CLI what a dependent job would do. It also means that changes on Server A would not result in triggering the build of B to occur either. Another option would be to use distributed SCM. That would mean the build workspace on Server B would pull components from 2 different streams (one on Server A and one on Server B). This means that states of the code on Server A would be replicated on Server B. The snapshot would contain every component so you have reproducability and traceability. We would need to make a change to the Plugin though to support the multiple credentials. Having us support multiple build workspaces would be interesting but I am not sure it would be in our immediate plans when multiple jobs or distributed SCM could do 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] [teamconcert] (JENKINS-20994) Make "Just accept and fetch from a build workspace" more full featured
Heather Fraser-Dube commented on JENKINS-20994 Make "Just accept and fetch from a build workspace" more full featured Removing the .jazz directory is not ideal. It will result in a complete re-load (as opposed to just the files that changed). I have raised 296206: Make "Just accept and fetch from a build workspace" more full featured in jazzdev to help us track this. I am curious, how do you decide if the component is "well-formed"? Is this something you do as part of the build or when setting up the build. Also can you describe how you would use "automated creation of build definitions" if that feature was available? I guess I am wondering when it would be automatically generated, which pieces would be configured? What were the other reasons for not using a build definition? 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-21146) Toolkit path broken in mixed-OS environment
Heather Fraser-Dube assigned JENKINS-21146 to Heather Fraser-Dube Toolkit path broken in mixed-OS environment Change By: Heather Fraser-Dube (06/Jan/14 2:29 PM) Assignee: Heather Fraser-Dube 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-21146) Toolkit path broken in mixed-OS environment
Heather Fraser-Dube commented on JENKINS-21146 Toolkit path broken in mixed-OS environment The failure is occurring on the Jenkins master. The Jenkins master also needs access to the build toolkit when starting the build. If the Master is running on Windows, the /var/appl/... path is not going to be able to be treated as an absolute path. I see from the trace: Local Build toolkit="/var/appl/jenkins/rtctoolkit-4.0.1/jazz/buildsystem/buildtoolkit " Node Build toolkit="/var/appl/jenkins/rtctoolkit-4.0.1/jazz/buildsystem/buildtoolkit" I am wondering if you have setup toolkit directories appropriately. When configuring Team Concert (in the Jenkins configuration) you should be able to test the connection successfully. For the slaves you will need to configure where the toolkits are located. See https://wiki.jenkins-ci.org/display/JENKINS/Team+Concert+Plugin#TeamConcertPlugin-Master%2FSlaveConfiguration. 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-21038) Improve security in team-concert plugin
Heather Fraser-Dube edited a comment on JENKINS-21038 Improve security in team-concert plugin Thanks for the report and the suggestions. We had figured that access to the password file would be secured. We chose to have the password file only on the master because it felt like having it on the slaves would require a lot coordination when a password had to be updated. Does your organization make use of the credentials plugin? Are there other plugins that you use that also retrieve the passwords from it? I have raised a work item for this 295009: Improve security in Jenkins Team Concert 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] [teamconcert] (JENKINS-21038) Improve security in team-concert plugin
Heather Fraser-Dube commented on JENKINS-21038 Improve security in team-concert plugin Thanks for the report and the suggestions. We had figured that access to the password file would be secured. I have raised a work item for this 295009: Improve security in Jenkins Team Concert 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] [teamconcert] (JENKINS-20994) Make "Just accept and fetch from a build workspace" more full featured
Heather Fraser-Dube commented on JENKINS-20994 Make "Just accept and fetch from a build workspace" more full featured Have you tried changing the Jenkins workspace directory? You can do this in the configuration of the Job. Go to the Advanced Project Options section. Under there is a checkbox for "Use custom workspace" if you enable this, you can specify an alternate location of the Job's workspace. Or is it that you require further customization of where to load within the Jenkins workspace directory? 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
Heather Fraser-Dube commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links I understand your problem. I wish we had a better solution. The problem is that code that the build toolkit uses to create/update symbolic links is in C libraries (even when using Java 7 on linux). Therefore in order for them to be loaded they need to be on the path for Java which can't be modified once Java starts. We could improve toolkit packaging to make the libraries more accessible. But you still need to specify the libraries when starting Java. Yes, create a request on RTC for this. Maybe other people might have some better ideas. Are your slaves running on Windows or Linux? 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] [plugin] (JENKINS-20820) Post-Build deliver not working in Team concert plug-in
Heather Fraser-Dube commented on JENKINS-20820 Post-Build deliver not working in Team concert plug-in Create a Jazz Build Engine. You just need to define it. No builds need to be associated with it. It will only run briefly within your Jenkins Job to perform the post-build step. Add a step to your build to run the jazz build engine to invoke the post-build deliver participant. jbe -repository %repositoryAddress% -userId USER_ID -passwordFile PASSWORD_FILE -engineId ENGINE_ID -buildResultUUID %RTCBuildResultUUID% -participants com.ibm.team.build.autoDeliver -noComplete -verbose %RTCBuildResultUUID% is an env variable that will be substituted by Jenkins, it contains the build result UUID. ENGINE_ID is the id of the engine previously defined. USER_ID is the user id to use within RTC. PASSWORD_FILE is the file containing the password for the user. These will all likely be the same values as you configured Jenkins with. The jbe executable is located within the Toolkit. Example: /jazz/buildsystem/buildengine/eclipse/jbe If you receive an error about: Failed to load the JNI shared library ... \jre\bin\j9vm\jvm.dll Add a -vm arg specifying the location of the java.exe. This is what my extra step on Windows looks like: C:/BuildToolkits/RTC-BuildSystem-Toolkit-Win-4.0.4/jazz/buildsystem/buildengine/eclipse/jbe -vm C:/ibm-java-sdk-60-win-x86_64/sdk/jre/bin/java -repository %repositoryAddress% -userId heatherf -passwordFile C:/Jenkins/heatherf-password -engineId JenkinsPostDeliver -buildResultUUID %RTCBuildResultUUID% -participants com.ibm.team.build.autoDeliver -noComplete 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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube
commented on JENKINS-18705
Team Concert Plugin is failing in a multi-configuration project
Florian a workaround is to use environment variables :
Go to Jenkins > Manage Jenkins > Configure
In the Global properties section define an environment variable that references the path for the root of your workspace. It will need to be an absolute path.
example: MYMATRIXWS C:\MyMatrix\jobs
Go to Jenkins > Manage Jenkins > Manage Nodes choose your slave node choose Configure
In the Node properties section define the same environment variable again, but reference the path for the root of your workspace on the node. It will need to be an absolute path.
example: MYMATRIXWS C:\MySlaveMatrix\jobs
Go to Jenkins > Jobs choose your job choose Configure
In the section "Advanced Project Options" click the advanced settings button
Check the box "Use custom workspace" it will expand a section to supply workspace paths for the main build and the sub-builds.
In the "Directory" textbox, put in your environment variable followed by a directory in which to load for the main build.
example: ${MYMATRIXWS}/workspace/mainJob
- In the "Directory for sub-builds" textbox, put in your environment variable followed any subdirectory minus the directory for the main build, followed by /${JOB_NAME}
example: ${MYMATRIXWS}/workspace/${JOB_NAME}
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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project Florian, Do you need to have the source checked out/loaded in the main build as well as the children builds? 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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I have opened a defect in RTC to describe some of the I've seen issues with multi-configuration projects seen so far. 274912: Jenkins plugin and Matrix builds 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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project Unfortunately, no I haven't found any other workarounds. Environment variables for the build itself did not seem to be available to Jenkins in the deciding the workspace path. Only thing I can think of is defining environment variables in the environment that Jenkins runs in and seeing if they are substituted in the calculation of the workspace path. If that worked, setting it in the slave environment and the master environment might be an 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.
[JIRA] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I will experiment with this tomorrow if possible. 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
Heather Fraser-Dube commented on JENKINS-18292 Team Concert plugin cannot resolve Jenkins path and Build Definition Jazz Source Control path Created a work item in jazz.net corresponding to this issue. 274151: Absolute path in build definition is treated as a relative path by Jenkins 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] [teamconcert] (JENKINS-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project Actually the 2 directories are nested. The paths that are given for "Directory" and the "Directory for sub builds" must be absolute. 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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube
commented on JENKINS-18705
Team Concert Plugin is failing in a multi-configuration project
I've replicated the problem and my suggestion regarding the build definition is not likely to work. I have though figured out how to configure the project so that it will load into non-nested directories.
In the section "Advanced Project Options" click the advanced settings button
Check the box "Use custom workspace" it will expand a section to supply workspace paths for the main build and the sub-builds.
In the "Directory" textbox, put an absolute path and a directory in which to load for the main build.
ie. /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/mainJob
In the "Directory for sub-builds" textbox, put the same absolute path minus the directory for the main build followed by /${JOB_NAME}
i.e. /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/${JOB_NAME}
The JOB_NAME is a variable populated by Jenkins, there may be nicer variables, but I haven't found them. The other key point is to use an absolute path for each directory. The use of the variable will result in each of the sub jobs having their own directory.
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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project I see your point. I have been looking into this more. I am not sure how you configure a matrix build not to load in the root project, just in the sub project. Can you help me understand your matrix build configuration (so I can sort of replicate)? 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-18705) Team Concert Plugin is failing in a multi-configuration project
Heather Fraser-Dube commented on JENKINS-18705 Team Concert Plugin is failing in a multi-configuration project RTC SCM does not allow sandboxes to be nested within one another. The error indicates that the RTC repository workspace has been loaded in one directory (workspace) and the second build is trying to create a sandbox (workspace/jdk/IBM-JDK-7) within the original sandbox when doing the load. The directories are: /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace /data/demeter/dev/jenkins-build/jobs/RunAsfTests10/workspace/jdk/IBM-JDK-7 I am not sure if it is really your intent to have them nested, but its not supported. One option is in the Jenkins Job(s) under Advanced Project Options, check off "Use custom workspace" and specify a directory that will be a sibling of the other builds. Another option is to create a Build definition and on the Jazz Source Control tab specify the Load directory (right now its a relative path from the Jenkins Job's workspace). You might need a couple of build definitions, one for each 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] [teamconcert] (JENKINS-18691) Team Concert plugin is adding components to a workspace
Heather Fraser-Dube assigned JENKINS-18691 to Heather Fraser-Dube Team Concert plugin is adding components to a workspace Change By: Heather Fraser-Dube (10/Jul/13 10:14 PM) Assignee: Heather Fraser-Dube 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
Heather Fraser-Dube commented on JENKINS-18691 Team Concert plugin is adding components to a workspace If by milestone, you mean a build, this is actually how its supposed to work. The build workspace is to accept all incoming changes from the stream, this includes components not present in the workspace. However you can customize it so that it will accept changes only for some of the components, or even to create an integration of sorts where changes for some components come from one stream and changes for other components come from a different stream. The customization is done through the scoped flows for the build workspace. Open your build workspace in the workspace editor In the Flow Targets section select the flow with the stream and click the edit button. In the dialog presented you have the option to flow all components or to flow only some selected components. Choose to flow only checked components and pick only the components you want flowed from the stream. Save the build workspace when done. You will probably want to delete the extra components that you didn't want. It would also be a good idea to clear the area on disk where the rtc build workspace was loaded/checked out to in the last build (to get rid of the contents of those components that you didn't want). 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
Heather Fraser-Dube resolved JENKINS-18284 as Fixed Team Concert plugin doesn't load components as root folders The help has been updated to indicate for customized load, a build definition should be used. Change By: Heather Fraser-Dube (09/Jul/13 5:39 PM) Status: Open Resolved Assignee: Heather Fraser-Dube 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] [teamconcert] (JENKINS-18293) Team Concert plugin cannot cope with symbolic links
Heather Fraser-Dube resolved JENKINS-18293 as Fixed Team Concert plugin cannot cope with symbolic links Updated the help and the main page to indicate the setup for symbolic links Change By: Heather Fraser-Dube (09/Jul/13 5:28 PM) 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] [teamconcert] (JENKINS-18406) Team Concert plugin is not functional when Jenkins running under Websphere
Heather Fraser-Dube created JENKINS-18406 Team Concert plugin is not functional when Jenkins running under Websphere Issue Type: Bug Affects Versions: current Assignee: Heather Fraser-Dube Components: teamconcert Created: 19/Jun/13 1:33 PM Description: If Jenkins is running within WAS, the team concert plugin fails to run. This issue is being tracked within jazz.net. For full details see: 266411: HPI: Team Concert Plugin and Jenkins connection fails when Jenkins running under WAS https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/266411 Environment: Websphere 7.0.0.25 through 8.5 Project: Jenkins Priority: Major Reporter: Heather Fraser-Dube 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-18406) Team Concert plugin is not functional when Jenkins is running under Websphere
Heather Fraser-Dube updated JENKINS-18406 Team Concert plugin is not functional when Jenkins is running under Websphere Change By: Heather Fraser-Dube (19/Jun/13 1:34 PM) Summary: Team Concert plugin is not functional when Jenkins is running under Websphere 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
Heather Fraser-Dube commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links Finally, if you are running on Windows, you need to be sure that you have permission to create symbolic links. The Symbolic links article in the jazz.net library https://jazz.net/library/article/970/ describes how. 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
Heather Fraser-Dube commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links Also, looking at the trace included leads me to think that your sandbox (place where the load is occurring) is corrupted. The lack of symbolic link support should have generated a nicer error message. So I would also recommend that you delete everything that has been loaded before you try it out. 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
Heather Fraser-Dube assigned JENKINS-18293 to Heather Fraser-Dube Team Concert plugin cannot cope with symbolic links Change By: Heather Fraser-Dube (14/Jun/13 8:21 PM) Assignee: Heather Fraser-Dube 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
Heather Fraser-Dube commented on JENKINS-18293 Team Concert plugin cannot cope with symbolic links RTC support for symbolic links requires one or two libraries (.dll/.so files). Eclipse file system natives RTC file system natives The reason is Java 6 and earlier don't have support for creating/looking at properties of symbolic links. So RTC uses some C code to manage symbolic links. Java 7 has symbolic link support that works on linux, but on Windows it has some limitations when creating links when the target has not yet been created (type is defaulted to file which is not good if its a directory). If you are running Linux and can use Java 7 then the only .so you need is for the Eclipse natives. Otherwise, you will need both. I'll describe what has to happen on Windows, but the steps are similar for linux. In the Build engine directory (buildengine\eclipse\plugins), look for the com.ibm.team.filesystem.client_3.1.600.v20130415_0257.jar org.eclipse.core.filesystem.win32.x86_1.1.201.R36x_v20100727-0745.jar or equivalent jars for your platform/release. From the com.ibm.team.filesystem.client jar you want to extract the winfsnatives.dll (libfsnatives.so on linux). Take all the .dll/.so from the org.eclipse.core.filesystem jar. Place them directly in a directory (eg. c:\natives\winfsnatives.dll). Now when you start Jenkins, we need to tell java about the directory so that it can load the libraries from it. This is done through the -Djava.library.path variable. eg. java -Djava.library.path="c:\natives;%Path%" -jar jenkins-1.509.1.war We are just adding to what the default would be for Java. You could also add the directory to your path instead. I realize the setup is a little convoluted, we could probably help by packaging the toolkit a bit differently. But this might be simpler than trying to load the component through the CLI. 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.
