Working directory for job : unable to make it working #12650
-
|
Hi ! -> The task 3 has always an error, saying that the folder is not found. But the folder exists in the checkout copy ! |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 3 replies
-
|
You’ll need to share more specifics about your job and task definition and the error you see than this. There’s no way to know what you’re doing wrong from the description above. Check that your material definition in the pipeline has no ‘alternate checkout path’ set, or the checkout path you expect, and make sure that it reflected in your task working directories. the job console log will show you were materials are being cloned to. |
Beta Was this translation helpful? Give feedback.
-
|
On Fri, Mar 29, 2024 at 5:49 PM LeRatierBretonnien ***@***.***> wrote:
Hi !
I have a job with 3 sequential tasks :
1 - Script execution at root level of the checkout (ie "working directory"
= empty)
2 - make execution at root level of the checkout (ie "working directory" =
empty)
3 - do another make execution in a sub folder of the checkout (ie "working
directory" = pointing to a sub-folder)
-> The task 3 has always an error, saying that the folder is not found. But
the folder exists in the checkout copy !
What does the command contain?
Assume that the sub-folder is called "tests", and you need to run "make
all-tests", then you would need to specify
working directory: tests
command: make
arguments: all-tests
That is, the command should not contain the sub-folder (ie. it should not
be tests/make)
… —
Reply to this email directly, view it on GitHub
<#12650>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAF5JGXYMEAY2XFBOPYYLU3Y2UTILAVCNFSM6AAAAABFOGIPJGVHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZWGQZTKMRSGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your anwsers. Here are my jobs configuration : The first 2 jobs are performed properly (ie at the root of the checkout), but the third one is failing, saying that there is no "Makefile_deps" file. But the file is present in the working folder. Any hint or idea? |
Beta Was this translation helpful? Give feedback.
-
|
What happens if you add a task like this before step 3? can you share the actual full job console output of this new task and the failing task? |
Beta Was this translation helpful? Give feedback.
-
|
Good idea, thanks. |
Beta Was this translation helpful? Give feedback.
-
|
In your third task config check the two arguments are each on a separate line in the dialog. Based on that output, it looks like they are not - note how they are printed as “-f Makefile_deps” with quotes in the task, meaning they are being sent as a single arg to make. Also note how the error is |
Beta Was this translation helpful? Give feedback.
-
|
I don’t know why make strips the -f from the arg, that must just be how it works. |
Beta Was this translation helpful? Give feedback.
In your third task config check the two arguments are each on a separate line in the dialog.
Based on that output, it looks like they are not - note how they are printed as “-f Makefile_deps” with quotes in the task, meaning they are being sent as a single arg to make. Also note how the error is
No rule to make target ' Makefile_deps'with an extra space before it. This is the problem you have.