Skip to:
Using build-info, what's the right value to use for a unique ID that will be common across all builds from the same gerrit changeid/patchset?
Don't wait for me - aka propose a way to do it.
Now waiting on to suggest the proper way to detect snapshot/release builds from `ci-management/jjb/common/ include-agl-source-aglsetup.sh`.
This same script is run from the Jenkins jobs for all builds (CI, release, snapshot)
reassigning to for the final touch Thanks!
cherry-picking on guppy done: please review topic build-info
OK, backport aglsetup.sh to guppy. Use KISS and intuitive names.
Stephane's proposal is good.
we might do snapshot-daily-<....> as we probably get to weekly snapshots as well .
Best,
Jan-Simon
Using build-info, what's the right value to use for a unique ID that will be common across all builds from the same gerrit changeid/patchset?