Development Workflow

chietala

****Notice****

I'm not talking about workflow builder. I'm talking about the development process of building for Teamsite/sitepublisher.

**************

So I have been working with Teamsite/SitePublisher for almost 3 years now and I haven't found a good solution or real answer to my question. My question: Is there anyway to have a "agile development" workflow with these products. When I mean agile I mean iterative, work locally see changes, edit, see changes, when ready commit the code.

Downloading and uploading files and committing just to see some change is very time consuming. I'm a front-end dev so instant gratification is pretty much required for building stuff. Maybe I'm just doing it wrong, but there is no project manager, CTO, Teamsite Architect etc to put some sort of solution in place to make this less painful.

Any help would be appreciated.

Rick Poulin

You might want to change your thread title, since the most common meaning of "workflow" doesn't apply here and will trip up people regardless of your notice.

There's small things you can do, but overall there is no "local testing" when it comes to TeamSite. Best case is if you've got boatloads of money or a friendly Autowoven sales rep, get Development licenses and run instances in local VMs.

As for the build process, you can cut out the uploading if you use the file share. However, there's no "TeamSite Lite Webapp" for testing Java changes, so while there's ways to optimize the UITK build process, there's no avoiding some time wasted waiting for the TS UI to come up for minor changes.