tag:blogger.com,1999:blog-4930279255087763993.post4267872636562870545..comments2023-09-13T13:47:10.935+02:00Comments on { blog: 'Gøran Sveia Kvarv' }: Continuous Delivery with psake and TeamCity - Visualizing a pipelineGøran Sveia Kvarvhttp://www.blogger.com/profile/08537541145852324311noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-4930279255087763993.post-34456456656845194602012-10-09T09:01:23.413+02:002012-10-09T09:01:23.413+02:00Thank for your comments Eirik! I have been followi...Thank for your comments Eirik! I have been following that approach for a while now and should have written an update for this post. Your solution works much better!Gøran Sveia Kvarvhttps://www.blogger.com/profile/08537541145852324311noreply@blogger.comtag:blogger.com,1999:blog-4930279255087763993.post-47043384718433728902012-03-07T08:17:43.563+01:002012-03-07T08:17:43.563+01:00... as described here: http://stackoverflow.com/qu...... as described here: http://stackoverflow.com/questions/1367957/put-current-build-number-of-release-configuration-to-nightly-build-configuraAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4930279255087763993.post-17805486479728170472012-03-07T08:17:12.835+01:002012-03-07T08:17:12.835+01:00Nice work Gøran. Another way to get the build numb...Nice work Gøran. Another way to get the build number from the CI build is to use the variable %dep.btXX.system.build.number% variable. That way you don't have to put it in an artifact.Anonymousnoreply@blogger.com