LinuxMCE sqlCVS commit Procedure - Revision history

Marie.o: Changed the URL for sqlCVS batch check via web.

2018-02-12T22:38:03Z

Changed the URL for sqlCVS batch check via web.

←Older revision		Revision as of 22:38, 12 February 2018
Line 31:		Line 31:
	** If any problems are found going through these steps note this on the Mantis ticket and stop.		** If any problems are found going through these steps note this on the Mantis ticket and stop.
	** You may at your option "fix" the commit, but then you should do another anonymous commit, note it on the ticket, and have someone else should perform the validation steps.		** You may at your option "fix" the commit, but then you should do another anonymous commit, note it on the ticket, and have someone else should perform the validation steps.
	*** Step A: View the batch, refer to the ticket to find the correct batch: http://~~www~~.linuxmce.org/sqlCVS/?site=batch/view		*** Step A: View the batch, refer to the ticket to find the correct batch: http://schema.linuxmce.org/sqlCVS/?site=batch/view
	*** Step B: Check the commit for any duplicate vendor or product names.		*** Step B: Check the commit for any duplicate vendor or product names.
	*** Step C: Check the mantis ticket to see if the description is complete.		*** Step C: Check the mantis ticket to see if the description is complete.

Ray N at 17:57, 24 August 2009

2009-08-24T17:57:53Z

←Older revision		Revision as of 17:57, 24 August 2009
Line 1:		Line 1:
			[[Category: Development]]
	==NOTE: This is the tentative procedure for handling sqlCVS commits==		==NOTE: This is the tentative procedure for handling sqlCVS commits==

Marie.o: LinuxMCEsqlCVScommitProcedure moved to LinuxMCE sqlCVS commit Procedure: By seperating the words in the title, the article gets found during a search

2008-06-06T20:44:01Z

LinuxMCEsqlCVScommitProcedure moved to LinuxMCE sqlCVS commit Procedure: By seperating the words in the title, the article gets found during a search

←Older revision	Revision as of 20:44, 6 June 2008
(No difference)

Ddamron at 22:10, 12 April 2008

2008-04-12T22:10:03Z

Danielk: updated with actual command lines to run

2008-04-08T20:21:19Z

updated with actual command lines to run

←Older revision		Revision as of 20:21, 8 April 2008
Line 8:		Line 8:
	** This should describe in detail what the purpose of the commit is.		** This should describe in detail what the purpose of the commit is.
	** Each commit should only fix one bug or add one feature.		** Each commit should only fix one bug or add one feature.
			*** Please check this using: '''/usr/bin/pluto/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -r dce -U anonymous~nopass diff'''
	** If sql2cpp must be run this should be noted in the ticket as well.		** If sql2cpp must be run this should be noted in the ticket as well.
	** If there is any code associated with the commit it should be attached to the ticket.		** If there is any code associated with the commit it should be attached to the ticket.

	* Step 2: Validate your sqlCVS setup ~~with "sqlCVS -v"~~		* Step 2: Update your sqlCVS with the latest using web admin

			* Step 3: Validate your sqlCVS setup
	** If there are any problems please fix these before doing the commit.		** If there are any problems please fix these before doing the commit.
			*** Validate with: '''/usr/bin/pluto/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -v -r dce -U anonymous~nopass'''
			**** Do not delete records when it asks, these should be handled in a diff
			**** Some changes are not a problem, please ask on the IRC for help if this command shows any problems.

	* Step 3: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.		* Step 4: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.
	** Use the command line tool "/usr/bin/pluto/sqlCVS", and commit using "-U anonymous~nopass".		** Use the command line tool "/usr/bin/pluto/sqlCVS", and commit using "-U anonymous~nopass"
			*** Use this: '''sqlCVS -H sqlcvs.linuxmce.org -R 3999 -a -v -r dce -U anonymous~nopass -c "Mantis #... This does XYZ." checkin'''
	** The comment and the reference to the Mantis ticket will allow the person validating the commit to find the commit in sqlCVS.		** The comment and the reference to the Mantis ticket will allow the person validating the commit to find the commit in sqlCVS.
			** Add the reported batch number to the Mantis ticket.
	** Now monitor the ticket for any reported problems.		** Now monitor the ticket for any reported problems.

	* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.		* Step 5: Someone other than the person committing the fix will validate the sqlCVS commit.
	** If any problems are found going through these steps note this on the Mantis ticket and stop.		** If any problems are found going through these steps note this on the Mantis ticket and stop.
	** You may at your option "fix" the commit, but then you should do another anonymous commit, note it on the ticket, and have someone else should perform the validation steps.		** You may at your option "fix" the commit, but then you should do another anonymous commit, note it on the ticket, and have someone else should perform the validation steps.
	*** Step A: ~~pull~~ the ~~anonymous commit~~.		*** Step A: View the batch, refer to the ticket to find the correct batch: http://www.linuxmce.org/sqlCVS/?site=batch/view
	*** Step B~~: Run "sqlCVS -v"~~		*** Step B: Check the commit for any duplicate vendor or product names.
	*** Step C: Check the commit for any duplicate vendor or product names.		*** Step C: Check the mantis ticket to see if the description is complete.
	*** Step D: Check the mantis ticket to see if the description is complete.		*** Step D: If sql2cpp must be run with this database, do that as well and commit the code.
	*** Step E: If sql2cpp must be run with this database, do that as well and commit the code.		*** Step E: If there is any associated code, make sure that gets committed as well.
	*** Step F: If there is any associated code, make sure that gets committed as well.		*** Step F: Commit the change under your own validated login.
	*** Step G: Commit the change under your own validated login.		*** Step G: Validate the database on linuxmce.org: '''LD_LIBRARY_PATH=/opt/sqlCVS /opt/sqlCVS/sqlCVS -v'''
	*** Step H: Note the commit batch in the Mantis ticket and close the ticket.		*** Step H: Note the commit batch in the Mantis ticket and close the ticket.

Danielk: added short description of motivation for the proceedure.

2008-03-19T14:40:54Z

added short description of motivation for the proceedure.

←Older revision		Revision as of 14:40, 19 March 2008
Line 1:		Line 1:
	==NOTE: This is the tentative procedure for handling sqlCVS commits==		==NOTE: This is the tentative procedure for handling sqlCVS commits==

			This procedure is needed to avoid "breaking the build" and to get a clean history of commits so any problem commits can be reverted efficiently and without losing good commits in the process. As part of compiling LinuxMCE the database is automatically validated. If any errors are found the build script stops in it tracks and awaits human intervention.

			Note: Reverts require caution as well, since newer commits may depend on them, but this document deals with new commits.

	* Step 1: Create a Mantis ticket for the commit.		* Step 1: Create a Mantis ticket for the commit.
Line 17:		Line 21:
	* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.		* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.
	** If any problems are found going through these steps note this on the Mantis ticket and stop.		** If any problems are found going through these steps note this on the Mantis ticket and stop.
			** You may at your option "fix" the commit, but then you should do another anonymous commit, note it on the ticket, and have someone else should perform the validation steps.
	*** Step A: pull the anonymous commit.		*** Step A: pull the anonymous commit.
	*** Step B: Run "sqlCVS -v"		*** Step B: Run "sqlCVS -v"

Danielk: formatting

2008-03-19T14:34:45Z

formatting

←Older revision		Revision as of 14:34, 19 March 2008
Line 15:		Line 15:
	** Now monitor the ticket for any reported problems.		** Now monitor the ticket for any reported problems.

	* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit. (If any problems are found going through these steps note this on the Mantis ticket and stop.)		* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.
	** Step A: pull the anonymous commit.		** If any problems are found going through these steps note this on the Mantis ticket and stop.
	** Step B: Run "sqlCVS -v"		*** Step A: pull the anonymous commit.
	** Step C: Check the commit for any duplicate vendor or product names.		*** Step B: Run "sqlCVS -v"
	** Step D: Check the mantis ticket to see if the description is complete.		*** Step C: Check the commit for any duplicate vendor or product names.
	** Step E: If sql2cpp must be run with this database, do that as well and commit the code.		*** Step D: Check the mantis ticket to see if the description is complete.
	** Step F: If there is any associated code, make sure that gets committed as well.		*** Step E: If sql2cpp must be run with this database, do that as well and commit the code.
	** Step G: Commit the change under your own validated login.		*** Step F: If there is any associated code, make sure that gets committed as well.
	** Step H: Note the commit batch in the Mantis ticket and close the ticket.		*** Step G: Commit the change under your own validated login.
			*** Step H: Note the commit batch in the Mantis ticket and close the ticket.

Danielk: formatting

2008-03-19T14:33:21Z

formatting

←Older revision		Revision as of 14:33, 19 March 2008
Line 1:		Line 1:
	==NOTE: This is the tentative procedure for handling sqlCVS commits==		==NOTE: This is the tentative procedure for handling sqlCVS commits==

	* Step 1: Create a Mantis ticket for the commit.		* Step 1: Create a Mantis ticket for the commit.
	This should describe in detail what the purpose of the commit is.		** This should describe in detail what the purpose of the commit is.
	Each commit should only fix one bug or add one feature.		** Each commit should only fix one bug or add one feature.
	If sql2cpp must be run this should be noted in the ticket as well.		** If sql2cpp must be run this should be noted in the ticket as well.
	If there is any code associated with the commit it should be attached to the ticket.		** If there is any code associated with the commit it should be attached to the ticket.

	* Step 2: Validate your sqlCVS setup with "sqlCVS -v"		* Step 2: Validate your sqlCVS setup with "sqlCVS -v"
	If there are any problems please fix these before doing the commit.		** If there are any problems please fix these before doing the commit.

	* Step 3: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.		* Step 3: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.
	Use the command line tool "/usr/bin/pluto/sqlCVS", and commit using "-U anonymous~nopass".		** Use the command line tool "/usr/bin/pluto/sqlCVS", and commit using "-U anonymous~nopass".
	The comment and the reference to the Mantis ticket will allow the person validating the		** The comment and the reference to the Mantis ticket will allow the person validating the commit to find the commit in sqlCVS.
	commit to find the commit in sqlCVS.		** Now monitor the ticket for any reported problems.

	~~(Now monitor the ticket for any reported problems)~~		* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit. (If any problems are found going through these steps note this on the Mantis ticket and stop.)
			** Step A: pull the anonymous commit.
	* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.		** Step B: Run "sqlCVS -v"
	(If any problems are found going through these steps note this on the Mantis ticket and stop.)		** Step C: Check the commit for any duplicate vendor or product names.
	Step A: pull the anonymous commit.		** Step D: Check the mantis ticket to see if the description is complete.
	Step B: Run "sqlCVS -v"		** Step E: If sql2cpp must be run with this database, do that as well and commit the code.
	Step C: Check the commit for any duplicate vendor or product names.		** Step F: If there is any associated code, make sure that gets committed as well.
	Step D: Check the mantis ticket to see if the description is complete.		** Step G: Commit the change under your own validated login.
	Step E: If sql2cpp must be run with this database, do that as well and commit the code.		** Step H: Note the commit batch in the Mantis ticket and close the ticket.
	Step F: If there is any associated code, make sure that gets committed as well.
	Step G: Commit the change under your own validated login.
	Step H: Note the commit batch in the Mantis ticket and close the ticket.

