I suggest you ...

Extend to a more complete continuous integration / deployment service

5 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

4 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Bas Bossink commented  ·   ·  Flag as inappropriate

    To elaborate a bit on my previous comment at our shop we are using Git Flow, and would typically like to have one build definition per repository. For each repository a build of the correct branch can be triggered by a BitBucket commit/push hook. In the future we might want to split the packages of the feature/* branches to a separate feed.

  • Bas Bossink commented  ·   ·  Flag as inappropriate

    Allow the build of different branches for a single 'Build definition' such that the web hook determines which branch will be built.

  • Anonymous commented  ·   ·  Flag as inappropriate

    build logs, build based on tags in source control, artifacts other than packages, run grunt or gulp (nodejs) tasks, publish to azure cloud services

Feedback and Knowledge Base