majcica.com Report : Visit Site

Technical data of the majcica.com

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host majcica.com. Currently, hosted in Germany and its service provider is Strato AG .

the related websites

lalafo.rs airbnb.co.uk tripadvisor.co.uk airbnb.com creditman.co.uk hobi-plus.forumsclub.com forum.klix.ba tripadvisor.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called Apache/2.4.33 (Unix) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

skip to content mummy's blog as mother made it – mario majčica's web log about mario majčica contact me living documentation and test reports in vsts/tfs pipelines introduction in order to truly get advantage from all of the hard work that we put into our tests, we need to present our test run results and share our specifications in more convenient and accessible way. on windows platform in order to make this tasks happen, we can leverage tools that you are probably already using, specflow itself and a sidekick project of it called pickles. if none of what i just said does make sense, you are reading the wrong post, so please check the specflow documentation and read about bdd. however, if you are already familiar with it, you are using specflow and are looking for a decent way to automate the above-mentioned tasks, please continue reading as i may have a valid solution to it. all of the implementations that i came across till now, involved scripts, msbuild tasks and a lot of other cumbersome solutions. i saw potential in vsts/tfs build/release pipeline that through some specific build/release tasks are a neat solution automating these requirements. let’s start. generating specflow reports in vsts generating a nice and easy to consult report over our your test runs is relatively easy. specflow nuget package already includes all of the necessary to do so, that is the specflow executable itself. in my demo case, i am using nunit 3, however other frameworks are also supported. let’s check first what are the necessary manual steps to get the desired report. after executing my tests with nunit console runner with the following parameters nunit3-console.exe --labels=all "--result=testresult.xml;format=nunit2" specflowdemo.dll i am ready to generate my report. now i just need to invoke the specflow executable with the following parameters specflow.exe nunitexecutionreport specflowdemo.csproj /xmltestresult:testresult.xml /out:myreport.html and voila, the report is generated and it looks like following details over the various parameters accepted by specflow executable can be found here, test execution report . now, how do we integrate this into our vsts build pipeline? first, we need to run our tests in order to get the necessary test results. these may vary based on the testing framework that we are using. two supported ones are nunit or mstest. be aware that if you run your mstest’s with vstest runner, the output trx file will not be compatible with the format generated by mstest runner and the report will not render correctly. for that to work, you’ll need a specific logger for your vstest runner. once the tests are completed we are going to use the specflow report generator task that is part of the homonymous extension that you can find here . after adding the specflow report generator task in your build definition, it will look similar to this. in case you are interested in how each parameter influences the end result, check the above-mentioned link pointing to the specflow documentation as the parameters are the same as on per tool invocation via the console. now that your report is ready you can process it further like making it part of the artifact or send it via email to someone. generating pickles living documentation support documentation based on your specifications can be generated by pickles in many ways, such us msbuild task that could be part of your project, powershell library or simply by invoking the pickles executable on the command line. in case of trying to automate this task, you will probably use the console application or ps cmdlets. let’s suppose the first case, then the command that we are looking for is like following pickles.exe --feature-directory=c:\dev\my-project\my-features --output-directory=c:\documentation --documentation-format=dhtml all of the available arguments are described here . as the result you will get all of the necessary files to render the following page: back to vsts. in order to replicate the same in your build definition, you can use the pickles documentation generator task. add the task to your definition and it should look like somewhere like this all of the parameters do match the ones offered by the console application. you are now left to choose how and where further to ship this additional material. conclusion in this post, i illustrated a way on how to get more out of the tooling that you are probably already using. once you automate these steps chance is that they are going to stay up to date and thus probably get to be actually used. all of the tasks i used can also be used in the vsts/tfs release pipeline. i hope it helps. leave a comment may 7, 2018 mario majcica no comments deploy ssis packages from tfs/vsts build/release automating bi projects, based on microsoft tooling, was always a bit painful. personally, all of the things shipped with ssdt seemed a bit unloved from a microsoft side. what i would like to show you in this post is how i managed to automate the build and deployment of my integration services projects (.dtproj type). we will build our project in order to get the necessary ispac files, upload this artifact in tfs and then deploy it via a tfs release. let’s start with the build. as you may already know, is projects are not based, as most of visual studio projects, on msbuild. this is the first difficulty everyone faces once they start setting a ci/cd pipeline for this type of projects. the only way to build it is to use devenv.com executable that is part of the visual studio installation. for that, you will need a custom build task or you’ll need to execute a script that will handle the necessary. in my case, i made a custom build task for it (which can be found here ) and thus my build definition looks like this: following are the steps of my build. first i will ‘compile’ the ssis project, then copy the ispac files that were generated to the build staging folder, again i’ll copy my ssis configuration file (more about the configuration file later) to the same location and at the end, i’ll upload all of the files in the staging folder to tfs as my build artifact. now that my artifact is ready, we can proceed with the deployment in the release. in order to deploy the ssis package, i’ll use my own build/release task called deploy ssis . the release steps will look like the following. as you can see i will start with replacing the placeholders in the configuration file. the configuration file contains some environment dependent values and in the first step, i’ll make sure that those are substituted with the correct values that are coming from the environment variables in the release. but what is this configuration file i already mentioned a couple of times? it is a file that my deploy task is capable of processing and it contains a list of ssis environments and variables. there are no other ways of supplying this information, considering that it is not part of the ispacs, and as it was a necessity for my automation to provide them, i came up with a schema from which my deployment task will pick those up, add them to my ssis instance and eventually make all of the necessary references. following is an example of the configuration file. xhtml <?xml version="1.0" encoding="utf-8" ?> <environments> <environment> <name>myenv</name> <description>my environments</description> <referenceonprojects> <project name="businessdatavault" /> <project name="configuration" /> </referenceonprojects> <variables> <variable> <name>clienttodropbox</name> <type>boolean</type> <value>1</value> <sensitive>false</sensitive> <description></description> </variable> <variable> <name>initialcatalog</name> <type>string</type> <value>dv</value> <sensitive>false</sensitive> <description>initial catalog</descri

URL analysis for majcica.com

http://blog.majcica.com/category/testing/
http://blog.majcica.com/category/intellij-idea/
http://blog.majcica.com/page/2/
https://www.addtoany.com/add_to/facebook?linkurl=http%3a%2f%2fblog.majcica.com%2f2018%2f05%2f07%2fliving-documentation-and-test-reports-in-vsts-tfs-pipelines%2f&linkname=living%20documentation%20and%20test%20reports%20in%20vsts%2ftfs%20pipelines
http://blog.majcica.com/#content
http://blog.majcica.com/2017/12/20/managing-vsts-tfs-release-definition-variables-from-powershell/
http://blog.majcica.com/category/net/asp-net/
http://blog.majcica.com/2018/04/02/provisioning-webdeploy-in-vsts-tfs-release-via-dsc-script/
https://www.addtoany.com/add_to/whatsapp?linkurl=http%3a%2f%2fblog.majcica.com%2f2018%2f05%2f07%2fliving-documentation-and-test-reports-in-vsts-tfs-pipelines%2f&linkname=living%20documentation%20and%20test%20reports%20in%20vsts%2ftfs%20pipelines
http://blog.majcica.com/category/windows-8/
http://blog.majcica.com/2018/04/25/deploy-ssis-packages-from-tfs-vsts-build-release/
http://blog.majcica.com/2018/04/25/deploy-ssis-packages-from-tfs-vsts-build-release/#respond
http://blog.majcica.com/2018/02/12/automate-settings-retain-indefinitely-flag-on-your-releases/
http://blog.majcica.com/2018/05/07/living-documentation-and-test-reports-in-vsts-tfs-pipelines/
http://blog.majcica.com/2017/07/19/using-xl-deploy-in-vststfs-buildrelease-pipelines/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: majcica.com
Registry Domain ID: 15957535
Registrar Whois Server: whois.cronon.net
Registrar URL: http://www.cronon.net
Updated Date: 2015-03-16T00:00:00Z
Creation Date: 2015-03-16T00:00:00Z
Registrar Registration Expiration Date: 2018-04-03T00:00:00Z
Registrar: Cronon AG
Registrar IANA ID: 141
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +49.303001460
Reseller:
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID:
Registrant Name: Mario Majcica
Registrant Organization:
Registrant Street: Viale Sarca 159
Registrant City: MILANO
Registrant State/Province:
Registrant Postal Code: 20126
Registrant Country: IT
Registrant Phone: +31.3280582336
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID:
Admin Name: Mario Majcica
Admin Organization:
Admin Street: Viale Sarca 159
Admin City: MILANO
Admin State/Province:
Admin Postal Code: 20126
Admin Country: IT
Admin Phone: +31.3280582336
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID:
Tech Name: Hostmaster Strato Rechenzentrum
Tech Organization:
Tech Street: Cronon AG Professional IT-Services
Tech Street: Emmy-Noether-Str. 10
Tech City: Karlsruhe
Tech State/Province:
Tech Postal Code: 76131
Tech Country: DE
Tech Phone: +49.72166320305
Tech Phone Ext:
Tech Fax: +49.72166320303
Tech Fax Ext:
Tech Email: [email protected]
Name Server: docks05.rzone.de
Name Server: shades19.rzone.de
DNSSEC:
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2017-06-27T19:48:00Z <<<
For more information on Whois status codes, please visit https://www.icann.org/epp


  REGISTRAR CRONON AG

  REFERRER http://www.cronon.net

SERVERS

  SERVER com.whois-servers.net

  ARGS domain =majcica.com

  PORT 43

  SERVER whois.cronon.net

  ARGS majcica.com

  PORT 43

  TYPE domain

DOMAIN

  NAME majcica.com

NSERVER

  DOCKS05.RZONE.DE 81.169.146.15

  SHADES19.RZONE.DE 85.214.0.249

STATUS
ok https://icann.org/epp#ok

  CHANGED 2017-04-04

  CREATED 2007-04-03

  EXPIRES 2018-04-03

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .