We have a production JIRA server running on an old CentOS 5 box that needs to be upgraded or better yet trashed and renewed. Anyway, we also have a JIRA license that our local Atlassian support experts keep telling us to get renewed or it will prevent us from upgrading to JIRA v7.
Now, the version of JIRA we want to upgrade to is 7.1.4, which came out before our license expired last August. And the Atlassian License FAQ seems to say it's a perpetual license, not one that will expire and prevent us from using the app.
I read somewhere in the atlassian documentation that the JIRA v7 upgrades requires a valid support license - that it won't upgrade at all if the current product license is expired. But everywhere else the license documentation seems to say that if the version I'm are upgrading to was released while my license is valid then I should be able to upgrade to it.
Before I dive into the server (well...the test instance of that server) and start changing things I thought I'd ask around a bit to see.
From experience: you need a valid license if you want to upgrade your JIRA instance.
The JIRA upgrade guide also mentions this as one of the first things to check before you start your upgrade:
Check your license - Verify that your license support period is still valid.
You should always be able to run a version that was released before your maintenance expired. Whether some automatic updater will install it for you is another question. You can always install 7.1.4 without a license, and then add your license to it.
Related
I am trying to Upgrade my free trial Azure DevOps to a licensed version but i don't see any options to apply my licenses.
Is there a way to apply our new licenses without having to re-install?
In earlier versions, TFS included code which required a valid product key to be present in order for the server to start up.
Since TFS 2015.2, TFS no longer distinguish the versions in this way, so there is no product key left on the TFS Admin console Product Information Summary page to display. And the TfsConfig License command is not available since TFS 2015.2.
If your TFS is in a Trial, it will not stop work immediately. If your trial expires, you will see a banner in most pages of the TFS Web UI. You would have enough time to complete trial.After you get the trial expiration warning message, you could select the 'complete the trial of my TFS Deployment'. There does not have a field to let you input the TFS Key.
What's more, when the trial is completed, all users should be assigned an appropriate access level based on the licenses they have. An unlimited number of users who only need access to work items can be added as Stakeholders and will not require any license. Most other users who access your server will require a license.
To use later TFS version, need to buy monthly access. You could find more information in this link:https://www.visualstudio.com/en-us/docs/setup-admin/buy-access-tfs-test-hub
You can refer to this blog and these cases(#1,#2).
I am attempting to get TeamFoundation Server up and running and wanted to get it licensed before letting the programmers loose on it.
However, there does not seem to be a place to enter in my license key in the software. On their site, it states that it should be done in the Team Foundation Server Administration Console and that I should be looking for the 'License Type' and 'Product ID' sections, but I do not have these on my server.
Where do I plug in the license key, if I don't have those options?
On this post, it shows how it is supposed to look like - How to get current TFS license type?
Since TFS 2015.2, it no longer requires you to have a valid product key to be present.
Everyone can install TFS and it now depends on the user licenses. A team of up to 5 is free and thereafter you have to follow Microsofts licensing terms by buying monthly access to each member.
You can find more at this link: https://learn.microsoft.com/da-dk/azure/devops/organizations/billing/buy-access-tfs-test-hub?view=tfs-2018&viewFallbackFrom=vsts
I'm planning to upgrade TFS from 2013 to 2015. In case something goes wrong during the upgrade installation, I'll rollback and revert every thing to its original state (TFS 2013). I'm performing the upgrade on the same server, which means that if the upgrade is successful, TFS 2015 will override 2013.
Is there an article to follow in case of rollback? Preferably an official article from Microsoft.
Just as jessehouwing's answer above, you can follow the restore procedure, but if your setup includes Sharepoint, Report Server and one or more build servers you may need to revert those too, that would be a very tedious and complex job.
Another way is that you can make a system image to back up you environment first,then restore it in case something goes wrong during the upgrade installation. Please see Back up and restore your PC for details,or use any other backup tools.
You're basically looking at the Restore procedure outlined here:
https://www.visualstudio.com/en-us/docs/setup-admin/tfs/admin/backup/restore-data-same-location
But before you restore you need to uninstall TFS 2015 and reinstall TFS 2013 and its latest update packs.
If your setup includes SharePoint, Report Server and one or more build servers you may need to revert those too. As far as I know there is no definitive rollback documentation. The recommendation is to do a trial upgrade on a second environment, resolve any issues you may find and then perform the final upgrade.
The product page for Zephyr for JIRA used to say it was compatible with JIRA 6.3.10, so since it and all our other add-ons were compatible, we upgraded to 6.3.10 Tuesday. On Wednesday I was getting a Zephyr startup error so I opened an Ops ticket to look at the problem. Today the add-on manager tells me the version incompatible and the product page today says Zephyr is compatible through 6.3.9.
I opened up a case with Zephyr, but if they do not have an update soon, can I downgrade JIRA from 6.3.10 to 6.3.9 so I can get my QA team working again?
I did consider rolling back and upgrading to 6.3.9, but I'd lose two days worth of data and we've had code checked in; that would be an audit nightmare.
I wouldn't downgrade JIRA. I would unpack Zephyr and modify the versions supported by that and repack.
I suprised that 6.3.9 to 6.3.10 broke Zephyr, so I'd dig deeper into the actual error.
Test it all in staging of course
this article may be of use to you: https://confluence.atlassian.com/display/AGILE/JIRA+Agile+6.3.9+Release+Notes
We implemented a custom check in policy, and selected it for one of our TFS project.
If a TFS client does not have the policy installed, TFS will show an error message with the installation instructions. This is all good.
However we have a problem when there is a new version of the check in policy.
It seems like TFS only enforces the policy name and not its version.
So even if I remove the old policy reference and add the new, all clients who already has the old version installed are still allowed to use it.
I would have expect that TFS would not allow to use the old version of the check in policy.
How could we enforce this?
One possible workaround could be to checkin the latest version number as a file to a project which can be accessed by anyone. The check in policy itself would read that file, compare the version with it's own version and generate a PolicyFailure if the version does not match.
Maybe there is an easier/better way?
Finally I decided to use the workaround originally suggested:
"One possible workaround could be to checkin the latest version number as a file to a project which can be accessed by anyone. The check in policy itself would read that file, compare the version with it's own version and generate a PolicyFailure if the version does not match."
Works well.
You could add policy version number to the end of policy name and introduce the updated version as a new policy.
This solution comes with a little management overhead but makes sure the you get the error with every new policy version.