SharePoint 2013 Content Deployment Job best practices and Concepts

When you are working in a SharePoint world and there is team with you working on any site like developer tester and designer then – there is no chance for anyone to work directly on production server.

When you have installed SharePoint there – you will have to setup UAT server, development server, production server and probably you can install staging server in order to streamline entire life cycle of SharePoint activities, if you are working on SharePoint production server and editing site or designing some SharePoint site directly from production so you will end up with the smoke if any error occurs then your site which is hosted on SharePoint will go down. So how anyone can be safe from this disaster.

So there is concept of content deployment has been introduced in earlier version of SharePoint and now people have clear visibility about as to why they should setup all other server in SharePoint farm if really want to take advantage of content deployment job with SharePoint 2013.

There are different ways to configure content deployment job in SharePoint 2013– from CA SharePoint you can browse content deployment path option do tweak there. You can check from there how many objects has been exported and imported.  Actually you setup SharePoint 2013 content deployment job by 

specifying from where content will move – so in ideal scenario it would be from one site collection on UAT server to another site collection in production server.

If you are ok with scripts then you can write scripts for exporting object to production site collection.

SharePoint 2013 content deployment job failed:

If you have this status all the time with your job – and you don’t know the reason so you need to browse the log area of content deployment job – just click on that log file and open it.

SharePoint Content Deployment job best practices and concepts

Reaching SharePoint 2013 Content deployment Failed Job status:

If you want to check the status of content deployment fail job and see status and log area so follow the key sequence below mentioned as >>

Key Sequence for content deployment failed status log:

SharePoint Central Admin>> General Application Settings>> Configure Content Deployment Job>> check your job name there and click Failed >> and then browse the path mentioned for log there.

Google Code Service is being discarded

If you have been working with Google code project where your project was being collaborated so you have to be careful because now Google code service is being discarded by Google – as Google said it was becoming more abusive or spam by people once they upload the projects there so it was very difficult to manage it from Google.
Entire community has been using Google code service now if you need to migrate your  project from Google code to somewhere else so you can collaborate on it-There are few other services for such kind of activity are there that includes github, bitbucket and source forge and another service which is Google code importer service by Google itself.
Google code importer service is taking too much time to import your code from Google code to somewhere else as mentioned above.
If your site is linking some code hosted on Google code service so you need to migrate that code using one of services mentioned on Google code -so you can easily migrate that code somewhere else easily.

Google Code service is being discarded how to move project:

Easiest way to migrate your code is – instead of using export service which is http://code.google.com/export-to-github/ and move your code to github. But if it’s taking time so you can easily create your account in github and login and create repository there – simply by creating a link after verifying email from github and then you are done.

Now you need to import your code from Google code service to github so finally we have moved or imported our code from google code service by creating account in github and by using import option from github instead of using export service from Google code service.

Test case moved our code from Google Code Service to Github:

Our code was hosted at google code for blogger navigation which was moved  newly hosted or imported code at github and  url was
https://github.com/sqlservermanagementstudio/bloggernavigation/blob/master/blogger-page-navi.v1.js
So if you or someone is using that source code and referring that URL at Google code service so change it to newly created URL that contains code at github with the URL mentioned above for blogger navigation from Google code to github.

You will  be able migrate issues, wikis and all other stuff along with your project which was there at Google code service but only number of times download type of metadata might be missing like we were unable to find how many times users has downloaded code etc which was 100 k times at Google code service.
Otherwise rest of the wiki or issues were migrated from Google code service to github.
If you are facing issues please comment we will reply.