Very good tool. I'm trying to do something super basic but I haven't found a way to do it yet. 1. I create the trigger for when a git master repository is updated with a new commit. 2. I need to clone another repository and update the submodule, generate a new commit and push the changes. Try various things. I did the trigger correctly and then I created a very basic bash where the test works perfectly for me. But when the whole workflow is executed the last step fails me.
Hi @Nathan Russo, Interesting - it could be that production data is slightly different from your testing data. Is there a specific error message you can share? You can also get help on our public community Slack and Discourse :)
@@pipedreamhq Thanks for the quick response, the test data is actually non-existent. Because I use the event to activate the workflow without using the information that the trigger exports, then the next step is a bash file that when I do the test it works perfectly but when I do the deploy it doesn't work. The error seems to be that it cannot clone the project but when I do the test it clones it perfectly and ends up committing to the repository correctly.
@@pipedreamhq In the end I ended up solving it. I realized that the error was that I was trying to clone the same repo. So all I did was remove it. It strikes me that in each execution of the workflow it continues to maintain the repo that was cloned and does not delete it.
Very good tool.
I'm trying to do something super basic but I haven't found a way to do it yet.
1. I create the trigger for when a git master repository is updated with a new commit.
2. I need to clone another repository and update the submodule, generate a new commit and push the changes.
Try various things.
I did the trigger correctly and then I created a very basic bash where the test works perfectly for me. But when the whole workflow is executed the last step fails me.
Hi @Nathan Russo,
Interesting - it could be that production data is slightly different from your testing data.
Is there a specific error message you can share?
You can also get help on our public community Slack and Discourse :)
@@pipedreamhq Thanks for the quick response, the test data is actually non-existent. Because I use the event to activate the workflow without using the information that the trigger exports, then the next step is a bash file that when I do the test it works perfectly but when I do the deploy it doesn't work. The error seems to be that it cannot clone the project but when I do the test it clones it perfectly and ends up committing to the repository correctly.
@@pipedreamhq In the end I ended up solving it.
I realized that the error was that I was trying to clone the same repo.
So all I did was remove it.
It strikes me that in each execution of the workflow it continues to maintain the repo that was cloned and does not delete it.