The readme mentions that the directory where the git repositories are stored can be set at admin/project/project-release-settings, but this is not the case. The path that can be set there has a different purpose.

Does this setting still need to be added in in this form, or should this instruction be removed from the readme?

Comments

pfrenssen’s picture

This seems to have been removed in commit 4cfdf1c3ad.

Currently the path is stored in the 'project_dependency_sourcecode_directory' variable. Historically this was another variable: 'project_release_directory'. This is still present in the current version of the Project module, but has been marked as deprecated:

This setting has been temporarily deprecated. If your site depends on scanning for releases generated by an external tool, you should wait to upgrade until a future version of the project_release.module is available that restores this functionality. Set the value blank to acknowlege that you do not need this behavior, and this error will disappear.

pfrenssen’s picture

Status: Active » Needs review
StatusFileSize
new1.42 KB
rfay’s picture

Status: Needs review » Needs work

When I looked at this I didn't like form-altering the project-page settings forms, because none of them are directly related. I guess I think we should make our own settings page instead. (In the same tree)

rfay’s picture

Issue tags: +1.0 blocker

triaging

rfay’s picture

Status: Needs work » Closed (duplicate)
Issue tags: -1.0 blocker

If you don't mind, I'm going to make this a duplicate of #1327306: Provide additional Web UI features