Well an update, naming back to hardcoded server, didn't fix it.
ssh://${GERRIT_HOST}:${GERRIT_PORT}/${GERRIT_PROJECT} - breaks
ssh://myserver:${GERRIT_PORT}/${GERRIT_PROJECT} - breaks
ssh://myserver:29418/${GERRIT_PROJECT} - works
In all breaking cases, an extra '/' shows up as ssh:///
On Thursday, December 5, 2013 9:43:42 AM UTC-5, dpreilan wrote:
>
> I was changing my jobs to be more portable.
> I have a multijob job that gets triggered by gerrit and the GERRIT_*
> parameters get set and passed down to jobs.
> I changed my git url in a job to:
> ssh://${GERRIT_HOST}:${GERRIT_PORT}/${GERRIT_PROJECT}
>
> The job fails and looking at output: I see:
>
> ssh:///my_server_name:29418/my_project
>
>
> Notice extra '/'
>
>
> Looking at parameters for job and GERRIT_HOST doesn't have a leading '/'.
>
> For kicks, I changed job to:
>
> ssh:/${GERRIT_HOST}:${GERRIT_PORT}/${GERRIT_PROJECT}
>
>
> and job fails with output shows only 1 / as coded:
>
> ssh:/my_server_name:29418/my_project
>
>
> Where is extra '/' when I code as:
>
> ssh://${GERRIT_HOST}:${GERRIT_PORT}/${GERRIT_PROJECT}
>
>
> If I hardcode, the server name (don't use ${GERRIT_HOST}), it works.
>
>
> Thanks!
>
> Doug
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
