|
I'm finding that if you add a "publish to s3" step to a build promotion process - and you have multiple build promotion processes defined (say, one for Dev, Test, and Production) - you get a very strange interaction.
I wanted to publish to a different S3 bucket for each of Dev, Test, and Production - and wanted to wire that into the three different build promotion definitions.
However, upon Save, the configuration got very strange: Every build promotion process I had defined now had every S3 step from all promotions.
In other words I had defined:
Dev Promo
Publish to s3 dev bucket
Test Promo
Publish to s3 test bucket
Prod Promo
Publish to s3 prod bucket
but upon Save it became:
Dev Promo
Publish to s3 dev bucket
Publish to s3 test bucket
Publish to s3 prod bucket
Test Promo
Publish to s3 dev bucket
Publish to s3 test bucket
Publish to s3 prod bucket
Prod Promo
Publish to s3 dev bucket
Publish to s3 test bucket
Publish to s3 prod bucket
and every subsequent save actually multiplied the S3 configs.
Happy to provide more information if I can.
Scott
|
