Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 secrets Vault integration #1769

Merged
merged 1 commit into from
Nov 15, 2018
Merged

S3 secrets Vault integration #1769

merged 1 commit into from
Nov 15, 2018

Conversation

dincho
Copy link
Member

@dincho dincho commented Nov 13, 2018

- upload_build_artifacts:
requires:
- linux_package
filters:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please remind me what this filter means?

Before this change it was only on master. Now it looks like it is on:

  • Tags matching /^v.*$/
  • All branches? (I am not sure what default for branches is, and whether default branches is documented in Circle CI doc - I did not find it.)

Copy link
Member Author

@dincho dincho Nov 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, all branches. If there is no branch filters, it runs for all branches.
it's documented in the docs you refer:

If neither only nor ignore are specified then all branches will run the job.

About:

Before this change it was only on master. Now it looks like it is on:

This PR should not change the behaviour. However, the build artefact are uploaded for each branch build and on all release tags. Also the job itself have an extra check that uploads the "latest" build artefact on master only.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, I was reading incorrectly, it does not change semantics, correct.


I see this snippet is kept:

            aws s3 cp --acl public-read ${PACKAGE_TARBALL:?} s3://${S3_BUILDS_BUCKET:?}/
            if [ -n "$CIRCLE_BRANCH" -a "$CIRCLE_BRANCH" = "master" ]; then
              aws s3 cp --acl public-read ${PACKAGE_TARBALL:?} s3://${S3_BUILDS_BUCKET:?}/epoch-latest-${PKG_SUFFIX:?}.tar.gz
            fi

- upload_build_artifacts:
requires:
- linux_package
filters:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, I was reading incorrectly, it does not change semantics, correct.


I see this snippet is kept:

            aws s3 cp --acl public-read ${PACKAGE_TARBALL:?} s3://${S3_BUILDS_BUCKET:?}/
            if [ -n "$CIRCLE_BRANCH" -a "$CIRCLE_BRANCH" = "master" ]; then
              aws s3 cp --acl public-read ${PACKAGE_TARBALL:?} s3://${S3_BUILDS_BUCKET:?}/epoch-latest-${PKG_SUFFIX:?}.tar.gz
            fi

@dincho dincho merged commit d23b44f into master Nov 15, 2018
@dincho dincho deleted the 160452961_csm_integration branch November 15, 2018 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants