Date
1 - 7 of 7
Moving Diego Repositories
James Myers
Hi all,
We are currently in the process of moving all of the Diego repositories from `cloudfoundry-incubator` to the `cloudfoundry` organization. Specifically we are moving the following repositories to the `cloudfoundry` organization: - auction - auctioneer - bbs - benchmark-bbs - buildpack_app_lifecycle - cacheddownloader - cf-debug-server - cf-lager - cf_http - consuladapter - converger - diego-ssh - diego-upgrade-stability-tests - docker_app_lifecycle - executor - file-server - healthcheck - inigo - locket - rep - route-emitter - runtime-schema - vizzini - diego-cf-compatibility - diego-ci-pools - diego-ci - diego-design-notes - diego-dev-notes - diego-dockerfiles - diego-perf-release - diego-release - diego-stress-tests We are also moving the following from `pivotal-golang` to `cloudfoundry` as well: - archiver - bytefmt - clock - eventhub - lager - localip - operationq We are also renaming the following, and will be updating their package names accordingly: - benchmark-bbs -> benchmarkbbs - buildpack_app_lifecycle -> buildpackapplifecycle - cf-debug-server -> debugserver - cf-lager -> cflager - cf_http -> cfhttp - docker_app_lifecycle -> dockerapplifecycle - file-server -> fileserver - runtime-schema -> runtimeschema You might be asking yourself, what does this mean for me? Generally it means the following: - If you are importing any of the above repos in your golang code, you should change it from `github.com/cloudfoundry-incubator/REPO_NAME` to ` code.cloudfoundry.org/REPO_NAME`. - Update your golang code when you update your dependencies to reference the new package names marked above. - If you are consuming the Diego bosh release from bosh.io, you will need to update the location to http://bosh.io/releases/github.com/cloudfoundry/diego-release. Other than that, github redirects should handle most of the issues for you. As a side note we are also moving the following deprecated repositories to the `cloudfoundry-attic`: - diego-acceptance-tests - diego-smoke-tests - receptor - runtime-metrics-server Let us know if you have any questions. Best, Jim + Andrew, CF Diego Team |
|
Onsi Fakhouri <ofakhouri@...>
That stuff has always technically been foundation code and should have
toggle quoted message
Show quoted text
moved out of pivotal-golang into cloudfoundry-incubator long ago. Back when we made the org the rules about how orgs are structured weren't quite so clear. Onsi On Fri, Jun 24, 2016 at 4:18 PM, Alex Suraci <asuraci(a)pivotal.io> wrote:
why are we moving the pivotal-golang repos? I thought the point of that |
|
Amit Kumar Gupta
Congrats on making it official!
toggle quoted message
Show quoted text
I assume you folks are going to build some scripts or some "go fmt -r" to find/change all import paths that need updating. If you find anything useful that other teams might be able to leverage, sharing would be much appreciated. Cheers, Amit On Fri, Jun 24, 2016 at 4:20 PM, Onsi Fakhouri <ofakhouri(a)pivotal.io> wrote:
That stuff has always technically been foundation code and should have |
|
Kris Hicks <khicks@...>
I've found when doing this the easiest thing to do is to use sed to remove
toggle quoted message
Show quoted text
existing imports followed by goimports -w on the same files. KH On Sunday, June 26, 2016, Amit Gupta <agupta(a)pivotal.io> wrote:
Congrats on making it official! |
|
Will Pragnell <wpragnell@...>
Have we abandoned plans for the import path service Eric proposed back in
toggle quoted message
Show quoted text
April? If not, aren't we just going to have to update all our imports again once that rolls out? On 25 June 2016 at 18:36, Kris Hicks <khicks(a)pivotal.io> wrote:
I've found when doing this the easiest thing to do is to use sed to remove |
|
Will Pragnell <wpragnell@...>
Ignore me, I can't read... looks like this is using that already. Nice!
toggle quoted message
Show quoted text
On 27 June 2016 at 13:56, Will Pragnell <wpragnell(a)pivotal.io> wrote:
Have we abandoned plans for the import path service Eric proposed back in |
|
Eric Malm <emalm@...>
Hi, all,
We've finished moving these repositories into the 'cloudfoundry' GitHub org and updating them to base their import paths on the 'code.cloudfoundry.org' domain. In terms of tooling to assist with the move, we found that the existing gomvpkg utility, go-get-able from github.com/golang/tools/cmd/gomvpkg, handled most of the renaming correctly within an ordinary GOPATH, although it did not always rewrite paths within test files. In the case of BOSH releases that double as GOPATHs with their dependencies included via submodules, such as diego-release, we found the following Bash script to be effective at rewriting both the source files in the release and the BOSH packaging around them. It takes 3 arguments: the import path of the existing package, the import path of its new location, and the location of the BOSH release directory. It also assumes the existence of a separate GOPATH in `~/go` (a common location for a user's default GOPATH). #!/bin/bash set -x usage() { echo "$0 SOURCE_PACKAGE TARGET_PACKAGE BOSH_RELEASE_DIR" } src_component=$1 target_component=$2 bosh_release_dir=$3 if [ -z ${src_component} ]; then >&2 echo "ERROR: Specify a source package" usage exit 1 fi if [ -z ${target_component} ]; then >&2 echo "ERROR: Specify a target package" usage exit 1 fi if [ -z ${bosh_release_dir} ]; then >&2 echo "ERROR: Specify a BOSH release directory" usage exit 1 fi pushd $bosh_release_dir set -e gomvpkg -from ${src_component} -to ${target_component} set +e list=$(egrep -lir ${src_component} src/ --exclude="*.md" --exclude="*.test" --exclude=".git") echo $list | xargs -n 1 sed -i 's|'${src_component}'|'${target_component}'|g' echo $list | xargs -n 1 gofmt -w egrep -lir ${src_component} packages/ --exclude="*.md" --exclude="*.test" | xargs -n 1 sed -i 's|'${src_component}'|'${target_component}'|g' egrep -lir ${src_component} scripts/ --exclude="*.md" --exclude="*.test" | xargs -n 1 sed -i 's|'${src_component}'|'${target_component}'|g' egrep -lir ${src_component} jobs/ --exclude="*.md" --exclude="*.test" | xargs -n 1 sed -i 's|'${src_component}'|'${target_component}'|g' rm -f src/${target_component}/.git popd pushd ~/go GOPATH=$PWD go get ${target_component} cp -r src/${target_component}/.git ${bosh_release_dir}/src/${target_component} popd Diego-release also relies on its sync-submodule-config script ( https://github.com/cloudfoundry/diego-release/blob/develop/scripts/sync-submodule-config) to ensure that the submodule URLs are updated correctly as part of committing the update. If your release does not automatically sync its submodules this way, you will have to update the .gitmodules file in your repo by hand or with a `sed` command similar to those in the script above. Thanks, Eric, CF Runtime Diego PM On Mon, Jun 27, 2016 at 6:18 AM, Will Pragnell <wpragnell(a)pivotal.io> wrote: Ignore me, I can't read... looks like this is using that already. Nice! |
|