Project
TeamCity
Priority
Normal
Type
Feature
State
Open
Assignee
Pavel Sher
Subsystem
Server
Affected versions
No Affected versions
Fix versions
Medium Priority Pool
Fixed in build
No Fixed in build
Fixed in builds
no build yet
  • Created by   Yegor Yarko
    2 years ago (25 Sep 2009 16:04)
  • Updated by   Yegor Yarko
    2 weeks ago (09 May 2012 21:03)
 
TW-9578 Ability to trigger a build on last pinned build change
7
Issue is visible to: All Users
  The issue is visible to the selected user group only
Use case:
  • My build depends on last pinned build of another build configuration. I'd like to trigger my build whenever that pinned build changes (that is a newer build is pinned or the last pinned is unpinned). Currently this is only possible if the build is build by schedule and may produce many unnecessary builds.
Comments (4)
 
History
  
Linked Issues (?)
 
Yegor Yarko
  Yegor Yarko
25 Sep 2009 16:06
2 years ago
A further improvement of the feature may be not only processing pinned build, but specific build number and last finished/successful as well.
Related Changes
relates to
TW-5468: Allow to artifact-depend on last build with a given tag
Yegor Yarko
  Yegor Yarko
09 Apr 2010 11:22
2 years ago
This issue is much like TW-11553, but can have separate value when there is no artifact dependency on the build.
e.g. see http://www.jetbrains.net/devnet/message/5260396#5260396 - there can be no artifact dependency because the artifacts are transferred without TeamCity help.
Related Changes
Priority
Normal→ Minor
Michael Kuzmin
  Michael Kuzmin
10 Aug 2011 16:19
9 months ago
Yegor Yarko
  Yegor Yarko
08 May 2012 23:23
2 weeks ago
A current workaround might be to use URL trigger plugin and set it to monitor REST API URL like
http://localhost/app/rest/builds/buildType:(id:btXXX),pinned:true/id