Halyna Berezovska Atlassian Team

@David Keaveny thanks for using the pipe! I checked git secrets scan and such error is appearing when you do not have files with this extension. For example, at the snippet below command scanning txt files gives nothing, so it is all right and searching for *.cs files does not work, because such do not exist $ ls test.txt…

@chong_yang @Harri Rahikainen try again, it should work now

@Roland van Laar we made a revert, so any version should work now. To prevent such breaking changes from happening again: Unfortunately, there was a bad approach of checking the newest version and we are working on fixing that approach. Once done, we will recommend to update to the version with the proper one. Regards,…

@Michael Aebli @ktomk Now you can use the new version and any of these, it should work, I checked. In the future we will notify about such breaking changes and working on not happening this again

@Ibrahim @Roland van Laar @wjia @drichards-lightwell @Harri Rahikainen if you are still experiencing this in your pipe , you may try again, it should work now. Best ragards, Galyna

@drichards-lightwell hello, try, please, again , your version. I rechecked it

@ktomk I checked version 0.1.1 and 0.1.6, they are both working

Actually there are no such changes since 0.1.4 that affect functionality of uploading files.

@drichards-lightwell I am not sure about the porting. It will be known next week. But if it is simple for you to just update, it is the most recommended way Cheers, Galyna

@Harri Rahikainen @Roland van Laar try, please, version 0.1.6, it should work now

@Craig Turner @drichards-lightwell try, please, version 0.1.6, it should work now

@wjia , @Ayoub Ennassiri try, please, version 0.1.6, it should work now

Hello @Ibrahim , thanks for reporting As the workaround for the few days, while we review changes, is to use version 0.1.1. I will notify about the release Regards, Galyna

@drichards-lightwell yes, you're right. We need to review changes of dependent lib that caused such errors, so for the few days the workaround is to use 0.1.1 version. I will notify once the fix is released Kind regards, Galyna

Thanks @Craig Turner for reporting! Here is correct workaround, in Duplicated queston . Fixed release (we need to review changes) will be in few days, I will notify Cheers, Galyna

Thanks @Ayoub Ennassiri @wjia for reporting. It is correct workaround, fixed release (we need to review changes) will be in few days, I will notify Cheers, Galyna

@Jay Seletz hello, feel free to try new version 4.1.6 and ensure it fixes your issue! Kind regards, Galyna

Hi! And can you please give the part of a pipeline where it is failing? And also a destination, since serverless deploy pipe can deploy to several type of destinations

Hello, @Alexander Moreno Delgado ! We indeed have not many for GCP and your pipe is new, we don't have GCP similar pipes. If I got your point, you are asking if the pipe could be used by others just like our own pipes. For that we propose to write custom pipes and contribute to opensource. If you want to write a new custom…

@Zuberu Abdulrahman looks like the url you are trying to reach, was not accessible at that moment or request failed with some error. Could you execute curl to that url directly with --silent option to debug and put the logs here? It will help to investigate your issue. Thanks, Galyna

@Arturo_Robles could you please put the output of serverless --version command here? it will contain framework, plugin, sdk and components versions. It will help us to investigate the issue. And also the question is about destination of where you are deploying? Thanks for reporting. Cheers, Galyna

@Ryan Parry-Jones glad you succeeded. IF you have time, can you share logs of publishing failure, not building? Those logs you put, they were during building process, so we need specific logs to see if there is an issue with this pipe

Hello, @Adelphe MBATCHI ! Could you try to execute aws cli command update-envronment to debug it? Or just to check it if aws should recognize it: aws elasticbeanstalk describe-environments --application-name "<app_name>" --environment-names "<env_name>" --debug If it succeed then you can debug update command. Looking…

Yes, 8080 is the port that is often used. Perhaps that is why you cannot use again

Sorry, I saw the answer above. Thanks for sharing

@Garry Dias so you did succeed to make it?

@Garry Dias could you please share a part of pipeline and more logs if you have? did you expose the appropriate port ? without this it would not be accessible. Cheers, Galyna

@Adelphe MBATCHI hello, thanks for reporting. Can you please share details of logs if possible and the part of the pipeline where it has failed? There may be different reasons of failure like such some tiny mistakes in syntax, usage or sth else

@Juan Roberto Honorato hello, thanks for the reporting. Looks like the file you expect to be existed is either not created or deleted. Can you share more details to help you investigate the case? Cheers, Galyna

@Ryan Parry-Jones hello again! Could you please share your case in detail? I have tried this pipe out and it worked for me with *.yml and *.yaml files. I guess the case may be the following: your script has created some folders that cannot be reached by setup.py tools to write there. You can check the permissions for these…