GSIP 176

GSIP 176 CITE Automation RFP

Overview

This proposal is to announce a "request for proposal" seeking a solution for automated CITE TEAM Engine tests for build.geoserver.org within a budget of approximately $10,000 USD.

This approach is divided into three phases:

1. GSIP-176 Request for Proposal for CITE test automation.

2. Implementation and delivery of Automated CITE tests.

3. Code sprint activity to pass tests.

This proposal is in response to prior efforts noted at CITE-Test-Upgrade which were unsuccessful.

Applications

• Applicants are asked to send a quote to geoserver-devel describing their approach in sufficient detail for review.
• GeoServer GSIP proposals are welcome for applicants wishing feedback on their proposal prior to quoting
• During the selection process applicants are encouraged to attend bi-weekly GeoServer meeting for discussion and review.
• GeoServer PSC is responsible for the review and selection of applications

Requirements

• Required: Proposals are REQUIRED to run CITE TEAM Engine tests against a "nightly build" of GeoServer.
• Required: Proposal MUST provide testing of WMS, WFS and WCS CITE tests to match the capabilities of the system we are replacing. Special care is required for the WFS-T tests which cover transactions that modify a local database.
• Optional: Proposals MAY include testing of additional protocols (WMTS, WPS) tests.
• Recommended: Proposals SHOULD make use of
• Recommended: Proposals SHOULD describe how the testing of additional protocols (WMTS, WPS) may be added as part of the design.
• Required: Delivery is REQUIRED to meet GeoServer code contribution guidelines and include all scripts, source code, and documentation required for automated testing.
• Required: Delivery is REQUIRED in the form Jenkins jobs on build.geoserver.org showing the results of CITE testing.
• Recommended: Jobs with any logic SHOULD delegate to scripts as shown in the geoserver/build folder.
• Optional: Any build scripts added as MAY be documented developer manual with instructions for running locally.
• Recommended: Proposals SHOULD take into account that build.geoserver.org orchestration is managed by planet.federal.com, any changes to Jenkins configuration should be clearly described, and time allocated support deployment into this environment.

Clarifications, Discussion and Feedback

• This proposal does not assume or recommend an approach, we are open to your ideas and experience!
• The GeoServer data folder includes configurations for many CITE tests. This may be easier to manage and reuse via a git submodule?
• If considering use of the Team Engine Docker image and REST API, keeping in mind that this approach does not yet cover all protocols.
• This may be broken off into a distinct repository and included as a submodule
• We do not wish to maintain a fork of the Team Engine or tests. On the rare occasions we cannot use an official releases we would like to ensure these are managed as a submodule so we can manage exactly what revision used.

Request for Proposal Announcement

Announcement to be sent to geoserver-devel:

CITE Test Automation RFP

GeoServer PSC has an outstanding maintenance activity to automate CITE testing for our build server and have put together a budget (committee + sponsorship) of $10,000 USD towards this activity.

If you are in interested in this work please respond to the geoserver-devel email list with your proposal. For details see CITE-Test-Upgrade and GISP-176.

GeoServer Project Steering Committee

Applicants are welcome to attend bi-weekly GeoServer meeting for clarification of requirements and participate in the review process.

Budget

Budget for this activity:

• $5000 - OSGeo GeoServer Budget 2019
• $5000 - Sponsorship fundraising target

Sponsorship

As this activity covers operational improvements sponsorship structure is limited in number, and set at higher level than our traditional code-sprint activities:

• 3000 CITE Automation Sponsorship
• 2000 CITE Automation Sponsorship

To participate please email treasurer@osgeo.org to express your interest. As GeoServer is an OSGeo project your support does count towards the OSGeo sponsorship level. Keep in mind that the primary benefit of sponsoring this activity is supporting the GeoServer development team in reaching standards compliance:

• This opportunity is provided for organization that can benefit from standards compliance.

  Sponsors will be acknowledged at FOSS4G "State of GeoServer" presentations and during the OSGeo AGM.

• If you miss out, an additional code-sprint sponsorship opportunities are planned once CITE test automation is in place.

  • Code-sprint sponsorship slots will include visibility in GeoServer release announcements, and blog posts as CITE certifications are obtained.

  • Code-sprint sponsorship slots will be limited in number and valued from a marketing perspective.

As with any open source activity the hands-on "in-kind" participation shown during code-sprints and ongoing commitment of our core-contributors exceed any financial contribution. Sponsorship is an opportunity to thank those who can contribute financially when we have these opportunities to do so.

Proposed By

Jody Garnett

Assigned to Release

This proposal is for GeoServer 2.16.

State

• Under Discussion
• In Progress
• Completed
• Rejected
• Deferred

Motivation

Proposal

Backwards Compatibility

Feedback

Voting

Project Steering Committee:

• Alessio Fabiani:
• Andrea Aime:
• Brad Hards: +0
• Ian Turton:
• Jody Garnett:
• Jukka Rahkonen:
• Kevin Smith:
• Simone Giannecchini:

Links

• CITE Test Upgrade - Wiki Maintenance Page
• GeoTools / GeoServer PMC meeting - 2019-06-25