maxmustermann/pulumi
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
pulumi/scripts/publish_tgz.sh

34 lines
1.1 KiB
Bash
Raw Normal View History

Make a publish script; fix sed for multi-OS compat This change creates a scripts/ folder, moves our existing shell script, gocover.sh, underneath it, and factors the publish logic out of the Makefile and into the publish.sh file. The syntax for sed differs between Mac OS X and GNU versions of the tool, which is rather annoying. This fixes it by leveraging the fact that `sed -i.bak ...` works, although we now need to clean up the *.bak file left behind. (No big deal and way better than maintaining OS-dependent logic.)
2017-07-21 18:37:14 +02:00
#!/bin/bash
Publish tgz's in the middle of the build, packages at the end While it's safe to publish the tgz that we use internally for other repositories that are on "the link plan" after the build completes, we shouldn't publish packages to NPM and PyPi at that point. There are two reasons for doing this: 1. Publishing packages before they are tested, which means we could end up publishing packages that don't work. 2. NPM prevents publishing the same package more than once, so if we had to re-run the job (due to tests failing for transient issues), the publish step will start failing, preventing us from running the tests at all.
2018-03-06 23:36:50 +01:00
# publish.sh builds and publishes the tarballs that our other repositories consume.
cleanup
2018-09-03 18:49:57 +02:00
set -o nounset
set -o errexit
set -o pipefail
Make a publish script; fix sed for multi-OS compat This change creates a scripts/ folder, moves our existing shell script, gocover.sh, underneath it, and factors the publish logic out of the Makefile and into the publish.sh file. The syntax for sed differs between Mac OS X and GNU versions of the tool, which is rather annoying. This fixes it by leveraging the fact that `sed -i.bak ...` works, although we now need to clean up the *.bak file left behind. (No big deal and way better than maintaining OS-dependent logic.)
2017-07-21 18:37:14 +02:00
Only publish some artifacts from a single Linux leg We publish some artifacts from this repository, which are specific to an OS. In the past, we only had a single Linux leg and so we did not need any additional conditional logic. However, we now have multiple Linux legs (across different node versions) running in parallel, so if we try to publish the same artifacts at the same time, we can run into issues because two `aws s3 cp` jobs try to write to the same file at the same time. Follow similar logic to our skips we do around publishing NPM and PyPI packages here, as well.
2019-01-15 02:14:57 +01:00
# We run multiple legs on Linux, but only want to publish the tgz's from the one that publishes
# our NPM and PyPI packages. Otherwise, we may race with other legs when publishing to S3 which
# leads to issues about values being out of range.
if [ "${TRAVIS_OS_NAME:-}" = "linux" ] && [ "${TRAVIS_PUBLISH_PACKAGES:-}" != "true" ]; then
exit 0
fi
cleanup
2018-09-03 18:49:57 +02:00
readonly ROOT=$(dirname "${0}")/..
readonly PUBLISH="${GOPATH}/src/github.com/pulumi/scripts/ci/publish.sh"
readonly PUBLISH_GOARCH=("amd64")
readonly PUBLISH_PROJECT="pulumi"
Crossbuild and publish to new layout format
2017-09-22 04:10:33 +02:00
cleanup
2018-09-03 18:49:57 +02:00
if [[ ! -f "${PUBLISH}" ]]; then
Update the publish scripts for the new package structure (#334)
2017-09-07 20:07:52 +02:00
>&2 echo "error: Missing publish script at $PUBLISH"
exit 1
fi
Make a publish script; fix sed for multi-OS compat This change creates a scripts/ folder, moves our existing shell script, gocover.sh, underneath it, and factors the publish logic out of the Makefile and into the publish.sh file. The syntax for sed differs between Mac OS X and GNU versions of the tool, which is rather annoying. This fixes it by leveraging the fact that `sed -i.bak ...` works, although we now need to clean up the *.bak file left behind. (No big deal and way better than maintaining OS-dependent logic.)
2017-07-21 18:37:14 +02:00
cleanup
2018-09-03 18:49:57 +02:00
readonly OS=$(go env GOOS)
Run Travis on both macOS and Linux Unlike go binaries (where we can cross compile) the node module that we publish needs to be built on the platform we publish for. Update our `.travis.yml` file to also build on macOS and fix the publishing script so we don't don't cross publish Darwin from Linux. Once we have CI working for Windows, we'll remove the loop over PUBLISH_GOOS and each build will publish just the artifacts for the host OS.
2017-09-26 02:00:08 +02:00
Rename pulumi package to @pulumi/pulumi (#917) In order to begin publishing our core SDK package to NPM, we will need it to be underneath the @pulumi scope so that it may remain private. Eventually, we can alias pulumi back to it. This is part of pulumi/pulumi#915.
2018-02-12 22:13:13 +01:00
echo "Publishing SDK build to s3://eng.pulumi.com/:"
cleanup
2018-09-03 18:49:57 +02:00
for ARCH in "${PUBLISH_GOARCH[@]}"; do
export GOARCH="${ARCH}"
RELEASE_INFO=($($(dirname "${0}")/make_release.sh))
"${PUBLISH}" ${RELEASE_INFO[0]} "${PUBLISH_PROJECT}/${OS}/${ARCH}" ${RELEASE_INFO[@]:1}
Crossbuild and publish to new layout format
2017-09-22 04:10:33 +02:00
done
cleanup
2018-09-03 18:49:57 +02:00
Only publish some artifacts from a single Linux leg We publish some artifacts from this repository, which are specific to an OS. In the past, we only had a single Linux leg and so we did not need any additional conditional logic. However, we now have multiple Linux legs (across different node versions) running in parallel, so if we try to publish the same artifacts at the same time, we can run into issues because two `aws s3 cp` jobs try to write to the same file at the same time. Follow similar logic to our skips we do around publishing NPM and PyPI packages here, as well.
2019-01-15 02:14:57 +01:00
exit 0
Reference in a new issue Copy permalink