#Teamcity rest api code#
I’m not going to minify my code or use to crazy new-fangled pseudo-cosmic CSS. It’s not about NPM or Bower or any of that nonsense. This article is about AngularJS and it’s about TeamCity. You might want to be a little more selective on who you allow to access the server this way - I guess it depends on how secure your network is, how many clients access the dashboard and so on.
#Teamcity rest api windows#
Since my TeamCity server is running on a Windows box, I created the new file here:Ĭ:\ProgramData\JetBrains\TeamCity\config\internal.properties Weirdly, if the file doesn’t exist, there is no option to edit, so you have to go and create the file. From there you should be able to edit, or at least get the location of the internal.properties file. This is all because of a really logical thing called “Cross Origin Resource Sharing”, which you can enable pretty easily in TeamCity as long as you have admin permissions.Ĭheck out Administration -> Server Administration -> Diagnostics -> Internal Properties. You can’t hit a server from a web page unless that server is the server that served the web page you’re hitting the server with… unless of course you tell the server you want to hit that the web page you want to hit it with, served from a different server, is allowed to hit it. With that in mind, let’s get into the weeds and see how this thing works… Enable cross-site scripting (CORS) on your Team City server Likewise, though TeamCity is doubtless the best enterprise CI platform on planet earth, the REST APIs are pretty painful to consume. I found javascript to be a hateful language, filled with boilerplate and confusion. There is no sunshine and there are no rainbows in this article. I decided to do an old radiators are coded in WPF, which looks awesome on the big TVs dotted around the office, but doesn’t translate well for remote workers. I still contend that JavaScript isn’t a real language (give me Scala or C# any day of the week) but you can’t ignore the fact that this is how user interfaces are developed these days… so, yeah, I started with a tutorial on YouTube. I’d last done JavaScript several years ago and never really used it as a real language. Put that in your e-pipe and vape it, designer-bearded UX developers!Īnyway, when I started, I knew nothing about SPA development. They may be different technologies from different eras: one may be the last hurrah of bloated fat-client development and the other may be the latest and greatest addition to the achingly-cool, tie dyed hemp tool belt of the Single Page App hipster, but under the hood they’re very very similar. Yeah, that’s right, I just said WPF while talking about Javascript development. So, this isn’t supposed to be the ultimate guide to AngularJS or anything like that - I’m not even using the latest version - this is just some notes on my return to The World of the View Model after a couple of years away from WPF. Quick TeamCity Build Status with AngularJS ←home Quick TeamCity Build Status with AngularJS
0 kommentar(er)
