Project

General

Profile

Bug #4243

master-simtrace2 failed to build from October 19 onwards: $WORKSPACE environment missing

Added by laforge 23 days ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
10/30/2019
Due date:
% Done:

0%

Spec Reference:

Description

When we write a "contrib/jenkins.sh" job, we assume that all the jenkins environment variables as documented at https://wiki.jenkins.io/display/JENKINS/Building+a+software+project are available to the script. In the specific case, $WORKSPACE was used, which failed after the job had been moved inside docker.

I think it's generally a good idea to make sure all the jenkins environment variables as described at the link above are passed into the docker container, so authors of contrib/jenkins.sh don't have to consider undocumented osmocom-docker-specific restrictions but can use the normal set of environment variables..

For $WORKSPACE, it's questionable what to do. Probably best we mount it into the docker container, and then specify that mount point as "-e WORKSPACE"?

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)