Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore whitespaces in build directory name on jenkins #4923

Open
tmakar opened this issue May 11, 2023 · 5 comments
Open

Restore whitespaces in build directory name on jenkins #4923

tmakar opened this issue May 11, 2023 · 5 comments

Comments

@tmakar
Copy link
Contributor

tmakar commented May 11, 2023

With this PR (#4895) we have introduced the go binding into our main repo. Go seems to have issue with spaces in any folder names etc. so it fails on builds / tests, etc. As we are using build directory as our build directory name and it has a space in the name it will lead to issues with go. We have therefore removed this whitespace now.

return [(testName): {
    stage(testName) {
      withDockerEnv(image, dockerOpts) {
        // we use a space in the directory to test if paths are
        // properly escaped
        def buildDir='build directory'

With this issue the removal of whitespaces should be restored again. (we use a space in the directory to test if paths are properly escaped).

@markus2330
Copy link
Contributor

Thanks for creating the issue.

What is the upstream bug? Otherwise we don't know when we can revert this change. The one I found golang/go#1413 is already fixed?

@tmakar
Copy link
Contributor Author

tmakar commented May 11, 2023

Thanks for creating the issue.

What is the upstream bug? Otherwise we don't know when we can revert this change. The one I found golang/go#1413 is already fixed?

I took a look at golang/go#1413. This one is about GOROOT. The one we need is golang/go#16455, but it also seems to be "fixed". The solution seems to be to escape the name which contains spaces (generated pkg-config file) with \.

@markus2330
Copy link
Contributor

Doesn't sound too hard, can you apply this fix for us?

@tmakar
Copy link
Contributor Author

tmakar commented May 11, 2023

Doesn't sound too hard, can you apply this fix for us?

Sure, will do 😉

@tmakar tmakar linked a pull request May 11, 2023 that will close this issue
19 tasks
@tmakar tmakar removed a link to a pull request May 11, 2023
19 tasks
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 12, 2023
@tmakar tmakar closed this as completed May 13, 2023
tmakar added a commit to tmakar/libelektra that referenced this issue May 13, 2023
@markus2330
Copy link
Contributor

fix depends on #4924

@markus2330 markus2330 reopened this May 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants