Consider incorporating the functionality of this script in a csprocessor publish command: https://svn.devel.redhat.com/repos/ecs/toolkit/csp-additional-tools/publisher/publish It could be improved by automating the increment of the Edition attribute, and probably a bunch of other checks (like the presence of rhpkg on the system). It could optionally/eventually take an argument, or the csprocessor.cfg could specify its output target, to enable other publishing mechanisms. cspclient-0.23.2-1.noarch OS: Fedora release 17 (Beefy Miracle) JAVA: java version "1.7.0_b147-icedtea" OpenJDK Runtime Environment (fedora-2.1.fc17.1-i386) OpenJDK Client VM (build 22.0-b10, mixed mode)
s/Edition/Pubsnumber
It would be good if it could check if a build with the pubsnumber already exists, and then increment the pubsnumber until it finds one that is free.
This describes how you determine the latest published build: https://engineering.redhat.com/docs/en-US/Engineering_Content_Services/1/html-single/Publishing_Documentation/index.html#Removing_a_build_from_the_docs_stage
I won't be implementing this as it then makes the CSP bound to internal Red Hat use (or certain systems, atm it just needs publican and skynet which can be used on basically any system). While this is okay for the mean time its not in the long run and not worth the time to be put in for it to just be deleted at a later stage.
*** Bug 829947 has been marked as a duplicate of this bug. ***