The ares Jenkins server looks like it has a custom “run.sh” script in the “geoserver-cite” workspace used to run the CITE tests. As far as I can tell, this script is not tracked in version control anywhere.
There is also a setEnv.sh file responsible for setting the java version (which is specific to the machine) and a forms directory containing a bunch of xml files representing OWS requests or HTML forms.
The remaining directories all appear to be populated by the run.sh script, and include a copy of the current release artifacts, a copy of the current data directories used by the cite tests, a geoserver master checkout, and a cite master checkout.
Unless someone can point me to a location where the “run.sh” script (and the contents of the “forms” dir) are saved, I think we should probably add this script to version control.
Does anyone have any more information about this setup, or other thoughts?
I am happy to have this script saved into the build folder, and the cite jobs updated accordingly.
I would double check that any credentials are passed into the script (rather than being hard coded). That is the only thing I can think of for why it would not be committed already.
The ares Jenkins server looks like it has a custom “run.sh” script in the “geoserver-cite” workspace used to run the CITE tests. As far as I can tell, this script is not tracked in version control anywhere.
There is also a setEnv.sh file responsible for setting the java version (which is specific to the machine) and a forms directory containing a bunch of xml files representing OWS requests or HTML forms.
The remaining directories all appear to be populated by the run.sh script, and include a copy of the current release artifacts, a copy of the current data directories used by the cite tests, a geoserver master checkout, and a cite master checkout.
Unless someone can point me to a location where the “run.sh” script (and the contents of the “forms” dir) are saved, I think we should probably add this script to version control.
Does anyone have any more information about this setup, or other thoughts?
I don’t think there was any particular reason why I didn’t add the script to version control other than being lazy But Jody brings up a good point to check for any passwords, etc…. I can’t recall if there is any of that in there.
The ares Jenkins server looks like it has a custom “run.sh” script in the “geoserver-cite” workspace used to run the CITE tests. As far as I can tell, this script is not tracked in version control anywhere.
There is also a setEnv.sh file responsible for setting the java version (which is specific to the machine) and a forms directory containing a bunch of xml files representing OWS requests or HTML forms.
The remaining directories all appear to be populated by the run.sh script, and include a copy of the current release artifacts, a copy of the current data directories used by the cite tests, a geoserver master checkout, and a cite master checkout.
Unless someone can point me to a location where the “run.sh” script (and the contents of the “forms” dir) are saved, I think we should probably add this script to version control.
Does anyone have any more information about this setup, or other thoughts?
But Jody brings up a good point to check for any passwords, etc…. I can’t recall if there is any of that in there.