yetus-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <>
Subject [jira] [Commented] (YETUS-649) Travis CI support
Date Sun, 29 Jul 2018 21:00:00 GMT


Allen Wittenauer commented on YETUS-649:

It looks like supporting Travis CI is fairly easy.

* it would work exactly like the "old school" Jenkins builds.  In other words, "${WORKSPACE}"
is the extracted source tree. We know that is supported so long as .gitignore is configured
correctly for the patch dir

* Many env vars expose information we need:
  * TRAVIS_BRANCH name of the branch to build (this will be the PR branch in those instances)
  * TRAVIS_BUILD_DIR is the full source dir (our BASEDIR)
  * TRAVIS_BUILD_ID appears to serve the same purpose as the Jenkins build #
  * TRAVIS_JOB_ID probably same as the Jenkins instance #?
  * TRAVIS_PULL_REQUEST is the pull request # or false if it's a full build
  * TRAVIS_PULL_REQUEST_BRANCH is the branch the PR originated from (for github, we ask the
API for this btw)
  * TRAVIS_REPO_SLUG is the user/repo string for a PR.  useful for the github plugin

Off the top of my head, the big thing missing would be the URL information for Travis but
maybe we can figure that out or maybe we don't care?

All in all, this looks very do-able with a minimal amount of work.  It's tempting to just
write a wrapper for that puts the vars in the correct spot, but it's probably
better to just write a travis plugin that activates when the various travis env vars are present.

> Travis CI support
> -----------------
>                 Key: YETUS-649
>                 URL:
>             Project: Yetus
>          Issue Type: New Feature
>          Components: Test Patch
>            Reporter: Allen Wittenauer
>            Priority: Major
> Apache Yetus should support Travis CI as well as we do Jenkins

This message was sent by Atlassian JIRA

View raw message