Danielk: initial article

2008-03-19T14:30:57Z

initial article

New page

==NOTE: This is the tentative procedure for handling sqlCVS commits==

* Step 1: Create a Mantis ticket for the commit.
This should describe in detail what the purpose of the commit is.
Each commit should only fix one bug or add one feature.
If sql2cpp must be run this should be noted in the ticket as well.
If there is any code associated with the commit it should be attached to the ticket.

* Step 2: Validate your sqlCVS setup with "sqlCVS -v"
If there are any problems please fix these before doing the commit.

* Step 3: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.
Use the command line tool "/usr/bin/pluto/sqlCVS", and commit using "-U anonymous~nopass".
The comment and the reference to the Mantis ticket will allow the person validating the
commit to find the commit in sqlCVS.

(Now monitor the ticket for any reported problems)

* Step 4: Someone other than the person committing the fix will validate the sqlCVS commit.
(If any problems are found going through these steps note this on the Mantis ticket and stop.)
Step A: pull the anonymous commit.
Step B: Run "sqlCVS -v"
Step C: Check the commit for any duplicate vendor or product names.
Step D: Check the mantis ticket to see if the description is complete.
Step E: If sql2cpp must be run with this database, do that as well and commit the code.
Step F: If there is any associated code, make sure that gets committed as well.
Step G: Commit the change under your own validated login.
Step H: Note the commit batch in the Mantis ticket and close the ticket.

←Older revision		Revision as of 22:10, 12 April 2008
Line 8:		Line 8:
	** This should describe in detail what the purpose of the commit is.		** This should describe in detail what the purpose of the commit is.
	** Each commit should only fix one bug or add one feature.		** Each commit should only fix one bug or add one feature.
	*** Please check this using: '''/usr/bin~~/pluto~~/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -r dce -U anonymous~nopass diff'''		*** Please check this using: '''/usr/pluto/bin/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -r dce -U anonymous~nopass diff'''
	** If sql2cpp must be run this should be noted in the ticket as well.		** If sql2cpp must be run this should be noted in the ticket as well.
	** If there is any code associated with the commit it should be attached to the ticket.		** If there is any code associated with the commit it should be attached to the ticket.
Line 16:		Line 16:
	* Step 3: Validate your sqlCVS setup		* Step 3: Validate your sqlCVS setup
	** If there are any problems please fix these before doing the commit.		** If there are any problems please fix these before doing the commit.
	*** Validate with: '''/usr/bin~~/pluto~~/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -v -r dce -U anonymous~nopass'''		*** Validate with: '''/usr/pluto/bin/sqlCVS -H sqlcvs.linuxmce.org -R 3999 -v -r dce -U anonymous~nopass'''
	**** Do not delete records when it asks, these should be handled in a diff		**** Do not delete records when it asks, these should be handled in a diff
	**** Some changes are not a problem, please ask on the IRC for help if this command shows any problems.		**** Some changes are not a problem, please ask on the IRC for help if this command shows any problems.

	* Step 4: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.		* Step 4: Commit the change to sqlcvs.linuxmce.org with a comment that refers to the Mantis ticket.
	** Use the command line tool "/usr/bin~~/pluto~~/sqlCVS", and commit using "-U anonymous~nopass"		** Use the command line tool "/usr/pluto/bin/sqlCVS", and commit using "-U anonymous~nopass"
	*** Use this: '''sqlCVS -H sqlcvs.linuxmce.org -R 3999 -a -v -r dce -U anonymous~nopass -c "Mantis #... This does XYZ." checkin'''		*** Use this: '''sqlCVS -H sqlcvs.linuxmce.org -R 3999 -a -v -r dce -U anonymous~nopass -c "Mantis #... This does XYZ." checkin'''
	** The comment and the reference to the Mantis ticket will allow the person validating the commit to find the commit in sqlCVS.		** The comment and the reference to the Mantis ticket will allow the person validating the commit to find the commit in sqlCVS.