You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@madlib.apache.org by edespino <gi...@git.apache.org> on 2017/08/31 18:11:20 UTC

[GitHub] madlib pull request #180: MADLIB-1142. Allow passing REPONAME into Jenkins b...

GitHub user edespino opened a pull request:

    https://github.com/apache/madlib/pull/180

    MADLIB-1142. Allow passing REPONAME into Jenkins build/rat scripts.

    The variable REPONAME will be passed in via the Jenkins project configuration. If not set, it will default to a reponame of "madlib".
    
    This task could not happen until the git repositories have been renamed. Nandish has informed the dev team this has happened.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/edespino/madlib MADLIB-1142

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/madlib/pull/180.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #180
    
----
commit 3513107b646aa9efae65432c6c559795c9a06b64
Author: Ed Espino <ee...@pivotal.io>
Date:   2017-08-31T18:01:32Z

    MADLIB-1142. Allow passing REPONAME into Jenkins build/rat scripts.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] madlib pull request #180: MADLIB-1142. Allow passing REPONAME into Jenkins b...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/madlib/pull/180


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] madlib issue #180: MADLIB-1142. Allow passing REPONAME into Jenkins build/ra...

Posted by edespino <gi...@git.apache.org>.
Github user edespino commented on the issue:

    https://github.com/apache/madlib/pull/180
  
    FYI: This PR is expected to fail until it is committed and the Jenkins git hub repos name is updated. I will perform that after this has been merged.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] madlib issue #180: MADLIB-1142. Allow passing REPONAME into Jenkins build/ra...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit commented on the issue:

    https://github.com/apache/madlib/pull/180
  
    
    Refer to this link for build results (access rights to CI server needed): 
    https://builds.apache.org/job/madlib-pr-build/199/



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] madlib issue #180: MADLIB-1142. Allow passing REPONAME into Jenkins build/ra...

Posted by orhankislal <gi...@git.apache.org>.
Github user orhankislal commented on the issue:

    https://github.com/apache/madlib/pull/180
  
    LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---