I would also love to have a private repo for Jenkins config, I've been collecting a whole lot of it.
I could add a requirement line along the lines of "Delivery is required to include the system prerequisites and environment setup in the form of a bash script executable on Ubuntu 18" Does that wording sound alright? Torben On Tue, Jul 16, 2019 at 9:32 PM Jody Garnett <[email protected]> wrote: > Sounds good, still would like a private repo to store Jenkins > configuration (including that 10-lin bash script). > > Thanks for the response Torben, do you need to modify the note I put in > there about deliverable requirements? > -- > Jody Garnett > > > On Tue, 16 Jul 2019 at 16:12, Torben Barsballe < > [email protected]> wrote: > >> Follow-up: >> >> On Tue, Jul 16, 2019 at 2:49 PM Torben Barsballe < >> [email protected]> wrote: >> >>> Some comments on the Planet portion: >>> >>> It's also not clear what relationship should be setup with Planet, if >>>> someone that's not >>>> Planet wants to bid, what is the context? Planet is going to offer a >>>> set amount of time >>>> to help with setting up things in their locked down node execution >>>> environment? >>>> (no one but Planet employees can access the worker nodes and the build >>>> server >>>> outside of the Jenkins admin GUI). >>>> Or should the company/individual try to setup a sub-contract with >>>> Planet? >>>> >>> >>> It may be possible to make the master node accessible to PSC/Whomever >>> ends up setting up the CITE tests - I will see if I can get a solid yes/no >>> answer and report back. (And as an aside, I don't even have access to the >>> worker nodes, just the startup script that creates them). >>> >>> We (Planet) can provide the exact configuration used to create the >> worker nodes (OS + startup script; there's not a whole lot that goes into >> them - its Ubuntu 18 and a 10-line bash script). The implementor could use >> that to set up a dev environment while developing the CITE test >> configuration. Once something is working, we (Planet) can apply any >> required changes to the AWS configuration. Does that sound like a workable >> solution? >> >> Torben >> >>>
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
