Jody, I just created a PR if you want to discuss how to improve it : https://github.com/geoserver/geoserver/pull/5613.
I have experience with ANT scripts so I want you some help, don't hesitate to ask. Regards Alexandre Le mer. 26 janv. 2022 à 06:59, Jody Garnett <jody.garn...@gmail.com> a écrit : > I just tried the official Go command line tool of Transifex ( >> https://github.com/transifex/cli) which went out of Alpha last month. >> The result seems ok : I manage to send updated PROPERTIES source to >> Transifex from my laptop and to retrieve updated PROPERTIES language files >> from it, without any encoding changes. >> > > That is positive; we do not mind using experimental build tools so much, > we just do wish to be careful with what we ship as part of the application. > >> >> I have several questions for the dev team: >> - Should I create a ticket for this change ? >> > > Build changes are not especially useful to track on the issue tracker; but > can be handy to have a consistent record of the decisions made; make sure > we do not miss anything (like updating the developers guide). > > - Should I include the Go CLI of Transifex in the Git repo or only let >> instructions on how to get it and configure it? >> > > Add to the build instructions. > > - For the moment the CLI configuration file is in a .tx folder at the root >> of the repo: I will try to move it to a subfolder of the build folder : is >> it the right thing to do? >> > > Yes we try and keep our build stuff out of the way when we can. > > - I will also add SH and BAT files to easily execute the sync operations. >> > > I have taken to adding ant files which work for both platforms. > > - Is it possible to add some automatic executions of the sync operations >> somewhere in the CI/CD? At least the GIT->TRANSIFEX sync, somewhere in >> Jenkins? >> > > Yes we can make a jobs for common tasks. > > I would recommend running the script, pushing the changes to a branch, and > then making a pull request. It is scary having scripts commit on your > behalf (the release scripts are a challenge to debug). > >> >> >> -- >> Alexandre Gacon >> _______________________________________________ >> Geoserver-users mailing list >> >> Please make sure you read the following two resources before posting to >> this list: >> - Earning your support instead of buying it, but Ian Turton: >> http://www.ianturton.com/talks/foss4g.html#/ >> - The GeoServer user list posting guidelines: >> http://geoserver.org/comm/userlist-guidelines.html >> >> If you want to request a feature or an improvement, also see this: >> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >> >> >> Geoserver-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> > -- > -- > Jody Garnett > -- Alexandre Gacon
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
