Access Run ID from task/step about agola HOT 2 CLOSED

@ksa-real can you provide an example of use about the variable you need to be added? (es. a run config)

At the moment to get a run from agola we don't need to have the run ID, but it is needed only the projectref and runnumber since the agola api is /projects/{projectref}/runs/{runnumber}
I think the new variable could be for es. AGOLA_RUN_NUMBER that is incremental.

from agola.

Say I want to store a build number in Android app every time I run the "master" or "release branch" build (1.2.3-18, where 1.2.3 is version and 18 is a build number). If the builds are made just in master branch this is not a big issue as I can store version and build number e.g. in commit tags and use the most recent build for reference. For release branches it is somewhat more complicated, especially if builds from the same repo can run in parallel. One solution is ensure master and all release branches use the same change group to check all available tags to pick the next available build number. Not sure if change groups are implemented and builds can really run in parallel at the moment.
E.g. TeamCity provides an environmental variable that can be used to identify current build number, auto-incremented and unique per run.

from agola.