Continue fleshing out post-release job

Try updating package.jsons and commiting the
change to git.

Use TEST branch for now.
This commit is contained in:
Kris De Volder
2017-05-10 19:07:12 -07:00
parent 43c1ede00d
commit c2da9f4df8
4 changed files with 14 additions and 62 deletions

View File

@@ -9,31 +9,16 @@ echo "version=$version"
for extension_id in vscode-manifest-yaml vscode-concourse commons-vscode
do
cd $sources/$extension_id
echo "Should update version of $extension_id to $version"
echo "But this isn't implemented yet!"
npm version $version
echo ""
done
exit 99
release_version=`jq -r .version ${sources}/package.json`
echo "release_version=$release_version"
cd $sources
echo "Bumping version of ${extension_id}"
echo "release_version=${release_version}"
npm version patch
git add .
new_version=`jq -r .version ${sources}/package.json`
echo "new_version=${new_version}"
git config user.email "kdevolder@pivotal.io"
git config user.name "Kris De Volder"
git commit \
-m "Bump version of ${extension_id} to ${new_version}"
-m "Bump version of vscode extensions to ${version}"
git clone $workdir/sts4 $workdir/sts4-out
git clone $workdir/sts4 $workdir/out

View File

@@ -1,28 +0,0 @@
#!/bin/bash
set -e
workdir=`pwd`
echo "extension_id=$extension_id"
sources=$workdir/sts4/vscode-extensions/$extension_id
release_version=`jq -r .version ${sources}/package.json`
echo "release_version=$release_version"
cd $sources
echo "Bumping version of ${extension_id}"
echo "release_version=${release_version}"
npm version patch
git add .
new_version=`jq -r .version ${sources}/package.json`
echo "new_version=${new_version}"
git config user.email "kdevolder@pivotal.io"
git config user.name "Kris De Volder"
git commit \
-m "Bump version of ${extension_id} to ${new_version}"
git clone $workdir/sts4 $workdir/sts4-out

View File

@@ -1,11 +0,0 @@
inputs:
- name: sts4
outputs:
- name: sts4-out
platform: linux
image_resource:
type: docker-image
source:
repository: kdvolder/sts4-build-env
run:
path: sts4/concourse/tasks/bump-version.sh