You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When this was first introduced it was based off how AppVeyor does it in terms of project name, and it was a simple check to ensure that the CI build was happening on the intended project. This is not as simple in TeamCity, and we need to find a way to associate a TeamCity Build Configuration as being against the intended repository.
This will be done in a follow up issue, and this issue is simply about removing this check completely.
The text was updated successfully, but these errors were encountered:
This is currently not working as expected as it is based on how
AppVeyor worked, and needs to be ro-thought in terms of how TeamCity
and other providers work.
A follow up issue has been created to add this back into a future
release.
* release/0.3.0:
(#26) Ensure PrintVariables collection is used
(#24) Correctly assert branch name
(#22) Remove concept of IsMainRepsitory
(#25) Update dependencies of Package task
When this was first introduced it was based off how AppVeyor does it in terms of project name, and it was a simple check to ensure that the CI build was happening on the intended project. This is not as simple in TeamCity, and we need to find a way to associate a TeamCity Build Configuration as being against the intended repository.
This will be done in a follow up issue, and this issue is simply about removing this check completely.
The text was updated successfully, but these errors were encountered: