Skip to main content
DevOps

Return to Question

formatting code and copy edit
Source Link
chicks
chicks
  • 1.9k
  • 1
  • 12
  • 29

I use $CIRCLE_BUILD_NUM$CIRCLE_BUILD_NUM in different jobs in a workflow (but it seems like that get incremented in between jobs of the same workflow)?

I did some research and it looks like I can switch to CIRCLE_WORKFLOW_IDCIRCLE_WORKFLOW_ID which is unique for the workflow but then the ID is some really long string, not like the build numnumber which is a small integer, nice that I can use to append to build numbers and docker tags and such.

Any ideas?

I use $CIRCLE_BUILD_NUM in different jobs in a workflow (but it seems like that get incremented in between jobs of the same workflow)?

I did some research and it looks like I can switch to CIRCLE_WORKFLOW_ID which is unique for the workflow but then the ID is some really long string, not like the build num which is a small integer, nice that I can use to append to build numbers and docker tags and such.

Any ideas?

I use $CIRCLE_BUILD_NUM in different jobs in a workflow (but it seems like that get incremented in between jobs of the same workflow)?

I did some research and it looks like I can switch to CIRCLE_WORKFLOW_ID which is unique for the workflow but then the ID is some really long string, not like the build number which is a small integer, nice that I can use to append to build numbers and docker tags and such.

Any ideas?

Source Link
erotsppa
erotsppa
  • 131
  • 2

Anyone know how to use $CIRCLE_BUILD_NUM across different jobs in CircleCI?

I use $CIRCLE_BUILD_NUM in different jobs in a workflow (but it seems like that get incremented in between jobs of the same workflow)?

I did some research and it looks like I can switch to CIRCLE_WORKFLOW_ID which is unique for the workflow but then the ID is some really long string, not like the build num which is a small integer, nice that I can use to append to build numbers and docker tags and such.

Any ideas?