Codesion

Bugzilla 4.0.1 now available in Codesion

tonamedina — Tue, 14 Jun 2011 07:03:42 -0700

Upgrading our Bugzilla instances in Codesion was a project long time coming… yes, we know!

But you spoke loud and clear and we listened. Therefore, we decide to not just to upgrade our Bugzilla to the next version, but to skip a few major releases and go straight to the latest and greatest.

And it’s our pleasure to announce you that: all new Codesion Accounts, or old account just adding Bugzilla for the first time, will be enjoying a brand-spanking-new Bugzilla 4.0.1 instance from now on.

Old Bugzilla instances in Codesion will still be in 3.0.11… but just for a little longer. We promise! All instances will be gradually, and carefully, migrated to this new version soon with prior notice to the account owners.

So what’s new in 4.0.1? Pretty much everything in the user interface! However, in the backend it still remains the solid, battle-tested tool, plus the Codesion’s service reliability you’ve come to trust.

Some of the new features include:

Automatic Duplicate Detection When Filing Bugs
New Advanced Search UI
New Attachment Details UI
Autocomplete for Users and Keywords
General Usability Improvements
New Default Status Workflow
“Last Search” Now Remembers Multiple Searches
Cross-Domain WebServices with JSONP
Major WebService Enhancements
Mandatory Custom Fields
Voting Is Now An Extension
Users Get New CSS and Javascript Automatically
Many New Hooks
Other Enhancements and Changes

Codesion Enhancements: Deployment Updates, European Data Center, Analytics and more

copello0 — Thu, 02 Jun 2011 07:09:33 -0700

Greetings from the frog. From time to time, we would like to update you on our new features, and talk about our product plans for the future.

New Features

Codesion Publisher Iteration

Codesion Publisher allows one click deployment of your code to any hosted server and cloud providers like AWS, Google App Engine, and Joyent. A limitation in Codesion Publisher was that you cannot have the same type of recipe within a publishing target. For example, if you had one EC2 Server as a target, and you wanted to use SCP to deploy code to the EC2 server, you can only have one SCP recipe for that target. You can, within the same target, have another recipe, say rsync recipe. Based on customers’ input and feedback, customers want to have multiple SCP recipes, same types of recipes. This is now live. Following the previous example, you can now have as many SCP recipes within the same target. This is useful if you have multiple directories or apps on the same EC2 server.

Billing Information

We had many enterprise workgroup customers asking us to have better way to control the billing information on our invoices. Therefore, under Billing -> Billing Information -> Change, you can now add that detail information.

The information entered here will show up exactly on the invoice so that you can have an invoice and receipt to your finance department with the correct billing information.

New Data Center Availability

Codesion has now expanded to Europe. We now have a data center in Europe, located in Netherlands, that currently provides SVN access. As we continue to build out our data center, we will be offering more services locally within the Euro zone. If there are specific services that you would like to see in Europe, please create an idea and vote on it. Depending on your location in Europe, beta customers have seen 2x to 3x increase in performance when doing a checkout. You can do your own test and post your results to our article. If you are an existing customer and want to move your SVN service to Europe, please file a support case at support@codesion.com and we can manually move your repository. Self-service option will come soon.

Reminder

Given the recent Amazon outages, we want to let you know that as a Professional Edition customer, your data is safe with us. As a Professional Edition customer, you have multiple level of redundancies when it comes to your code. First, Pro Edition customers have a live, stand-by SVN server that is ready to replace the existing master server if anything goes wrong. This process takes less than 10 minutes to minimize any down time. This is on top of RAID disks and other hardware level redundancies. Next, we snapshot your SVN repository every 10-15 minutes to a hot backup server. This is a different server than the live, stand-by SVN server. Third, on a daily basis, we take the SVN backup on the hot backup server and back that up to our cold backup servers. These servers are located in a completely separate data center. Therefore, even if a tornado hits our main data center and completely destroys our live server farm and hot backup server farm, you still have your data safe within the cold backup servers. Finally, we can push the daily backup to you and you can follow your own disaster recovery and compliance processes.

Coming Soon

Ticket Integration Enhancements

Many of you have voted to improve and enhance our ticket integration framework with Trac, Buguzilla, TeamForge, Jira … etc. You told us that you want to be able to update more status fields, handle more actions. We will be doing an iteration on this to enhance its capability.

