It's all about the answers!

Ask a question

How to version control cloud images with RTC SCM?


Guowei Jim Hu (1.0k710353) | asked May 03 '12, 10:13 a.m.
Cloud images are going to be new type of "source code" which need to be put under version control.

The huge size of the individual image make it unrealistic to store in RTC as normal source files.

Is there a way to store the images on an external storage other than the primary RTC repository but maintain a link somehow with RTC SCM to track the version change?

3 answers



permanent link
Geoffrey Clemm (30.1k33035) | answered May 03 '12, 11:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
What do you have in mind by "track the version change"?
A couple of things you can do:
- Link the cloud image to a work item, using the Add_Related_Artifacts operation (assumes that there is a URL for the cloud image).

- Link the could image to a build (so it shows up in the build results window).

Cheers,
Geoff

Cloud images are going to be new type of "source code" which need to be put under version control.

The huge size of the individual image make it unrealistic to store in RTC as normal source files.

Is there a way to store the images on an external storage other than the primary RTC repository but maintain a link somehow with RTC SCM to track the version change?

permanent link
Guowei Jim Hu (1.0k710353) | answered May 03 '12, 2:14 p.m.
What do you have in mind by "track the version change"?
A couple of things you can do:
- Link the cloud image to a work item, using the Add_Related_Artifacts operation (assumes that there is a URL for the cloud image).

- Link the could image to a build (so it shows up in the build results window).

Cheers,
Geoff



Thanks, Geoff,

The images are currently stored on cloud which is RED zone.
We need to have a safe place to store them.
And as more releases come out, we'll need to track the versions corresponding to indevidual releases.
From what you said, we'll also need to make them accessible via a web url to create a link to RTC repository.

permanent link
Geoffrey Clemm (30.1k33035) | answered May 03 '12, 9:41 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, you'll definitely need to expose them via a URL. I'd probably recommend using the work item approach, since build result objects are probably too easy to delete, and because the work item can act like a "change set" for your external cloud objects.

Cheers,
Geoff

What do you have in mind by "track the version change"?
A couple of things you can do:
- Link the cloud image to a work item, using the Add_Related_Artifacts operation (assumes that there is a URL for the cloud image).

- Link the could image to a build (so it shows up in the build results window).

Cheers,
Geoff



Thanks, Geoff,

The images are currently stored on cloud which is RED zone.
We need to have a safe place to store them.
And as more releases come out, we'll need to track the versions corresponding to indevidual releases.
From what you said, we'll also need to make them accessible via a web url to create a link to RTC repository.

Your answer


Register or to post your answer.