Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

Attribute at the file level

Like ClearCase can I have attribute attached at the file level in RTC? Any workarounds?

Thanks!

0 votes



6 answers

Permanent link
See enhancement 15526. Not currently scheduled. Please add your
comments/support to that work item. To come up with a potential
workaround, we'd need to know what you are using the attribute for.

Cheers,
Geoff

theju wrote:
Like ClearCase can I have attribute attached at the file level in RTC?
Any workarounds?

Thanks!

0 votes


Permanent link
Hi,

I need to set an attribute for a file to record whether that file should be released to a customer or not. This is for the release management.

Thanks!

See enhancement 15526. Not currently scheduled. Please add your
comments/support to that work item. To come up with a potential
workaround, we'd need to know what you are using the attribute for.

Cheers,
Geoff

theju wrote:
Like ClearCase can I have attribute attached at the file level in RTC?
Any workarounds?

Thanks!

0 votes


Permanent link
To do that, I think you need enhancement 15526 ... unless someone else
on the forum can think of a workaround.

I'd encourage anyone with such an example to post it as a comment to
work item 15526, so that the development team is aware of how you want
to use this functionality (and is aware that you need it).

Cheers,
Geoff

theju wrote:
Hi,

I need to set an attribute for a file to record whether that file
should be released to a customer or not. This is for the release
management.

Thanks!

gmclemmwrote:
See enhancement 15526. Not currently scheduled. Please add your
comments/support to that work item. To come up with a potential
workaround, we'd need to know what you are using the attribute for.

Cheers,
Geoff

theju wrote:
Like ClearCase can I have attribute attached at the file level in
RTC?
Any workarounds?

Thanks!

0 votes


Permanent link
For now you can keep a file with a list of files (either by item id - created programatically or by hand). This can be either an exclusion/inclusion list, that is up to you. Of course, file properties are best, and will be available in 3.0. But for now, the file could get you far enough and unblock until you can use properties.

0 votes


Permanent link
How to restrict the delivery of change-sets targeted for future sprints? For e.g., The project is currently at Sprint-1 and there are WIs planned for Sprint-2. I don't want developers to deliver a change-set that is associated with a WI planned for Sprint-2. How do I do this?

Thanks!

0 votes


Permanent link
On Mon, 10 Aug 2009 15:23:00 +0000, theju wrote:

How to restrict the delivery of change-sets targeted for future sprints?
For e.g., The project is currently at Sprint-1 and there are WIs planned
for Sprint-2. I don't want developers to deliver a change-set that is
associated with a WI planned for Sprint-2. How do I do this?

Thanks!

There is a precondition you can configure for the SCM Deliver operation
called "Require workitems and Comments". When you add this precondition
to the deliver operation there's an option to require that the workitem
associated with the change set be planned for the current iteration.

--
Jared Burns
Jazz Process Team

0 votes

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details

Question asked: Aug 06 '09, 1:53 p.m.

Question was seen: 5,199 times

Last updated: Aug 06 '09, 1:53 p.m.

Confirmation Cancel Confirm