Home → Questions →

Branch specific version

• Edit

oliver

05 Jul, 2018 06:59 AM

I would like to use

version: 1.0.{build}-{branch}

in all branches except for master, where I want it to be

version: 1.0.{build}

is this possible?

1. Support Staff 1 Posted by Owen McDonnell on 05 Jul, 2018 03:01 PM

   

   Sure. It's documented here
   I think something like this should work...
   

   version: 1.0.{build}-{branch}
   ...
   for:
   - 
     branches:
       only:
         - master
     version: 1.0.{build}
   

   • Edit

2. 2 Posted by oliver on 06 Jul, 2018 08:31 AM

   

   That is perfect. Thank you Owen.

   Just one more thing, as it is related:
   does do_not_increment_build_number: true work with this as well?

   • Edit

3. Support Staff 3 Posted by Owen McDonnell on 06 Jul, 2018 05:43 PM

   

   Yes, that should work.

   • Edit

4. 4 Posted by oliver on 09 Jul, 2018 01:27 PM

   

   I have this config:

     version: 0.1.{build}
   
     environment:
         PSGalleryAPIKey:
             secure: xxxxx
         access_token:
             secure: xxxxx
         matrix:
             - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017
             # waiting on https://github.com/RamblingCookieMonster/BuildHelpers/pull/60
             # - APPVEYOR_BUILD_WORKER_IMAGE: WMF 4
             - APPVEYOR_BUILD_WORKER_IMAGE: Ubuntu
               PowershellVersion: "6.0.0"
             - APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017
               PowershellVersion: "6.0.0"
   
     # Fail the Build with the first Job that failes
     matrix:
         fast_finish: true
     # Don't rebuild when a release is tagged on GitHub
     skip_tags: true
     # Do not increase AppVeyor's build number
     do_not_increment_build_number: true
     # Logic for skipping CI is in the build script
   
     for:
     -
         branches:
             only:
                 - master
         do_not_increment_build_number: false
   
     init:
         - ps: |
             if (-not ($env:PowershellVersion)) {$env:PowershellVersion = "5.1"}
             if (([version]$env:PowershellVersion).Major -ge 6) {$env:posh = "pwsh"} else {$env:posh = "powershell"}
             Add-Content (Join-Path $Home ".git-credentials") "https://$($env:access_token):x-oauth-basic@github.com`n"
         - git config --global credential.helper "store --file ~/.git-credentials"
         - git config --global user.email "[email blocked]"
         - git config --global user.name "AtlassianPS automation"
   
     install:
         - ps: '& $env:posh -File "./Tools/setup.ps1"'
   
     build_script:
         - ps: '& $env:posh -Command "Invoke-Build"'
   
     # on_failure:
         # - ps: $blockRdp = $true; iex ((new-object net.webclient).DownloadString('https://raw.githubusercontent.com/appveyor/ci/master/scripts/enable-rdp.ps1'))
   

   I get the following error

   Error parsing appveyor.yml: Invalid setting or section: do_not_increment_build_number (Line: 29, Column: 5) on line

     do_not_increment_build_number: true
   

   and if I comment that out, I get the same error on:

     for:
     -
         branches:
             only:
                 - master
         do_not_increment_build_number: false
   

   • Edit

5. Support Staff 5 Posted by Owen McDonnell on 09 Jul, 2018 04:05 PM

   

   Try putting do_not_increment_build_number: inside a pull_requests: key, like this,

   for:
   - 
     branches:
       only: 
        - master
     pull_requests:
       do_not_increment_build_number: true
   

   • Edit

6. 6 Posted by oliver on 09 Jul, 2018 04:55 PM

   

   Thank you, Owen - that works. But is not what I am trying to do.

   This will only have Pull Request to have a random hash appended to the version, so that the build number is not increased.
   I want all commits of all branches to behave like that. With the exception of the master branch - master should increase the build number

   • Edit

7. 7 Posted by Ilya Finkelshte... on 09 Jul, 2018 09:49 PM

   

   We created this workaround for you. It is a kind of hack but should work.

   • Edit

8. 8 Posted by oliver on 10 Jul, 2018 07:34 AM

   

   I really appreciate this, Owen & Ilya.
   I will use that.

   Is this something AppVeyor would like to support as a feature?
   Should I create a github issue asking for this feature (as a non-workaround)?

   • Edit

9. 9 Posted by Ilya Finkelshte... on 10 Jul, 2018 07:58 PM

   

   Sure, feel free to add GitHub issue. However we need to see how many people will vote for it.

   Alternative solution by the way: use separate AppVeyor project for master and separate for other branches.

   • Edit

10. 10 Posted by oliver on 10 Jul, 2018 08:17 PM

    

    oh! I like this better. Thanks!

    • Edit

11. oliver closed this discussion on 10 Jul, 2018 08:17 PM.

12. oliver re-opened this discussion on 05 Aug, 2018 08:19 PM

13. 11 Posted by oliver on 05 Aug, 2018 08:26 PM

    

    Hey, Ilya...
    This setup didn't quite work out as I hoped.
    I would appreciate it, if you could take a look and point out where my mistake is.

    location of appveyor.yml: <projectroot>/Tools/appveyor.yml
    config in the UI: screenshot: vivaldi_2018-08-05_22-21-29.png

    config in the UI for the branches:
    AppVeyor project AtlassianPS.Configuration: vivaldi_2018-08-05_22-22-52.png
    AppVeyor project AtlassianPS.Configuration@next: vivaldi_2018-08-05_22-23-34.png

    and this commit triggered both to run the CI:
    * https://ci.appveyor.com/project/AtlassianPS/atlassianps-configurati... * https://ci.appveyor.com/project/AtlassianPS/atlassianps-configurati...

    • vivaldi_2018-08-05_22-21-29.png 2.41 KB
    • vivaldi_2018-08-05_22-22-52.png 2.38 KB
    • vivaldi_2018-08-05_22-23-34.png 2.46 KB
    • Edit

14. Support Staff 12 Posted by Owen McDonnell on 06 Aug, 2018 04:21 AM

    

    The screenshots you have for different branches UI config are not settings that are shared between UI and yaml file configuration. You can see that list here.

    Rather, you should have
    

    branches:
      only:
        - master
    

    or
    

    branches: 
      except:
        - master
    

    in your config file.
    • Edit

15. 13 Posted by oliver on 06 Aug, 2018 06:44 AM

    

    So I would have to have 2 different appveyor.yml files with exactly the same content except for the branches: block?

    • Edit

16. Support Staff 14 Posted by Owen McDonnell on 06 Aug, 2018 04:27 PM

    

    Yes, and each project pointing to a different config file (or let one of the projects use 'default' config file and location).

    • Edit

17. 15 Posted by oliver on 06 Aug, 2018 04:31 PM

    

    great! thanks

    • Edit

18. oliver closed this discussion on 06 Aug, 2018 04:31 PM.

19. oliver re-opened this discussion on 06 Aug, 2018 04:31 PM

20. oliver closed this discussion on 06 Aug, 2018 04:31 PM.