Discrepency in Stage name pipeline vs Configuration Files

[Justinvolved]

Hi,

I have noticed when I create a Cofiguration Files, there are stages Integration, Testing, Production that can be associated.
When I create a Pipeline based on the Main/Release Branch template the second stage is named "Test" instead of "Testing", which gave me some trouble understanding why during deployment the configuration file could not be found :-)

Cheers,
Justin

[rhessinger]

Hi @Justinvolved,

We can definitely improve the error message when trying to deploy a config file when an instance is not found. Would you be able to share your OtterScript with us for how you are deploying the config files? Also, how do you have your deployment target configured (single server, group, environment, etc...) on your stage?

Thanks,
Rich

[Justinvolved]

Hi @rhessinger,

My point was actually that I think you might want to rename the second stage in the template for the "Main/Release Branch Pipeline" so this also is "Testing" That way ootb both already match up.
The error message was actually pretty ok, but since I used all defaults I was suprised about the naming difference.

Justin

[atripp]

Hi @Justinvolved ,

Ah, thanks for clarifying that! Yes... they should be Testing to follow everything else. Pipeline templates are a brand-new feature :)

This was a trivial change, and will be updated in next version as BM-3805

Cheers,
Alana