Bug 824693
Summary: | RFE: Pubsnum++ | ||
---|---|---|---|
Product: | [Community] PressGang CCMS | Reporter: | Misha H. Ali <mhusnain> |
Component: | CSProcessor | Assignee: | Lee Newson <lnewson> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 1.x | CC: | jwulf |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | 0.25.3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-07 01:12:20 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
Misha H. Ali
2012-05-24 02:18:19 UTC
We already have this partially. You can currently do: csprocessor build <SPECID> --override pubsnumber=<NUMBER> Though an incremental option is a good idea. Perhaps something like: csprocessor build <SPECID> --override pubsnumber=+<NUMBER> Would the following just override the original entry in the content spec with a new number or set the number to the incremented value permanently. What I had in mind was that for someone with multiple books, they would not need to recall what the last override was but just add a (non build) command to accept the pubsnum value and add 1 to it and save the new value in the content spec. This way, I don't need to know what the number is, just that I need to increment it, most likely as an additional step in my build and brew process, right after a successful build so that it is ready to go for next time. Hmm hadn't thought much about that but it's a good point. What I would like to do (and why I haven't done much on this) is have a command to get the correct pubsnumber from Brew. Doing this would then allow a publish command (see Bug #829947) to be created. Reference: https://fedorahosted.org/koji/wiki/XML-RPC_APIs Important Note: When a csprocessor project is created or checked out the KOJI_HUB_URL will be blank in the csprocessor.cfg file. This means that it will attempt to use the default value from csprocessor.ini. This can be changed by adding a URL to the csprocessor.cfg file for the KOJI_HUB_URL variable. |