Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Welcome to the TOSCA Gitlab CI/CD to deploy on AWS Challenge. In this challenge, we are looking for you to create Gitlab CI/CD pipeline to deploy Angular 2+ application on AWS using Weblogic 12c & Gradle.

Let us know any question you have!

Technology stack

  • Angular 7
  • AWS
  • Weblogic 12c
  • Gradle
  • CI/CD
  • Docker
  • YAML

Prerequisites

  • An AWS account. Members are requied to use their own AWS account.
  • GitLab account.

References

  • Angular 2+ application to be deployed is provided in forum
  • Another Angular 2+ POC application built using Gradle & deployed on Weblogic 12c has be provided in forum.

Requirements

  • Create a GitLab CI/CD pipeline configured by a file called .gitlab-ci.yml. It should test/lint & build the Angular 2+ applicaiton after this is should will deploy the application on WebLogic 12c hosted on AWS.

  • The CI/CD should make use of docker container that should have at least Java, Gradle and NodeJS to complete the build & deployment on a Webloc 12c server hosted on AWS.

  • The CI/CD should be triggered whenever code push happens to the staging branch & it should do the following:

pipeline {

    stages {
        stage('Test') {
            steps {
		  		<Lint the code>
            }
        }
        stage('Build') {
            steps {
                <Call Gradle Build Task>
            }
        }
        stage('Deploy') {
            steps {
                <Deploy Build Result to Weblogic (Sandbox) & host on AWS>
            }
        }
    }
}


Final Submission Guidelines

  • Full source code with all the requirements implemented.
  • Detailed readme that describes how to configure, build and run the app.
  • Verification video !important.

Licenses & attribution

  • Third-party assets used to build your item must be properly licensed or free for commercial use. MIT, some modified BSD, Apache 2 licenses are ok. If a library is not commercial-friendly you will need to get our approval first.
  • Sufficient information regarding third-party assets must be present in your documentation. This includes the author, license info and a direct link to the asset online.

FAQs

After submission as a submitter what should be my next step?

Once the challenge submission phase is over the assigned reviewers are going to review all the submissions based on the challenge scorecard. They are expected to raise all issues found in the submissions they are reviewing. After the completion of review phase the Appeal phase status. In this phase, the submitters should go to the Online Review page, select the project & have a look at the issues raised by the reviewers. If you disagree with the reviewer on any issue/comment, raise an appeal by clicking the 'Appeal' button associated with the section and entering the appeal comment.

When & where I can see the challenge results?

After the Appeal response phase is over the results are displayed on the challenge specification page as well as on the online reivew page.

ELIGIBLE EVENTS:

Topcoder Open 2019

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30096504