The specified changeset number was not found

Apr 9, 2013 at 2:15 PM
When creating a new release, I was unable to associate a changeset number. Error message returned is "The specified changeset number was not found". I've been doing releases here for years the same way - visit the history, copy the changeset number (a430101140a3), paste the changeset numbe into the release page, and no problem. Has anything changed or should I be doing this another way?

Joe
Apr 9, 2013 at 5:48 PM
Hi Joe,

Thanks for reporting this.
We recently switched to using full SHA rather than first 12 characters of a git commit ID. However, the UI still displays only 12 characters to keep it clean.
We have logged a bug to handle your particular scenario. In the mean while, please copy the full commit ID from the changeset URL, as a work around.

Do let us know if you need any further help.

Regards,
Pranav
Apr 9, 2013 at 5:58 PM
Pranav,

I tried to edit the release and the UI doesn't allow more than 12 characters in the input field.

Thanks,

Joe
Apr 10, 2013 at 10:46 PM
Hi Joe,

This should be fixed now.
Could you please try and let us know?

Regards,

Pranav
Apr 10, 2013 at 11:22 PM
Pranav,

Thank you - it's working now.

Joe