Skip to content
Permalink
Branch: dev
Commits on Mar 12, 2018
  1. Add generate uber jar tasks for end-to-end-tests (#381)

    dramaticlly committed Mar 12, 2018
    * add generate uber jar for end-to-end-tests
    on blox release, copy the uber jar to correct path
Commits on Mar 1, 2018
  1. Add copy task for build outputs (#380)

    xjhe committed Mar 1, 2018
Commits on Feb 20, 2018
  1. Fix the E2E test for codebuild to let deploy first (#378)

    wbingli committed Feb 20, 2018
    The gradle task order does not imply execution order, therefore the
    default endpoint for testEndToEnd is null as deployment output file is
    not ready yet.
    
    For local development, it won't be a problem as the deployment output
    file should exist already. We make the code build as two steps so we
    could have default endpoint ready before run test task.
Commits on Feb 17, 2018
  1. Allow `testEndToEnd` task takes configuration from command line optio…

    wbingli committed Feb 17, 2018
    …ns (#377)
    
    * Allow `testEndToEnd` task takes configuration from command line options
    
    It also remove the dependency on the deployment, so run test will only
    run test without deployment. To run both deploy and test, you can do
    `gradle deploy testEndToEnd`.
    
    Refactor the e2e test to move the share part into abstract class.
    
    * Address per feedback
Commits on Feb 12, 2018
  1. Add broader deploy permissions for CodeBuild worker (#376)

    wjbuys committed Feb 12, 2018
    This adds ec2:* and apigateway:* permissions to the CodeBuild worker, so
    that it can deploy infrastructure changes to the end-to-end test stack.
    
    Without this, we have to manually redeploy any time we change our
    cloudformation templates or the FE API.
  2. Add end-to-end test for UpdateEnvironment (#375)

    wjbuys committed Feb 12, 2018
    The main goal of this PR is to add an end-to-end test for
    UpdateEnvironment.  Apart from adding the new test case, this also fixes
    the following issues that was preventing the end-to-end test from
    working:
    
    - fix an FE bug where environmentName was present in both the URI path
      and the request body of updateEnvironment
    - the test cluster now has multiple instances, and the tests verify that
      tasks are started on all of them
    - the test stack has an additional task definition, so that we can
      change task definitions
  3. Add end-to-end test for UpdateEnvironment

    wjbuys committed Feb 12, 2018
    This tests that an environment is fully upgraded when the environment is
    updated to a new task definition.
  4. Update end-to-end tests to work with a 2-host cluster

    wjbuys committed Feb 12, 2018
    This also adds another task definition that we can use for the
    UpdateEnvironment test.
  5. Remove duplicate environmentName from UpdateEnvironmentRequest

    wjbuys committed Feb 12, 2018
    The environmentName is already part of the path parameters of the
    request, so it shouldn't be in the request body.
  6. Fix NullPointerException for inactive environments in scheduler handl…

    wjbuys committed Feb 12, 2018
    …er (#373)
    
    The scheduler handler incorrectly assumed that an environment will
    always have an active environment revision. This is not true for
    newly-created environments, and would cause scheduler invocations to
    fail with a NullPointerException.
    
    Instead, it now returns an empty SchedulerOutput as soon as it's clear
    that the environment has no active revisions.
  7. Remove unused/broken updateEnvironment cucumber test case (#374)

    wjbuys committed Feb 12, 2018
    This test case didn't work, and was not being run. It also relies on
    UpdateEnvironment returning full Environment/EnvironmentRevision
    objects, which is no longer the case.
  8. First-pass implementation of UpdateEnvironment in DataService (#372)

    wjbuys committed Feb 12, 2018
    This is the simplest possible implementation of UpdateEnvironment. It
    doesn't take into account possible race conditions or partial failures
    for updateing `latestEnvironmentRevisionId` on the environment, but as
    long as callers only rely on the environmentRevisionId return from the
    call itself, there should be no problem.
Commits on Feb 8, 2018
  1. Setup CodeBuild for Blox end-2-end test (#369)

    wbingli committed Feb 8, 2018
    * Setup CodeBuild for Blox end-2-end test
    
    - A cloudformation to setup the codebuild project and permission
    - buildspec and properties for test and environment config
    - README for the setup
    
    * Add build report as artifacts and update readme
    
    * Update CF template to configure CodeBuild project with artifacts
  2. Add UpdateEnvironment API to frontend (#371)

    wjbuys committed Feb 8, 2018
  3. Add UpdateEnvironment to Frontend API

    wjbuys committed Feb 8, 2018
    Also refactor the tests to extract some common model creation functions.
    Ideally, we should figure out how to share the ModelBuilders from
    DataService soon.
  4. Remove role/instanceGroup fields from ds.updateEnvironmentRequest for…

    wjbuys committed Feb 8, 2018
    … now
    
    It's not clear whether we want to update these fields as part of the
    environment revision yet, removing them until we figure it out.
Commits on Feb 7, 2018
  1. Add stop task to scheduler (#368)

    xjhe committed Feb 7, 2018
    * Add stop task to scheduler
    
    * Allow scheduler to return multiple actions
    
    * Refactor and rename some of the methods
Commits on Feb 3, 2018
  1. Fix deprecation warning from `downloadClient` task (#367)

    wjbuys committed Feb 3, 2018
    Using `inputs.file` with a Task as argument was causing a warning:
    
    "Using TaskInputs.file() with something that doesn't resolve to a File
    object has been deprecated and is scheduled to be removed in Gradle 5.0.
    Use TaskInputs.files() instead."
Commits on Feb 1, 2018
  1. DataService integration test: happy case! (#366)

    xjhe committed Feb 1, 2018
    * Add Junit integration test for data service createEnvironment
    
    * Break data service integration test into separate files
    
    * Use the default account id, environment and cluster for testing
Commits on Jan 31, 2018
  1. Map FE Exception and generate related apigateway SDK exception (#365)

    wbingli committed Jan 31, 2018
    * Map FE Exception and generate related apigateway SDK exception
    
    It takes ResourceNotFoundException from data service as an example, it
    covers:
     - Handle Spring exception with status code and json response
     - Config API to generate proper exception data model per status code
     - Configure apigateway SDK generation to have proper exception for exception
     - Update end-2-end test to verify the error handling
    
    * Address review comments
    
    - Move e2e describe verification to the test case
    - Move APIresponse for ResourceNotFound status code and message to the
    ResourceNotFoundExceptionResponse itself
Commits on Jan 30, 2018
  1. Move all group/version declarations to root project's build.gradle (#364

    wjbuys committed Jan 30, 2018
    )
  2. Add Junit integration test for data service createEnvironment (#358)

    xjhe committed Jan 30, 2018
    * Add Junit integration test for data service createEnvironment
    
    * Redo the spring wiring for integ test
    
    * Revise the test base and inject DynamoDBLocalSetup as autowire
  3. Add JSON-RPC error/exception resolvers that support POJOs (#362)

    wjbuys committed Jan 30, 2018
    This adds Jackson-based (de)serialization for JSON-RPC servers and clients that will serialize/deserialize Throwable instances that have custom fields correctly.
  4. Fix integration tests to correctly test for exceptions

    wjbuys committed Jan 30, 2018
    Even when the JSON-RPC layer started mapping exceptions correctly, the
    integ tests would fail because there's some error wrapping and incorrect
    comparisons going on.
    
    This change generifies the cucumber steps that check for exceptions
    using assertJ's rich assertions, and fixes some error wrapping issues.
  5. Wire new exception mappers into DataService

    wjbuys committed Jan 30, 2018
    This actually wires up the Exception/ErrorResolvers into the JSON-RPC
    client/server used for the DataService, and adds the necessary Jackson
    annotations to the DataService's exceptions.
  6. Add client and server side error/exception resolvers that support POJOs

    wjbuys committed Jan 30, 2018
    This adds Jackson-based serialization for JSON-RPC servers and clients
    that will serialize/deserialize Throwable instances that have custom
    fields correctly.
    
    This commit doesn't actually wire up the new resolvers yet.
  7. Simplify pull request template (#363)

    wjbuys authored and wbingli committed Jan 30, 2018
    Removes TODO and obsolete changelog/testing steps.
  8. Refactor integration test to verify Lambda and Spring integration wit…

    wbingli committed Jan 30, 2018
    …h a sample controller (#361)
    
    * Refactor integration test to verify Lambda and Spring integration using a sample controller
    
    * Address comments
  9. Sort swagger model to make the swagger.yml generation to be updated o…

    wbingli committed Jan 30, 2018
    …nly if model changed (#360)
  10. Update E2E test to use DeleteEnvironment API to cleanup environment (#…

    wbingli committed Jan 30, 2018
    …359)
    
    - Fix DeleteEnv DDB issue to delete record anyway
    - Remove e2e project dependency on data-service, dynamo and lambda json rpc
    - Remove Dyanmodb helper for e2e test
Commits on Jan 26, 2018
  1. Update Froentend SDK with new DeleteEnvironment API (#357)

    wbingli committed Jan 26, 2018
  2. Cleanup build warnings (#356)

    wbingli committed Jan 26, 2018
    Fix all the build warnings:
     - "scheduling-manager:compileTestJavaNote: Some input files use or
     override a deprecated API."
     - "EnvironmentRepositoryDDBTest.java uses unchecked or unsafe
     operations."
     - "ERROR StatusLogger No log4j2 configuration file found....."
Commits on Jan 25, 2018
  1. Remove the mapper for EnvironmentRevision from frontend model to data…

    wbingli committed Jan 25, 2018
    … service model to rmeove the compile warning (#355)
    
    There is no need to mapper EnvironmentRevision to data service model. We will create the environment by update environment API.
  2. Generate swagger from a package and update swagger for delete-environ… (

    wbingli committed Jan 25, 2018
    #354)
    
    * Generate swagger from a package and update swagger for delete-environment api
    
    * Update per comment
Older
You can’t perform that action at this time.