Our import is stuck at step 1 of 7 "Restoring your collection". Any suggestions?
As of 11/1/2017 it has been running for 70hrs
Related
We are currently using Jira Software Server (version 8.7.1) and have tried running our code in the Script Console on IntelliJ. But it seems to have a problem recognizing the imported classes although we made sure to specify the correct directory for it to import them.
These are the errors we get while running the scriptrunner code in IntelliJ
We are at loss here and we would really appreciate your help!
I want to create a new team project in TFS2018. The create fails with error TF400797. After some research I discovered when I choose Team Foundation Version Control the creation of a new project succeeds! So, the problem has to deal with Git as our source control provider. We use TFS as our Git Server.
The version of TFS we use is:
Microsoft Visual Studio Team Foundation Server
Version 16.131.27701.1
Is there a way to migrate JIRA issues to GitLab EE starter?
We have two projects each having 1 board on JIRA that I would like to migrate.
After emailing the GitLab team, this feature is in the Roadmap and is "scheduled for release in 3-6 months" as of June 15, 2017.
And 3 to 6 months later indeed, in April 2020, for GitLab 12.10:
(I mean, talk about "six to eight weeks"!)
Import Issues from Jira to GitLab
Until now, the only way to get Jira issues into GitLab was manually, with our CSV importer, or by hand-rolling your own migration utility.
GitLab 12.10 includes an MVC to automatically import your Jira issues into GitLab. This is the first of many planned enhancements to make transitioning from Jira to GitLab as frictionless as possible.
To get started, set up the Jira integration on your GitLab project, click the import icon at the top of your project’s Issue List, and select Import From Jira.
See documentation and Epic.
Note that, with GitLab 13.2 (July 2020), you now have:
Map Jira users to GitLab users when importing issues
When importing issues from Jira to GitLab, you can now map Jira users to GitLab project members prior to running the import.
This enables the importer to set the correct reporter and assignee on the issues you’re moving to GitLab.
See Documentation and Issue.
After emailing the GitLab team, this feature is in the Roadmap and is "scheduled for release in 3-6 months" as of June 15, 2017.
In the meantime, you can use the script that #M. Awais mentioned in the comments.
I am getting an exception when using OpsHub Visual Studio Migration Utility (Trial Version) when trying to Migrate from TFS to VSTS .
I have put in the key that was emailed to me in the second step. This error was received after the validation completion. Here is the StackTrace from OpsHub.log
(com.opshub.JSON.QuartzIntializationServlet) - Unexpected error ocurred during context initialization.
java.lang.NullPointerException
at com.opshub.license.install.LicenseInstaller.installLicense(LicenseInstaller.java:77)
at com.opshub.JSON.QuartzIntializationServlet.registerLicFile(QuartzIntializationServlet.java:369)
at com.opshub.JSON.QuartzIntializationServlet.installLicenses(QuartzIntializationServlet.java:345)
----------Few lines below was the following error------------
(com.opshub.eai.config.service.ConfigServiceImpl) - Trial license is not installed
com.opshub.license.exception.LicenseNotExistException: Trial license is not installed
at com.opshub.license.verify.LicenseVerifier.validateTrialLicense(LicenseVerifier.java:440)
at com.opshub.license.verify.LicenseVerifier.validateIntegrationTerms(LicenseVerifier.java:238)
at com.opshub.license.verify.LicenseVerifier.verify(LicenseVerifier.java:168)
Any help would be appreciated . TIA
I suggest that you can migrate TFS to VSTS through TFS Data Import Service for Visual Studio.
More information, you can refer to this blog: Import your TFS Database into Visual Studio Team Services and the tool and guide can be download from here: Team Foundation Server to Visual Studio Team Services Migration Guide and Database Import Tooling.
As mentioned in the comments , the newer version of OpsHub Visual Studio Migration Utility . Thank you.
I created a build job on Jenkins that is attached to a TFS server. I used Team Explorer Everywhere to facilitate this. The first time I ran the job, I got the following message:
Error: You must accept the End User License Agreement for this product.
Which is fine, I ran the tf eula command and accepted the EULA.
The problem is that I'm still getting the same error when running the job.
Here is the solution that I used to resolve the issue:
Set the Source Code Management to None
Add build step and choose Execute Windows batch command
type tf eula -accept in the command window
Run the build
Remove the above build step
Set Source Code Management back to Team Foundation Server and enter the details
Run the build again and it ran without error
Hope it helps
To date we've had to perform this a couple times now, and so we've created a project which performs the acceptance of the EULA.
In the Build section of this new project, we have an Execute Windows batch command step which is as follows:
"C:\Team Explorer Everywhere for Team Foundation Server\TEE-CLC-11.0.0.1306\TEE-CLC-11.0.0\tf.cmd" eula -accept
Obviously you might need to change your path accordingly.
Now when we encounter this problem, we 'build' that project and it accepts the EULA for us.
I had the same issue on Jenkins/TFS server.
I used:
tf eula -accept
On mac make sure when you add the full path and choose Execute shell script
not just
tf eula -accept
I created a simple seperate build with only one Build task
Execute shell
/Applications/TEE_CLC_14_0_1/tf eula -accept
Ran it
Then ran my larger build