Bug 818043

Summary: RFE: csprocessor publish command
Product: [Community] PressGang CCMS Reporter: Joshua Wulf <jwulf>
Component: CSProcessorAssignee: Lee Newson <lnewson>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.xCC: jwulf, lcarlon, sburgess, sgordon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-18 11:25:55 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Wulf 2012-05-02 05:03:25 UTC 
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)
Comment 1 Joshua Wulf 2012-05-02 05:05:08 UTC 
s/Edition/Pubsnumber
Comment 2 Joshua Wulf 2012-05-02 09:02:34 UTC 
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.
Comment 3 Joshua Wulf 2012-05-02 09:04:18 UTC 
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
Comment 4 Lee Newson 2012-05-18 11:25:55 UTC 
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.
Comment 5 Lee Newson 2012-06-07 22:36:20 UTC 
*** Bug 829947 has been marked as a duplicate of this bug. ***