Skip to Main Content
Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Jul 23, 2019

uDeploy AccuRev Plugin Change Request

When importing artifacts using AccuRev plugin, Users see all file timestamps are changed to current date and time at uDeploy Website.

We are requesting to add the option of keeping original file timestamp in this plugin. The original timestamp means the timestamp associated with an artifact when it is uploaded to AccuRev system.

Importing artifacts mainly takes two steps:
1) AccuRev plugin retrieves artifacts using AccuRev CLI to the storage used by UCDAgent
2) UCD Agent uses "CreateVersion" and "AddFilesToVersion" UCD APIs to add artifacts to UCD Code station.

We have performed following tests related to these 2 steps. They gave us the inside of where timestamp changes take place.
1) This test was done on the UCD server. The UCD agent for version import is also installed on this UCD server. We set environment variable ACCUREV_MOD_TIME=1. According to AccuRev online doc, this setting will prevent timestamp change.
We manually executed the "pop" AccuRev CLI to retrieve files from stream SHCRSC_DEV. The test result showed that timestamps of retrieved files did not change.

2) We already have a desktop tool that uses the "CreateVersion" and "AddFilesToVersion" UCD APIs to import files from developer's workstation to UCD code station.
The second test was done using this tool. The test result showed that the uploaded files kept original timestamps.

These test results showed that the file timestamp changes actually happened in the AccuRev plugin, because both AccuRev CLI and UCD APIs do not make those changes.

In order to keep file timestamps, the code changes are needed in AccuRev Plugin.

Idea priority High
RFE ID 134823
RFE URL
RFE Product UrbanCode Deploy
  • Guest
    Aug 28, 2019

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.