TeamForge Release 6.2 Webinar Q&A

On June 26th, I presented the webinar, “TeamForge Release 6.2 – What’s New,” In the session, I talked about how TeamForge 6.2 can help you increase developer productivity, drive transparency and ensure compliance. I also did live demos of the new features and explained the functionality.

We also had an engaging Q&A session where I referenced resources and in some cases, next steps on how to get started or get going with TeamForge so I thought it would be helpful to post the Q&A as a follow-up and thank you to those who joined me.

If you missed the session live, you can watch the recording and download my slides. For more information about this topic, please visit www.collab.net/teamforge6.2 here, you can access additional webinars, informative assets, and free product downloads.

Don’t forget to register for our upcoming webinars. CollabNet offers multiple webinars a month that cover a variety of topics related to software development.

As promised, here’s the follow up to the live audience questions.

Q: Are there any improvements in terms of installations/setup or does it follow the same old installation steps as in 6.1?
A:In 6.1.1 we’ve made significant improvements to the installation of TeamForge.  For instance to install TeamForge it requires one yum command – “yum install teamforge”, and for upgrades, it’s simply “yum upgrade teamforge” In addition we’ve added a  new dependency checker that shows you what’s going on during the installation process. And these additions that we made in 6.1.1 are part of the 6.2 installation as well.

 

Q: Would these reports be available in the CollabNet desktop plug-in (he just showed the browser)?
A: They’ll be available through a web page interface directly in the desktops, similar to how burndown, capacity, open by priority, and open vs closed charts are available today.

 

Q: Is there a report or dashboard that shows all of a developer’s tracker assignments across projects? Similar to My Assigned Items, but meant to be viewed by a manager.
A: Yes.  We have an add-on (CLI) available today that allows you to create custom reports and add them to a project page. This Command Line Interface (CLI) add-on allows you to create custom reports with data directly from the datamart, and allows you to push them to existing project pages.

 

Q: Is there an additional cost associated with the GIT pieces?
A: Yes, it is an additional license to get Git SCM on top of TeamForge. Please talk with your TeamForge Account Manager or Support Representative for particular pricing.

 

Q: How difficult is the migration process from an existing 5.4 Linux server to a 6.2 Windows server?  Any quick tips?
A: Currently we only offer 6.2 on Linux, and we’re working on setting a release date for 6.2 on windows soon. In addition, we’re targeting same OS upgrades, so from Linux 5.4 to Linux 6.2, and not to Windows 6.2. We do have a migration script that migrates the data, but if you want to upgrade to Windows, I’d suggest working directly with our Professional Services team to ensure that everything goes smoothly, once we have 6.2 available on Windows.

 

Q: How does TeamForge compare to TeamFoundationServer, and which points do you often use to convince people to switch from tfs over to tf (aside from the usual tfs is just ms centric and bound to its own version control system)
A: The biggest difference is how TeamForge can support several different SCM types, such as Subversion, Git, Perforce, and CVS. Also Microsoft locks you int their methodologies and fixed processes, whereas TeamForge is committed to being process agnostic so that it can handle agile methodologies, waterfall methodologies, and everything in between. Further, the installation and configuration process is a lot more lightweight and straightforward than TeamFoundation Server, and in most cases can be done in an afternoon by one site administrator, as opposed to having a team of consulting coming in to get TeamFoundationServer up and running.

 

Q: Something that isn’t clear for me when I looked at the site: TeamForge seems to be available for download, and there is no need for internet cloud storage, is it so? And if so, which is its license either for personal/open source projects, and for professionals?
A:  Internet Cloud storage is optional for TeamForge, and TeamForge can work with having everything installed in your environment, or hosted by CollabNet. We offer TeamForge free for up to 10 users, and this is a fully functional version of TeamForge. For open source projects, we can work directly with you on setting something up for your project.

 

Q: Can TeamForge integrate with teamcity? Of course, tc can connect to git or svn, but I wonder if tc can be used instead of jenkins/hudson inside the tf panel.
A: Yes, and we actually have a few customers that integrate with TeamCity already and it’s a great combined solution showing how Continuous Delivery can be done with TeamForge.

 

Q: How does TF enforce a Git Master repository?  It seems like commits could be happening in developer clone repos without any way to prevent this…
A: Any time you do a Git push, such as just “git push”, that’s going to push to your master TeamForge repository.  So if you have it synced up through Gerrit that’s where it’s going to go.  If you do a push to a branch that’s hosted in Gerrit,will push to that Gerrit branch.  Then within Gerrit you can fetch that for code review or you can get that branch directly from Gerrit and then once it’s approved you can push it back to the master which is inside of TeamForge.  So the repository hosted by TeamForge is used as the master repository.

 

Q: Does 6.2 bring any new dashboarding capabilities around TeamForge license capacity / utilization?
A: No, it does not.

 

Q: Is the  Jenkins/Hudson integration dependent on LabManagement or can we use inelastic/static provisioning?
A: Absolutely.  Lab Management is only value add to get elastic provisioning.  You don’t need to use Lab Management to use Hudson and Jenkins plug-in at all.

 

Q: How would users request access to a project through gerrit or reviewboard? Are the repos publicly viewable?
A: Users would have to talk to their project admin to give them access on a per project basis.  For instance, if you’re in one project and you don’t have access to either of those you would a have to ask your project admin if you don’t have project admin access to get those permissions to access ReviewBoard and Gerrit.  Once you access that then you’ll be able to see Gerrit in ReviewBoard within that project context. Now another key thing on this is if you have multiple projects you can have a hybrid solution – You can have access to ReviewBoard in one project, but not the other so you’d only be able to see ReviewBoard information for one project and not the other and the same is true for Gerrit as well.  So it allows you to only share information across those tools for projects that make sense for those developers.

Q: Any plans to add code review integration for Code Collaborator – similar to what’s been done for Review Board?
A: No, not at the moment.  However, if there’s more information that you want to send to me directly about Code Collaborator let me know and we can look at it.

 

 

Q: Where can I find the definitions of tables/views in the operational datastore and datamart?
A: These are available directly in our help docs

 

Q: Any tie-ins anticipated with Jdeveloper?
A: No, not at the moment.  If you’re thinking about it from a IDE integration right now we support Visual Studio and Eclipse for IDE; however, if you’re looking at JDeveloper the best way is to get it in via JDevelopers web-page plugin, and viewing TeamForge’s web UI directly in the IDE.

 

Q: Any plans to add Sonar?
A: Yes, that’s on our list of integrations that we want to eventually support through CollabNet Connect, but we haven’t targeted a specific release to offer this yet.

 

Q: Is Agile stuff available natively or do you have to install it?
A: it’s available natively

 

Q: If you have TeamForge 6.1.1 for Windows, will you make available an upgrade install?
A: Yes.  You’ll be able to upgrade from 6.1.1 to 6.2 on Windows.  This is something new we added and – and 6.1.1 was basically a migration option for – for 6.1.1 to further future versions of TeamForge. Stay tuned on the availability of TeamForge 6.2 on windows.

 

Q: Can you apply TeamForge for creating and reviewing documents the same as you would for Source Code stuff?
A: Yes, we have our own document management tool that’s inside of TeamForge and it has its own review tool within it.  Essentially, you can put something up in the document structure, an interface similar to Windows Explorer.  When you put that document in the document space you can change the status to either draft, and then you can also add a review to it and you can assign users within your TeamForge project to review that document.  The difference is is you’re not getting the inline annotation that you would get with code review, but you will be able to get it and see who’s reviewed it, who’s not, and  what your status is.

 

Q: Does TF 6.2 support ingest and parsing of externally generated requirements?
A: In general, we allow for connecting to third party tools directly through CollabNet Connect, but if you have a specific tool that you have in mind, let us know and we can investigate further.

 

Q: When will 6.2 be available on Forge.mil? [Should Remove this question
A:N/A – This Q should be removed

 

Q: How Git support in TeamForge 6.2 compares to GitHub?
A: The big difference is GitHub is really meant for hosting your Git repository.  TeamForge is a full application life cycle management tool so you get anything from your planning phase which is done in the TeamForge tracker to the coding phase which is done in combination of your SCM tool and the tracker to reviewing, which  could be part of your code review tools such as Gerrit and Git and Code Review.  So really what you’re thinking about is a lot more wider selection of tools. The other part is TeamForge allows for a master repository centrally located that can be gated by Gerrit.  So now you have a gating area using Gerrit to actually allow for being able to push to just Gerrit and then a master repository as the main Git – Gerrit repository inside of TeamForge.  To me, the big difference is you’re looking at a much wider solution than what GitHub supports.  And also we’re a lot more flexible.  So if you want to actually have it hosted in your own private environment we – we support that.  If you want to have a private cloud support or a public cloud support.  So the deployment options is a lot more flexible than what GitHub has as well.

Tagged with: , , , , , , , , , , , ,
Posted in TeamForge

Leave a Reply

Your email address will not be published. Required fields are marked *

*