Re: Job stuck on "git pull --no-edit"

2020-11-17 Thread David Villasmil Govea
Thanks for replying.
I understand that “—no-edit” would prevent git from asking for a commit
message. And indeed this is the case if I do it manually.

But I do get your point about working in a clean environment... I think
I’ll go for that, don’t want anti-patterns happening here.

Thanks!

David

On Tue, 17 Nov 2020 at 15:26, 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi,
>
> this seems like you are mis-using git here. For deploy, checkout into a
> clean workspace and do the build. What happens in your case is, that the
> pull creates a merge commit ( you want fast-forwards only for automated
> updates in most cases), so thats why git  wants a merge commit message. (
> you could get around by specifiing  a message, but I would advise against
> it.)
>
> Björn
>
> david.v...@gmail.com schrieb am Dienstag, 17. November 2020 um 15:26:14
> UTC+1:
>
>> Hello,
>>
>> I have the following simple script. I just want to connect via ssh to my
>> build server, "git pull" and just build the docker and push it to the
>> registry.
>>
>> (If i don't include the "git pull --no-edit", it works fine)
>>
>> I just want to do "git pull". But when there are changed being pulled,
>> git gives me a "commit message" editor, and won't let me continue until i
>> enter something.This blocks me from automatically deploying, so i'm trying
>> with "--no-edit" but the deployment gets stuck there for some reason (i i
>> do it manually, works properly)
>>
>> YML_FILES="eks/"
>> YML_PATH="infra-api-server-deployment.yaml"
>> DOCKER_PATH="/api-server"
>> IMAGE_NAME="api-server"
>> cd $DOCKER_PATH
>> git pull --no-edit   *< STUCK HERE*
>> docker build -t $IMAGE_NAME:$NEW_VER .
>> docker push $IMAGE_NAME:$NEW_VER
>> cd $YML_FILES
>> kubectl apply -f $YML_PATH
>>
>> Help would be greatly appreciated!
>>
>> David
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/IH0D0_ZFdhU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/b08ac8f5-ee9f-4f23-8a5c-f489db47ab23n%40googlegroups.com
> 
> .
>
-- 
DVG

-- 
Imagination is more important than knowledge
Albert Einstein

-- 
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/CAPTi0gp%2BvYMLcjn%3DN%2BChonUjHAa%3DnHjDV%3DE1KPYSNDuxL6Hduw%40mail.gmail.com.


Re: Job stuck on "git pull --no-edit"

2020-11-17 Thread David Villasmil Govea
No, I’m CONNECTING to the build box as root.

On Tue, 17 Nov 2020 at 14:50, chencho  wrote:

> Are you running jenkins as root?
>
>
>
> On Tue, Nov 17, 2020 at 3:41 PM David Villasmil Govea <
> david.villas...@gmail.com> wrote:
>
>> Thanks Jerome.
>>
>> Actually I’m ssh’ing into the build box as root. And if I manually do it
>> as root, it works properly.
>>
>> On Tue, 17 Nov 2020 at 14:39, Jérôme Godbout  wrote:
>>
>>> Might not be directly related but some idea:
>>>
>>>
>>>
>>> Is the git repository repos inside the known host file for ssh access?
>>> It might need
>>>
>>> ssh-keygen -R “MyDomain.com” -f “~/.ssh/known_hosts”
>>>
>>> ssh-keygen -t rsa “MyDomain.com” >> “~/.ssh/known_hosts”
>>>
>>>
>>>
>>> Might help to avoid host confirmation in some case. Also make sure you
>>> have the proper ssh key available to the user, you can drop whoami and
>>> ssh-add list of key into your provider. This is issues I could foresee
>>> related to SSH git. Maybe something else.
>>>
>>>
>>>
>>>
>>> une compagnie
>>>
>>> RAPPROCHEZ LA DISTANCE
>>>
>>> *Jérôme Godbout*
>>> Développeur Logiciel Sénior /
>>> Senior Software Developer
>>>
>>> *p:* +1 (418) 800-1073 ext.:109
>>>
>>> amotus.ca <http://www.amotus-solutions.com/>
>>> statum-iot.com
>>>
>>> <https://www.facebook.com/LesSolutionsAmotus/>
>>> <https://www.linkedin.com/company/amotus-solutions/>
>>> <https://twitter.com/AmotusSolutions>
>>> <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
>>>
>>> *COVID-19 : we are glad to inform you that Amotus
>>> <https://www.amotus-solutions.com/> are up and running with limited impact
>>> on our performance. We will keep you informed of any changes as they occur.*
>>>
>>> *COVID-19 : nous sommes fiers d’informer nos collaborateurs que Amotus
>>> opèrent adéquatement et que l’impact sur notre productivité est minimisé.
>>> Nous vous tiendrons au courant de tout changement.*
>>>
>>>
>>>
>>> *From:* jenkinsci-users@googlegroups.com <
>>> jenkinsci-users@googlegroups.com> *On Behalf Of *David Villasmil
>>> *Sent:* November 17, 2020 9:26 AM
>>> *To:* Jenkins Users 
>>> *Subject:* Job stuck on "git pull --no-edit"
>>>
>>>
>>>
>>> Hello,
>>>
>>>
>>>
>>> I have the following simple script. I just want to connect via ssh to my
>>> build server, "git pull" and just build the docker and push it to the
>>> registry.
>>>
>>>
>>>
>>> (If i don't include the "git pull --no-edit", it works fine)
>>>
>>>
>>>
>>> I just want to do "git pull". But when there are changed being pulled,
>>> git gives me a "commit message" editor, and won't let me continue until i
>>> enter something.This blocks me from automatically deploying, so i'm trying
>>> with "--no-edit" but the deployment gets stuck there for some reason (i i
>>> do it manually, works properly)
>>>
>>>
>>>
>>> YML_FILES="eks/"
>>>
>>> YML_PATH="infra-api-server-deployment.yaml"
>>>
>>> DOCKER_PATH="/api-server"
>>>
>>> IMAGE_NAME="api-server"
>>>
>>> cd $DOCKER_PATH
>>>
>>> git pull --no-edit   *< STUCK HERE*
>>>
>>> docker build -t $IMAGE_NAME:$NEW_VER .
>>>
>>> docker push $IMAGE_NAME:$NEW_VER
>>>
>>> cd $YML_FILES
>>>
>>> kubectl apply -f $YML_PATH
>>>
>>>
>>>
>>> Help would be greatly appreciated!
>>>
>>>
>>>
>>> David
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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/85285e93-26cf-4a98-bd3a-ee8eaf3368ben%40googlegroups.com
>>> <https://grou

Re: Job stuck on "git pull --no-edit"

2020-11-17 Thread David Villasmil Govea
Thanks Jerome.

Actually I’m ssh’ing into the build box as root. And if I manually do it as
root, it works properly.

On Tue, 17 Nov 2020 at 14:39, Jérôme Godbout  wrote:

> Might not be directly related but some idea:
>
>
>
> Is the git repository repos inside the known host file for ssh access? It
> might need
>
> ssh-keygen -R “MyDomain.com” -f “~/.ssh/known_hosts”
>
> ssh-keygen -t rsa “MyDomain.com” >> “~/.ssh/known_hosts”
>
>
>
> Might help to avoid host confirmation in some case. Also make sure you
> have the proper ssh key available to the user, you can drop whoami and
> ssh-add list of key into your provider. This is issues I could foresee
> related to SSH git. Maybe something else.
>
>
>
>
> une compagnie
>
> RAPPROCHEZ LA DISTANCE
>
> *Jérôme Godbout*
> Développeur Logiciel Sénior /
> Senior Software Developer
>
> *p:* +1 (418) 800-1073 ext.:109
>
> amotus.ca <http://www.amotus-solutions.com/>
> statum-iot.com
>
> <https://www.facebook.com/LesSolutionsAmotus/>
> <https://www.linkedin.com/company/amotus-solutions/>
> <https://twitter.com/AmotusSolutions>
> <https://www.youtube.com/channel/UCoYpQgsmj1iJZyDjTQ3x8Ig>
>
> *COVID-19 : we are glad to inform you that Amotus
> <https://www.amotus-solutions.com/> are up and running with limited impact
> on our performance. We will keep you informed of any changes as they occur.*
>
> *COVID-19 : nous sommes fiers d’informer nos collaborateurs que Amotus
> opèrent adéquatement et que l’impact sur notre productivité est minimisé.
> Nous vous tiendrons au courant de tout changement.*
>
>
>
> *From:* jenkinsci-users@googlegroups.com 
> *On Behalf Of *David Villasmil
> *Sent:* November 17, 2020 9:26 AM
> *To:* Jenkins Users 
> *Subject:* Job stuck on "git pull --no-edit"
>
>
>
> Hello,
>
>
>
> I have the following simple script. I just want to connect via ssh to my
> build server, "git pull" and just build the docker and push it to the
> registry.
>
>
>
> (If i don't include the "git pull --no-edit", it works fine)
>
>
>
> I just want to do "git pull". But when there are changed being pulled, git
> gives me a "commit message" editor, and won't let me continue until i enter
> something.This blocks me from automatically deploying, so i'm trying with
> "--no-edit" but the deployment gets stuck there for some reason (i i do it
> manually, works properly)
>
>
>
> YML_FILES="eks/"
>
> YML_PATH="infra-api-server-deployment.yaml"
>
> DOCKER_PATH="/api-server"
>
> IMAGE_NAME="api-server"
>
> cd $DOCKER_PATH
>
> git pull --no-edit   *< STUCK HERE*
>
> docker build -t $IMAGE_NAME:$NEW_VER .
>
> docker push $IMAGE_NAME:$NEW_VER
>
> cd $YML_FILES
>
> kubectl apply -f $YML_PATH
>
>
>
> Help would be greatly appreciated!
>
>
>
> David
>
>
>
>
>
> --
> 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/85285e93-26cf-4a98-bd3a-ee8eaf3368ben%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/85285e93-26cf-4a98-bd3a-ee8eaf3368ben%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/IH0D0_ZFdhU/unsubscribe.
> To unsubscribe from this group and all its topics, 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/QB1PR01MB384460F4FDABDD4D38B388E0CDE20%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM
> <https://groups.google.com/d/msgid/jenkinsci-users/QB1PR01MB384460F4FDABDD4D38B388E0CDE20%40QB1PR01MB3844.CANPRD01.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer>
> .
>
-- 
DVG

-- 
Imagination is more important than knowledge
Albert Einstein

-- 
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/CAPTi0gqnO%2BdstBtdh10c0SN8zMEuKrCau5Ut%2Bg58A595EYTmPA%40mail.gmail.com.


Job stuck on "git pull --no-edit"

2020-11-17 Thread David Villasmil
Hello, 

I have the following simple script. I just want to connect via ssh to my 
build server, "git pull" and just build the docker and push it to the 
registry.

(If i don't include the "git pull --no-edit", it works fine)

I just want to do "git pull". But when there are changed being pulled, git 
gives me a "commit message" editor, and won't let me continue until i enter 
something.This blocks me from automatically deploying, so i'm trying with 
"--no-edit" but the deployment gets stuck there for some reason (i i do it 
manually, works properly)

YML_FILES="eks/"
YML_PATH="infra-api-server-deployment.yaml"
DOCKER_PATH="/api-server"
IMAGE_NAME="api-server"
cd $DOCKER_PATH
git pull --no-edit   *< STUCK HERE*
docker build -t $IMAGE_NAME:$NEW_VER . 
docker push $IMAGE_NAME:$NEW_VER 
cd $YML_FILES
kubectl apply -f $YML_PATH

Help would be greatly appreciated! 

David


-- 
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/85285e93-26cf-4a98-bd3a-ee8eaf3368ben%40googlegroups.com.


Re: Jenkins can't find existing artifacts

2016-04-26 Thread David Villasmil Govea
Hello all,

I finally found my problem. I had configured the job to do the git clone.
But for some reason I also added the cloning on the build steps... once i
removed that jenkins started getting the files properly.

I would still like to understand why this would happen...

Regards,

David


On Tue, Apr 26, 2016 at 9:30 AM Lionel Orellana  wrote:

> Or **/logfiles/*
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/_6bHcXQ7EPQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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/033fbba3-4ddb-4723-a4f6-13b1e0f1d313%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
ᐧ

-- 
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/CAPTi0gpD9GSNB7aCivzfVtdR3CxiOhPEi5oaim%3Ddd6N3Dz-aeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Jenkins can't find existing artifacts

2016-04-25 Thread David Villasmil
Hello,

Thanks for answering. Funny thing, it didn't generate an error, but still 
didn't get the files... :(

David

On Monday, April 25, 2016 at 8:45:05 AM UTC-4, David Villasmil wrote:
>
> Hello Guys,
>
> I have a jenkins running a job, after which I want it to "archive 
> artifact", which is basically just get some files.
>
> The Job clones a github and when ran, it generates some log files which I 
> need. The patter is:
>
> logfiles/*
>
> I added a command to list the directory to make sure the files are there, 
> and indeed they are.
>
> + ls -la logfiles
> total 24
> drwxr-xr-x 2 root root 4096 Apr 22 23:23 .
> drwxr-xr-x 8 root root 4096 Apr 22 23:23 ..
> -rw-r--r-- 1 root root0 Apr 22 23:23 1461367410777_testuuid_61746144-
> 3A3A--4944-3D5343414C41.log
> -rw-r--r-- 1 root root 1248 Apr 22 23:23 1461367410777_testuuid_61746144-
> 3A3A--4944-3D5343414C41_shortmsg.csv
> -rw-r--r-- 1 root root 2521 Apr 22 23:23 1461367410777_testuuid_61746144-
> 3A3A--4944-3D5343414C41_stats.log
> -rw-r--r-- 1 root root 8035 Apr 22 23:23 1461367410777_testuuid_61746144-
> 3A3A--4944-3D5343414C41_trace_msg.log
> Archiving artifacts
> ERROR: No artifacts found that match the file pattern "logfiles/*". 
> Configuration error?
> ERROR: ‘logfiles/*’ doesn’t match anything, but ‘*’ does. Perhaps that’s 
> what you mean?
> Build step 'Archive the artifacts' changed build result to FAILURE
>
>
> I don't really understand why they are not found.
>
> I have tried many different patterns, like "**/logfiles/*.log", 
>  "**/logfiles/*.*",  "**/logfiles/*",  and even asking specifically for the 
> file like 
> "logfiles/1461367410777_testuuid_61746144-3A3A--4944-3D5343414C41_shortmsg.csv"
> Always same result.
>
> Can any one help?
>
> Regards,
>
> David
>

-- 
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/804b9bbe-082c-4aee-8f96-aaed10eb87a2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins can't find existing artifacts

2016-04-25 Thread David Villasmil
Hello Guys,

I have a jenkins running a job, after which I want it to "archive 
artifact", which is basically just get some files.

The Job clones a github and when ran, it generates some log files which I 
need. The patter is:

logfiles/*

I added a command to list the directory to make sure the files are there, 
and indeed they are.

+ ls -la logfiles
total 24
drwxr-xr-x 2 root root 4096 Apr 22 23:23 .
drwxr-xr-x 8 root root 4096 Apr 22 23:23 ..
-rw-r--r-- 1 root root0 Apr 22 23:23 1461367410777_testuuid_61746144-
3A3A--4944-3D5343414C41.log
-rw-r--r-- 1 root root 1248 Apr 22 23:23 1461367410777_testuuid_61746144-
3A3A--4944-3D5343414C41_shortmsg.csv
-rw-r--r-- 1 root root 2521 Apr 22 23:23 1461367410777_testuuid_61746144-
3A3A--4944-3D5343414C41_stats.log
-rw-r--r-- 1 root root 8035 Apr 22 23:23 1461367410777_testuuid_61746144-
3A3A--4944-3D5343414C41_trace_msg.log
Archiving artifacts
ERROR: No artifacts found that match the file pattern "logfiles/*". 
Configuration error?
ERROR: ‘logfiles/*’ doesn’t match anything, but ‘*’ does. Perhaps that’s 
what you mean?
Build step 'Archive the artifacts' changed build result to FAILURE


I don't really understand why they are not found.

I have tried many different patterns, like "**/logfiles/*.log", 
 "**/logfiles/*.*",  "**/logfiles/*",  and even asking specifically for the 
file like 
"logfiles/1461367410777_testuuid_61746144-3A3A--4944-3D5343414C41_shortmsg.csv"
Always same result.

Can any one help?

Regards,

David

-- 
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/1146d4e6-d155-4046-add7-9fd4c1a9a7ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.