Hi,
I was struglling with understand why a GO_TO_REVISION_FROM and a
GO_REVISION_TO of one material would always have the same value even with 1
commit and after some testing i realized that these variables don't
represent the revision that was deployed before and the new revision to be
deployed, they actually represent the first revision that was committed
post the current version and the last revision committed which is why if
there is only 1 commit, they have the same value.
I don't think this is clear in the documentation. Below is a paste of the
current documentation.
*GO_FROM_REVISION_${material name or dest}*
If you are using more than one material in your pipeline, the 'from'
revision for each material is available. The environment variable is named
with the material's "materialName" attribute. If "materialName" is not
defined, then "dest" directory is used. Non alphanumeric characters are
replaced with underscores ("_").
*GO_TO_REVISION_${material name or dest}*
If you are using more than one material in your pipeline, the 'to' revision
for each material is available. The environment variable is named with the
material's "materialName" attribute. If "materialName" is not defined, then
"dest" directory is used. Non alphanumeric characters are replaced with
underscores ("_").
I believe this is important because perhaps the FROM variable could be used
to define which version should be the target for a rollback but having
this, it should be the FROM-1.
Also, and perhaps this was a change later in time, these variables are also
available even when only using 1 material.
I'm using version 18.1
Perhaps the documentation should be updated.
Regards
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
