Project

General

Profile

Actions
Copy link

Task #7057

closed

Bug #6939: [Deployment] Package the SSO server

review 6939-package-sso-server branch on both the arvados-dev repository and on the sso-provider repository.

Added by Ward Vandewege over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Tom Clegg
Target version:
2015-09-02 sprint
Actions
Copy link
 #1

Updated by Tom Clegg over 8 years ago

  • Assigned To set to Tom Clegg
Actions
Copy link
 #2

Updated by Ward Vandewege over 8 years ago

  • Subject changed from review to review 6939-package-sso-server branch on both the arvados-dev repository and on the sso-provider repository.
Actions
Copy link
 #3

Updated by Ward Vandewege over 8 years ago

  • Subject changed from review 6939-package-sso-server branch on both the arvados-dev repository and on the sso-provider repository. to review 6939-package-sso-server branch on both the arvados-dev repository and on the sso-provider repository.

The big picture here is that I've extended the run-build-packages-all-targets.sh script so that it can be used to build the Arvados SSO package, which is totally separate from our other Arvados packages because it's a standalone codebase.

We're going to create a separate build pipeline for the Arvados SSO package on Jenkins, which will be tied to checkins into that code tree.

Testing/reviewing instructions:

  • check out the 6939-package-sso-server branch from the sso-provider repository somewhere (I'll call this directory SOMEWHERE below).
  • check out the 6939-package-sso-server branch from the arvados-dev repository
  • Test building the SSO package locally (not in a docker container) with:

    cd jenkins
    WORKSPACE=SOMEWHERE ./run-build-packages-sso.sh --target debian8

  • Test building the SSO package for one target (debian7) with:

    WORKSPACE=SOMEWHERE ./run-build-packages-one-target.sh --command run-build-packages-sso.sh

  • Test building the SSO package for all targets with:

    WORKSPACE=SOMEWHERE ./run-build-packages-all-targets.sh --command run-build-packages-sso.sh

  • Test building the 'fat' SSO package for one target (debian8) with:

    WORKSPACE=SOMEWHERE ./run-build-packages-one-target.sh --target debian8 --command "run-build-packages-sso.sh --build-bundle-packages"

  • Test building all Arvados packages for one target (assuming your Arvados tree lives in SOMEWHEREELSE)

    WORKSPACE=SOMEWHEREELSE ./run-build-packages-one-target.sh --target centos6

  • Test building all Arvados packages for all targets (assuming your Arvados tree lives in SOMEWHEREELSE)

    WORKSPACE=SOMEWHEREELSE ./run-build-packages-all-targets.sh

Actions
Copy link
 #4

Updated by Tom Clegg over 8 years ago

  • Status changed from New to In Progress
Actions
Copy link
 #5

Updated by Tom Clegg over 8 years ago

Functional
  • Should exclude database.yml, application.yml, and *~ (ideally we'd exclude everything that's excluded by .gitignore, minus git-commit.version, right? Perhaps there's a way to get the "files that are currently being gitignored" list from git and pass it to fpm?)
  • In run-build-packages.sh, clear COMMAND where we do that with other vars like BUILD_BUNDLE_PACKAGES=0
Code
  • Fix code duplication in COMMAND_ARR stuff for "bare" and "big" packages in run-build-packages-sso.sh -- it looks like the only differences are "-x .../vendor/bundle" and the package name, right?
  • Fix code duplication between run-build-packages-sso.sh and run-build-packages.sh (can we "source" a file with the stuff we've already written as functions?)
Actions
Copy link
 #6

Updated by Ward Vandewege over 8 years ago

Tom Clegg wrote:

Functional
  • Should exclude database.yml, application.yml, and *~ (ideally we'd exclude everything that's excluded by .gitignore, minus git-commit.version, right? Perhaps there's a way to get the "files that are currently being gitignored" list from git and pass it to fpm?)
  • In run-build-packages.sh, clear COMMAND where we do that with other vars like BUILD_BUNDLE_PACKAGES=0
Code
  • Fix code duplication in COMMAND_ARR stuff for "bare" and "big" packages in run-build-packages-sso.sh -- it looks like the only differences are "-x .../vendor/bundle" and the package name, right?
  • Fix code duplication between run-build-packages-sso.sh and run-build-packages.sh (can we "source" a file with the stuff we've already written as functions?)

I've addressed all of these in pushes to both branches. Thanks!

Actions
Copy link
 #7

Updated by Tom Clegg over 8 years ago

  • Status changed from In Progress to Resolved
  • Remaining (hours) set to 0.0
Actions
Copy link

Also available in: Atom PDF