Closed abesto closed 6 years ago
Note that since we follow the same pattern in all CircleCI 2.0 configs, we'll need to propagate this change to all of them. To prevent duplicate work, I'd recommend cutting a release to do a “live-fire exercise” after merge.
trying now. good analysis
moved past, but the build is flakey.. hopefully won't die a lot :) https://github.com/openzipkin/zipkin-aws/issues/100
We should at some point get all the builds running or passing on JDK 10 or 11 anyway
green!
Problem: as noted in https://github.com/openzipkin/zipkin-aws/pull/95#issuecomment-408819158, the release process (initiated by pushing a tag
release-MAJOR.MINOR.PATCH
) wasn't triggered. CircleCI at https://circleci.com/gh/openzipkin/workflows/zipkin-aws/tree/release-0.12.1 says “zipkin-aws/release-0.12.1 has no workflows configured”.Analysis: the documentation states that unless explicitly configured, workflow jobs are not triggered for any tags.
trigger_publish
is configured to be triggered onrelease-
tags. However, itrequires
build
, andbuild
is not configured with atags
filter, so it was not run. Note also that conceptually, I thinkbuild
is not an actual dependency oftrigger_publish
(but it is an actual dependency ofpublish_stable
).Solution: remove the dependency of
trigger_publish
onbuild
, and allowbuild
to run on tagsMAJOR.MINOR.PATCH
, which is the same filter configured forpublish_stable
. The build flow should now go:master
:build
->publish_snapshot
release-0.0.0
-> flow(trigger_publish
creates tag0.0.0
) -> flow(build
->publish_stable
)publish_snapshot
to not run because it has notags
filter, and the default is to not trigger on tags.PoC: pushed a tag
release-0.0.0
toabesto/zipkin-aws
with these changes, and it triggered a workflow (which terminated early at the “don't run on forks” check we have in.circleci/config.yml
for thetrigger_publish
step): https://circleci.com/gh/abesto/zipkin-aws/2