Closed eloekset closed 3 years ago
I gave up on using the Azure Pipeline tasks for extracting archives and copy files and replaced them with bash scripts instead.
Referring to the latest commit https://github.com/fluentmigrator/fluentmigrator.github.io/commit/d32f47005cd85ade667006f00bb32f9a5a256414 it looks like it's doing things correctly again now.
Straight forward bash scripts should make the pipeline more stable, since it won't be affected by breaking changes to Azure Pipeline tasks.
Thank you. Makes sense to me. I personally think Azure Pipelines tasks is job security for whoever works on it at Microsoft :)
Related to #24 Travis was replaced by Azure Pipelines, and now the release script is broken.
Investigation so far seems that something has changed regarding the delete task that is used to clear all files from the local git repo, except the .git folder itself. Release is done by extracting the content of a new zip file over the working directory of the local git repo, and then do
git add .
,git commit
andgit push
. The result is:Even though we know the latest build artifacts have changes compared to the latest git release, those changes are not discovered by git, so there must be something wrong happening when the content of the zip file is copied into the working directory of the local git repo.
So far I've tried to replace the delete task with a bash script to delete everything except the .git folder:
This bash script doesn't give any output, so I'm not sure if the commands actually delete anything:
However a separate bash script lists the files of the working directory after the delete script has executed, and it shows that the files and folders are still there:
The ./api folder and its sub folders should not be there.