I was under the impression that to actually deploy a pipeline, either as a new pipeline or an update to the existing ci/pipelines, would require additional permissions against the Concourse framework. If I am mistaken, apologies. I suppose one could modify the existing pipeline job scripts to include additional work, but I am disinclined to include any exploratory testing as part of an existing test script, it being volatile by intent. The thought I had was to deploy a new, temporary pipeline to the staging area, so as not to dirty the existing main/develop pipeline. If there is a better approach, I'm certainly open to alternatives.
On Mon, Jul 2, 2018 at 12:34 PM, Alexander Murmann <amurm...@pivotal.io> wrote: > Hi Patrick, > > The pipeline definition is in ci/pipelines. is that what you are looking > for or do you need access to push pipeline changes? > > On Mon, Jul 2, 2018 at 12:08 PM, Patrick Rhomberg <prhomb...@apache.org> > wrote: > > > Hello all. > > > > I'm currently investigating the state of our FlakyTest consumption, > > believing that a lot of these markers are no longer accurate and that the > > annotated tests deserve promotion to the actual test jobs. [1] > > So as not to prematurely reintroduce flaky tests to the main body of > the > > pipeline, I would like to run those tests to abundance overnight to build > > confidence in the tests performance. Ideally, this would be in the > actual > > testing environment we use elsewhere, such as the Staging pipeline. > > To that end, I am requesting permissions to access and modify the > Apache > > Geode pipelines. > > Thank you. > > > > Imagination is Change. > > ~Patrick Rhomberg > > > > [1] According to the script used to build the develop-metrics "pipeline", > > there have only been 10 (of ~90) flaky test classes that produced > failures > > in the last 114 (currently all) FlakyTest job runs. > > See > > https://concourse.apachegeode-ci.info/teams/main/pipelines/ > > develop-metrics/jobs/GeodeFlakyTestMetrics/builds/48 > > and > > others > > >
