Addressing Configuration files in Build vs Release

[Justinvolved]

Hi,

I think I am misunderstanding something around build vs release and their relation to the Configuration Files.
I have an application with some configuration files, and a pipeline When I go through "Create New Build", with the pipeline selected, the deployment to test fails with:

I created a release based on the same build, and this is succesfully deployed including the configuration files:

Both are connected to the same release pipeline, but there must be a difference in the context and the way I can address variables maybe? In OtteScript I use $PipelineStageName to get the correct configuration file...

Thanks,

Justin

[atripp]

Hi @Justinvolved ,

That is definitely a bug in the Operation, as there shouldn't be a NullReference exception like that.

Just to confirm... in the first example, you created a build without a release? I.e. you just "directly" selected a pipeline? But then, it worked when you created a build in a release?

Cheers,
Alana

[Justinvolved]

Hi @atripp

Sorry for the delayed response.
Yes, so I created a build, and during the creation of the build you are asked to select a pipeline.

After that the build was successful, but deployment failed. So then I created a release, based on the same build #1, and that does succeed. Where the issue is in the build #1 case the nullreference occurs on the config files.

My overview now shows the deploy from the build failed, but in the release it succeeded:

I could setup buildmaster to be accesible by you, please let me know if that helps.

Justin

[atripp]

Thanks for clarifying @Justinvolved

I was able to reproduce this issue, looks like it was a regression with "releaseless builds". Easy fix... it'll be in the next maintenance release as BM-3808. The release is scheduled for this Friday :)

Cheers