-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
add travis configuration #2
Conversation
Nice work getting this pull request opened! This pull request adds a All projects have different needs, ranging from standard unit tests to custom configuration. Regardless of the definition of "success" for your project, this is the place to define it. There isn't much in this file right now, but we're going to change that. We'll make a change to configure the build environment. You might be noticing a few things about this configuration file, like the programming language. You can trigger Travis CI builds with new commits. To trigger Travis CI, add the below text in place of the 2.5 Step 2: Specify the Ruby versionTo get the CI build to succeed, replace the placeholder text and commit the change. ⌨️ Activity: Define a specific version of a language
I'll respond below with your next step.
|
Co-authored-by: github-learning-lab[bot] <37936606+github-learning-lab[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work getting your CI build to succeed! 🎉
Notice that your pull request shows all checks have passed with 2 successful checks.
You'll notice that there are two build status checks. One build is for the branch and the other build is for the pull request (more accurately, the merge of your initial-travis-config
branch into the base branch main
).
Why did my CI build succeed?
The .travis.yml
file defines your build environment and which automated tests to run. The entire delivery process is defined through this single .travis.yml
file. If this file is present and your commit passes the tests as outlined in the .travis.yml
file, your CI build will succeed.
Step 3: Merge the configuration
Now that our CI build is succeeding, merge this pull request so the .travis.yml
file is pushed to main
.
⌨️ Activity: Share your configuration with the team by merging it
- Click merge pull request, and delete your branch
I'll respond below with your next step.
The Now that your CI build is succeeding, let's add some validations to your project. I've opened a new pull request for your next steps.
|
No description provided.