Skip to content

mdanylyuk/tfs4jira

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

61 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

README

This document is a howto for running the TFS4JIRA Synchronizer as an Azure Web App. We prepared this deployment option for those, who doesn't want to host the Stynchronizer using their own infrastructure, but are OK with running it, by themselves, as a cloud app.

The fastest way - for a quick, 1h eval###

Prerequisites

You have to have a basic git skills.

How To

Now go to your web app site and log in.

The default user/pass is Alice/contoso!

The production ready way

prerequisites

  • Microsoft Azure account with active subscription.
  • Access to Azure portal.
  • Knowledge what the Azure web app is.
  • Ability and willingnes to handle the Synchronizer installed as a Microsoft Web App - We, at Spartez, will fully support you with the Synchronizer, but the Azure part is entirely on you.

How To

Preparing the instance:

  • Go to the Azure portal and sign in.
  • Go to "App Services"
  • Add a new service - choose "Web app" - published by Microsoft.
  • Click "Create"
  • Fill in the create form. Remember to chose "Windows" as the OS! Take note of your web app url.
  • Now wait till the service is deployed.

The bare instance is now ready, now you need to configure it for the Synchronizer:

  • Go to the freshly created service (App services >> name of your service).
  • Go to Deployment >> Deployment credentials and set the deployment username and password. Remember to save it.
  • Go to Deployment >> Deployment option and choose the "local Git Repository" as a Deployment Source.
  • Go to Settings >> Application settings and:
    • Disable PHP,
    • Set "Always On" to "On"
    • Save the changes.
  • Go to Settings >> Properties and take note of the "GIT URL". You will need it in the next step.

Installing the synchronizer: The steps below are to be executed on any machine with a git client installed.

  • Use git client and clone the repo - git clone WEB_APP_GIT_URL .
  • Go to the newly created repo.
  • Add a new remote - git remote add tfs4jira https://bitbucket.org/spartez-software/tfs4jira-azure-web-app.git
  • Download the synchronizer - git fetch tfs4jira and git reset --hard tfs4jira/master
  • Upload the synchronizer to Azure - git push origin master

Go to your web app site. You should see the Synchronizer login screen. One last thing: Change the default user/password!!!

How to change the user/password

  • Edit the App_Data/security/users.xml
  • Commit the changes and git push to the origin/master
    • git commit -a
    • git push origin master

How to update the synchronizer

  • Go to the directory, where your web app git repo is. (or just clone it again, see "Installing the synchronizer" above.)
  • git fetch tfs4jira - download the newest version
  • git rebase tfs4jira/master - to preserve user/pass changes
  • git push origin master --force

How to do a backup/restore

We recommend to use the Azure's site backup/restore.

  • Stop the application. Go to App services >> name of your service >> Overview and click "Stop"
  • Wait for your Synchronizer to stop. You can see this in the azure portal Activity Log.
  • Go to Settings >> Backups (if you have not configured it before, there will be a nice wizard to guide you trough it)
  • Click "Backup" to make a backup.
  • After it has succeeded go to Overview and start your Synchronizer.

If your backup ends up with "Partially Succeeded" - this means you forgot to stop the app or did not wait long enough for your synchronizer to stop.

restore

  • Go to App services >> name of your service >> Settings >> Backups
  • Click restore, choose the backup to restore from and click "Ok"
  • Wait for the app to restore itself - this might take some time.

If you are getting a "Error 403 - This web app is stopped." after a restore, go to the Overview and Stop and Start the app.

What Azure App Service Plan do I need

At the very minimum you need the B1 Basic plan - due to the "always on" feature, needed for the synchronization to run without pauses. However, we do recommend to use at least S1 Standard plan - due to the backup/restore feature.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published