Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1197

Add new branch workflow to IGB bitbucket pipelines

        Details

        • Story Points:
          2
        • Sprint:
          B - Summer 2018

          Description

          Edit bitbucket-pipelines.yml to enable building of branch-specific installers for testing. Change the installer name to include branch name in addition to version.

          See: https://confluence.atlassian.com/bitbucket/branch-workflows-856697482.html

            Attachments

              Issue Links

              relates to

              New Feature - A new feature of the product, which has yet to be developed. IGBF-1207 Investigate & document how run Dockerized IGB build environment under AWS for developing new pipeline configurations

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Hide
                Permalink
                spatil26 Sanket Patil (Inactive) added a comment -
                • $BITBUCKET_BRANCH variable is works only if used inside default pipeline configuration.
                • As per our discussion i am using $BITBUCKET_BRANCH variable inside default configuration instead of creating new custom configuration.
                • For branch name Bitbucket automatically replaces spaces with '-' . So, I think its safe to go with branch name for renaming installers.
                Show
                spatil26 Sanket Patil (Inactive) added a comment - $BITBUCKET_BRANCH variable is works only if used inside default pipeline configuration. As per our discussion i am using $BITBUCKET_BRANCH variable inside default configuration instead of creating new custom configuration. For branch name Bitbucket automatically replaces spaces with '-' . So, I think its safe to go with branch name for renaming installers.
                Hide
                Permalink
                spatil26 Sanket Patil (Inactive) added a comment - - edited

                Branch flow makes thing even more simpler.
                I have tested the pipeline configuration using branch flow. It is working as expected.
                I have added three branches under branches configuration

                • IGBF-* : for any topic branch, name starting with IGBF
                • master
                • release:
                  default configuration will be triggered whenever there is no branch found under branches configuration. I have remover custom configuration as it is no longer required.

                For default, topic branch and master branch, installers name will contain branch name. This was possible using $$BITBUCKET_BRANCH variable.

                Show
                spatil26 Sanket Patil (Inactive) added a comment - - edited Branch flow makes thing even more simpler. I have tested the pipeline configuration using branch flow. It is working as expected. I have added three branches under branches configuration IGBF-* : for any topic branch, name starting with IGBF master release: default configuration will be triggered whenever there is no branch found under branches configuration. I have remover custom configuration as it is no longer required. For default, topic branch and master branch, installers name will contain branch name. This was possible using $$BITBUCKET_BRANCH variable.

                  People

                  • Assignee:
                    spatil26 Sanket Patil (Inactive)
                    Reporter:
                    ann.loraine Ann Loraine
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    2 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: