CI upstream workspace

[johnwason]

@Levi-Armstrong how does the CI handle the upstream workspace packages? Does it rebuild them, or it is pulling them from a cache? I didn't see where the cache is being pulled from, or where the upstream is cloned.

[Levi-Armstrong]

I am using the ccache action, though I am not sure if it just caches the target workspace or if it caches all three workspaces (target, upstream and downstream). Industrial CI does the cloning of each and they provide variables for each that you have access to. Now this relative to linux ci builds the windows build does not use industrial ci.

[johnwason]

I am seeing a "upstream_ws" directory in the CI logs. Where does that come from?

[Levi-Armstrong]

It comes from this line in the CI.

[johnwason]

Ok, so I guess ccache is also catching that workspace.

[Levi-Armstrong]

I believe that is true. In the CI script you set a variable telling it where the ccache directory is so it must use this same directory for all workspaces Then the github actions saves everything in this directory. There may be a way to specify a different ccache directory for each workspace, or you could add steps to remove directories for the ccache directory before the action saves.