Codesion Analytics

We have been diligently working on a new product that will bring intelligence and insight to your code and development process. I don’t want to talk too much about it yet because I like to show and wow rather than talk. As we continue to iterate and develop, I will be showing different aspects of it in future blogs.

Bugzilla Upgrade

Finally, we will be upgrading Bugzilla to 4.0.1. This is a big upgrade with new, enhanced UI for the 4.x version of Bugzilla. This process will begin in a few weeks and we will have proper process and notifications for existing customers using Bugzilla.

Subversion 1.6.15 upgrade

markbathie — Wed, 09 Feb 2011 21:18:07 -0800

In keeping up with the latest Subversion has to offer we have upgraded our SVN cluster to SVN 1.6.15. As a rule of thumb we generally like to wait a few months after a new release before upgrading our servers, unless the release contains critical security fixes. This release brings with it a bunch of bug fixes and improvements. SVN is designed to be backwards compatible, so no need to rush out and upgrade your client, but we always recommend upgrading when possible. Check out the release notes, and change log for more details.

Pivotal Tracker Integration now Live

copello0 — Thu, 16 Dec 2010 13:31:00 -0800

Here at Codesion, we provide source control and agile tools to individual developers, professional workgroups, to the Enterprise. Although many of our features are core to companies that are doing mission critical development, we have not forgotten about individual developers.

Many of you have told us that you are using Pivotal Tracker, a free, light-weight Agile management tool. Here are some of their key features:

Iceboxes - Create unordered tasks that you plan to work on in the future.
Backlog - Create ordered tasks that you plan to work on, but have not started yet. Backlog tasks can be easily shifted into the current milestone.
Current Tasks - Tasks that you are working on in the current iteration.

Based on your feedback, we have released our ticket integration framework to Pivotal Tracker. From your Subversion commit message, push commit information and update tasks to Pivotal Tracker.

Secure Shell (SSH) Deploy with Publisher

markbathie — Thu, 09 Dec 2010 11:45:00 -0800

You’ve been asking for it, and today we have responded by adding to Codesion Publisher (our deployment engine), the ability to configure a deployment target (remote host) with tunneled SSH password authentication. Previous to this you would need to configure an SSH key pair, and upload your SSH private key to us.

So if the host you’re deploying your code to supports tunneled SSH auth, you just need to enter your username and password, and your up and running. Happy deploying!

Codesion Upgrades to Subversion 1.6.13

copello0 — Thu, 11 Nov 2010 14:52:07 -0800

In keeping up with the latest releases of Subversion, we rolled out Subversion 1.6.13 on all our servers early this week. Please refer to the change log for more information.

Pre-Commit Web Hooks Now Available

copello0 — Mon, 25 Oct 2010 13:06:17 -0700

Many customers have expressed their requirement to perform certain actions prior to developers checking-in their code. For example:

Validate certain commit messages, such as a Trac or other ticket system ID
Validate that the files added follow a specific file naming convention

Based on these validations, we can setup rules to accept or reject these commits. We’ve now made this possible for all customers with pre-commit web hooks. Here’s how it works:

1) Log into your Codesion account and choose the “Services” tab, then “Subversion - Commit Hooks”

2) Select “Pre-Commit Web Hook” and enter your script URL, for example: https://yourserver.com/pre_commit_hook

this is the HTTP(s) URL that you want to send the commit information to

3) Select the Timeout between 5 seconds and 5 minutes

this determines how long we wait for a response from your HTTP script

4) Select the Default Action to deny or allow the commit

if we did not get a response from your script, in other words, it timed out, then the default action determines whether to deny or allow commit

5) Once a user performs a commit to the SVN repository, Codesion will send the commit information to your URL

6) The commit will either be denied or allowed based on your custom pre-commit script

Parallel ("Multi-node") Publishing Now Available

copello0 — Mon, 13 Sep 2010 10:21:30 -0700

Codesion Publisher now offers parallel publishing to multiple servers for Professional Edition plans.

You can now add additional hosts / servers as part of your SSH configuration:

When you publish, Codesion Publisher will, in parallel, publish your content to multiple servers at the same time. For Professional Edition plans, you can add up to a total of 5 servers for parallel publishing.

Click on the “+” button to add more servers. Clicking on “X” will remove the server from the list. We assume that all servers will be using the same SSH credentials, including the private key.