Re: Wrong Boolean Conditioned Token

Yesss Perfect!! Thanks so much!!! It works! El martes, 5 de septiembre de 2017, 15:44:00 (UTC+2), slide escribió: > > I think when using File Matches, you need to specify an ant-style file > pattern like you were trying before. Try putting this in the box (verbatim): > > Includes "**/tes

Re: Wrong Boolean Conditioned Token

I think when using File Matches, you need to specify an ant-style file pattern like you were trying before. Try putting this in the box (verbatim): Includes "**/test_resultados_miniprueba.csv" If you click on the help icon (question mark) next to the fields, they can give you valuable information

Re: Wrong Boolean Conditioned Token

Can you confirm whether it does exist under the folder "Workspace"? If you add a shell script step before the conditional step which runs "ls -l" what's the output? Cheers -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from t

Re: Wrong Boolean Conditioned Token

I've tried too with "Files Match" Condition and it does the same (nothing): It returns: [INFO] -

Wrong Boolean Conditioned Token

Hi guys! I don't know how to put a conditioned token to evaluate if a file exists with the Conditional Step Plugin in Jenkins: This returns the following cons