Setting the context version in deb package post build

[Stickyeyes]

We currently have a build process in Bamboo that checks out our source code from the master branch in stash on commit and then builds a debian DEB package ready for deployment. Our deployment proces then pushes this DEB package to AWS S3 ready for installation on our verious servers.

The problem I have is that the context files, which is required when building a DEB package, requires a version number for the DEB file. This is used when installing a DEB package to determine if the DEB package has already been installed. The problem is that the release version number, as determined by the release version section of the deployment plan is generated too late in the process.

I would like to use the release version number created by the deployment process to stamp the version in the context file, but the DEB package is built at this point in the process. Again, I dont want to move the building of the package into the deployment process because we have different target environments in the deployment process, and because building the DEB package during deployment seems like the wrong place to do this.

Does anyone have any suggestions? Has anyone else used Bamboo to build and deploy DEB packages? How did you solve the context file version problem?

[Stickyeyes]

Ah, interesting, thanks!

Still annoying that I'll have to build the deb file in the build phase , then unpack it in the deployment phase and then build it again :(

[Marcin Gardias]

Perhaps you can get what you want using variables. Let's say you name your relases 1.0.<incremented_number>

You can define a Global variable, for the part of the release name you want to increment at deployment time and use it to generate release number during build.

You use the same variable in your version naming scheme and use autoincrement variable option.

[Stickyeyes]

Seems a bit clunky, especially as the release versioning part of Bamboo seems absolutely perfect, it's just that its not possible to get hold of the version number bamboo generates. If it were available as a bamboo variable I could at least unpack the deb file in the deployment phase, write the variable in to the context file then repackage everything again.

I'm begining to find a lot of the descisions made for Bamboo make life incredibly difficult. At least with Jenkins we had the flexibility to pass variables around willy-nilly!

[Marcin Gardias]

deployment release name _is_ available during deployment phase: bamboo.deploy.release