Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1466

Update appveyor.yml to use current in-progress build version

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.4.7
    • 2.4.8
    • process
    • None

    Description

      We need to update this for release so that when send out VF's, the proper nuget version is used. Note that 2.4.8.0 should always be reserved for the final GA release. I am not sure if this is possible, but would be awesome - even if requires manually updating appveyor.yml after every tag push.

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            That's what we have now, the version tag in appveyor.yml uses the format 2.4.8.{build} where AppVeyor appends it's own internal build number, eg the current build is 2.4.8.170. However, on tag builds we override the version to whatever the tag is, eg 2.4.8.

            To ensure unofficial nuget packages that go to MyGet represent the current version, we would need to update the appveyor.yml after each release. For example, the next likely release after 2.4.8 is 2.5.0 so would set the appveyor version to 2.5.0.{build}.

            mike.goldsmith Michael Goldsmith added a comment - That's what we have now, the version tag in appveyor.yml uses the format 2.4.8.{build} where AppVeyor appends it's own internal build number, eg the current build is 2.4.8.170. However, on tag builds we override the version to whatever the tag is, eg 2.4.8. To ensure unofficial nuget packages that go to MyGet represent the current version, we would need to update the appveyor.yml after each release. For example, the next likely release after 2.4.8 is 2.5.0 so would set the appveyor version to 2.5.0.{build}.
            jmorris Jeff Morris added a comment -

            Michael Goldsmith -

            Sorry, I was conflating appveyor and MyGet. That is actually what I am asking exactly, can we update the appveyor.yml after every release? Preferably as a trigger from the tag event? I am not sure this is possible, but if it is...we should do it!

            jmorris Jeff Morris added a comment - Michael Goldsmith - Sorry, I was conflating appveyor and MyGet. That is actually what I am asking exactly, can we update the appveyor.yml after every release? Preferably as a trigger from the tag event? I am not sure this is possible, but if it is...we should do it!

            I'm not sure we could / should automate this because we can't always be certain what the next release will be. For example: is the next next release 2.4.9 or 2.5.0 or 3.0.0. I think if we add updating the appveyor.yml to the scheduled next build number to our release process it should be fine.

            mike.goldsmith Michael Goldsmith added a comment - I'm not sure we could / should automate this because we can't always be certain what the next release will be. For example: is the next next release 2.4.9 or 2.5.0 or 3.0.0. I think if we add updating the appveyor.yml to the scheduled next build number to our release process it should be fine.
            jmorris Jeff Morris added a comment -

            Work was done in NCBC-1323 to support this.

            jmorris Jeff Morris added a comment - Work was done in  NCBC-1323 to support this.

            People

              jmorris Jeff Morris
              jmorris Jeff Morris
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty