Re: IAR (EWARM) failure to build on Jenkins
Is it a Jenkins agent that you are running this on, or the controller? If
an agent, are you running as a Windows service, or using something like
SSH? If the controller, what user is the controller running as? You need to
figure out what user account the command is being run as. If it is
different from the user you are currently running the command as on
cmd.exe, then you need to try as the user that Jenkins is using to run the
command. There could be some different in environment between the two which
could be causing the problem.
On Tue, Jul 19, 2022 at 8:02 AM Faisal Tariq wrote:
>
> Hi Slide,
> Good suggestion on checking the environment variable.
>
> I am not sure how to do what you stated above:"Anothing thing to try
> would be (if you are not already) run the command as the same user the
> Jenkins agent (or controller) is running as and see if you see the same
> behavior". Could you kindly elaborate .
>
> Thanks
>
> Faisal
>
>
>
> On Monday, July 18, 2022 at 9:34:51 PM UTC-5 slide wrote:
>
>> In the command window (cmd.exe) that you are running the command from,
>> can you run the "set" command to get a list of env variables and do the
>> same thing as part of your Jenkins run and see if there are any environment
>> variables are missing from the Jenkins run? Generally, Jenkins will not
>> have all of the environment variables that you might have in your user
>> account. Anothing thing to try would be (if you are not already) run the
>> command as the same user the Jenkins agent (or controller) is running as
>> and see if you see the same behavior.
>>
>> On Mon, Jul 18, 2022 at 4:37 PM Faisal Tariq wrote:
>>
>>> Hi Slide,
>>>
>>> Yes, the command line that I am using matches "exactly" in both the cmd
>>> and Jenkins (I am sure of that). What is being called "argument" is
>>> present in the project (*.ewp) file which the IAR build environment knows
>>> what to replace it with i.e. C:\...\. However when run
>>> through Jenkins, it fails to recognize this and does not know what to
>>> replace it with and displays the error?
>>>
>>> Thanks
>>> Faisal
>>>
>>> On Monday, July 18, 2022 at 5:55:49 PM UTC-5 slide wrote:
>>>
Does the command line you are using in Jenkins match exactly to what
you are running in Jenkins? Are you using a Jenkinsfile? The argument looks
more like a bash variable specification than one that would run in cmd.exe.
On Mon, Jul 18, 2022 at 3:42 PM Faisal Tariq wrote:
> Hello,
>
> I would like to know who all are using IAR EWARM to build on Jenkins
> without any issues? Please read on to see my issue.
>
> I am running an IAR IDE build script to build an example file. When I
> run it locally through a Windows “cmd” screen, it evokes IAR IDE and does
> a
> build successfully. However, when I run the same script through Jenkins I
> get an error message, as follows:
>
> The unknown argument variable
> “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$” was encountered while loading
> the project “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>
> The above path is where the pack gets installed. Has anyone
> encountered anything similar where the script runs fine in Windows “cmd”
> screen, but fails when evoked through Jenkins?
>
> Also, this may not be related, but the complete error message was as
> follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
> Jenkins). However the one that I ran through cmd did not complain about
> the
> $(CMSIS_PACK_PATH… and built successfully.
>
> SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See SLF4J Error Codes
> for further
> details.
> The unknown argument variable
> “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$” was encountered while loading
> the project “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>
> Thank you all in advance. Please let me know if you need any
> additional information.
>
> --
> 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 jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com
>
> .
>
--
Website: http://earl-of-code.com
>>> --
>>> 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
Re: IAR (EWARM) failure to build on Jenkins
Hi Slide,
Good suggestion on checking the environment variable.
I am not sure how to do what you stated above:"Anothing thing to try
would be (if you are not already) run the command as the same user the
Jenkins agent (or controller) is running as and see if you see the same
behavior". Could you kindly elaborate .
Thanks
Faisal
On Monday, July 18, 2022 at 9:34:51 PM UTC-5 slide wrote:
> In the command window (cmd.exe) that you are running the command from, can
> you run the "set" command to get a list of env variables and do the same
> thing as part of your Jenkins run and see if there are any environment
> variables are missing from the Jenkins run? Generally, Jenkins will not
> have all of the environment variables that you might have in your user
> account. Anothing thing to try would be (if you are not already) run the
> command as the same user the Jenkins agent (or controller) is running as
> and see if you see the same behavior.
>
> On Mon, Jul 18, 2022 at 4:37 PM Faisal Tariq wrote:
>
>> Hi Slide,
>>
>> Yes, the command line that I am using matches "exactly" in both the cmd
>> and Jenkins (I am sure of that). What is being called "argument" is
>> present in the project (*.ewp) file which the IAR build environment knows
>> what to replace it with i.e. C:\...\. However when run
>> through Jenkins, it fails to recognize this and does not know what to
>> replace it with and displays the error?
>>
>> Thanks
>> Faisal
>>
>> On Monday, July 18, 2022 at 5:55:49 PM UTC-5 slide wrote:
>>
>>> Does the command line you are using in Jenkins match exactly to what you
>>> are running in Jenkins? Are you using a Jenkinsfile? The argument looks
>>> more like a bash variable specification than one that would run in cmd.exe.
>>>
>>> On Mon, Jul 18, 2022 at 3:42 PM Faisal Tariq wrote:
>>>
Hello,
I would like to know who all are using IAR EWARM to build on Jenkins
without any issues? Please read on to see my issue.
I am running an IAR IDE build script to build an example file. When I
run it locally through a Windows “cmd” screen, it evokes IAR IDE and does
a
build successfully. However, when I run the same script through Jenkins I
get an error message, as follows:
The unknown argument variable
“${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$” was encountered while loading
the project “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
The above path is where the pack gets installed. Has anyone encountered
anything similar where the script runs fine in Windows “cmd” screen, but
fails when evoked through Jenkins?
Also, this may not be related, but the complete error message was as
follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
Jenkins). However the one that I ran through cmd did not complain about
the
$(CMSIS_PACK_PATH… and built successfully.
SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See SLF4J Error Codes
for further
details.
The unknown argument variable
“${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$” was encountered while loading
the project “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
Thank you all in advance. Please let me know if you need any additional
information.
--
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 jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com
.
>>>
>>>
>>> --
>>> Website: http://earl-of-code.com
>>>
>> --
>> 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 jenkinsci-use...@googlegroups.com.
>>
> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/65dafad4-e8b2-4ac6-9367-3398be3679b2n%40googlegroups.com
>>
>>
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this
Re: IAR (EWARM) failure to build on Jenkins
In the command window (cmd.exe) that you are running the command from, can
you run the "set" command to get a list of env variables and do the same
thing as part of your Jenkins run and see if there are any environment
variables are missing from the Jenkins run? Generally, Jenkins will not
have all of the environment variables that you might have in your user
account. Anothing thing to try would be (if you are not already) run the
command as the same user the Jenkins agent (or controller) is running as
and see if you see the same behavior.
On Mon, Jul 18, 2022 at 4:37 PM Faisal Tariq wrote:
> Hi Slide,
>
> Yes, the command line that I am using matches "exactly" in both the cmd
> and Jenkins (I am sure of that). What is being called "argument" is
> present in the project (*.ewp) file which the IAR build environment knows
> what to replace it with i.e. C:\...\. However when run
> through Jenkins, it fails to recognize this and does not know what to
> replace it with and displays the error?
>
> Thanks
> Faisal
>
> On Monday, July 18, 2022 at 5:55:49 PM UTC-5 slide wrote:
>
>> Does the command line you are using in Jenkins match exactly to what you
>> are running in Jenkins? Are you using a Jenkinsfile? The argument looks
>> more like a bash variable specification than one that would run in cmd.exe.
>>
>> On Mon, Jul 18, 2022 at 3:42 PM Faisal Tariq wrote:
>>
>>> Hello,
>>>
>>> I would like to know who all are using IAR EWARM to build on Jenkins
>>> without any issues? Please read on to see my issue.
>>>
>>> I am running an IAR IDE build script to build an example file. When I
>>> run it locally through a Windows “cmd” screen, it evokes IAR IDE and does a
>>> build successfully. However, when I run the same script through Jenkins I
>>> get an error message, as follows:
>>>
>>> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
>>> was encountered while loading the project
>>> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>>>
>>> The above path is where the pack gets installed. Has anyone encountered
>>> anything similar where the script runs fine in Windows “cmd” screen, but
>>> fails when evoked through Jenkins?
>>>
>>> Also, this may not be related, but the complete error message was as
>>> follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
>>> Jenkins). However the one that I ran through cmd did not complain about the
>>> $(CMSIS_PACK_PATH… and built successfully.
>>>
>>> SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
>>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>>> SLF4J: See SLF4J Error Codes
>>> for further
>>> details.
>>> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
>>> was encountered while loading the project
>>> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>>>
>>> Thank you all in advance. Please let me know if you need any additional
>>> information.
>>>
>>> --
>>> 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 jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com
>>>
>>> .
>>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/65dafad4-e8b2-4ac6-9367-3398be3679b2n%40googlegroups.com
>
> .
>
--
Website: http://earl-of-code.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeG2K1eVU93ZAYnqzXu1NbRqFGkPQxBL%2BZVDaDkHAv_vQ%40mail.gmail.com.
Re: IAR (EWARM) failure to build on Jenkins
Hi Slide,
Yes, the command line that I am using matches "exactly" in both the cmd and
Jenkins (I am sure of that). What is being called "argument" is present in
the project (*.ewp) file which the IAR build environment knows what to
replace it with i.e. C:\...\. However when run through
Jenkins, it fails to recognize this and does not know what to replace it
with and displays the error?
Thanks
Faisal
On Monday, July 18, 2022 at 5:55:49 PM UTC-5 slide wrote:
> Does the command line you are using in Jenkins match exactly to what you
> are running in Jenkins? Are you using a Jenkinsfile? The argument looks
> more like a bash variable specification than one that would run in cmd.exe.
>
> On Mon, Jul 18, 2022 at 3:42 PM Faisal Tariq wrote:
>
>> Hello,
>>
>> I would like to know who all are using IAR EWARM to build on Jenkins
>> without any issues? Please read on to see my issue.
>>
>> I am running an IAR IDE build script to build an example file. When I run
>> it locally through a Windows “cmd” screen, it evokes IAR IDE and does a
>> build successfully. However, when I run the same script through Jenkins I
>> get an error message, as follows:
>>
>> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
>> was encountered while loading the project
>> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>>
>> The above path is where the pack gets installed. Has anyone encountered
>> anything similar where the script runs fine in Windows “cmd” screen, but
>> fails when evoked through Jenkins?
>>
>> Also, this may not be related, but the complete error message was as
>> follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
>> Jenkins). However the one that I ran through cmd did not complain about the
>> $(CMSIS_PACK_PATH… and built successfully.
>>
>> SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
>> SLF4J: Defaulting to no-operation (NOP) logger implementation
>> SLF4J: See SLF4J Error Codes
>> for further details.
>> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
>> was encountered while loading the project
>> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>>
>> Thank you all in advance. Please let me know if you need any additional
>> information.
>>
>> --
>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com
>>
>>
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/65dafad4-e8b2-4ac6-9367-3398be3679b2n%40googlegroups.com.
Re: IAR (EWARM) failure to build on Jenkins
Does the command line you are using in Jenkins match exactly to what you
are running in Jenkins? Are you using a Jenkinsfile? The argument looks
more like a bash variable specification than one that would run in cmd.exe.
On Mon, Jul 18, 2022 at 3:42 PM Faisal Tariq wrote:
> Hello,
>
> I would like to know who all are using IAR EWARM to build on Jenkins
> without any issues? Please read on to see my issue.
>
> I am running an IAR IDE build script to build an example file. When I run
> it locally through a Windows “cmd” screen, it evokes IAR IDE and does a
> build successfully. However, when I run the same script through Jenkins I
> get an error message, as follows:
>
> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
> was encountered while loading the project
> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>
> The above path is where the pack gets installed. Has anyone encountered
> anything similar where the script runs fine in Windows “cmd” screen, but
> fails when evoked through Jenkins?
>
> Also, this may not be related, but the complete error message was as
> follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
> Jenkins). However the one that I ran through cmd did not complain about the
> $(CMSIS_PACK_PATH… and built successfully.
>
> SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See SLF4J Error Codes
> for further details.
> The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
> was encountered while loading the project
> “C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
>
> Thank you all in advance. Please let me know if you need any additional
> information.
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com
>
> .
>
--
Website: http://earl-of-code.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdWKaELY-%2BakhKByezduBGHb8P0toMLiJEjCapGgiKYKQ%40mail.gmail.com.
IAR (EWARM) failure to build on Jenkins
Hello,
I would like to know who all are using IAR EWARM to build on Jenkins
without any issues? Please read on to see my issue.
I am running an IAR IDE build script to build an example file. When I run
it locally through a Windows “cmd” screen, it evokes IAR IDE and does a
build successfully. However, when I run the same script through Jenkins I
get an error message, as follows:
The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
was encountered while loading the project
“C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
The above path is where the pack gets installed. Has anyone encountered
anything similar where the script runs fine in Windows “cmd” screen, but
fails when evoked through Jenkins?
Also, this may not be related, but the complete error message was as
follows with the SLF4J: in both cases (i.e. in Windows Cmd screen and
Jenkins). However the one that I ran through cmd did not complain about the
$(CMSIS_PACK_PATH… and built successfully.
SLF4J: Failed to load class “org.slf4j.impl.StaticLoggerBinder”.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See SLF4J Error Codes
for further details.
The unknown argument variable “${CMSIS_PACK_PATH_Maxim#MAX32670#1.0.3}$”
was encountered while loading the project
“C:\IAR_Examples\MAX32670_Example_TEST\DMA\IAR\DMA.ewp”.
Thank you all in advance. Please let me know if you need any additional
information.
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/0f65d2f1-aea9-40dc-9a2f-8c92d6e8a9a6n%40googlegroups.com.
