It's all about the answers!

Ask a question

pre-conditions to prevent delivery of code of specific files types such as .xsd


Radha Sastrigal (111020) | asked Mar 24 '17, 10:55 a.m.
edited Mar 28 '17, 4:41 p.m. by Geoffrey Clemm (30.0k23035)

 Hello,


We have a need to add a constraint on either specific users or specific file types being delivered, for example: .XSD  Due to the specialized nature of the work only handful team members work on schema changes. However, there's no policing or controls we know of that have prevented this from occurring. 
We do have an approval pre-conditions however that is only at work item level on not necessarily checks for content being checked in
Any suggestions on how to prevent specific file types being delivered to stream? 


Comments
Geoffrey Clemm commented Mar 27 '17, 7:35 p.m. | edited Mar 27 '17, 7:37 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Radha:  Please clarify your question.   In particular, are you looking for a pre-condition on delivery  (as the question states) or for a pre-condition on checkin (as is stated a couple of times in the Body)?


Radha Sastrigal commented Mar 27 '17, 9:03 p.m.

 Geoffrey, pre condition to prevent delivery


Geoffrey Clemm commented Mar 28 '17, 4:42 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

OK, I've edited the question to clarify that it is "deliver" (and not "checkin") that needs to be controlled.

2 answers



permanent link
Shashikant Padur (4.2k27) | answered Mar 26 '17, 11:20 p.m.
JAZZ DEVELOPER

You would need to write a custom deliver precondition which would look at the changes in the change set and if it matches the files with these extensions and do not have the right role reject the change set. The user would then have to recreate the change set without these files and deliver it again.



permanent link
Ralph Schoon (59.7k23643) | answered Mar 27 '17, 1:12 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Mar 27 '17, 1:14 a.m.

Preconditions must not deliver. They can only prevent an operation. https://rsjazz.wordpress.com/2012/12/14/do-not-modify-the-triggering-element-in-an-operationadvisor/  Use follow up actions.

The Interface does not prevent this, but you can get into serious trouble, so you should not violate the rule. The SCM API does not support this as far as I know.


Comments
Geoffrey Clemm commented Mar 27 '17, 1:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I don't believe Radha was asking for a pre-condition that would deliver, but rather was asking for a precondition for the deliver operation, to prevent the deliver from delivering certain file types.


Ralph Schoon commented Mar 27 '17, 10:23 a.m. | edited Mar 27 '17, 10:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

If they want that, the question summary is totally wrong and they also probably want to prevent the checkin and not the deliver which requires 6.0.4.


Radha Sastrigal commented Mar 27 '17, 12:48 p.m.
You are right Geoffrey.

Ralph - We use Jazz v.4.0.6
1) What would you suggest would be best fit for preventing check-in of change-sets of specific file type by all developers?
2) What settings do we configure to make this happen?

Shashikant Padur commented Mar 27 '17, 11:02 p.m.
JAZZ DEVELOPER
If you are looking at preventing a check-in there is no support for writing check-in preconditions. In the upcoming release (604) we have provided the capability to write custom check-in preconditions.

Custom deliver precondition is the way to go to achieve this functionality.

Ralph Schoon commented Mar 28 '17, 4:30 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 Right, also the example you provided in your answer is the best way to get starting.

Your answer


Register or to post your answer.