[JIRA] (JENKINS-15121) Invalid URL's on Project/Build pages for deployed artifacts

Wed, 19 Sep 2012 14:45:53 -0700

pickgr1 commented on Bug JENKINS-15121

For our specific scenario, we are using shared NFS storage for our artifacts. We have a simple apache front-end setup for users to browse/download the artifacts so we don't place any extra burden on our Jenkins masters.

We also have a geographically diverse build environment with masters and slaves distributed at different sites around the world - sometimes the master and slave is not co-located. The slave will always upload it's artifacts to the local "artifact server" which is essentially a NAS with a web front-end.

So for our rather complicated environment, we need to provide a URL to the artifacts based on where the slave is located. Ideally, what we need is a way to configure a URL that is based on some environment that is slave-specific.

For now, we've just modified the jelly so that the artifacts are just listed without a hypertext reference. If there was a way to just turn this off globally without having to hack the jelly files, that would be a big improvement for us.

Thanks for your consideration.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to