• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Should be able to trigger builds via Stash. We could do something smart here and be branch aware.

      The way I believe this should work

      1. Uses Application Links between Stash and Bamboo
      2. When a commit is made, it posts the commit and some repository metadata to the Bamboo server
      3. Custom endpoint on the Bamboo side that does a database query to figure out what plans use the repository posted to it
      4. Runs change detection for the plans that match

            [BAM-11459] Stash should be able to trigger builds

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3015443 ] New: JAC Suggestion Workflow 3 [ 3601717 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2702012 ] New: JAC Suggestion Workflow [ 3015443 ]
            Owen made changes -
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1420198 ] New: Confluence Workflow - Public Facing v4 [ 2702012 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 610370 ] New: Bamboo Workflow 2016 v1 [ 1420198 ]
            Sten Pittet (Inactive) made changes -
            Remote Link New: This issue links to "BDEV-6968 (Atlassian JIRA Extranet - Special Projects)" [ 86975 ]

            I see Stash 3.1 was release today but I don't see this mentioned in the changelog.
            Also is there an ETA on when this will be released for bamboo?
            We are waiting for this feature before we complete our trial of bamboo.

            Kyle Nicholls added a comment - I see Stash 3.1 was release today but I don't see this mentioned in the changelog. Also is there an ETA on when this will be released for bamboo? We are waiting for this feature before we complete our trial of bamboo.

            Well, that is good to hear.

            I'll actually be in Australia (Brisbane) the next week and a half, traveling there starting tomorrow. (I live in Germany.) I'll not be able to be online for a Skype meeting during the day though. I have to work in my real Job, which doesn't have anything to do with Atlassian products. These concerns come from my "hobby business". We can have a meeting in the evening (after 6 p.m.) though. Can I send you my Skype handle via email?

            Scott

            Scott Molinari added a comment - Well, that is good to hear. I'll actually be in Australia (Brisbane) the next week and a half, traveling there starting tomorrow. (I live in Germany.) I'll not be able to be online for a Skype meeting during the day though. I have to work in my real Job, which doesn't have anything to do with Atlassian products. These concerns come from my "hobby business". We can have a meeting in the evening (after 6 p.m.) though. Can I send you my Skype handle via email? Scott

            The different components, Jira, Confluence, Stash, Bamboo (the ones I work with), even though the UI's are fairly standardized, they still have idiosyncrasies, which make them feel very much "unalike", for a lack of a better word.

            Thats because we started off very much as different products. The way we view things today is as one experience and its going to take time for us to moved the products in that direction. Its a lot of work but we will eventually get there. That includes the few of the issues you've flagged such as UI discrepancies, Application Links and the directory management experience.

            But for sure, it seems like between the applications/ components, there is still a "throw it over the wall to the other side (another component/ application) and hope it sticks" kind of connectivity/ feeling and that needs deep thought and change, before I can say I really love Atlassian's products.

            Absolutely! We've got a team formed here in the Developer Tools group called Fusion thats working hard on this exact problem. Could we organise a time to meet on Skype to collect your thoughts in more detail? cc mcook

            James Dumay added a comment - The different components, Jira, Confluence, Stash, Bamboo (the ones I work with), even though the UI's are fairly standardized, they still have idiosyncrasies, which make them feel very much "unalike", for a lack of a better word. Thats because we started off very much as different products. The way we view things today is as one experience and its going to take time for us to moved the products in that direction. Its a lot of work but we will eventually get there. That includes the few of the issues you've flagged such as UI discrepancies, Application Links and the directory management experience. But for sure, it seems like between the applications/ components, there is still a "throw it over the wall to the other side (another component/ application) and hope it sticks" kind of connectivity/ feeling and that needs deep thought and change, before I can say I really love Atlassian's products. Absolutely! We've got a team formed here in the Developer Tools group called Fusion thats working hard on this exact problem. Could we organise a time to meet on Skype to collect your thoughts in more detail? cc mcook

            Not different really. It's just asking for even more fidelity in the communication between Stash and Bamboo, so that actions triggered in Bamboo can be very specific.

            I realise Atlassian has made a very component based system and not all components started out at the same time with the same engineers and same thinking/ concepts and one realizes this, when one uses them in depth (for instance the differing depths of look and feel point and click customization). The different components, Jira, Confluence, Stash, Bamboo (the ones I work with), even though the UI's are fairly standardized, they still have idiosyncrasies, which make them feel very much "unalike", for a lack of a better word. Atlassian needs to really concentrate on this overall issue. This improvement is just one small example. To me, the components are still much too segregated. When I worked with the user directory between the components for instance, I was never certain what the heck was going on. Why do I have to even choose or work with this stuff? (and I've locked myself out of Stash because of it!!!) Or making "application links". Why do I need this? I have the components/ applications, from Atlassian, they should just.....link up themselves. Leave me out of it please! Sorry, getting ranty.... I apologize.:-D

            But for sure, it seems like between the applications/ components, there is still a "throw it over the wall to the other side (another component/ application) and hope it sticks" kind of connectivity/ feeling and that needs deep thought and change, before I can say I really love Atlassian's products.

            Sorry again for going off on a tangent and slight rant, but the above feeling is always in the back of my head, when I work with the software.

            I am glad this suggestion got attention. There is still a lot more work to do in the exact same direction.

            Scott

            Scott Molinari added a comment - Not different really. It's just asking for even more fidelity in the communication between Stash and Bamboo, so that actions triggered in Bamboo can be very specific. I realise Atlassian has made a very component based system and not all components started out at the same time with the same engineers and same thinking/ concepts and one realizes this, when one uses them in depth (for instance the differing depths of look and feel point and click customization). The different components, Jira, Confluence, Stash, Bamboo (the ones I work with), even though the UI's are fairly standardized, they still have idiosyncrasies, which make them feel very much "unalike", for a lack of a better word. Atlassian needs to really concentrate on this overall issue. This improvement is just one small example. To me, the components are still much too segregated. When I worked with the user directory between the components for instance, I was never certain what the heck was going on. Why do I have to even choose or work with this stuff? (and I've locked myself out of Stash because of it!!!) Or making "application links". Why do I need this? I have the components/ applications, from Atlassian, they should just.....link up themselves. Leave me out of it please! Sorry, getting ranty.... I apologize.:-D But for sure, it seems like between the applications/ components, there is still a "throw it over the wall to the other side (another component/ application) and hope it sticks" kind of connectivity/ feeling and that needs deep thought and change, before I can say I really love Atlassian's products. Sorry again for going off on a tangent and slight rant, but the above feeling is always in the back of my head, when I work with the software. I am glad this suggestion got attention. There is still a lot more work to do in the exact same direction. Scott

              Unassigned Unassigned
              jdumay James Dumay
              Votes:
              37 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: