- Open Source GPDB compile
- No ORCA yet -- getting there soon

[#151180202]
Signed-off-by: NGoutam Tadi <gtadi@pivotal.io>

GPOS using GPDB for memory allocation is still a feature hidden behind a
GUC and requires more performance testing to be considered for the
default allocation behavior of GPOS. For now it can be ignored from
determing if a build of GPDB is release worthy

functions

Concourse doesn't support AIX natively, we need to clone the repo
with the correspond commit on remote machine, compile the packages,
and download them back to concourse container as output.

Testing client and loader for platform without gpdb server is
another challenge. We setup GPDB server on concourse container just
like most installcheck tests, and use SSH tunnel to forward ports
from and to the remote host. This way both CL tools and GPDB server
feel they are on the same machine, and the test can run normally.

* run pxf_automation as part of pxf regression test
Signed-off-by: NAlexander Denissov <adenissov@pivotal.io>

* added missing input
Signed-off-by: NLav Jain <ljain@pivotal.io>

* Fix symbolic links

* create extension pxf before running automation tests

* Hack python psi module by copying it from system to gpdb python

* remove if exists for extension

* Run pxf_automation before regression tests

* Change owner to gpadmin before running tests

* Generalize copying of PSI package

* Generalize install path using GPHOME

ccp tag 1.0.0-beta.1 don't support centos7
revert job 'mpp_resource_group_centos7' from pipeline

Signed-off-by: NZhenghua Lyu <zlv@pivotal.io>

Migrations efforts for concourse 3 that are backwards compatible with
concourse 2.7.3

Includes using the image_resource in external task yamls for pipeline
jobs that use a sles based docker image. Currently unknown why the sles
image in particular causes image_resource issues.
Signed-off-by: NDivya Bhargov <dbhargov@pivotal.io>
Signed-off-by: NJim Doty <jdoty@pivotal.io>

Need flexibility to be able to control at what freqeuncy pipeline gets triggerd,
one such usecase is same pipleine code runs with asserts on every commit and
without asserts daily/weekly. So, adding a time resource via which can control
the triggering. Plus, parameterize the trigger to control the things.

comment out several tests which will fail on CCP cluster

[ci skip]

Now that catalog updates are allowed, we should disable binary swap
validation.  Once the next catalog freeze comes, someone can flip this
back.

* Make PXF part of the gpdb binary

* Fix popd error

Signed-off-by: NNadeem Ghani <nghani@pivotal.io>

* Refactor GPHDFS regression to run for pxf

* remove customized Hadoop home location

* PXF tarball creation inside GPDB pipeline

* Remove legacy directory

* Use enable_pxf instead of with_pxf

Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Add MM_gpinitstandby as part of release candidate

Follow up commit on 51a1cad7

Signed-off-by: NShoaib Lari <slari@pivotal.io>

Signed-off-by: NLav Jain <ljain@pivotal.io>
Signed-off-by: NOleksandr Diachenko <odiachenko@pivotal.io>
Signed-off-by: NShivram Mani <smani@pivotal.io>
Signed-off-by: NJohn Gaskin <jgaskin@pivotal.io>
Signed-off-by: NAlexandra Wang <lewang@pivotal.io>

New jobs should also be added to the "All" group, but we expect that
there may be exceptions and it's not a dealbreaker

If the reusable anchors are declared at the end, some yaml parsers may
have trouble reading the file. In this case, pyyaml was throwing:

```
yaml.composer.ComposerError: found undefined alias 'ccp_create_params'
  in "<string>", line 702, column 11:
          <<: *ccp_create_params
              ^
```

Signed-off-by: NMarbin Tan <mtan@pivotal.io>

Signed-off-by: NNadeem Ghani <nghani@pivotal.io>

Signed-off-by: NJim Doty <jdoty@pivotal.io>

In order to protect users of the concourse cluster provisioner service from
some pending breaking changes, we are pinning the master pipeline to the latest
tag for the concourse cluster provisioner repo.  We will in the future facilitate
upgrades on the master pipeline to take advantage of the next release.
Signed-off-by: NJim Doty <jdoty@pivotal.io>

1)add pipeline job for resource group test
2)make test cases independent of segment count and hosts count

Discussed w/ CJ - we'll work offline on a better way to address groups but will temporarily accept this 

The job runs FTS tests and has failed intermittently.  By increasing
gp_segment_connect_timeout, we reduce the chance that test environment will
cause failures.
Signed-off-by: NAsim R P <apraveen@pivotal.io>

We would like to have the VMs up if there's a failure.

Signed-off-by: NMarbin Tan <mtan@pivotal.io>
Signed-off-by: NLarry Hamel <lhamel@pivotal.io>

Signed-off-by: NXin Zhang <xzhang@pivotal.io>