Home → Questions →

Build Pipeline - Are there any Steps executed once for build matrix?

• Edit

matt_mckinstry

19 Mar, 2018 10:50 AM

I have a Build Matrix which produces 4 build jobs

Configuration
- Release
- ReleaseBlah
Platform
- x86
- x64

Are there any steps within the Build Pipeline that are executed only once for all of the jobs?

The reason I ask is that we would like to patch our AssemblyInfo.cs and push this back to our git repo. We would also like to Tag our build too. Obviously we would only want this to happen once per build regardless of how many build jobs there are.

The plan for our versioning scheme for branches is:
Master & Develop -> 1.2.3.0, 1.2.4.0, 1.2.5.0 (We need to increment this based on existing value from git)
Fix/ABC -> 1.2.4.{version}, 1.2.4.{version}
Feature/XYZ -> 1.2.5.{version}, 1.2.5.{version}

We may be able to munge something together using APPVEYOR_JOB_NUMBER -eq 1, however we could get into a bit of bother if we eventually move to the $99 subscription with 2 concurrent jobs

1. 1 Posted by Ilya Finkelshte... on 19 Mar, 2018 09:11 PM

   

   How urgently you need it? I am asking because we recently decided to extend this issue to any environment variable and matrix dimension, not only image.

   We desperately need this with challenges presented with heterogeneous Windows/Linux builds we meet now, so it should be done in a few weeks.

   If you are in rush, then yes APPVEYOR_JOB_NUMBER or APPVEYOR_JOB_NAME environment variables plus some custom scripting as a way to go.

   • Edit

2. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:27 AM.